-
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
TEAM.md -> EDITORS.md? #64
Comments
FWIW I like MAINTAINERS.md, for the reason you gave at the end there. |
Helps with whatwg/meta#64. See also: - whatwg/meta#69 - whatwg/meta#65
Helps with whatwg/meta#64 See also: whatwg/meta#69.
Thanks @snuggs for taking care of this! |
@annevk oh crap. Probably should have not used Fixes in this case. Perhaps Addresses. My bust. A convention i've used in OSS for dependencies when you have a lot to maintain.
Dank je ;-) https://help.github.com/articles/closing-issues-using-keywords/ |
oh ok as long as #65 is still open. Whew. ;-) |
@snuggs yeah, I think it's fine that this one is closed. I fiddled a bit with your commit messages to make sure nothing else got closed. 😊 |
@annevk #TeamWorkToMakeTheDreamWork 🎉 ...or MAINTAINER work (pun intended). |
Helps with whatwg/meta#64 See also: whatwg/meta#69.
If we change this, and I think we should given the conflict with GitHub teams, it needs to be changed in whatwg/meta and whatwg/html. Anwhere else?
(We could also go for MAINTAINERS.md potentially, given that it's not always the editor that merges.)
The text was updated successfully, but these errors were encountered: