-
Notifications
You must be signed in to change notification settings - Fork 6
Editing
Editors are appointed by the chairs of the CG to lead the work on a specification. They name appears somewhere near the top of the specification they are in charge of. There can be multiple co-editors on a single specification.
We are be using the ReSpec to reduce boilerplate and to make it easier to make specs that fulfill the expectactions for Spec. There's an introduction here: https://www.w3.org/respec/guide.html, and a full documentation here: https://www.w3.org/respec/
The following guidelines for Editors are based on https://browserext.github.io/charter/ and generally accepted best practices.
-
If the group has made a decision about something, you must follow it. Otherwise, follow your best judgment.
-
If you're not sure about something (or if you're sure but sense it would be controversial), open a github issue about it.
-
Every once in a while, if you've made substantive changes to your spec, send a mail to [email protected] inviting people to review the spec.
-
You're the first line of support if people file github issues or send mails about your spec. Answer the obvious things, drive the discussion with the group on the rest.
-
Pull requests for anything except trivial changes (typos, grammar or markup fixes...) can only be accepted when the authoris a member of the CG, as per https://github.com/browserext/browserext.github.io/blob/master/CONTRIBUTING.md
-
Be respectful of others and behave in a professional manner, regardless of disagreements and cultural or personal differences. Refer to the Code of Ethics and Professional Conduct