jeffemmett
/
web3
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[meta/plan,meta/projects/roadmap-v0.1][m]: updates on plan and roadmap (more which is not yet ready to push).

This commit is contained in:
Rufus Pollock 2022-03-21 21:45:53 +01:00
parent fdec8a3866
commit bd99b6bfcb
2 changed files with 56 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
meta/plan.md
View File

@ -9,17 +9,17 @@ Features
* [x] **MMVP website up** so that we can share with people
* [x] with a signup offer
* [x] with a participate offer?
* **Announced e.g. on Emerge, Blog etc** so that more people find out about this, & we have articulated the purpose of the project clearly
* **About the project (? + thesis of structured sensemaking)** so that we can share about the project to others esp more in depth
* **Library (based on Zotero)** so that we have a place to collect the upper layer of the sensemaking info graph
* **Taxonomy for library and other material**
* **Concept underlay** so that ...
* **Wiki system**
* [x] **Announced e.g. on Emerge, Blog etc** so that more people find out about this, & we have articulated the purpose of the project clearly
* [ ] **About the project (? + thesis of structured sensemaking)** so that we can share about the project to others especially in more depth
* [ ] **Library (based on Zotero)** so that we have a place to collect the upper layer of the sensemaking info graph 🚧 have library but not a good integration yet
* [ ] **Taxonomy for library and other material**
* [ ] **Concept underlay** so that ...
* [ ] **Wiki system**
## Milestones (WIP)
* [x] v0.1: single page site for the project, vision for the project
* [ ] v0.2: Working wiki + 1 substantive essay
* [x] v0.2: Working wiki + 1 substantive essay
* [ ] v0.3: ...
* [ ] v1: website with integrated library and wiki. contribution flow.
@ -28,14 +28,14 @@ Features
## Fri 11 March
* [x] [website-v0.1](projects/website-v0.1.md)
* [ ] [announce-v0.1](projects/announce-v0.1.md) DEFERRED to next week
* [x] [announce-v0.1](projects/announce-v0.1.md) DEFERRED to next week **✅ 16 March**
# Workstreams
* [ ] Online web "home" for the published material e.g. "Making Sense of Web3" so that ... ⏫
* [ ] [website-v0.1](projects/website-v0.1.md) **🏃‍♂️ v0.0.1 https://github.com/life-itself/web3/issues/53 issue**
* [x] [website-v0.1](projects/website-v0.1.md) **🏃‍♂️ v0.0.1 https://github.com/life-itself/web3/issues/53 issue**
* [ ] Collaboration and Contribution (paths and involved already interested people) so that we get more contributions
* [ ] Content ⏫ **see below and https://github.com/life-itself/web3/issues/55 issue**
* [ ] Content ⏫ **see [design](design.md)**
* [ ] Library 🔼 see https://github.com/life-itself/web3/issues/44
# Content
@ -44,17 +44,6 @@ Features
* [x] Merge Theo/Rufus issue tree **2022-02-25 done by Catherine**
* [x] Tidy up main issue tree **✅2022-02-28 largely done today - last branch in main issue tree on collective sensemaking still needs some work**
* [x] Transfer to spreadsheet and add details e.g. material needed, prioritization
* [ ] Publish issue trees
* [ ] Reports - write up well with good referencing [aside: how easy is it to pdf in "proper" format via Git e.g. like the primers one]
* [ ] ➕2022-02-26 What we are bringing / aiming for (and what’s distinctive about this approach)
* [ ] Write up our approach to sensemaking and why it matters (write up existing notes into a coherent essay)
# Inbox
* [ ] Clear pathway for involvement (Job stories)
* [ ] Where do we publish the original SCQH so that we can link others to it
* [ ] Do we need it given we have the tidied version in about page?
* [ ] Reports - write up well with good referencing [aside: how easy is it to pdf in “proper” format via Git e.g. like the primers one]
* [ ] ➕2022-03-11 Set up sponsorship for the project
* [ ] Identify a platform to get sponsored through (github or opencollective or ...)
* [ ] (?) Set up github sponsors for Life Itself
* [ ] Write up our approach to sensemaking and why it matters (write up existing notes into a coherent essay)

60
meta/projects/roadmap-v0.1.md
View File

@ -14,27 +14,32 @@ What & Why: We want a clear near-term roadmap with associated tasks so that
A clear near-term (1m) roadmap and a vaguer 6m roadmap in [plan](../plan.md)
* [ ] Milestones / Goals
* [ ] Rough timeline
* [ ] Backlog
* [ ] Prioritization
* [ ] Milestones / Goals
* [ ] Rough timeline
* [ ] Next actions
Meta (how we organize)
### Meta (how we organize)
* [ ] Team structure
* [x] Team structure
* [x] Scrum Lead **✅ Eilidh**
* [x] Product Owner **✅ Rufus***
* [ ] Team process
* [ ] Clear PM infrastructure (e.g. are we using markdown/hackmd/git/obsidian or gdocs)
* [ ] Can we do all the work "in the open"?
* [ ] Materials
* [x] Product Owner **✅ Rufus**
* [x] Team process
* [x] Clear PM infrastructure e.g. where are we ...
* [x] Recording meeting notes **✅ ?? GDocs?**
* [x] Recording actions and tasks. Options are: github issues, planning docs in wiki, gdocs, spreadsheet (e.g. issue tree)? **✅ Github issues for day to day tasks. May do larger "epic/project" planning in `meta` section of wiki. Finally, Issue tree spreadsheet provides overview and we will attach tasks to items there**
* [x] Can we do all the work "in the open"? **Pretty much. For some job stories or interviews may need to record privately and process before sharing**
* [x] Are we doing iterations and of what form? **✅ Yes, we are going to do 2 week iterations.**
* [x] Materials
* [x] Where is the primary location for materials etc e.g. are we using markdown/hackmd/git/obsidian or gdocs? **✅ consolidate on the wiki (markdown + github) using coggle only to provide overviews or brainstorm. More discussion below. For drafting people can use whatever they are comfortable with**
* [x] Existing materials are tidied up (e.g. PA10) **✅ 2022-03-11 DONE except for job stories**
## Tasks
* [x] Prep
* [x] Background reading
* [ ] Backlog generation
* [ ] Prioritization
* [ ] Backlog and prioritization
* [ ] Summary
* [ ] Misc
* [x] Consolidate our claims database stuff in one place ✅ **2022-03-11 have consolidated on coggle for now**
@ -61,15 +66,40 @@ General concepts of project management
* [x] plan **✅ Read it**
* [x] design **✅ Read it**
* [x] Read issue tree https://docs.google.com/spreadsheets/d/12Yh1kuxH4uoposLUJsJifM2W_zixkAhlc7QgcKavfls/edit#gid=2049708942 ✅ **have read through issue tree, next action is to add in answers**
* [ ] fill in issue tree answers
* [ ] fill in issue tree answers
## Brainstorm and Organize Plan
### Brainstorm and Organize 👈
🚩 already have issue tree and plan.md - do we need to do more and if so where ...
Brainstorming major next steps
* [ ] library integration
* [ ] guide - https://github.com/life-itself/web3/issues/77
* [ ] ⏩ review current status and what remains to be done
* [ ] post existing materials
* [ ] tech side
Re the claims
Outcome vision
* [ ] A page for each major claim in the taxonomy
* [ ] The evaluation progress of each claim
* [ ] The evaluation (e.g. true/false)
* [ ] Aspirations it links to
* [ ] Who's making it and where (big egs)
Random
* [ ] A page for the major episodes we've done as the landing page for them separate from the youtube
* [ ] Where do these go? **✅ `/notes/`**
* [ ] Do we flag them into news somehow? **🚧 someday**
### Simplification of tools and process for content
H: Consolidate and simplify material and structure
H: Consolidate and simplify material and structure => consolidate on the wiki using coggle only to provide overviews or brainstorm.
Why?
@ -108,4 +138,4 @@ Currently have 4 locations for claims. We want to consolidate on one.
* [ ] Why? ✅ **Job stories help us prioritize our efforts (plus motivation for ourselves and others as to why we are doing this). E.g. if we know what journalists are looking for X we can focus on that which seems a high impact thing to do.**
* [ ] What are questions / topics we should write about?
* A useful tool which collects google searches people are making about web3: https://answerthepublic.com/reports/54ce111d-ff4f-49fa-b2de-411695bd9910 These would make useful titles or section headings in blog posts about Web3.
* ![](https://i.imgur.com/tCS26FA.png)
* ![](https://i.imgur.com/tCS26FA.png)