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
One of the things the TSC has struggled with is to try and define the scope of what projects could fit under the TSC.
Simultaneously, the TSC created a mentorship program (the incubator) and has extended those mentorship resources to critical projects in need.
Another aspect of this mentorship has been a neutral home (the Node.js Foundation) which helps when building up a contribution base around the project.
However, the long term implications of hosting graduated projects are outside of what I believe the TSC is comfortable maintaining, based on the last meeting.
I'd like to use this issue to discuss any concerns with splitting the long term hosting of graduated projects from the TSC. There are several options for where to host these assets and any long term governance concerns we might have can be structured into where and how they are hosted. It also almost goes without saying that whatever this home might be it would need to be part of a neutral foundation with assurances that the project is autonomous and governed by its contributors.
As a side benefit, this could get us out of the problem we've struggled with regarding "picking winners." We can extend mentorship to projects the Node.js ecosystem depends on without hosting them forever in "The Node.js TSC" which has an implicit endorsement.
The text was updated successfully, but these errors were encountered:
One of the things the TSC has struggled with is to try and define the scope of what projects could fit under the TSC.
Simultaneously, the TSC created a mentorship program (the incubator) and has extended those mentorship resources to critical projects in need.
Another aspect of this mentorship has been a neutral home (the Node.js Foundation) which helps when building up a contribution base around the project.
However, the long term implications of hosting graduated projects are outside of what I believe the TSC is comfortable maintaining, based on the last meeting.
I'd like to use this issue to discuss any concerns with splitting the long term hosting of graduated projects from the TSC. There are several options for where to host these assets and any long term governance concerns we might have can be structured into where and how they are hosted. It also almost goes without saying that whatever this home might be it would need to be part of a neutral foundation with assurances that the project is autonomous and governed by its contributors.
As a side benefit, this could get us out of the problem we've struggled with regarding "picking winners." We can extend mentorship to projects the Node.js ecosystem depends on without hosting them forever in "The Node.js TSC" which has an implicit endorsement.
The text was updated successfully, but these errors were encountered: