[meta/*,journal/1][m]: 3 specific projects now on website, announce and creating roadmap.

Start zettling the meta stuff a bit.

journal/2022-03-11.md

@@ -0,0 +1,24 @@
+# 2022-03-11
+
+# Brainstorm
+
+### 👉 FOLLOW THE ISSUE TREE 👈
+
+* [ ] Home Page
+  * [ ] About the project
+  * [x] ⏫ fix "get updates"
+* [ ] Latest releases
+* [x] Planning the work
+* [ ] Technical refactor
+
+### Latest release section
+
+* [ ] Where do the Latest Release go to?
+  * [ ] What are options?
+    * Directly to YouTube
+    * To a page on our site
+  * [ ] Which do we choose? ✅ **To a page on our site** because we then have a permalink for that item and we don't repeat ourselves in too many places and we can add much more context e.g. transcript of the item.
+  * [ ] Where does that page live?
+  * [ ] How do we pull those pages into the front page?
+    * hard code
+    * select automatically => have some kind of flag and then being able to select for that.

meta/claims-db.md

@@ -0,0 +1,14 @@
+# Claims & Aspirations DB
+
+### Claims/Aspirations Database 2022-03-11
+
+* [ ] Analysis of needs for DB
+  * [ ] Identify needs for this "database" e.g. a) does it need to be structured b draft as well as finished material c) planning or publication (or both) 
+  * [ ] Choose canonical location
+  * [ ] Move stuff there and de-duplicate
+* [ ] Key features for aspirations & claims database #todo/process to somewhere in the wiki (design section?) 
+  * Aspiration title
+  * Aspiration Description
+  * Title for Claim
+  * Short Description
+  * Example	Who holds this position

meta/design.md

@@ -2,6 +2,21 @@
 
 e.g. information architecture, job stories etc.
 
+
+Launchable and *announceable* website.
+
+
+## Wireframes and Mockups
+
+### Home page
+
+Mockup of home page (design): https://excalidraw.com/#room=8bc8a0afb0afc89015dc,W3jd48r8_B2llA2CZ8A33A
+
+v0.1 Wireframe
+
+![website-homepage-v0.1-2022-02-23.excalidraw](../../excalidraw/website-homepage-v0.1-2022-02-23.excalidraw.svg)
+
+
 # Content Plan (and Info Architecture)
 
 Excalidraw: https://excalidraw.com/#room=77b4b0841586502dc440,OS7tGXbkYEf_W5Lgu8PflA
@@ -16,4 +31,18 @@ Excalidraw: https://excalidraw.com/#room=77b4b0841586502dc440,OS7tGXbkYEf_W5Lgu8
 * Library `/library`: 
 
 
-Currently have `ideologies` folder too. I wonder if we merge into notes.
+Currently have `ideologies` folder too. I wonder if we merge into notes.
+
+
+# Issue Tree
+
+* [x] How rough and ready are we in process and hence appearance? **✅2022-03-11 publish early, publish often and accept being "rougher" though flagging what is polished and not. - see [how-rough-and-ready](how-rough-and-ready.md)**
+* [ ] Do we need to distinguish claims from aspirations from debates from questions people have?
+* [ ] Are questions vs hypotheses a better way to frame (or even more attractive on the internet)
+  * Questions seem less polarizing: Crypto will transform the world ... vs Can Crypto transform the world?
+    * In a proper thesis setup where everyone understands we are dealing in claims and examining them and brings a rigorous open-mindedness then theses are better because can be evaluated ...
+    * But we can always turn a claim into a question and vice-versa ...
+    * Hypotheses are more accurate than claims but a bit more obscure in terminology
+  * H: (70%) use questions rather than claims/hypotheses
+* Do we call ourselves "Making sense of Web3" or "Making sense of Crypto and Web3" or "Making Sense of Crypto"
+  * Do we mention Crypto at all? ✅ **Yes, crypto is more widespread and even less controversial in definition so definitely want to mention it**

meta/how-rough-and-ready.md

@@ -0,0 +1,21 @@
+---
+created: 2022-03-11
+---
+
+# How rough and ready are we?
+
+* Being polished:
+  * Why? Look more professional, inviting to e.g. journalists, policy-makers, being an authoritative voice
+  * Cons: slows thing down (a lot), makes it harder for community to contribute
+* Being more rough
+  * Eases contribution
+  * Have stuff public early is good (and pushes us to complete it - when you don't publish you can keep polishing forever)
+
+Are there ways we can have both? e.g. allow contribution but flag articles which are finished & polished vs those which are draft still
+
+Ans: publish early, publish often and accept being "rougher" though flagging what is polished and not. 
+
+* We want community contribution and that both necessitates some "rough and ready" material and that form encourages contribution
+* Getting stuff out encourages us to polish and improve it
+* The world is more open to "open source" approach - "not wearing a tie is ok"
+* We can flag material as "polished" and "draft"

meta/issue-tree.md

@@ -0,0 +1,3 @@
+* What are the various claims for web3/crypto (+ve or -ve) and their constructive evaluation so that as individuals and societies we make good choices whether to support, improve or curb it as well as to allocate our resources (attention, energy, money) effectively, and, finally this is happens in as a constructive, intersectional and depolarizing way as possible?
+  * What are the key high level problems / aspirations / hopes that crypto / web3 movement talks to?
+  * What is our evaluation? How does crypto/web3 hope to address that, what risks are there and how else can we address them?

meta/plan.md

@@ -1,5 +1,7 @@
 # Plan
 
+High level plan is given by issue tree: https://docs.google.com/spreadsheets/d/12Yh1kuxH4uoposLUJsJifM2W_zixkAhlc7QgcKavfls/edit#gid=2049708942
+
 # Goals
 
 Features
@@ -26,9 +28,7 @@ Features
 ## Fri 11 March
 
 * [ ] [website-v0.1](projects/website-v0.1.md)
-* [ ] Launch DEFERRED to next week
+* [ ] [announce-v0.1](projects/announce-v0.1.md) DEFERRED to next week
-  * [ ] Announce on Emerge
-  * [ ] Announce on Life Itself
 
 # Workstreams
 
@@ -45,23 +45,16 @@ Features
   * [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]
+* [ ] 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]
-* [ ] Publishing an announce/intro piece on e.g. Emerge
-  * [ ] BONUS: (or 2nd article) is about this an exemplar for collective sense-making in a “time between worlds”
-* [ ] ⏫ What material do we already have ...? **🏃‍♂️ 4 interviews, SCQH ...**
 * [ ] ➕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)
-    * [ ] Interview Rufus and/or Stephen to clarify what’s the challenge in the sensemaking
 
-## Things to merge from old brainstorm
+# Inbox
 
-* [ ] Announcement post
-  * [ ] Publishing an intro piece on Emerge: Announcing the initiative (just turn SCQH into that …)
-  * [ ] BONUS: (or 2nd article) is about this an exemplar for collective sense-making in a “time between worlds”
 * [ ] 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]
-* [ ] Engagement and signups
+* [ ] ➕2022-03-11 Set up sponsorship for the project
-  * [ ] 👍👍 Sign up to get updates / news …
+  * [ ] Identify a platform to get sponsored through (github or opencollective or ...)
-  * [ ]  Subscribe to our youtube channel
+  * [ ] (?) Set up github sponsors for Life Itself

meta/projects/announce-v0.1.md

@@ -0,0 +1,26 @@
+---
+created: 2022-03-10
+due: 2022-03-17
+---
+
+# Announcing the Initial Launch (march 2022)
+
+## Tasks
+
+* [ ] Announcement post
+  * [ ] Life Itself announce
+    * [ ] Back post about original launch in Jan using current content of lifeitself.us/web3/
+    * [ ] Update current web3 page to redirect or point to new site
+  * [ ] Publishing an intro piece on Emerge: Announcing the initiative (just turn SCQH into that …)
+* [ ] Identify good online fora to share in
+
+### Possible Places to post
+
+- ycombinator
+- reddit (buttcoin plus pro forums)
+- people to email (?)
+
+### Future
+
+* [ ] BONUS: (or 2nd article) is about this an exemplar for collective sense-making in a "time between worlds"
+

meta/projects/roadmap-v0.1.md

@@ -0,0 +1,110 @@
+---
+created: 2022-03-10
+---
+
+# Get a Roadmap v0.1
+
+What & Why: We want a clear near-term roadmap with associated tasks so that
+
+* we know what to prioritize
+* have goals (to inspire us)
+* can efficiently self-organize in a distributed, part-time and part-volunteer team
+
+## Acceptance
+
+A clear near-term (1m) roadmap and a vaguer 6m roadmap in [plan](../plan.md)
+
+* [ ] Milestones / Goals
+* [ ] Rough timeline
+* [ ] Next actions
+
+Meta (how we organize)
+
+* [ ] 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] 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
+* [ ] Summary
+* [ ] Misc
+  * [x] Consolidate our claims database stuff in one place ✅ **2022-03-11 have consolidated on coggle for now**
+
+### Prep
+
+General concepts of project management
+
+* [x] Read about agile delivery playbook.datopian.com/agile/ **✅ Read it and clarified questions**
+* [x] Read about PARA https://www.lucapallotta.com/para/ ✅ **Read**
+
+### Background
+
+* [x] Read the PA10
+  * [x] Read it all the way through quickly **✅ Read it**
+  * [x] Note questions (in the doc using comment facility) **✅ Read it**
+  * [x] Add TODOs for key info in the doc (maybe list here). Suggest answers and then check with Rufus ✅ **Added TODOs as comments**
+  * [x] Material to process (or process out)
+    * [x] Plan of Work brainstorm ✅ **Processed and deleted**
+    * [ ] Job Stories 
+    * [x] Key claims list ✅ **Processed to coggle claims taxonomy and deleted**
+    * [x] Key aspirations ✅ **Processed to coggle and deleted**
+* [ ] Read meta folder https://github.com/life-itself/web3/tree/main/meta
+  * [ ] plan
+  * [ ] design
+* [ ] Read issue tree https://docs.google.com/spreadsheets/d/12Yh1kuxH4uoposLUJsJifM2W_zixkAhlc7QgcKavfls/edit#gid=2049708942
+
+## Brainstorm and Organize Plan
+
+🚩 already have issue tree and plan.md - do we need to do more and if so where ...
+
+### Simplification of tools and process for content
+
+H: Consolidate and simplify material and structure
+
+Why?
+
+* S+C: using 3+ locations atm and several tools
+  * we have google docs (docs & sheets), git, coggle, excalidraw etc
+  * Markdown in github (with obsidian)
+  * coggle
+  * even core team members a bit confused over all the locations of stuff
+* Want to get clear on what we use for what.
+* H: consolidate on the wiki using coggle only to provide overviews or brainstorm.
+  * What about meeting notes etc?
+
+Concrete example: aspirations and claims "database" => see the next item.
+
+### Consolidate our claims database stuff in one place
+
+Currently have 4 locations for claims. We want to consolidate on one.
+
+* [x] Consolidate overview of the aspirations/claims
+  * [x] What are current locations? ✅ **2022-03-10 currently 4 locations: In Issue Tree spreadsheet a) "Claims" b) "Aspirations and Claims"; then also c) https://coggle.it/diagram/YhTzF8ZnKihmLdpm/t/web3-taxonomy-of-aspirations-and-claims d) claims list in wiki https://github.com/life-itself/web3/tree/main/claims here**
+  * [x] Choose location for overall list ✅ **Consolidate on coggle https://coggle.it/diagram/YhTzF8ZnKihmLdpm/t/web3-taxonomy-of-aspirations-and-claims (for now as of 2022-03-10) as the best version. Next would be to converge with wiki**
+  * [x] Move brainstorm of aspirations/claims from gdocs to the coggle ✅ **there was only fairer and stable economy section and most already there so not much to move. Have deleted from gdocs**
+  * [x] Move from apirations & claims spreadsheet **✅ All already there**
+  * [ ] Consolidate wiki list https://github.com/life-itself/web3/tree/main/claims to coggle
+    * [ ] 
+* [x] Consolidate on a page on the wiki as focal location
+  * [x] Create the index page
+  * [x] Where? `/claims/`
+  * [x] Do we embed the coggle? ✅ Yes, at least to start with
+  * [x] Do we list on index page the other claim pages in the wiki (and how)? ✅ **For now we won't. In future we can use our CMS system to do so.**
+
+### Misc
+
+* [ ] 🔽2️⃣ Process job stories brainstorm somewhere https://docs.google.com/document/d/1AV2xXDgTiNRVv6_M7CoGhiFl8pBj5hDGi_qdsHOU_3M/edit#heading=h.g248tv329855
+  * [ ] Where? ✅ **`meta/job-stories` in the wiki and just remove any identifying info from user interviews**
+  * [ ] 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)

meta/projects/website-v0.1.md

@@ -21,9 +21,14 @@ Mockup of home page (design): https://excalidraw.com/#room=8bc8a0afb0afc89015dc,
   * [x] Guide section
   * [x] Library section
   * [ ] About the project
+  * [ ] Get Involed
 * [x] About page **✅ with SCQH**
 * [ ] Library page
 * [ ] ⏫ Sign up to get updates / news …
+* [ ] Misc
+  * [x] ⏫ Analytics
+  * [ ] Navbar
+  * [ ] Footer
 
 Bonus
 
@@ -37,9 +42,6 @@ Bonus
 * [ ] Library page
 * [ ] Guide page
 * [ ] Notes section (wiki)
-* [ ] Misc
-  * [x] ⏫ Analytics
-  * [ ] Navbar
 
 ### Home Page