Re: [tsc-voting] [presto-tsc] Nominate Ariel as a Committer for Various Repos
Andrii Rosa
+1
|
|
Re: [tsc-voting] [presto-tsc] Nominate Ariel as a Committer for Various Repos
zluo@...
+1
On Mon, Aug 16, 2021 at 10:38 AM Bin Fan <binfan@...> wrote:
|
|
Re: Nominate Ariel as a Committer for Various Repos
Bin Fan
+1
On Mon, Aug 16, 2021 at 10:37 AM <rongrong100@...> wrote:
|
|
Re: Nominate Ariel as a Committer for Various Repos
rongrong100@...
+1 Rongrong
|
|
Re: Nominate Ariel as a Committer for Various Repos
Shixuan Fan
+1. I really appreciate his tremendous effort on the project, especially open source.
From:
presto-tsc@... <presto-tsc@...> on behalf of jamessun via lists.prestodb.io <jamessun=fb.com@...> As I’ve discussed with many of you offline, I would love to nominate Ariel Weisberg (https://github.com/aweisberg) to be a committer for the following repositories.
An initial example PR has been created for repo prestodb.github.io: https://github.com/prestodb/prestodb.github.io/pull/147
Ariel has been one of the most active members of the Presto open source community. He has made huge contribution to the community. This change might also help to scale out PrestoDB’s committership. Please vote on this proposal.
As a reminder, given the current TSC makeup, each TSC voting members has one vote per company. Specifically, we will be looking for one vote from Facebook, Twitter, and Alluxio.
Thanks!
James
|
|
Nominate Ariel as a Committer for Various Repos
jamessun@...
As I’ve discussed with many of you offline, I would love to nominate Ariel Weisberg (https://github.com/aweisberg) to be a committer for the following repositories.
An initial example PR has been created for repo prestodb.github.io: https://github.com/prestodb/prestodb.github.io/pull/147
Ariel has been one of the most active members of the Presto open source community. He has made huge contribution to the community. This change might also help to scale out PrestoDB’s committership. Please vote on this proposal.
As a reminder, given the current TSC makeup, each TSC voting members has one vote per company. Specifically, we will be looking for one vote from Facebook, Twitter, and Alluxio.
Thanks!
James
|
|
Company affiliations of TSC members
oliverjacob73@...
I was reading through the TSC charter document and noticed that the voting process changes once there are at least 6 companies represented in the TSC. I was also looking at https://github.com/prestodb/presto/wiki/committers and I can see who is in the TSC, but I can't tell which companies they represent. Would it make sense to list the company affiliations of each of the members?
|
|
Call for agenda items for Aug 3, 2021 TSC meeting
Tim Meehan
Hello,
If you have any items that you would like to bring up in the TSC meeting tomorrow, please add them to the agenda by creating a pull request against the agenda file.
Thank you, Tim
|
|
回复:[presto-tsc] Call for collaboration: Open Source Roadmap for H2 2021
James (Mingming) Xu
Hi, This is James from Alibaba, I missed the last email, I will add some to the roadmap.
|
|
Re: Call for collaboration: Open Source Roadmap for H2 2021
Tim Meehan
Hello,
I just wanted to thank everyone who contributed to this document, in particular those from Facebook, Uber, Twitter, Ahana and ByteDance. By the looks of it, we have an impressive few months ahead, and I’m looking forward to it:
https://docs.google.com/document/d/1rkZ0vuSVHTyRPAaflG6lAt5K_6djdjTKm-jTJybBhRk/edit?usp=sharing
This document has now been closed to contributions, but that doesn’t mean it’s too late to add anything--please reach out if there’s something that was missed and you would like me to add to it.
As next steps, I’ll be following up on making sure all tasks in H2 have associated Github issues. I’ll be reaching out individually to the POCs mentioned in the document.
As issues are created and identified, they’ll be tagged with the 2021H2 milestone. You can follow along here: https://github.com/prestodb/presto/milestone/38
I aim to have this completed by the end of next week, July 23rd. If you contributed to this document, you can get a head start by creating a Github issue for the change.
Looking forward to a productive and collaborative half.
Tim
From:
Tim Meehan <tdm@...> Hello,
As mentioned in the last TSC meeting, we would like to collaborate and share our plans for the upcoming half. The steps are the following:
I hope this process brings greater transparency to what we’re all working on, and encourages better collaboration by improving visibility into the projects we’re tracking.
Tim
|
|
Re: [presto-conformance-wg] Presto Conformance Program Chair Election
Rohan Pednekar
Thanks, Gale and foundation members. I look forward to working with you all and the presto community.
On Wed, Jun 30, 2021 at 1:16 PM Gale McCommons <gmccommons@...> wrote:
--
Best, Rohan
|
|
Re: [presto-conformance-wg] Presto Conformance Program Chair Election
Gale McCommons <gmccommons@...>
Hi Team, The election for the Presto Foundation conformance program chair has concluded. Based on the criteria set in the TSC charter, there were four individuals eligible to vote. Out of the four voters, three voted. The person elected for the position is Rohan Pednekar. Congratulations, Rohan! Thank you! Gale -- Gale McCommons Program Manager, Linux Foundation M: +1 210 367 1795 Book time with me: https://calendly.com/gmccommons/meeting
On Wed, Jun 23, 2021 at 1:50 PM Gale McCommons <gmccommons@...> wrote:
|
|
Re: [presto-conformance-wg] Presto Conformance Program Chair Election
Gale McCommons <gmccommons@...>
Hi Team - please find attached a correction to the nomination statements. Thank you! Gale -- Gale McCommons Program Manager, Linux Foundation M: +1 210 367 1795 Book time with me: https://calendly.com/gmccommons/meeting On Wed, Jun 23, 2021 at 12:31 PM Gale McCommons via lists.prestodb.io <gmccommons=linuxfoundation.org@...> wrote:
|
|
Re: Presto Conformance Program Chair Election
Gale McCommons <gmccommons@...>
Hi All, Voting starts today to elect the chairperson of the Presto Conformance Program. Per the Conformance Program charter, the position will be voted in by the voting members of the TSC. Please find attached the nomination statements for the nominees. Section 3.a of the TSC charter allows one vote per represented company for any election or decision that requires a vote. The designated voter for each represented company will receive a link today to vote in this election, and the election will remain open until June 29. Please let me know if you have any questions or feedback. Thank you, Gale -- Gale McCommons Program Manager, Linux Foundation M: +1 210 367 1795 Book time with me: https://calendly.com/gmccommons/meeting
On Tue, Jun 15, 2021 at 3:29 PM Gale McCommons <gmccommons@...> wrote:
|
|
Re: Presto Conformance Program Chair Election
Gale McCommons <gmccommons@...>
Hi Team, This is a gentle reminder to please submit your nominations by end of day today (6/22). Thank you Gale -- Gale McCommons Program Manager, Linux Foundation M: +1 210 367 1795 Book time with me: https://calendly.com/gmccommons/meeting
On Tue, Jun 15, 2021 at 3:29 PM Gale McCommons <gmccommons@...> wrote:
|
|
Call for collaboration: Open Source Roadmap for H2 2021
Tim Meehan
Hello,
As mentioned in the last TSC meeting, we would like to collaborate and share our plans for the upcoming half. The steps are the following:
I hope this process brings greater transparency to what we’re all working on, and encourages better collaboration by improving visibility into the projects we’re tracking.
Tim
|
|
Presto Conformance Program Chair Election
Gale McCommons <gmccommons@...>
Presto Foundation Conformance Program Working Group, The position for Conformance Program Chair is open for election. The nomination period is open for one week followed by a one week voting period. Please reply to this email to submit your nomination. You may nominate yourself or another candidate. Please find below the timeline for this election. Election Timeline: June 15 - June 30 Nomination period: June 15 - June 22 Voting period: June 23 - June 29 Results announced: June 30 Term: 1 July 2021 through 30 June 2022 Please let me know if you have any questions. Thank you! Gale -- Gale McCommons Program Manager, Linux Foundation M: +1 210 367 1795 Book time with me: https://calendly.com/gmccommons/meeting
|
|
Call for agenda items for June 8th, 2021 TSC meeting
Tim Meehan
Hello,
If you have any items that you would like to bring up in the TSC meeting tomorrow, please add them to the agenda by creating a pull request against the agenda file.
Thank you, Tim
|
|
Re: Nominating Ariel Weisberg
yingsu00@...
+1 for committer. Ariel reviewed all my blogposts and his reviews were of high quality. He was also the one who set up many of the community logistics platforms.
I’m not TSC member therefore I won’t vote for Ariel’s TSC membership. But I agree with @Dipti that TSC and committership should be separately managed and elected. A TSC member does NOT have to be a committer in my humble opinion. As per my understanding, TSC members should deeply understand the industry and most cutting edge technologies, and can set the direction of the Presto community and increase its market share and adoption rate not just within every participating company but also the whole industry.
Thanks, Ying
|
|
Re: Github Status Checks
Tim Meehan
Hello,
As we have all related company’s voting members of the TSC submitting their vote in favor, voting is now concluded and we’ll enable the status checks shortly. Thank you!
Tim
From:
Tim Meehan <tdm@...> Hello,
As mentioned in the TSC meeting today, I’d like to enable the Github status checks requirement to the master branch, which means status checks must pass before a PR can be merged. This is to prevent accidental merge of a failing test into the master branch, or to prevent known failing tests from affecting other PRs. If there’s unrelated flaky tests, then the idea is we should fix these tests or mark them as disabled.
Documentation on Github status checks are here: https://docs.github.com/en/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging
Please give this a +1 if you agree that code should not be merged with known test failures.
Thanks Tim
|
|