Governing coala
This is a proposal on how to decentralize the management of coala by introducing teams.
There will be several teams. Each team ideally consists out of one team leader and at least two coala members. Each member may only lead one team at a time.
Teams are choosen by the need of something that needs to be done, not by the availability of members doing it. The proposed teams are:
- core: Developeing and maintaining the coala core repository. In Addition everything that needs to be done and has no fitting team will be assigned to the core team.
- bears: Developing and maintaining the coala-bears repository. Wrap more existing tools, help with writing new bears and update existing ones.
- research: Work on new architecture for coala parts. Help with thesis writing and implementing algorythms for the science community.
- docs: Improve the existing documentation, wiki, tutorials and guides. Introduce new ones as needed.
- plugins: Develope and maintain the coala plugins for multible text editors or IDEs.
- engagement: Create all promotional material, or help creating it, like flyers, blog posts, homepage content and such. Also manage conference attendence and feedback handling.
- website: Coding staff for the homepage.
- review: If there is a big pr or a very complicated one this team is ment to come from outside the other teams to help with the review process. Also in general this team should train the rest of the org how to do good reviews.
- GSoC: Temporary admin team for things like the Google Summer of Code that don't need to be done the whole year.
The idea for the teams is that every member can apply to the teamleader to join a team. As a member of a team you should mainly feel responsible for issues assigned to the team but are free to keep working on any part of coala you want to. This is not meant to be in your way but instead to help team leaders know who they can assign issues to and ask questions about the topic.
Any coala member may propose him or herself to be a team leader. The proposal should be public and include reasons and plans to take that particular team forward. (Archived in the wiki.)
For each team, every member may vote once for any potential team leader excluding him/herself. Abstaining is possible.
The team leader will get pinged about issues matching his team's responsibilities and then assigns team members to work on them. It is the team leader's responsibility to make shure issues assigned to his team get fixed. It is not the leader's responsibility to fix all issues but to manage them.
Also the team leader is the contact person for other members about the responsibilities of the team.
- Leader max 2 per company
- Leaders may resign at any point. Reelections if more than a month left
- Membership need renewal after 2 years
- Members get a coala Mail alias
About the teams:
- Engagement and website should be the same. Engagement would be a super set of website (Including things like planet coala, etc)
- You should add triaging/issue managing, label creation, etc to review Instead of GSoC, make it internship programs ? (GCI, Outreachy, etc)
Also (just idle thoughts) I think it would be a swell Idea if we can do a documentation project in Outreachy. It'd get us introduced to outreachy with a non-coding task (ensuring we can finish it) and also get us a good member on the documentation team possibly
Also,
Leaders may resign at any point.
is not something you would want to advertise I think ?
-- Abdeali
Do you think it would be better if we break up core a little further? It's a pretty big thing. Maybe 2-3 subcategories?
-- hypothesist
Make gitmate cc Team leaders for issues
Get kanban board for leader->team
-- sims1253
coala