Document recurring flows
- Dominant language
- No language data
- Stars
- 17
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Document recurring flows and who's responsible for each of them.
| Frequency | Flows | Responsible Party |
|-|-|-|
| Weekly | Swarm Sync & Sub-Swarm Syncs | Facilitation Lead? |
| Biweekly | All-Builders Radio Show | Facilitation Lead |
| Monthly | Payout Tx for Roles, Swarm, Expenses | Admin Lead |
| Quarterly | Community Town Hall, Deactivations | Facilitation Lead |
| Quarterly | Est Tax Payment | Accounting Lead |
| Quarterly | Rep Update Tx, Token Airdrop Tx | Admin Lead |
| Yearly | Retreat | Facilitation Lead |
| Yearly | Tax Filing | Accounting Lead |
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the repository's operational resources and checking how recurring flows are currently documented. Use the issue's frequency, flow, and responsible-party table as the source, and consider the work done when each listed recurring flow has a documented owner.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100