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

TSC (Technical Steering Committee) #119

Closed
gdams opened this issue Jun 12, 2017 · 4 comments
Closed

TSC (Technical Steering Committee) #119

gdams opened this issue Jun 12, 2017 · 4 comments
Labels
help wanted Issues that need an extra hand helping out with them important High priority issues that are not buildbreakers but may still require more attention than others
Milestone

Comments

@gdams
Copy link
Member

gdams commented Jun 12, 2017

myself and @karianna have started discussion about some form of committee to ensure that AdoptOpenJDK is driven forwards in a way that most suits the org. Node.js have a TSC which is in charge of this and you can read about that here.

To me there are a few key things to be considered when creating a committee such as the TSC.

Membership

How many members?

So I think that for now we should have a small handful of members, perhaps 6?

How do people join?

To start the ball rolling I think that we should create an issue where we can nominate members and we can then have an anonymous poll for people to vote. Once the TSC is setup, members should be able to nominate other org members for consideration in the monthly meetings.

Are there restrictions?

To avoid giving one company too much power, I think the first rule should be that only 1/3 of members can be from one company.

Governance

What does being a TSC member mean?

I feel that the TSC members should have monthly meetings to discuss progress. They should represent a wide spectrum of skills used in the AdoptOpenJDK org. They should be in charge of deciding the the direction in which the AdoptOpenJDK org grows. They should handle the admin side of the GitHub org (creating/deleting repos, adding/blocking users etc).

What I want to make clear is that this wouldn't be an "exclusive" club. All meetings should be published to the rest of the org so that members can follow progress. The aim of the TSC is to represent the org so the members should be approachable and open to accepting ideas from the wider community

@gdams gdams added help wanted Issues that need an extra hand helping out with them important High priority issues that are not buildbreakers but may still require more attention than others labels Jun 12, 2017
@karianna
Copy link
Contributor

The meetings would also be completely open to the public / community.

@karianna karianna added this to the 1.x.x milestone Jun 12, 2017
@gibfahn
Copy link

gibfahn commented Jun 12, 2017

The meetings would also be completely open to the public / community.

In Node we tend to find that too many people on the call breaks the web conferencing tool you use (Hangouts/Cisco/whatever), so we live-stream the meetings on youtube, and allow people to post questions on the meeting issue or in IRC. We upload them afterwards as well obviously.

@karianna karianna added this to Backlog in temurin-build Jun 13, 2017
@sxa
Copy link
Member

sxa commented Mar 18, 2018

@karianna @gdams Any reason to keep this open now that we've got AdoptOpenJDK/TSC#9 to track progress on the TSC project?

@gdams
Copy link
Member Author

gdams commented Mar 18, 2018

closing

@gdams gdams closed this as completed Mar 18, 2018
@karianna karianna moved this from Backlog to Done in temurin-build Mar 18, 2018
@karianna karianna modified the milestones: 1.x.x, 1.0.0 May 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Issues that need an extra hand helping out with them important High priority issues that are not buildbreakers but may still require more attention than others
Projects
No open projects
temurin-build
  
Done
Development

No branches or pull requests

4 participants