Temurin-build: TSC (Technical Steering Committee)

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