Skip to content
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

Merged
merged 13 commits into from
Oct 13, 2017
Merged

Contributing #362

merged 13 commits into from
Oct 13, 2017

Conversation

mnot
Copy link
Member

@mnot mnot commented Jun 27, 2017

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.

@mnot mnot added the meta label Sep 29, 2017
@mnot
Copy link
Member Author

mnot commented Sep 29, 2017

@mcmanus I changed this to just be like the QUIC process, where we flag things with has-consensus after the issue is confirmed on-list, just like QUIC. I think that will cause less confusion (esp. since I see Martin starting to adopt has-consensus in his WGs), and we don't have to flag everything with consensus as such, especially for non-controversial drafts. WDYT?

@mcmanus
Copy link
Contributor

mcmanus commented Sep 29, 2017

whoami to stand in the way of github progress? merge it!

@wtarreau
Copy link

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.

@mnot
Copy link
Member Author

mnot commented Sep 30, 2017

Hm. I read 'we' as being inclusive -- literally, "the reader along with others."

Further up (in existing text) is:

To be active in the Working Group, you can participate in any of these places. Most activity takes place on the mailing list, but if you just want to comment on and raise issues, that's fine too.

I'm happy to expand that to make it clear that "we" is "all participants" -- would that help?

@wtarreau
Copy link

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.

@mnot
Copy link
Member Author

mnot commented Oct 1, 2017

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.

@wtarreau
Copy link

wtarreau commented Oct 1, 2017

OK fine, thanks.

@mnot mnot merged commit c33218f into master Oct 13, 2017
@mnot mnot deleted the contributing branch October 13, 2017 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

None yet

3 participants