Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

Define Working Group expectations and create boilerplate #201

Closed
7 tasks
dshaw opened this issue Dec 28, 2017 · 3 comments
Closed
7 tasks

Define Working Group expectations and create boilerplate #201

dshaw opened this issue Dec 28, 2017 · 3 comments

Comments

@dshaw
Copy link
Contributor

dshaw commented Dec 28, 2017

Attempting to integrate the TSC WORKING_GROUP.md doc, revealed some gaps between what we assert as CommComm contributions and how this is defined today for the Node.js project.

At the 2017-12-28 CommComm Meeting we identified the current boilerplate as a blocker for landing #194. This issue captures the intent to remove the Working Group bootstrap governance in the PR and collaborate here to create new definition in line with CommComm governance and contribution expectations.

CommComm Bootstrap Governance items to ratify or define:

  • Define Working Group scope and authority
  • Collaborators
  • WG Membership
  • WG Meetings
  • Consensus Seeking Process
  • Developer's Certificate of Origin 1.1
  • Code of Conduct
@bnb
Copy link
Contributor

bnb commented Mar 12, 2018

@dshaw have there been any updates on this?

@bnb
Copy link
Contributor

bnb commented Mar 22, 2018

I'd like to add this to the agenda, it's come up a few times in the past two weeks.

@bnb
Copy link
Contributor

bnb commented Sep 5, 2018

Going to close this and re-open a new issue with a bit more focus (given the current state of things) and that can be labeled as "Good First Issue" for someone new to the project.

@bnb bnb closed this as completed Sep 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants