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 grown beyond the point where it's realistic 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, and while following the Core Team guidelines.

More detail about expectations for Project Area Leaders is at the bottom of this page.

Critical responsibilities of a Project Area Leader:

• Give feedback on PRs in their area
• Merge acceptable PRs in their area
• File issues for their area as they arise.
• Triage issues in their area
• Respond to help requests in their area

Optional, but would be really nice, responsibilities of a Project Area Leader:

• Making major contributions to the design and implementation of new features in their area

Above all, a Project Area Leader is supposed to keep their area moving. Their primary goal is to unblock anyone else working in their area, and do so in a way that benefits their area, the BeeWare project, and the BeeWare community as a whole.

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 - @eliasdorneles
• Batavia - ?
• Toga (core) - ?
  • iOS - @Ocupe, @phildini
  • Cocoa/MacOS - @Ocupe, @phildini
  • Android - @eliasdorneles
  • GTK - ?
  • qt - ?
  • Django - ?
  • Windows - ?
• Briefcase (core) - ?
  • MacOS - @phildini
  • iOS - @phildini
  • Android - ?
  • Linux - ?
  • Windows - ?
• BeeKeeper - ?
  • Comb - ?
  • Waggle - ?
• pybee.github.io (the pybee.org website) - @glasnt, @goanpeca
• Rubicon - @dgelessus
• Colosseum - ?
• Duvet - ?
• Cricket - ?
• Beefore - ?
• Podium - ?
• Ouroboros - ?
• Bugjar - ?

Final thoughts on the nature of Project Area Leaders

• Project Area Leaders are non-exclusive
  • More than one person can be a Project Area Leader for a certain part of BeeWare, and one person can be a Project Area Leader for more than one area.
• Project Area Leaders can volunteer for as long or short a period as they want.
  • The Core Team might move a volunteer off the Project Area Leader list if it looks like a volunteer has gone missing for an extended period of time. An example of "gone missing" is the PRs are starting to pile up, and a Core Team member has to start jumping in and doing triage to keep that are of the project going.
• Being a Project Area Leader should not be viewed as the BeeWare project demanding work of volunteers.
  • There is no shame or blame from us in a Project Area Leader realizing the load is too high and they have to step down.
  • Being a Project Area Leader is entirely "challenge by choice", and we are grateful for any time a volunteer gives.
• Project Area Leaders should aspire to follow the core team guidelines.
• Project Area Leaders can still work on other parts of BeeWare
  • Being a Project Area Leader is the core team recognizing expertise and dedication, not trying to limit what a member can do.