TODO-Shannon.md

Shannon's Open Tasks

Web/Repo Tasks (Small):

1. • Set policy for closing repos without leaders
2. • Regularly assess old repos that may be defunct
3. • Update members on community page
4. • Update https://github.com/BlockchainCommons/Community/blob/master/standard-communications-text.md
5. • Clean Out HackMD (P***)
6. • Flag Unpublished in HackMD
7. • Any Feedback on #62
8. • Coordinate W's Tech Excerpts (from big video)
9. • Added newest testimony (Sign, email)
10. • Review https://twitter.com/ChristopherA/status/1435664587479650308 for messaging for other docs
11. • Review & Update C's LinkedIn Profile

Admin:

1. • Get Access to Team Email
2. • Get Access to Accounting Email
3. • Get Access to Bank Account
4. • Get Access to Credit Card
5. • Get Access to Multisig

Yearly:

1. • Revise Yearly

Lifehash

1. • Link Articles in LifeHash Repo to Crypto Commons Repo
2. • Add bc-lifehash to Crypto Commons Repo

BTCPay:

1. • Move BTCPay to New Account (2022): 1 of 2
2. • Investigate Lightning
3. • Enable Lightning (low-priority)

SmartCustody:

1. • Write about Defining/Creating Adversaries
2. • Recovery of Multisigs Standards
   • Need Standards
   • Storing Metadata
   • Working with Tap Root
   • Not Having SPF

Possible Grants:

1. • Reach Out About #SC 2 (PRI)
2. • Ethereum / NFTs
3. • Community Membership / Collaboration

CryptoRequest:

1. • Release CryptoReQuest Article (start of December)

Gordian Server:

1. • Put Gordian Server in LBTCftCL (requires PATH)
2. • Incorporate RPC PR (pending)

Learning Bitcoin:

1. • Announce Weekly LBTCftCL Seminars (early January)
2. • Article?
3. • Add diagram of forks & branches to TRANSLATING
4. • First LBTCftCL Seminar (January 19th)

Secure Development

1. • Line edit Pseudonymity Guide, one section at a time. (U: Maybe Wednesday)
   • Verify section by section that there isn't work that he's planning
2. • Make sure Main README says how to run scripts
3. • Do We Want to talk about Guide First?
   • What are use cases? Even non-pseudonymous people who are interacting with pseudonyms.
   • Does Pseudonymity Guide Overlap into Secure Development?
   • Supply chain attacks? Liability? Physical Threats in Less Secure Countries?
   • Cover Thease Reasons? https://twitter.com/ChristopherA/status/1450971497174999041?s=20

Repo Maintenance Tasks:

1. • Better standards for labels on PRs and issues
2. • Better topics for Community Discussion Categories?
3. • Test Main Web Pages, GitHub Pages in Twitter Validator https://cards-dev.twitter.com/validator
4. • Change Seedtool to Seed Tool throughout repos
5. • Make community logo work in GitHub dark mode
6. • See if We Should Have Vulnerability Disclosure Info in our Repos, Per https://openssf.org/blog/2021/09/27/announcing-the-openssf-vulnerability-disclosure-wg-guide-to-disclosure-for-oss-projects/
7. • Do we want to have a blockchain commons shared GPG key?
8. • Archive vs Update Old Projects Decisions?
   • Itemize Them
   • Decide

Web/Repo Tasks (Large):

1. • Design UniversalResources.info

Community/Patron Tasks:

1. • Add to Airgapped README.md links for UR overview and other topics, repos, and important discussions, that might be needed by a newly arrived airgapped community person (Issue #66)

Standup Scripts:

1. • Try to get j's better scripting back on track

Overview:

1. • Review V's Notes (week of September 19)
2. • Review Roadmap for Rest of Year (week of September 19)
3. • Related to roadmap is review if our strategy is current https://github.com/BlockchainCommons/Community/blob/master/Strategies.md
4. • Discuss Vinay's post-mortem recommendations
5. • Vinay would like to volunteer againt if we in particular focusing on "responsible key management" and funding opportunities in ethereum community for that.

Writing Tasks:

1. • Write About Writing Use Cases (SOON)
   • Write Some Use Cases for Our Usage
2. • Write about Object Identity BLock (OIB)
3. • Why Are Web Assembly & Rust Strategy Important & What Are Those Strategies?
4. • Improve Docs on Signing CLA
5. • Q4 Report (DECEMBER)
6. • Write about SSKR for Identity Developers in W3C-CCG: keys in browsers, don't necessarily use BIP39
7. • Write About Autonomy Chart
8. • Write Release Procedures for iOS
9. • Puzzle through what do to unpublished Open Development draft https://hackmd.io/md7blDMZQjCmP0qB7k1iiQ. @ChristopherA's biggest concern is that the principles are missing something, or are not quite right, or at wrong level (aren't principles but something else).

Writing Tasks (Small):

1. • Add xfp to multisig articles: the [fingerprint/path/to/key]xpub is increasingly called an "xfp" = extended fingerprint. We've not been calling it that.

Tweetstorms

1. • Tweetstorm OIBs, Seedtool
2. • BTCR: Article & Tweetstorm based on https://the-rubric.castos.com/episodes/the-granddaddy-of-dids, with quotes & links

#SC:

1. • #SC for NFTs (once we have a plan)

Video Tasks:

1. • Create Images for Long QR Tool Video
   • Add Slides Requested by C.
   • Add Title & Final from W.
   • Release to Youtube
   • Write Tweetstorm to go with it

Release Manager Tasks:

1. • Work with Fastlane
   • Install
   • Use for Seedtool Release
   • Integrate for use with QRTool
   • Integrate for use with Cosigner

Cosigner:

1. • Prepare Cosigner for Release
   • Withdraw February Build
   • Update Store Text from Issue
   • Remove Front-Page Discussion of Alpha/Testnet
   • Make Mainnet the Default
   • Check Rest of Text
   • Write Mini-Manual
   • Link to Mini-Manual
   • QA For iOS
   • Submit for iOS w/full notes (manual) for Apple
   • A for MacOS
   • Submit for MacOS w/full notes (manual) for Apple
2. • Write Integration Manual for Cosigner & Guardian
3. • Write Integration Manual for Cosigner & Wallet (if it becomes more active)
4. • Write Cosigner Article
   • Write Tweetstorm to go with it
5. • Write Cosigner Mini-Manual
   • Write Tweetstorm to go with it
6. • Produce Short Cosigner Video
   • Write Script for Short Cosigner Video
   • Create Images for Short Cosigner VIdeo
   • Write Tweetstorm to go with it
7. • Produce Long Cosigner Video
   • Write Script for Long Cosigner Video
   • Create Images for Long Cosigner VIdeo
   • Write Tweetstorm to go with it
8. • Proof BlockchainCommons/GordianCosigner-iOS#43

Videos

Jekyll Tasks

1. • Link Anchors for Headers on Web Pages

Stale Tasks

Writing Tasks:

1. • Proceed on Gordian Seal
   • Check in with M.
   • Create Mock-up Landing Page
   • Mock Up Logo
   • Give Logo + Short to M.
   • Collect Info Needed for 99d.
   • Link Youtube videos in places like:
     • ?
2. • Design pages for four Gordian principles that describe sub principles and list how different reference apps meet those principles.
   • What is principle?
   • How did we apply it?
   • What other things fall into principle? (no app does it yet)
3. • Write SmartContract Article, on Signature, Vaults, Covenants
   • What are they?
   • What are they good for?
   • New Flags?
   • UTXO Tricks?
   • https://raghavsood.com/blog/2018/06/10/bitcoin-signature-types-sighash
   • https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018615.html
   • https://arxiv.org/abs/2006.16714
   • https://pinboard.in/u:ChristopherA/t:vault/
   • https://bitcoinmagazine.com/technical/noinput-class-bitcoin-soft-fork-simplify-lightning
4. • Expand Timelock Work
   • Edit Timelock Article
   • Write about script
   • Write about rust library creation
5. • Potential Article: Identifying Stuff, LifeHash, Short Hex, Name
   • Talk with W. about why he did things & the UI of his choices (why anything is in specific places0
6. • Article: Why We Choose BSD+ Patentic and Creative Commons By
7. • Talk with C. about SSKR vocabulary (shard, share, deck, etc)

Video Tasks:

1. • Consider 3-5 minute short videos

Web/Repo Tasks:

1. • Consider https://bitcoin.design/guide/ for language & pointers to our work
2. • Clean up Bean Count repo, so that it's more appropriate for Documentation

Tweet Tasks:

1. • Short 2-3 Tweet Mini-Storms on BCC Content

Gordian Wallet:

Pending

1. • Look at Wallets
   • ColdCard
   • BlueWallet
   • Spectre's Desktop App
   • Capture Info:
2. • Gordian Co Signer Docs (after crypto-request specification)
   • Full manual
   • How to Use with Core
   • How to Use with Cold
   • How to Use with Gordian
3. • GG Docs (next week?)
4. • Set Up Monitoring of BCC Machines?
5. • Review adding YAML schema info to markdown files, initially LBTCftCL, and testing against Google. See https://www.software.ac.uk/resources/guides/adding-schema-dot-org
6. • Gordian Signer Manual
   • Pending: UX Rev (mid-Jan?)
7. • Explain why Engagement Model is Important & How TO Do It & package that with Ruby 1.0.0
   • Engagement Model is meant to show the human experience.
     • There should be a System Document showing flows, which is somewhat orthogonal to the human experience of the Engagement Model
     • But the Engagement a way to ensure that we have all the pieces when we get started, and to make it possible for outsiders to understand what’s going on
     • Forces us to look at the less common parts of the flow, like the beginning and the end, which can easily be the most dangerous sections
     • We can’t do a security review just from Engagement Model, but we feel that it’s a requirement: the first step of a full review
     • Successful here: we spotlighted areas that they weren’t currently dealing with!
   • So BCC Goal: say why this process is important, and why we’re doing it
     • Unlike BCC Engagement Models: this is is real
8. • Review MD Files in Gordian Guardian

Future Possibilities

3. Do We Want to Use "What We Could Do?" as a possibility showcase
   • If so, try to better highlight how each item could help individuals
4. Write Weekly Articles(?)
5. Chapter in LBTCftCL on BCC CLIs
6. Chapter in LBTCftCL on BCC libraries
7. Section in LBTCftCL on BC-UR
8. Is there more we can do on BC-UR? Intro? Other Stuff?
9. v2 of #SC
10. Should LBTCftCL Have an Exam?

Recently Completed

14. • Further integration of Gordian Seed Tool
15. • Write Article or Tweets about Translations [2022]
16. • Update Internship Info, matching dates of https://www.summerofbitcoin.org/how-it-works [Wednesday]
17. • Make Sure UR Docs Talk About Creation
18. • Document Coldcard & Passport Seed Backup Methodologies
19. • Add URs to all test vectors
20. • Write high-level vision of next-generation architecture
21. • Finalize GST Manual Changes for 1.4 (52+) [NW1]
22. • Update All GST Pics as Needed in Manual [NW2]
23. • Do Final Edit of GST 1.4 Manual [NW3]
24. • Write responses for different sorts of crypto-requests, per derivation
25. • Thoroughly test file names of new GST
26. • Update manual for GST 1.4
27. • Write Printing Cover Sheet as Suggested in BlockchainCommons/Gordian#82 (reply in thread)
28. • Look at updated GST SSKR Cover Page, Should We Add Stuff (TODAY): Master Key Fingerprint, Ethereum Fingerprint, URL for seedtool? mention other places to recover (or just a page: GST, seedtool-cli)
29. • Respond to SoB about Internships [Wednesday]
30. • Tweetstorm Case Studies