Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Umbrella Program #2

Merged
merged 15 commits into from
Oct 19, 2015
Merged
Prev Previous commit
Next Next commit
Numerous edits based on feedback.
mikeal committed Oct 6, 2015
commit e0b2b53750483d0ce0e14460af978d6df29cb5ab
21 changes: 11 additions & 10 deletions Applications/Core TLP.md
Original file line number Diff line number Diff line change
@@ -4,7 +4,7 @@ Currently the Node.js Foundation directly oversees the development of the core p

## History & Metrics

Created by Ryan Dahl, now the largest programming ecosystem on the planet.
Created by Ryan Dahl, now the largest programming ecosystem in the world.

## Scope

@@ -18,14 +18,15 @@ The Core TLP will have sole responsibility and discretion over the node.js proje
* Maintaining the list of additional Collaborators.
* Development process and any coding standards.
* Mediating technical conflicts between Collaborators and Working Groups.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is why we have collaboration WG, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

* Node.js build and CI infrastructure.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Some list items end with periods and some don't. Doesn't really matter either way but should probably be consistent.


## Governance

https://github.com/nodejs/io.js/blob/master/GOVERNANCE.md
https://github.com/nodejs/node/blob/master/GOVERNANCE.md

## Contributions

https://github.com/nodejs/io.js/blob/master/CONTRIBUTING.md
https://github.com/nodejs/node/blob/master/CONTRIBUTING.md

## Tools

@@ -57,13 +58,13 @@ All relevant IP is already managed by the Node.js Foundation.

## Working Groups

* [Website](https://github.com/nodejs/io.js/blob/master/WORKING_GROUPS.md#website)
* [Streams](https://github.com/nodejs/io.js/blob/master/WORKING_GROUPS.md#streams)
* [Build](https://github.com/nodejs/io.js/blob/master/WORKING_GROUPS.md#build)
* [Tracing](https://github.com/nodejs/io.js/blob/master/WORKING_GROUPS.md#tracing)
* [Roadmap](https://github.com/nodejs/io.js/blob/master/WORKING_GROUPS.md#roadmap)
* [Docker](https://github.com/nodejs/io.js/blob/master/WORKING_GROUPS.md#docker)
* [Addon API](https://github.com/nodejs/io.js/blob/master/WORKING_GROUPS.md#addon-api)
* [Website](https://github.com/nodejs/node/blob/master/WORKING_GROUPS.md#website)
* [Streams](https://github.com/nodejs/node/blob/master/WORKING_GROUPS.md#streams)
* [Build](https://github.com/nodejs/node/blob/master/WORKING_GROUPS.md#build)
* [Tracing](https://github.com/nodejs/node/blob/master/WORKING_GROUPS.md#tracing)
* [Roadmap](https://github.com/nodejs/node/blob/master/WORKING_GROUPS.md#roadmap)
* [Docker](https://github.com/nodejs/node/blob/master/WORKING_GROUPS.md#docker)
* [Addon API](https://github.com/nodejs/node/blob/master/WORKING_GROUPS.md#addon-api)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Intl is missing, but it's missing from the WORKING_GROUPS.md document. Oops.
  • i18n groups (named or unrenamed) aren't included.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i18n groups are much wider than core so the plan is to keep them as a top level WG. This makes it a bit easier to engage with them about localization and other opportunities related to other TLPs.

## Provisional

10 changes: 5 additions & 5 deletions Project Lifecycle.md
Original file line number Diff line number Diff line change
@@ -33,7 +33,7 @@ While certain processes are strongly recommended because of the TSC's experience

* TC is 5 members or greater.
* No more than 1/4 of the TC is affiliated with the same employer.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may need an easing in of this like we did with the io.js TC. Perhaps 1/3rd until the TC is 8, at which point it becomes 1/4?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the scale for leaving incubation. When entering incubation it's expected that the project is not in-line with this. Do we want to alter this as a consideration for leaving incubation?

* Members of the TC live in at least 4 different timezones.
* Members of the TC live in at least 4 different timezones and representing no fewer than three countries.
* The decision making and release process is documented and publicly accessible.

A project may apply to graduate from incubation at any time by calling for a vote in the TSC.
@@ -77,18 +77,18 @@ A proposal to join the Node.js Foundation as a Top Level Project or Working Grou
* List of initial TC members.
* List of initial Working Groups.
* Prior to being admitted the project:
* Must include [DCO](https://github.com/nodejs/io.js/blob/master/CONTRIBUTING.md#developers-certificate-of-origin-10).
* Must include [DCO](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#developers-certificate-of-origin-10).
* Must include approved license (MIT, Apache2, etc).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

vague, do we need the foundation legal committee to come up with a list? perhaps we can enumerate the basic ones and say "licenses beyond this list must be approved by the TSC" (or foundation legal committee?)

* Must include a [Code of Conduct](https://github.com/nodejs/io.js/blob/master/CONTRIBUTING.md#code-of-conduct).
* Must include a [Code of Conduct](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md#code-of-conduct).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think all existing projects have a CoC so it's arguably something of a double standard to require new projects to have one. That maybe applies to the DCO as well, not sure.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In what context do you mean “all existing projects?”

Do you mean all within the foundation or all projects that we’d consider for the incubator?

The intention here is to require that they add it before being admitted, pretty much exactly the same expectation we have with the DCO.

-Mikeal

On Oct 14, 2015, at 1:55PM, Ben Noordhuis [email protected] wrote:

all existing projects

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Existing foundation projects, like nan and node-gyp. Neither has a CoC or DCO as far as I'm aware.

EDIT: Correction: nan has a DCO.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PRs sent to nan and node-gyp. We need to be more careful about this in the future.

On Oct 14, 2015, at 2:06PM, Ben Noordhuis [email protected] wrote:

In Project Lifecycle.md #2 (comment):

+A proposal to join the Node.js Foundation as a Top Level Project or Working Group must include:
+
+* Introduction and project description.
+* Project history.
+* Any available metrics or even estimates about the user base, ecosystem and community.
+* Project scope.
+* Current governance process.
+* Current contribution process.
+* List of current tools in use by the project (forums, issue trackers, GitHub orgs, etc).
+* Existing IP Policy and relevant intellectual property (trademarks, domain names, etc).
+* List of initial TC members.
+* List of initial Working Groups.
+* Prior to being admitted the project:

  • * Must include DCO.
  • * Must include approved license (MIT, Apache2, etc).
  • * Must include a Code of Conduct.
    Existing foundation projects, like nan and node-gyp. Neither has a CoC or a DCO as far as I'm aware.


Reply to this email directly or view it on GitHub https://github.com/nodejs/TSC/pull/2/files#r42053137.


Each proposal should be sent as a pull request to this repository in the Applications directory. Proposals do not have to be complete to be submitted, the TSC can work with the authors and their respective communities in each Pull Request.

### Approved Licenses

At this time the foundation is only accepting projects which use an MIT, BSD, or Apache2 license.
At this time the foundation is only accepting projects which use an MIT, BSD, ISC or Apache2 license.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

derp, just saw this, above mention of approved license should say "see below" instead of enumerating a partial list.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also, which BSD License? there's a whole family of them ..


### Admittance

The Node.js Foundation is quite new and currently has a limited number of resources available to mentor new projects. As such, projects are chosen for admission in groups as mentors become available. The next set of projects will be chosen on November 1st.
The Node.js Foundation is quite new and currently has a limited number of resources available to mentor new projects. As such, projects are chosen for admission in groups as mentors become available.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"has limited resources"


You can apply at any time and the TSC and available mentors will help improve your application while awaiting the next available approval phase.