Skip to content

Commit

Permalink
First stab at a "Responsibility" section
Browse files Browse the repository at this point in the history 
Definitely *not* happy with the wording yet.  Throwing it out there for
feedback.
  • Loading branch information
@lizmat
lizmat committed Nov 30, 2019
1 parent f315ca7 commit 21c86e1
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions solutions/meta/CoC.md
View file
Expand Up @@ -53,6 +53,14 @@ If you have been unable to sway a troll, or you are otherwise not able to handle

The most important thing to remember in these situations is simply: *Don't Panic!*. Rash behavior will never help the situation.

# Responsibility

If you are contributing to the Rakudo core (on any backend, nqp or Rakud code), you are responsible for making sure that your contributions do not break Rakudo (either with the tests in Rakudo itself, or in roast (aka spectest)).

But this responsibility goes further than that: should your change break modules in the ecosystem, you have become responsible for getting those fixed as well: either by doing this yourself, or by engaging other members of the community to try and fix that.

Should all of this fail, then there is no choice but to revert your contribution.

# Good Intentions

Even within a community where every member is filled with good intentions, it is possible that conflicts arise. Especially in a community as diverse in culture, age and gender, and as geographically spread as the Raku community, misunderstandings can and will occur for **any** reason.
Expand Down

2 comments on commit 21c86e1

@vrurg
Copy link
Contributor

@vrurg vrurg commented on 21c86e1 Nov 30, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if it really belongs here. Community in general is bigger than just Rakudo core development. Each subproject can have its own guidelines and that's fine. Perhaps, this is what this section has to be about (in "pseudo-code language"): Follow the guidelines of the project you contribute to. Breaking the guideline rules is considered a form of trolling.

@japhb
Copy link

@japhb japhb commented on 21c86e1 Nov 30, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, this commit feels "off"; especially the last sentence doesn't sound right. To me it seems a bit like "If you aren't willing to be responsible for literally the entire ecosystem, we won't accept your changes and we'll just revert you if you try." That sets the bar too high for contributors just trying to make a small improvement.

I think @vrurg has a point in his comment, that we want to speak more generally in the community-wide CoC doc, although I do want to be careful to separate "innocently unaware of all the rules" from active trolling; otherwise we become unfriendly to beginners. Maybe "Follow the guidelines of the project you contribute to. We're happy to assist beginners to learn the ropes, but repeated violations of guidelines you've already received feedback on can be very frustrating for our friendly volunteers." Hmmm, still feels a bit off, but not sure in what way.

As for the Rakudo specifics: I do think people hacking on core code should be responsible for making sure their changes pass internal tests and roast -- they exist for exactly that reason, after all -- and I think core hackers should also be responsible for following the compatibility rules that we've already set down. However, I'm unsure about ecosystem responsibility.

Ecosystem authors often have to take time away from the Raku community for extended periods, and it may be difficult to reach some of them even to accept a PR. It may be worth having a policy for that situation as well (though almost certainly in a separate document, because I think that's more about procedure for dealing with unhealable ecosystem problems than behavior/conduct).

Please sign in to comment.