-
Notifications
You must be signed in to change notification settings - Fork 134
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
[Discussion] What is the TSC's role? #75
Comments
Update: This will largely (if not fully) answered via #77 |
Closing due to lack of participation. |
My timeline of issues on this... 2015-10-06 #3 "Core Project definition" by @Trott 2015-11-02 BOD meeting:
2016-01-21 #35 "Increasing the scope of the TSC and Incubator" by @mikeal 2016-03-02 #54 "Can we effectively define a "project"" by @mikeal 2016-03-03 #58 "Splitting mentorship from long term project hosting" by @mikeal 2016-03-07 #59 "Flatten project, scope TSC, big changes to structure" by @mikeal 2016-03-23 #59 Closed and topic handed over to @rvagg 2016-03-24 #77 "Proposed Node.js Foundation Mission, Structure and Strategy" by @rvagg 2016-03-31 #84 "Define "Node.js core"" by @rvagg 2016-06-20 #113 "Define "Node.js core" - Mark II" by @mhdawson 2016-07-05 #116 "Add PR for TSC scope" by @mhdawson |
#59 (now closed without action) consumed the a large portion of the past 3-4 meetings of the TSC and the CTC. There is a question that has been raised: "What is the TSC's role?" ref1 ref2
The README.md actually offers many points on this:
The Charter outlines the Responsibilities of the TSC which lists some specifics, but broadly defines "all technical development within the Node.js Foundation".
To me, an outsider, this looks pretty cut-and-dry... so, what role(s) are in question?
Additionally, @Fishrock123 expressed that he believes "the TSC is probably mis-named at this point." Ignoring the difficulties in changing the name... what name MIGHT better describe the Committee?
All of this is important to helping "bring outsiders along on the same journey" as @rvagg said.
BTW, I want to commend the TSC for it's candor in all of this.
The text was updated successfully, but these errors were encountered: