search

prestodb / tsc

Presto Foundation TSC
https://prestodb.io
Apache License 2.0
6 stars 33 forks source link

TSC Nomination Period is Open #97

Closed micmarti85 closed 1 year ago

micmarti85 commented 1 year ago

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:

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)

micmarti85 commented 1 year ago

@tdcmeehan Please take a look at this issue, this is my recommendation for running this election. Please let me know if you approve and I will tag the Presto TSC and share via email and slack.

tdcmeehan commented 1 year ago

One correction: I believe our rules state that any committer may be eligible for nomination, but voting is done by TSC members who are not up for election.

micmarti85 commented 1 year ago

One correction: I believe our rules state that any committer may be eligible for nomination, but voting is done by TSC members who are not up for election.

I made the correction, is it good to go?

tdcmeehan commented 1 year ago

LGTM!

tdcmeehan commented 1 year ago

Actually, usually we use Opa Vote to do the voting. Could we do it that way for consistency? @micmarti85

micmarti85 commented 1 year ago

Yes assuming there are more than 4 candidates we can absolutely use opavote🙂

On Thu, Dec 15, 2022 at 3:16 PM Timothy Meehan @.***> wrote:

Actually, usually we use Opa Vote to do the voting. Could we do it that way for consistency? @micmarti85 https://github.com/micmarti85

— Reply to this email directly, view it on GitHub https://github.com/prestodb/tsc/issues/97#issuecomment-1353657320, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2D3NRCAOZ567LLIZP2QMDWNN4DRANCNFSM6AAAAAAS64KTAM . You are receiving this because you were mentioned.Message ID: @.***>

--

MICHELLE MARTINEAU | PROGRAM MANAGER

@.*** https://www.linuxfoundation.org/ https://github.com/micmarti85 https://www.linkedin.com/in/michelle-martineau/

tdcmeehan commented 1 year ago

@micmarti85 could we leave the nomination period open a couple of extra days, since this falls around a holiday period and people may have sporadic availability?

micmarti85 commented 1 year ago

Yes absolutely

On Thu, Dec 22, 2022 at 3:22 AM Timothy Meehan @.***> wrote:

@micmarti85 https://github.com/micmarti85 could we leave the nomination period open a couple of extra days, since this falls around a holiday period and people may have sporadic availability?

— Reply to this email directly, view it on GitHub https://github.com/prestodb/tsc/issues/97#issuecomment-1362545803, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2D3NVZ4KECEH3DGHM4FVLWOQFVZANCNFSM6AAAAAAS64KTAM . You are receiving this because you were mentioned.Message ID: @.***>

--

MICHELLE MARTINEAU | PROGRAM MANAGER

@.*** https://www.linuxfoundation.org/ https://github.com/micmarti85 https://www.linkedin.com/in/michelle-martineau/

mbasmanova commented 1 year ago

I'd like to nominate Deepak Majeti from Ahana:

Here are Deepak's aspirations:

Data volumes continue to grow, however, adding more hardware to scale data processing frameworks started to show diminishing returns. Data centers are also hitting the power wall. There is now a huge demand for low-cost data processing frameworks on-prem and on the cloud.

Many modern data processing frameworks are now implementing native execution extensions to address the need mentioned above. For example, Spark has Photon, Sapphire, and Gluten. Presto must now evolve to these needs with the help of the Prestissimo project. Presto TSC is responsible for the overall technical oversight. It is essential that some members of the TSC understand Prestissimo very well and are part of its development.

It would be my honor to be part of the Presto TSC and help Presto effectively integrate with Prestissimo. Prestissimo needs to be a first-class citizen of Presto. However, Prestissimo along with Velox are complex C++ projects. The complex pieces to name a few include the build system, consistency with the Presto Worker Protocol, and bridging the gap between the Java Worker and the C++ Worker in terms of functionality and robustness. I believe my current contributions to Prestissimo and Velox, my previous experience at Vertica, and my contributions to Apache Arrow, Apache ORC, and Apache Parquet put me in an excellent position to assist with the above challenges.

Presto will become a more formidable industry-impacting project when it leverages Prestissimo and Velox effectively. I would love to be part of this journey by becoming a member of the Presto TSC.

majetideepak commented 1 year ago

@mbasmanova I am honored to have received your nomination. Thank you.

Below are the rest of my nomination details.

apc999 commented 1 year ago

Nominating Beinan Wang (@beinan) to be the TSC member for the next year

GitHub username: beinan

Email: beinan@alluxio.com

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

Beinan has contributed more than 60 commits

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

Does he currently hold any formal leadership roles within the Presto community?

Does he commit to attending the monthly TSC calls?

yingsu00 commented 1 year ago

Dear TSC committee, I'd like to nominate myself as the TSC member for the year 2023.

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

I have been working in Presto for 4 years and as a committer for 2 years. I know the Presto architecture well and am confident to bring the performance of it to a higher level, either in the Java engine or C++ native engine.

Core projects:

My Commit Stats:

Releasing, Performance Engineering, Tooling, etc.

Community work

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

As it has always been, I still hold the aspiration to make Presto + Velox a query engine with world leading performance and popularity, competitive with other top players like Databricks, Snowflake, etc. My primary goal is to deliver a top TPCDS score that is comparable to the latest best publication from Databricks. Making the world fastest Parquet reader, and preparing the performance tracking system are just a few beginning steps. I expect some real and extensive performance work in the coming year, including many tracking runs, in depth analyses, and many small and big improvements. I hope what I do can provide the TSC some insights, and also hope to get help from TSC to make this goal happen.

I will be continuing helping the community to grow and prosper. In addition to perfecting the community routine work, I will also try to grow more contributors by providing counsels and guidelines and initiating more projects.

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

Yes, TSC Member and Committer

Do you commit to attending the monthly TSC calls?

Yes

micmarti85 commented 1 year ago

@micmarti85 could we leave the nomination period open a couple of extra days, since this falls around a holiday period and people may have sporadic availability?

@tdcmeehan I have updated the timeline to extend nominations until next Monday 1/9/2023

Goodsamsam commented 1 year ago

@micmarti85 @tdcmeehan - Per the issue description here and the charter of the TSC - TSC members must be committers. code owners are not committers right?

tdcmeehan commented 1 year ago

@Goodsamsam according to the charter, committers are defined by a project's CONTRIBUTING file: https://github.com/prestodb/tsc/blob/master/CHARTER.md#2-technical-steering-committee (2.c)

For prestodb/presto, code owners are explicitly called out as committers: https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#committers

Technically, any project within the Prestodb org who has an explicitly mentioned maintainer in the CONTRIBUTING file of the repo may be considered a committer as 2.d.ii in the charter states that:

Committers are Contributors who have earned the ability to modify ("commit") source code, documentation or other technical artifacts in a project’s repository; and

i.e. a project's repository may call out a maintainer and this can be considered a committer from the charter's standpoint.

Feel free to propose language in the charter that makes this even more clear. This has been socialized in TSC meetings.

Goodsamsam commented 1 year ago

@tdcmeehan thanks for your response. It very good if the TSC being made broad however to be fair to all code owners and also committers - it important to clarify this.

Committers are defined in the charter in the next section to the one that you pointed out. This should eliminate the confusion about who is a committer.

Section 2 d iii says “iii. A Contributor may become a Committer by a majority approval of the TSC. A Committer may be removed by a majority approval of the TSC.”

If code owners have gone through the voting process via majority approval , the list of committers maintained here https://github.com/prestodb/presto/wiki/committers should be updated with all the code owners.

also the process outlined here follows the charter: https://github.com/prestodb/presto/wiki/How-to-become-a-Presto-committer

If not, code owners probably fall into the category of contributors.

tdcmeehan commented 1 year ago

@Goodsamsam code owners updates are always voted on by the TSC, since as you mention that would require TSC approval. Perhaps the best thing to do is update the wiki to clarify the rules and point to the various contributing files that define committership for the project. Feel free to propose edits to those wikis.

Goodsamsam commented 1 year ago

many will happy to see this

once Linux foundation confirms that majority TSC voting was done for all code owners, given the public list only shows voting for full committers and none of the code owners have gone through any public voting, we can add everyone to the committers page. any reason none of the code owners went through the same public voting process?

prestodb/team-velox team is not public, can you please share all on this list? i contribute changes to https://github.com/prestodb/presto/wiki/committers to add @vinothchandar @7c00 @shangxinli @sdruzkin @team-velox people - they all got upgrade !

tdcmeehan commented 1 year ago

Note that most TSC decisions are done on Github. All codeowners updates can be traced to a corresponding PR and verified independently. For example, the team Velox list was added by this PR: https://github.com/prestodb/presto/pull/18171 (Note electronic votes typically use lazy consensus.) One can look at the blame for the codeowners file to verify past votes.

Happy to chat further on Slack: https://join.slack.com/t/prestodb/shared_invite/zt-1mptx1bo6-67RMuR0eVRBdqj0swldIAw

Thanks!

Goodsamsam commented 1 year ago

@tdcmeehan or @micmarti85 who is on the team-velox list? So to update the committers page

It was asked in the PR 18171 that approved the list as a code owner as well, but wasn’t answered and just approved . there is no record of each codeowner getting added to this approved list per the charter? Who can add members to that list?

tdcmeehan commented 1 year ago

@Goodsamsam I invited you to the org so you can see the composition of this list. I am the only administrator of the team-velox list, so only myself and other PrestoDB administrators could change the membership of it. While Ying did have this question, she had visibility into that list as a member of the PrestoDB org (as all TSC members who voted did), which I clarified offline with her.

Thanks for making the wiki edit--much appreciated!

tdcmeehan commented 1 year ago

GitHub username: tdcmeehan Email: tdm@meta.com

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

I have been TSC Chair for the project since the beginning of 2021, and a committer since 2020. I've given numerous keynotes at Presto events and talks to external conferences evangelizing the Presto community and our technical roadmap. As TSC Chair I've moderated monthly meetings since 2021, helped found the Presto Conformance Program, onboarded the codeowners program which has added 17 new contributors to the project, worked with external teams to provide tools to improve community engagement, and am among the top 5 reviewers in the main repository.

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

I believe the TSC can provide guidance, clarity, and help to push forward the following areas: deliver on the One Presto vision; grow and help mature the community; evangelize our accomplishments.

On the One Presto vision, we'll want technical guidance from the TSC as we work through significant projects hardening and solidifying Presto on Spark and integrating Velox into that stack; maturing Prestissimo and making it the first choice of deployment for new users; improving Presto's resource management to better handles failures, slowness, and unpredictable reliability of hardware for interactive workloads; significantly improving the default optimizations that are applied to queries and require less rewriting from users. These all coalesce on making Presto the best default platform for the Lakehouse and reduce the need for replatforming on other tools.

On the community side, the TSC will need to improve visibility into performance related to PR turnaround time, open issue count and duration, and conversion of new users into contributors. This starts as measurement, but over time we'll want to create SLAs and improve these SLOs, always striving and thinking of ways of reducing key SLOs with the goal of increasing community conversions and creating a vibrant, active developer community aligned on the One Presto direction.

On the evangelization side, I will continue to broadcast the community's accomplishments to conferences, meetups and other events.

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

I currently am a committer, TSC member and TSC chair.

Do you commit to attending the monthly TSC calls?

Yes, and additionally moderating these calls.

tdcmeehan commented 1 year ago

I would also like to nominate James Sun (Github user name: highker). I will let him fill in his aspirations to the TSC, however anyone acquainted with Presto will know of his significant technical accomplishments. In addition to leading the RaptorX project and implementing connector plan participation, he provides invaluable guidance to community PRs, being the top reviewer to the project for the past half (as with most halves).

aditi-pandit commented 1 year ago

GitHub username: aditi-pandit Email: aditi@ahana.io

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

I have been involved with the Prestissimo and Velox projects since 2021.

Core projects :

I presented in PrestoCon Dec 2022 on "Building Large Scale Query Operators for Prestissimo" based on my experience with Window operator development in 2022.

Please provide 3-6 sentences on what you aspire to achieve on the TSC Based on my current and previous experiences in data infrastructure products there are few areas I want to influence in Presto:

i) Prestissimo : Since the last 2-3 years there has been an initiative to improve price performance of Presto by moving to a C++ based query execution engine. This development is in line with the industry and other similar projects like Photon at Databricks. One of the goals I want to influence is the advancement of Presto/Velox in the Open Cloud platforms: S3 on AWS, etc. This includes SQL coverage, performance and other functionality.

ii) Advanced analytics : In previous work experiences I've worked on advanced Database features in the query optimizer/extensibility areas for improving the analytics capabilities of SQL engines. I hope to provide thought leadership in this area to the Presto community.

iii) Community work : I want to contribute to more helpful documentation, customer case studies in Presto. At Ahana we care about great production deployment experiences for customers and I hope to carry that forward in a way to influence the open source Presto product.

Do you currently hold any formal leadership roles within the Presto community? Yes, Presto Code Owner Committer (Prestissimo).

Do you commit to attending the monthly TSC calls? Yes.

micmarti85 commented 1 year ago

NOMINATIONS ARE CLOSED 1/10/2022 @ 12AM

We have 4 new 2023 TSC representatives. Thank you to the outgoing reps for your service in 2022.

New Presto Foundation TSC Representatives

Since only 4 positions were available and only 4 nominations were complete/confirmed, there will be no vote this year. Thank you to all who participated in this years elections.

micmarti85 commented 1 year ago

Presto Foundation TSC Community, On 1/10/2023 we announced the results of the TSC Member election. After this announcement was made, several community members reached out expressing surprise that the seats had not come to a vote considering there had been 6 nominees. The rules for the election stated that nominations made by others must be confirmed publicly by the nominee under this GitHub issue, however, this does not seem to have been clear to the community as a whole. We are in the process of determining a path forward, we appreciate everyone’s patience as we navigate this situation and hope to find a resolution soon.

aditi-pandit commented 1 year ago

Hi everyone,

Totally understand the situation from yesterday. I'm open to going through the new voting process.

In any case, I'm very excited about Presto and really look forward to strong contributions and influence in its future direction.

Good luck !

Thanks, Aditi

micmarti85 commented 1 year ago

@aditi-pandit Thank you for your comment.

We will be conducting an election for the fourth TSC Members seat. The community members who were nominated by others but did not confirm will have until the end of the week to confirm their nominations. Starting next week we will have an election. This election is only for the fourth seat, the members below have been assigned to the TSC for the 2023 calendar year.

2023 Presto Foundation TSC Representatives

  1. majetideepak, Ahana
  2. Yingsu00, Ahana
  3. tdcmeehan, Meta
  4. (TBD)

I have moved this new nomination period to a new Issue. (issue #100)