search

adafruit / cookiecutter-adafruit-circuitpython

Cookiecutter template for Adafruit's CircuitPython libraries.
MIT License
22 stars 37 forks source link

Create CircuitPython Community CoC. #144

Closed kattni closed 3 years ago

kattni commented 3 years ago

Fixes #141.

Please do not merge this until the conversation has been concluded.

I made a few simple changes to get started - swapping out "CircuitPython" for "Adafruit" in a few places, and making some of the wording more generalised. "Adafruit" remains in places where we need to make specific decisions about content.

I'm realising that, unfortunately, since a second file needed to be generated to make cookiecutter generate the proper CoC depending on library-type choice, it doesn't render it as a diff from the original.

None of the changes I made need to stay in - I simply wanted to create a starting point for this conversation.

kattni commented 3 years ago

Hey, folks. I think a clarification of the scope of this Code of Conduct is needed before we continue. I may be the one who is unclear on what was being proposed or what is desired.

It is my understanding that the idea was to create a CoC that applied to libraries added to the Community Bundle. If that is the case, the moderation responsibilities fall to the maintainer of the particular project, not to Adafruit. Therefore continuing to include support(at)adafruit.com or any email that forwards to them would defeat the purpose. As well, referencing the Adafruit Discord also defeats the purpose, as any issue that occurs there is within Adafruit's scope, and within the Code of Conduct listed on Discord.

Any action taken by a community maintainer on their own project could be applied to the Adafruit community as well (e.g. if the violation is serious enough, Adafruit may reciprocate the resolution), but Adafruit should not be taking action on behalf of the community maintainer. As well, if a violation of the Adafruit CoC somehow relates to a maintainer project (e.g. a discussion on Discord about the project results in a CoC violation), the maintainer can reciprocate Adafruit's action as well.

If the scope is meant to apply to the project and therefore responsibility is meant to fall to the project maintainer, then we need to generalise the wording to, in the event of a violation, suggest filing an issue on a repository, or emailing the project maintainer directly. The Discord verbiage should likely be removed entirely, as, again, any actions on Discord are covered by the Adafruit CoC. I believe there is more that should be changed, but this should at least give you an idea of what my understanding is.

Please let me know what the intention was for this CircuitPython Community Code of Conduct.

jposada202020 commented 3 years ago

My understanding was to make a more general CoC, to be used for the community Bundle as described in issue #141

askpatrickw commented 3 years ago

My understanding was to make a more general CoC, to be used for the community Bundle as described in issue #141

And I would say for the Community in General... and the places the Community is hosted which would include Adafruit but not just Adafruit. If I was doing a livestream on CP (will never happen) and someone showed up and was offensive, that would mean the same things as doing it on Adafruit Discord.

If I was doing a livestream on making the best peanut butter and jelly sandwich (still won't happen) then it wouldn't have anything to do with CP or Adafruit unless I guess the person involved was the same in both cases.

kattni commented 3 years ago

@lesamouraipourpre Would you also like to take a look? Thanks!

kattni commented 3 years ago

Thanks for the feedback! I've asked @FoamyGuy to test this to make sure both the Community and Adafruit methods build with the appropriate CoC (I'm not super experienced with Jinja, so I want to make sure I did it properly). Please hold off on merging until that test is completed. Thank you!