The charter specifies a CONTRIBUTORS file that the TOC

In the original PR which updated TSC policies and procedures, we had an open discussion on TSC membership criteria. The topic was "Should TSC members be required to be Presto committers?"

There were discussions on this in one of the TSC calls, and also on PR #28.

Let's continue the discussion here, and then roll changes into the new version once we have consensus.

cc/ @zhenxiao

https://github.com/prestodb/presto/wiki/How-to-become-a-Presto-committer%3F

The purpose of this issue is to allow Nominees from Issue #97 to publicly accept their nomination and complete the required information. This supplementary nomination period will remain open through 1/16/2023 @ 12:00am EST and will be followed by a week of voting conducted using OpaVote.

Please see timeline below for exact dates and times.
Nomination Period Extension: 1/11/2023-1/16/2023 @ 12:00am EST
Voting Period: 1/16/2023- 1/23/2023 @ 12:00am EST
Winner Announced: 1/23/2023 @ 12:00pm EST

Nomination statements:
Beinan Wang (@beinan)
James Sun (@highker)
Aditi Pandit (@aditi-pandit)

If anyone has any questions or concerns please let me know.

We need to move off of the FB code of conduct

TSC Nomination Period is Open

Individuals interested in running for these positions or individuals interested in nominating others must record the nominations by sending an email to [email protected]. Please note that any committer may be eligible for nomination, but voting is done by TSC members.

If you are nominating someone other than yourself, please confirm their interest privately BEFORE you nominate them publicly.

Please include in the nomination:

TSC Voting Member Self-nomination template

*Please copy and paste the template below the line and submit your self-nomination to the TSC chair and [email protected].

At the end of the self-nomination period, all submissions will be compiled into a single public document.*

Your name

TSC self-nomination

GitHub username:

Email:

Please provide 2-3 sentences on your involvement in the Presto project

Please provide 3-6 sentences on what you aspire to achieve on the TSC

Do you currently hold any formal leadership roles within the Presto community?

Do you commit to attending the monthly TSC calls?

Project attendance and participation

Please provide a list of your attendance to official Presto meetings, discussions in the Slack workspace, and other community events

Please provide a list of outreach efforts you have made on behalf of the Presto project

Please provide a list of examples of public designs, issues, or RFCs you have contributed to (review, author, or otherwise)

Voting will begin April 25th and will be conducted using google forms.

Important Dates:
April 19 Start call for nominations by submitting an issue here.
April 24 May 3 End nomination period, 11:59 pm Eastern Time
April 25 May 6 Send slate of respective nominees to all TSC members for voting.
April 29 May 10 Voting period ends, 11:59 pm Eastern Time
April 30 May 13 Election winners announced to all members
May 1 May 14 Newly elected representatives begin term

@nezihyigitbasi has been volunteered.

Another discussion item from the policies and procedures update: How frequently should TSC members be elected, and how long should their terms be? The goal is to have staggered elections, so that there is continuity.

The original proposal was to have 2 year terms, with half the TSC up for election every calendar year. @zhenxiao proposed 1/3 TSC up for election to ensure greater continuity.

Let's reach consensus on the length of a TSC term, and work backwards from there.

TSC Nomination Period is Open

The Presto Foundation has 4 TSC member roles that have expired as of November 1, 2022. Individuals interested in running for these position or individuals interested to nominate others must record the nominations under this GitHub issue. Please note that any committer may be eligible for nomination, but voting is done by TSC members who are not up for election.

Please include:

• GitHub username:
• Email:
• Please provide 2-3 sentences on your involvement in the Presto project
• Please provide 3-6 sentences on what you aspire to achieve on the TSC
• Do you currently hold any formal leadership roles within the Presto community?
• Do you commit to attending the monthly TSC calls?

If you are nominating someone other than yourself, please confirm their interest privately BEFORE you nominate them publicly. It is also required that individuals nominated by others accept their nominations directly under this GitHub issue.

Voting will begin January 3rd if needed and will be conducted using google forms.

Election Timeline:
December 14, 2022, 11:45am EST: Start of nomination period
January 9, 2022, 11:45pm EST: End of nomination period
January 10, 2022, 11:45pm EST: Start of voting period
January 17, 2023 11:45pm EST: End of voting period
January 18, 2023 8:00am EST results announced
Term: January 18, 2023 - January 15, 2024 (edited)

We received an email a few days ago that the GSoC application period for open source projects will be Feb 7 - Feb 21.

If this is something we want to participate in as the Presto Foundation, we'll need to assemble the following:

• A list of ideas
• Mentors matched to the ideas
• Answers to the short answer questions on the application

This year projects can be for 175 hours or 350 hours. This corresponds roughly to five or nine weeks, plus a three week bonding period between student acceptance and the beginning of the work.

I'd like to recommend the following process. Please add any ideas or indicate willingness to be a mentor in comments on this thread prior to February 7. If we have enough ideas (per Google, at least four) and paired mentors on February 7th to form a viable application, I will assemble the suggestions into an ideas page and submit the application prior to the program deadline.

Here are some reference documents regarding GSoC:

• Mentor guide
• How to define an ideas list
• What makes a good mentor?

Ideas

If you have a project idea, here's a template with the questions we'll need to answer on the application:

### Project title/description

### More detailed description of the project (2-5 sentences)

### Expected outcomes

### Skills required/preferred

### Possible mentors 

### Expected size of project (175 or 350 hour)

### Difficulty (easy, medium, hard)

Mentoring

If you're willing to be a lead mentor or co-mentor for an idea someone else proposed, please add a comment to this thread and link to the idea you'd like to help with.

If you do volunteer, please ensure you can provide whatever level of mentorship you've offered should the idea be funded. This is to ensure we can meet our commitments to the students and to the program.

If you have any questions, please ask!

Based on the discussion at the October Technical Steering Committee meeting, I am creating this issue to get feedback from community.

Clearly it is important that PrestoDB or any large software project evolves within a strategic architecture context that has been widely agreed upon, clearly articulated, and that informs day-to-day design and code decisions. This context often operationalizes as architecture blueprints and design guidelines that inform day-to-day engineering work.

The TSC architect role would ideally implement a community version of that strategic architecture function. It would be complementary to the committer role as it would help inform roadmap and design, focusing on cross-component and cross-release level concerns. It would also bring in state-of-the-art awareness, and awareness of other systems, thus complementing the day-to-day focus of committers. The two roles could perhaps intersect at the feature design level. The committers would continue to make the final decision as to what code ultimately gets merged. The TSC Architect role would have a vote only on design related decisions.

A key criteria for the TSE architect role would be a substantial track record of delivering distributed database/systems technology into production, a commitment to the success of the PrestoDB project, and a willingness to follow through and take ownership at the feature design level. Essentially those with scar tissue building other distributed systems and a passion for the success of PrestoDB and willingness to dive in at the design level and into code as well. Ideally, this role would already know the PrestoDB code inside and out but this is not the high order bit.

We are looking for feedback on this proposal.