Giters

tc39 / how-we-work

Documentation of how TC39 operates and how to participate

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

How to be an editor

littledan opened this issue · comments

commented

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.

commented

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