The following was presented to the Board by Ashley and myself on 2017-02-13 during the public Board Meeting.
Ashley and I have had a chance to review some of our membership's top goals for this year-- and today, we'd like to discuss our first joint effort.
We know some of you are excited for us to introduce you to the unique dynamic that has made the Node.js project so successful-- so, we'd like to start with what we believe is one of the biggest tenants to that success: our Contribution Policy.
While we grant complete autonomy to our groups so they can choose any policy they desire- the unanimous choice across them is to:
publicly offer PRs
allow sufficient time for iteration and feedback
commit when consensus has been reached.
Our Membership expects us to participate in our Individual Member roles under the same standards to which the community holds itself. To that end, we are pledging our commitment to follow our community's Contribution Policy.
Starting today, we will be hosting and maintaining a new Board repository under the Node.js GitHub organization. We will post board related topics for community review, feedback and iteration. Once matured to a satisfactory state, by community standards, we will pursue approval here- with the Board. Any of you, of course, are encouraged to visit, review, and even participate.
We, the Board, currently have a few initiatives underway that have not met this standard-- so unfortunately, Ashley and I, cannot commit affirmative votes at this time. We apologize for any delays this causes. We are excited and look forward to assisting you in swiftly ushering them through the process over the next few weeks and months-- so they are ready for our future meetings without delay.
At this point, we're certain you are concerned about some private issues that are inappropriate to make public. We, of course, acknowledge and understand these exceptions. Fortunately, our community also has procedures for similar scenarios.
Our Security group regularly needs to discuss vulnerabilities and find resolution in private. They issue generalized statements to the community without providing sensitive information.
Our Moderation group discusses controversial or concerning events in a semi-private repository that is available to members that have made significant and valuable contributions to the project.
Using these, and other, existing examples-- we can operate within our Community's expectations and avoid any friction that can slow progress. If you get a chance, we encourage you to review the CONTRIBUTING.md base policy that is in the TSC repo.
The following was presented to the Board by Ashley and myself on 2017-02-13 during the public Board Meeting.