Closed oskarth closed 5 years ago
Teams (fallback in terms of responsibilities):
- [ ] Core (310 fixup) @mandrigin
Do we need to add team documents as well?
@mandrigin It'd be useful as it documents thinking, and makes it clear what we are spending time and resources on. I think in Core's case the document you started is useful already, just with metadata and perhaps short research timebox to make sure prios still make sense wrt critical path. What do you think?
@mandrigin yes, it can be a living document
All swarm leads should be prepared to give an update on Core Dev call Monday (https://github.com/status-im/pm/issues/90, as well as having a skeleton research issue (with timebox and rough summary and participants).
Then we have 1 week for either full or partial research, and a then vacation break for presumably a bunch of people. Then Q1 is full steam ahead.
Feel free to PM me if something is unclear or if you need help to bounce stuff 1:1 with research portion.
Action point for tomorrow: decide on what to do re teller network and DAO, if there will be swarm updates in this repo or if we it should be out of scope. Right now this/these are the only ones missing for this issue to be complete per janitor swarm.
These have now been committed, closing issue as done.
See https://github.com/status-im/swarms#getting-started for how to create a swarm. Initial PR can be done in <5m if so desired (contributors, rough summary, timebox research).
Acceptance criteria for each swarm at this stage: Swarm proposal in GH with contributors, rough summary and timeboxed research.
SNT Utility:
Essential swarms:
[x] DAO @iurimatias
[x] Patient Zero / Onboarding / Polish @hesterbruikman @mandrigin @rachelhamlin
[x] Protocol @oskarth
[x] Janitors @jarradh
Teams (fallback in terms of responsibilities):
FYI @rachelhamlin and @hesterbruikman where PM/UX(R) is applicable, and @jarradh @naghdy in general.