search

vacp2p / research

Thinking in code
MIT License
62 stars 4 forks source link

Chore(Org): Create labels for tracks and GH board automation #112

Closed oskarth closed 1 year ago

oskarth commented 1 year ago

Problem

As Vac is growing, so is the surface area of the types of work we deal with. During the last offsite, we discussed having tracks to track efforts across multiple projects, people and repos. We want a simple way to track this cross-repo, and get visibility in the work that we are doing and should be doing.

Tracks

Specifically for Secure Messaging, and with a lot of overlap with Waku Product.

1. RLN (relay and other applications)
2. Operator outreach
3. Anonymity
4. FT-Store
5. Discovery
6. Protocol Incentivization (with Service Credentials)
7. Restricted run (e.g. filter, WebRTC)
8. Conversational security
9. nwaku productionization
10. nwaku maintenance
11. Network testing
12. Platform outreach
13. SDKs (incl bindings)
14. go-waku productionization

zkWASM track:

1. Kickoff

RFCs:

1. Waku specs
2. Logos Blockchain specs
3. Codex specs
4. App specs
5. Process
6. Academic collaboration / Research outreach

Applied ZK/Explorations tracks:

1. Validator privacy
2. Zerokit
3. Exploration

Meta track:

1. Vac Organization

Proposed solution

Additionally:

Optional

Automatic syncing across repos (doesn't seem worth effort now tbh, but could be done)

oskarth commented 1 year ago

Labels file here https://github.com/vacp2p/research/blob/master/.github/labels.yml

A bit annoying to keep in sync across multiple repos, but once things settle down should be fine

oskarth commented 1 year ago

GH cross-repo credentials: Note that ADD_TO_PROJECT_PAT will expire in 30d, GH recommends not making this without a due date. Will see in a month how easy this is to update.

oskarth commented 1 year ago

Future TODO: Once happy, clean up old vac-research CI project

oskarth commented 1 year ago

Seems to work! Closing.