-
Notifications
You must be signed in to change notification settings - Fork 161
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
Comments
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 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.... |
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? |
The way I'd like to use 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?
The text was updated successfully, but these errors were encountered: