Conversation
freakboy3742
left a comment
freakboy3742
left a comment
There was a problem hiding this comment.
Looking good. I've left a few comments about content that needs to be added (some of which might need some further discussion).
Two broad comments:
- Could you wrap this at 80(ish) chars? The long lines are a PITA to review.
- I've flagged a couple of specific examples, but end-of-line punctuation needs a once over.
| Becoming an Apiarist | ||
| ---------------------------- | ||
|
|
||
| Introduction of a new Apiarist into the team is at the sole discretion of the existing Core Team. While there are no solid rules to this, in general, someone will be invited to be an Apiarist on a BeeWare project if they have demonstrated solid contributions to the project. This can also be extended to someone with specific domain knowledge (for example, iOS/macOS) which might be lacking in the existing team. It also doesn't have to be based on commits. Anyone who is able to demonstrate a vested interest in the project in general may ask to be given permission to commit to the project. |
There was a problem hiding this comment.
"no solid rules" -> "not currently any solid rules"
|
|
||
| Introduction of a new Apiarist into the team is at the sole discretion of the existing Core Team. While there are no solid rules to this, in general, someone will be invited to be an Apiarist on a BeeWare project if they have demonstrated solid contributions to the project. This can also be extended to someone with specific domain knowledge (for example, iOS/macOS) which might be lacking in the existing team. It also doesn't have to be based on commits. Anyone who is able to demonstrate a vested interest in the project in general may ask to be given permission to commit to the project. | ||
|
|
||
| All new apiarists will be 'inducted' (for lack of a better word) in the core values and guidelines of the project. |
There was a problem hiding this comment.
Add: A summary of the core values can be found on the about page. Anyone who joins the team will be expected to uphold those values, and contribute to discussions about evolving those values over time.
|
|
||
| Those busy bees on the `Core Team </community/team>`_ have a number of responsibilities to keep the hive that is BeeWare moving. This is an evolving project, so this page is subject to change. | ||
|
|
||
| These include, but aren't limited to, responding to issues, reviewing and merging code, and architecture of the BeeWare project as a whole. |
There was a problem hiding this comment.
add: mentoring new contributors
| These include, but aren't limited to, responding to issues, reviewing and merging code, and architecture of the BeeWare project as a whole. | ||
|
|
||
|
|
||
| There are people we trust to make code decisions, there are people we trust to make code and organizational decisions, and there is a person with whom the metaphorical buck stops, who guides the vision of the whole organization and is often it's biggest cheerleader |
There was a problem hiding this comment.
Full stop at end of sentence.
| - Any member of the BeeWare community. Given we work in the open on GitHub, anyone can suggest changes to the code and have their code merged. The only limit to your ability to contribute is having your work merged by a team member with the rights to do so. | ||
|
|
||
| Apiarist: | ||
| - Any Bee with a Commit Bit. These members have demonstrated ability in relation to the project -- this could be on a technical level (JavaScript, Python, Objective-C expertise; GTK, macOS knowledge), or on another level (community management, code review). |
There was a problem hiding this comment.
Point of order - would we still give the commit bit to someone who doesn't have the ability to merge code? A really great community organiser, for example, doesn't need the commit bit. As currently configured, there isn't an Apiarists team on Github - only Senior Apiarists. Should we have one, but not give that group commit access to anything?
In that vein, would it be better to rephrase "apiarist" as:
A bee who has been recognised as a trusted contributor. These bees have demonstrated ability in relation to a specific part of the BeeWare project over a period of time. This could be on a technical level (JavaScript, Python, Objective-C expertise; GTK+, macOS knowledge), or on another level (community management, code review). Apiarists may also have the commit bit for the project where their expertise is recognized.
| - Any Bee with a Commit Bit. These members have demonstrated ability in relation to the project -- this could be on a technical level (JavaScript, Python, Objective-C expertise; GTK, macOS knowledge), or on another level (community management, code review). | ||
|
|
||
| Senior Apiarists: | ||
| - Apiarists with elevated access in GitHub, and also an added level of responsibility to oversee the project as a whole. They are able to make architectural decisions, but ultimately answer to the BDFN |
There was a problem hiding this comment.
Full stop at end of sentence.
|
|
||
| * **Assume that if someone has done something the "wrong" way, it's because we've failed in communicating process.** | ||
|
|
||
| * **Assume any expression of anger or frustration comes from a genuine place of wanting to use a BeeWare tool/library.** |
There was a problem hiding this comment.
Add: * Encourage other members of the community to reflect these ideals in their own communications, both inside and outside the BeeWare community.
The idea here: One of the biggest contributions Jacob and Adrian made to Django was clamping down on bad language/bad behaviour in Django fora. This "leading by example" is part of what made the Django community such a pleasant place. It also set the scene for CoC discussions a few years later, because it's a lot easier to have a conversation about civility when everyone is being civil (c.f., Linus.)
| * **Assume that if someone has done something the "wrong" way, it's because we've failed in communicating process.** | ||
|
|
||
| * **Assume any expression of anger or frustration comes from a genuine place of wanting to use a BeeWare tool/library.** | ||
|
|
There was a problem hiding this comment.
It feels like there's a break here between "social behavior" and "technical behavior". Is there value in splitting this into two distinct lists?
|
Updates have been made to the PR |
Co-authored-by: Russell Keith-Magee <russell@keith-magee.com>
2 participants
See the commit comment history for existing discussions