You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
We need to create and make public a process for adding new members #11
Like all working groups, this working group needs to publish specific processes and guidelines for admitting new members.
So far, we do not have anything in place, and people have been added in a very ad-hoc manner. We've also told people they can't join yet for various reasons. These reasons may be valid, but it's still a problem that this wasn't done through any sort of well structured, transparent process.
For reference, policies across working groups are pretty divergent around this. Here's a few:
Core
Liberal contribution agreement leads to onboarding new "committers" with a CTC that handles disputes
Website
Liberal contribution agreement leads to commit bit and addition to WG, no on-boarding. Most contributions land, disputes handled by the whole WG.
"Admin" group is elected subset of the working group. Can land stuff without review.
HTTP, Streams, and a few others:
Anyone who asks is added to the WG
Most i18n groups
Initially anyone who asks is added. Once established people are added to WG after initial contribution or participation in reviews.
The most interesting have been the website and i18n. The 18n groups just organically grew and adopted policies but they are all relatively similar from what I can tell. The website is optimized for getting contributions in quickly without ever having meetings.
@sup there may not need to be a "CTC" in this context. What I was trying to do was just give an overview of the range of structures people have put in place to bring people into different groups related to the work they are doing.
The problem we have here is that working groups tend to tailor their admission process based on the work they are doing. Since this group is still figuring out it's scope of work and the things it needs from contributors it will have a difficult time defining this. As you can see, most WGs simply leave admission almost entirely open in their early phases while they figure that out.
@sup oh, haha. CTC == "Core Technical Committee." They are the people who make final decisions around node core code and policies when they are controversial (meaning that anyone objects to the change being made). Most changes to core are un-controversial an land after they are reviewed but a small portion need the CTC to make a final decision.
Like all working groups, this working group needs to publish specific processes and guidelines for admitting new members.
So far, we do not have anything in place, and people have been added in a very ad-hoc manner. We've also told people they can't join yet for various reasons. These reasons may be valid, but it's still a problem that this wasn't done through any sort of well structured, transparent process.
We need to fix this, and soon IMO.