Umbrella Program #2
Conversation
|
@nodejs/tsc |
| * Contribution process and practices. | ||
| * Maintaining the list of additional Collaborators. | ||
| * Development process and any coding standards. | ||
| * Mediating technical conflicts between Collaborators and Working Groups. |
There was a problem hiding this comment.
This is why we have collaboration WG, right?
There was a problem hiding this comment.
the collaboration wg is there to share knowledge about how to best collaborate and to build tools that help us do so, the TC or WG responsible for each repo is ultimately the arbiter of conflicts. this line delegates that responsibility from the TSC (where it current resides because of the TSC Charter passed by the foundation's board of directors) to the Core TLD for the "node.js" project.
|
|
||
| ## History & Metrics | ||
|
|
||
| Created by Ryan Dahl, now the largest programming ecosystem on the planet. |
There was a problem hiding this comment.
What is this section for? Feels a little incongruous.
There was a problem hiding this comment.
It was a placeholder and hasn't been updated because we all know what node.js core is ;)
|
@mikeal This doesn't need to mention how the tsc is governed because we have to adopt how it already is because of how the foundation as chartered, correct? |
|
@Fishrock123 correct, the TSC Charter was already passed by the board and establishes the TSC and its governance. If this is passed by the TSC the authority over Core will be moved, by the TSC, from the TSC directly to the Core TLP, leaving the rest of the "technical side" of the foundation with the TSC. As such, this document describes the process by which TLPs get accepted and run under the TSC. |
|
This looks fine overall. I'm a bit wary about attempting to solve too many problems before they're actually problems but in general this appears solid. Let's just make sure we leave it open for iteration once we start actually onboarding other projects. |
|
Overall looks good to me but you probably have to update the list of TC members due to the recent changes |
|
|
||
| ### Security | ||
|
|
||
| All projects in the foundation share the same base security policy. The foundation's security team triages issues sent to security@nodejs.org. Top Level Projects, whether in the incubator or not, are expected to maintain a private security repository where the security team can bring project specific issues. |
There was a problem hiding this comment.
style: inconsistent word wrap. also, other places.
|
Please, no spaces in file names. |
| @@ -0,0 +1,69 @@ | |||
| ## Introduction | |||
|
|
|||
| Currently the Node.js Foundation directly oversees the development of the core platform and associated working groups. The addition of Top Level Projects will predictably increase the workload on the TSC and so it makes sense to transfer these responsibilities to a Top Level Project concerned solely with the development of the platform. | |||
There was a problem hiding this comment.
This line is going to become redundant as soon as this is adopted. Perhaps this belongs under "History" or "Context" or something
|
"Top Level" should become "Top-level" (note the unfortunate lower-casing of the |
|
Ok, tons of fixes are in. Pretty sure I handled all the current complaints but let me know if I missed any. |
| * **Shigeki Ohtsu** <ohtsu@iij.ad.jp> ([@shigeki](https://github.com/shigeki)) | ||
| * **Brian White** <mscdex@mscdex.net> ([@mscdex](https://github.com/mscdex)) | ||
|
|
||
| ## Working Groups |
There was a problem hiding this comment.
Should this say "Core working groups" and link to WORKING_GROUPS.md for 'the rest' ?
There was a problem hiding this comment.
That's only the chartered WGs, there's a ton of un-chartered ones as well.
|
|
||
| ## Top Level Project and Working Group Requirements | ||
|
|
||
| All TLPs and WGs are expected to operate in a transparent manor. Decisions must be made publicly through a documented public process managed by each TLP TC or WG. |
There was a problem hiding this comment.
In a glass house? Or did you mean 'manner'?
| * Working Groups | ||
| * Mentors | ||
| * Top Level Projects | ||
| * Core TLP |
There was a problem hiding this comment.
Indent error? Or are "Mentors" and "Core TLP" subcategories?
There was a problem hiding this comment.
The “Core TLP” is pretty much the whole “project” as it stands today, so it is its own category and will have its own WGs. I’m sending a small change to make that clearer.
On Oct 14, 2015, at 1:57PM, Ben Noordhuis notifications@github.com wrote:
In README.md #2 (comment):
+If your project is interested in joining the Node.js Foundation please read the [Project Lifecyle.md](./Project Lifecycle.md) documentation.
+
+## TSC Members
+
+## Top Level WG and TLPs
+
+* Working Groups
- * Mentors
+* Top Level Projects- * Core TLP
Indent error? Or is "Core TLP" a subcategory?—
Reply to this email directly or view it on GitHub https://github.com/nodejs/TSC/pull/2/files#r42051998.
|
TSC Voted in favor of this in nodejs/node#2795 |
This is the living document for the foundation's umbrella program for multiple top level projects.
Please review and provide feedback.