Github

[jsmorabito]

How can we set up our Github organization, repositories, issues/labels, permissions, etc to allow for our community to scale?

current state

• milestones (not currently used)
• issue triaging (process formalization in progress Github Issue Triage #1284)
• issue labels Github Issue Labels #1055
• epic issues (potentially underutilized. examples Parser #1122 Self-Hosted Real-Time Collaboration #840 Multiplayer UX #1119)
• project boards
• teams
• organization and repository permission levels not explicit or formalized

questions

• what should github user permissions be set to for optimal efficiency

notes

• Preliminary thoughts on scaling github here: https://roamresearch.com/#/app/athensresearch/page/bto7svyxW
• https://blog.zenhub.com/how-to-use-epics-and-milestones/
  • we should use milestones for sprints (ie if we operate in 2 week sprints each sprint is a milestone with issues and objectives located within
  • epics for larger initiatives that collect smaller issues, typically include a mot
    • example epics (website redesign, handbook overhaul, database management, onboarding tour)

[tangjeff0]

4 larger abstractions for issues:

1. milestones - haven't used yet
2. epics (meta-issues) - have made a few. Haven't done a great job of keeping them up to date
3. project boards - have made a few. Haven't done a great job of keeping them up to date
4. Monthly Priorities - past two months May 2021 Priorities: Self-Hosted RTC, Handbook Structure, and Website #1099 June 2021 Priorities, Part 1 #1271

Biggest problem with all these is keeping them up to date. Not sure if any/all of them are that good. TODO: see how larger projects do project mgmt and organize larger numbers of issues.