Thanks Beinan for submitting this nomination, and thanks to everyone on the TSC for considering and voting on this nomination.  I’m pleased to report that Chunxu has received a majority of the votes from the TSC and is now a committer.  Congratulations Chunxu!  And thanks for your contributions.

Tim

+1
Chunxu’s contribution is substantial and I support him becoming a committer.

thanks,
Ying

The next Presto TSC meeting will be next week, September 13^th at 9am Pacific/12pm Eastern time (one week later than is customary).

TSC meetings are open to the entire technical community, and are meant to be a forum to discuss technical direction, community concerns, and bring up new ideas.

If you’d like to bring up a topic for the TSC, please send a PR to the agenda here: https://github.com/prestodb/tsc/blob/master/meetings/2022-09-13.md

Tim

The next Presto TSC meeting will be next week, August 2^nd at 9am Pacific/12pm Eastern time.

TSC meetings are open to the entire technical community, and are meant to be a forum to discuss technical direction, community concerns, and bring up new ideas.

Next meeting we’ll be talking about the Presto Router, a load balancing component that sits in front of multiple Presto clusters to scale out and provide a unified interface.  If you’d like to bring up a topic for the TSC, please send a PR to the agenda here: https://github.com/prestodb/tsc/blob/master/meetings/2022-08-02.md

Tim

The next Presto TSC meeting will be next week, July 5th^th at 9am Pacific/12pm Eastern time.

TSC meetings are open to the entire technical community, and are meant to be a forum to discuss technical direction, community concerns, and bring up new ideas.

There are no open agenda items for this next meeting yet.  If you’d like to bring up a topic for the TSC, please send a PR to the agenda here: https://github.com/prestodb/tsc/blob/master/meetings/2022-07-05.md

Tim

The next Presto TSC meeting will be next week, June 7th^th at 9am Pacific/12pm Eastern time.

TSC meetings are open to the entire technical community, and are meant to be a forum to discuss technical direction, community concerns, and bring up new ideas.

At the next session, we’ll give an update on the Presto Conformance Program, and also review a design for a history-based optimizer.

If you’d like to bring up a topic for the TSC, please send a PR to the agenda here: https://github.com/prestodb/tsc/blob/master/meetings/2022-06-07.md

Tim

+1

Hi Presto TSC members,

I would like to nominate Nikhil Collooru (github ID: NikhilCollooru) as a Presto committer. Nikhil has been contributing to Presto for close to 3 years now. He worked in different areas and contributed to multiple modules. He has good knowledge in code related to metastore, file listing, split generation, split scheduling, hive writer, task lifecycle, etc. He actively reviews PRs and provide quality feedback.

Here are some detailed stats on his contribution:

- 98 commits

- 64k lines of addition, 52k lines of removal

- 69 PR reviews, 199 review comments

Some of his major contributions (in chronological order):

- Refactored and modularized presto-orc into an independent module

- Introduced versioned metastore partition caching

- Added support for reading manifest and avoid listFiles call in coordinator

- Improved SOFT_AFFINITY strategy to be more resilient to node downtime

- Added support for returning partial results

- Reduced the number of HdfsConfiguration copies and thereby reduce the coordinator CPU utilization

Please reply to this email to vote.

Thanks

James

Hi Presto TSC members,

I would like to nominate Nikhil Collooru (github ID: NikhilCollooru) as a Presto committer. Nikhil has been contributing to Presto for close to 3 years now. He worked in different areas and contributed to multiple modules. He has good knowledge in code related to metastore, file listing, split generation, split scheduling, hive writer, task lifecycle, etc. He actively reviews PRs and provide quality feedback.

Here are some detailed stats on his contribution:

- 98 commits

- 64k lines of addition, 52k lines of removal

- 69 PR reviews, 199 review comments

Some of his major contributions (in chronological order):

- Refactored and modularized presto-orc into an independent module

- Introduced versioned metastore partition caching

- Added support for reading manifest and avoid listFiles call in coordinator

- Improved SOFT_AFFINITY strategy to be more resilient to node downtime

- Added support for returning partial results

- Reduced the number of HdfsConfiguration copies and thereby reduce the coordinator CPU utilization

Please reply to this email to vote.

Thanks

James

Hi,

This is regarding the commit https://github.com/prestodb/presto/pull/17706.

As it is commented on the PR, this is being reverted as  it is breaking a connector.

Could we please know which connector was it breaking and will this revert be merged to mainline too?

Thanks,

Ankush.

 The next Presto TSC meeting will be next week, April 12^th at 9am Pacific/12pm Eastern time.

TSC meetings are open to the entire technical community, and are meant to be a forum to discuss technical direction, community concerns, and bring up new ideas.

If you’d like to bring up a topic for the TSC, please send a PR to the agenda here: https://github.com/prestodb/tsc/blob/master/meetings/2022-04-12.md

Tim

Hey folks, there were no agenda items today, so cancelling today’s meeting.  See you next month.

Tim

 The next Presto TSC meeting will be next week, Mar 8^nd at 9am Pacific/12pm Eastern time.

TSC meetings are open to the entire technical community, and are meant to be a forum to discuss technical direction, community concerns, and bring up new ideas.

If you’d like to bring up a topic for the TSC, please send a PR to the agenda here: https://github.com/prestodb/tsc/blob/master/meetings/2022-03-08.md

Tim

 The next Presto TSC meeting will be next week, Mar 8^nd at 9am Pacific/12pm Eastern time.

TSC meetings are open to the entire technical community, and are meant to be a forum to discuss technical direction, community concerns, and bring up new ideas.

If you’d like to bring up a topic for the TSC, please send a PR to the agenda here: https://github.com/prestodb/tsc/blob/master/meetings/2022-03-08.md

Tim

Hello all,

The election has concluded, and the new TSC consists of:

• Bin Fan
• James Sun
• Rebecca Schlussel
• Rongrong Zhong
• Tim Meehan
• Ying Su
• Zhenxiao Luo

Thanks everyone for submitting your nominations and participating in this election.

For this initial class, some term limits last until November of next year, and some extend until May of the following year.  We’ll determine who belongs to which term by random coin toss at our next TSC meeting, after which it will be added to the charter.

Thank you

Tim

Hello all,

Tl;dr: we’re now accepting nominations for the next TSC class.  Please see the TSC README to see instructions on how you can submit a nomination to the TSC.

To begin with, I wanted to make an announcement that tsc#68 has been merged.  Just to summarize, the main changes to the TSC were:

1. Most votes become lazy consensus votes.
2. New committers now are voted in by TSC members, not the broad set of committers.
3. TSC members now have term limits, with elections occurring every half year for roughly half the TSC.
4. The new TSC group will consist of a smaller pool of individuals (7, rather than the current group of 15).

The idea behind these changes were to reduce friction points from participation among committers and TSC members, namely: removing the high burden of voting required to vote in new committers, allowing for lazy consensus for most votes, and reducing the TSC size to make it a smaller, focused and more agile group.

With these changes being accepted and merged, the time has now come to vote in our next set of TSC members.

The process will work as follows:

1. Today, we start accepting nominations for TSC membership.  By current rules, TSC members must be committers.  The instructions are found on the README for the TSC, and have also been linked on the README for the main project.
2. Nominations close on Thursday, November 4^th, after which we’ll begin the process of voting via OpaVote.
3. Voting closes on Thursday, November 11^th, at which point we’ll have our new TSC class.

For details, please see the README above, and the TSC charter.

I’m looking forward for the upcoming TSC to help guide the technical project.

Tim

Hello all,

Tl;dr: we’re now accepting nominations for the next TSC class.  Please see the TSC README to see instructions on how you can submit a nomination to the TSC.

To begin with, I wanted to make an announcement that tsc#68 has been merged.  Just to summarize, the main changes to the TSC were:

1. Most votes become lazy consensus votes.
2. New committers now are voted in by TSC members, not the broad set of committers.
3. TSC members now have term limits, with elections occurring every half year for roughly half the TSC.
4. The new TSC group will consist of a smaller pool of individuals (7, rather than the current group of 15).

The idea behind these changes were to reduce friction points from participation among committers and TSC members, namely: removing the high burden of voting required to vote in new committers, allowing for lazy consensus for most votes, and reducing the TSC size to make it a smaller, focused and more agile group.

With these changes being accepted and merged, the time has now come to vote in our next set of TSC members.

The process will work as follows:

1. Today, we start accepting nominations for TSC membership.  By current rules, TSC members must be committers.  The instructions are found on the README for the TSC, and have also been linked on the README for the main project.
2. Nominations close on Thursday, November 4^th, after which we’ll begin the process of voting via OpaVote.
3. Voting closes on Thursday, November 11^th, at which point we’ll have our new TSC class.

For details, please see the README above, and the TSC charter.

I’m looking forward for the upcoming TSC to help guide the technical project.

Tim