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

How to be an editor #12

Open
littledan opened this issue Apr 16, 2018 · 1 comment
Open

How to be an editor #12

littledan opened this issue Apr 16, 2018 · 1 comment
Assignees

Comments

@littledan
Copy link
Member

littledan commented Apr 16, 2018

As TC39 expands into an editor group, there are certain workflows that editors have, including

  • Tagging issues
  • Reviewing issues and small PRs
  • Reviewing PRs for Stage 4 features
  • Applying standard practice for when PRs are ready to merge
  • How to manually check that a PR has appropriate IPR provenance

It'd be great to document these.

@littledan
Copy link
Member Author

I wrote some initial documentation in https://github.com/tc39/how-we-work/blob/master/management.md#ecma-262-editor-group , but I'd appreciate some help from people who have experience cutting specification releases as an editor. What process do you recommend following? cc @bterlson @caridy @ljharb

cc @sffc who is interested in editing for ECMA-402

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants