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

Document teams #38

Closed
annevk opened this issue Sep 15, 2017 · 3 comments
Closed

Document teams #38

annevk opened this issue Sep 15, 2017 · 3 comments

Comments

@annevk
Copy link
Member

annevk commented Sep 15, 2017

The way I'd like to use teams:

  • Anyone can join any team they desire. To join just let someone know or file an issue against whatwg/meta.
  • Everyone tries to ensure the appropriate teams are pinged on relevant issues/pull requests
  • Teams have no formal authority, though it's fine to add them as contributors to repositories for ease of collaboration. For all repositories we care about protecting master primarily. The bar for write access to other branches is much much lower.
  • Teams have no responsibility either. If you ping a team and get no feedback, moving things forward responsibly is still on you.
  • Creating new teams should be easy via filing an issue against whatwg/meta. Review should take some care it's not too much of a niche or overlap with existing teams.

I was thinking we'd put this in a Markdown to point folks to or maybe add it to the FAQ? Should we have a GitHub-specific FAQ?

@domenic
Copy link
Member

domenic commented Sep 15, 2017

The bar for write access to other branches is much much lower.

Last I checked GitHub didn't separate out "ability to push to other branches" from "ability to close (or label) issues". It's probably fine, but you can imagine bad situations where someone closes issues too aggressively.

Everything else is pretty great.

I wonder if we should try to formalize the topic: x labeling system we're using for HTML, and link teams to topics? Maybe over-ambituous and annoying to maintain though, as opposed to teams which are just automatically taken care of by GitHub for us.

Putting this in Markdown (in whatwg/meta) makes sense. And linking to it from either the FAQ or some kind of central how-to-participate page sounds reasonable. Not sure it's really an "FAQ" per say....

@annevk
Copy link
Member Author

annevk commented Sep 15, 2017

For your first concern we should maybe add "patience" and "due diligence" to Working Mode somehow.

Does GitHub have features to link teams to topics? Sounds useful... And yeah, it would be nice to have similar labels throughout all our repositories, but it'll be a bit of a hassle to maintain. Perhaps time for another bot?

@snuggs
Copy link
Member

snuggs commented Sep 17, 2017

annevk added a commit that referenced this issue Sep 18, 2017
annevk added a commit to whatwg/whatwg.org that referenced this issue Sep 18, 2017
annevk added a commit that referenced this issue Sep 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants