Project Area Leaders

BeeWare, despite being such a young project, has a huge surface area for an Open Source project. BeeWare is also entirely run by volunteers, and it's quickly becoming unfeasible for the project founder or the core contributors to stay on top of all the changes going on across the project.

To help with this, BeeWare has Project Area Leaders.

A Project Area Leader is responsible for their area of the project. They're empowered to file issues, do issue triage, approve and merge PRs, and help set the direction of their part of BeeWare. Their role is to keep improving their part as part of the larger fabric of BeeWare.

Core responsibilities: Triaging and approving PRs for their area of the project, responding to help requests, and checking in with the project via chat at least every two weeks. Because BeeWare is a highly active project, if a Project Area Leader doesn't check in with the project chat regularly, they agree that they might be replaced temporarily or permanently to keep their area of the project moving.

Current Project Areas, and their leaders are listed below. This is not an exhaustive list, but a good starting point. Any currently unclaimed project could potentially be claimed by you reading this - check in with the gitter chat and ask if you have interest.

• VoC - ?
• Batavia - ?
• Toga (core) - ?
  • iOS - @phildini
  • Cocoa/MacOS - @phildini
  • Android - ?
  • GTK - ?
  • qt - ?
  • Django - ?
  • Windows - ?
• Briefcase (core) - ?
  • MacOS - @phildini
  • iOS - @phildini
  • Android - ?
  • Linux - ?
  • Windows - ?
• BeeKeeper - ?
  • Comb - ?
  • Waggle - ?
• Rubicon - ?
• Colosseum - ?
• Duvet - ?
• Cricket - ?
• Beefore - ?
• Podium - ?
• Ouroboros - ?
• Bugjar - ?