Opensource.guide: [RFC] Sustaining Growth > Sustaining Healthy Communities

[nayafia]

Hey open source maintainers! We would love your feedback on the Sustaining Growth > Sustaining Healthy Communities article. We will leave this open for comments until Sep 1, 2016.

Does anything seem inconsistent with your experience? What is missing? Are there any other helpful resources on this topic?

Feel free to comment and discuss here, or even open a pull request to suggest changes.

View | Edit

[MikeMcQuaid]

Resist fixing easy bugs.

Perhaps "resist fixing easy, non-critical bugs" as I think that users' needs should take priority over contributors if it's something severe.

Otherwise 👍

[benbalter]

CONTRIBUTORS.txt

Elsewhere the convention is .md

[lee-dohm]

I feel like "Don't tolerate bad actors" should be at the top of this section. It's that important.

I've actually got a lot of material regarding bad actors. I'll try to form it up into a PR.

[jessfraz]

the part about CONTRIBUTORS.txt might also want to mention .mailmap, it makes getting stats about contributors more accurate because a person using multiple emails gets mapped to the same user. See: https://git-scm.com/docs/git-shortlog

[kytrinyx]

In Issues, label bugs that are suitable for beginners: for example, "good first bug", "help wanted", or "first-timers-only".

I'd like to suggest that we remove "help wanted" from this as an example, since it's really hard to act on. I want help with all the bajillion issues in my repository, but that doesn't mean that someone coming in to the project would be able to help.

Also: let's standardize on hyphenation vs no hyphenation in the label names.

[jessfraz]

ya "help wanted" from experience sometimes leads to that huge rabbit hole 4
levels deep with no escape

On Tue, Aug 23, 2016 at 9:57 AM, Katrina Owen [email protected]
wrote:

In Issues, label bugs that are suitable for beginners: for example, "good
first bug", "help wanted", or "first-timers-only".

I'd like to suggest that we remove "help wanted" from this as an example,
since it's really hard to act on. I want help with all the bajillion issues
in my repository, but that doesn't mean that someone coming in to the
project would be able to help.

Also: let's standardize on hyphenation vs no hyphenation in the label
names.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/github/open-source-handbook/issues/55#issuecomment-241800657,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYNbHzIeTlyoOXQ649C3lI7vHfQDUVRks5qiyaVgaJpZM4Jn9qh
.

Jessie Frazelle
4096R / D4C4 DD60 0D66 F65A 8EFC 511E 18F3 685C 0022 BFF3
pgp.mit.edu http://pgp.mit.edu/pks/lookup?op=get&search=0x18F3685C0022BFF3

[nayafia]

@benbalter does GitHub have a POV on file extension? should I just leave it generic with "CONTRIBUTING file"?

[benbalter]

.md will render nicely as HTML, whereas .txt and no extension will render as monospaced text. I'd recommend .md as the best practice, for human readability, but all three will be recognized, in terms of the above-issue banner.

[joshsimmons]

Minor detail, but I suggest "drive-thru contributors" as a replacement for "drive-by contributors" here and elsewhere in this handbook. All credit due to @vmbrasseur who uses the former in an excellent talk she does on the subject. It serves the same purpose and doesn't have the negative connotations that drive-by does. More here: https://lwn.net/Articles/688560/

Love the "Don't tolerate bad actors" section. My recent Open West keynote included a "Don't tolerate jerk behavior" section and it was probably the most popular segment of the entire talk. "Our communities are only as awesome as the worst behavior we tolerate." No suggestion for that section, just a +1

[nayafia]

Closed per #98.