-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contributing #362
Contributing #362
Conversation
# Conflicts: # CONTRIBUTING.md
…ting # Conflicts: # CONTRIBUTING.md
@mcmanus I changed this to just be like the QUIC process, where we flag things with |
whoami to stand in the way of github progress? merge it! |
I'm seeing a few (but very few) occurrences of the word "we" which plays a bit against "you" and may make newcomers feel a bit of resistance (ie: we decide, you abide). I think it's important to keep in mind to use "the group" or something like this instead to avoid newcomers thinking that decisions are taken by a few people as is often the case in opensource projects for example, and make them realize that by participating they become part of this group. |
Hm. I read 'we' as being inclusive -- literally, "the reader along with others." Further up (in existing text) is:
I'm happy to expand that to make it clear that "we" is "all participants" -- would that help? |
Semantically I agree with your view and share it as well, but keep in mind we're talking to people completely external to this group and thinking whether or not they're going to join by reading this file serving as a rule. Maybe indeed adding a line after the one you quoted saying 'Anyone participating to a discussion or an issue automatically becomes part of the Working Group, sometimes referred to as "we" in this document'. But in general I think that "we" should be avoided as it rarely includes "you", especially when there are probably 2 or 3 occurrences only. |
OK. I added an explicit statement about "membership" at the top -- that should clarify things. I don't think that with that context "we" is harmful or misleading. |
OK fine, thanks. |
Revise contributing.md to reflect our working practices more closely.
Specifically, editors can make proposals in the drafts that close issues, as long as they remember to label them
proposal
.This is more aligned with the quicwg process; it's different (they use
has-consensus
) because we have a large number of existing issues with consensus.