Community-committee: Add language around emeriti to docs 馃摑

Created on 3 May 2018  路  3Comments  路  Source: nodejs/community-committee

Further to conversation stemming from #294 and #301, CommComm documentation needs to include language around emeriti, specifically:

  • if an emeriti wants to become active, the process on how that could work

As it stands now, the documentation is not explicit. It simply reads that emeriti ...may request that the CommComm restore them to active status.

As suggested here, it would be advisable to have context on how the TSC handles parallel situations.

good-first-issue

Most helpful comment

Does someone wants to tackle this PR? This should be quite simple and represents a perfect good first issue!

All 3 comments

For now, the process for returning from emiriti to active that was used was quite simple:

  • The emerit opens a PR on the README moving themselves from the emiriti section to the active section
  • The rest of the CommComm has a vote during the next meeting to validate said return.

This is simple enough and works for now, so I'd say we stick to that, but we do need to write it somewhere I think.

Does someone wants to tackle this PR? This should be quite simple and represents a perfect good first issue!

For anyone considering making this as their first PR, I'm happy to review it before it's merged ^_^

You can request a review using my github handle in the right-side bar on the PR interface.

Was this page helpful?
0 / 5 - 0 ratings