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

[Discussion] What is the TSC's role? #75

Closed
williamkapke opened this issue Mar 23, 2016 · 3 comments
Closed

[Discussion] What is the TSC's role? #75

williamkapke opened this issue Mar 23, 2016 · 3 comments

Comments

@williamkapke
Copy link
Contributor

#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:

  1. The [TSC] is the technical governing body of the Node.js Foundation.
  2. It admits and oversees all top-level Projects in the Node.js Foundation.
  3. TSC members are responsible for top level technical community concerns.
  4. The TSC establishes the default governance, conduct, and licensing policies for all Top Level Projects.

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.

@williamkapke
Copy link
Contributor Author

Update: This will largely (if not fully) answered via #77

@williamkapke
Copy link
Contributor Author

Closing due to lack of participation.

@williamkapke
Copy link
Contributor Author

williamkapke commented Jul 20, 2016

My timeline of issues on this...

2015-10-06 #3 "Core Project definition" by @Trott

2015-11-02 BOD meeting:

Director Vagg updated the Board regarding the umbrella (project lifecycle), noting that
the TSC has created a core top-level project and that authority over core has been given
to that project.

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
› mentions "Node.js Core (managed by the CTC)"
› moved to #59 on March 9th

2016-03-03 #58 "Splitting mentorship from long term project hosting" by @mikeal
› moved to #59 on March 9th

2016-03-07 #59 "Flatten project, scope TSC, big changes to structure" by @mikeal
› Lots of discussion

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
› Proposal taken to Board and "they got spooked"
› Board wants a definition of "Node.js Core"

2016-03-31 #84 "Define "Node.js core"" by @rvagg
› Lists of projects/things emerges
› Discussed in 2016-04-07 meeting (#87)
› Discussed in 2016-04-21 meeting (#94)
› Discussed in 2016-05-05 meeting (#99)
› Discussed in 2016-06-16 meeting (#110)
› Discussed in 2016-06-30 meeting (#115)
› Discussed in 2016-07-14 meeting (#118)

2016-06-20 #113 "Define "Node.js core" - Mark II" by @mhdawson
› moved to PR #116 per discussion in 2016-06-30 meeting
› Discussed in 2016-07-14 meeting (#118)

2016-07-05 #116 "Add PR for TSC scope" by @mhdawson
› Discussed in 2016-07-14 meeting (#118)
@rvagg may trim down #77 to try to get a mission statement approved by The Board

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant