Re: [VOTE] Graduate Apache Pinot as TLP

[Abhishek Tiwari]

+1 (non-binding)

On Wed, Jun 23, 2021 at 10:34 PM Xiang Fu  wrote:

> +1
>
> Xiang Fu
>
>
> > On Jun 23, 2021, at 9:21 PM, Atri Sharma  wrote:
> >
> > +1(binding)
> >
> > On Wed, Jun 23, 2021 at 1:14 AM Mayank Shrivastava 
> wrote:
> >>
> >> Dear Incubator Community,
> >>
> >> We have discussed Apache Pinot Podling graduation in the
> general@incubator
> >> DISCUSS thread [1], and addressed all the questions and concerns
> brought up
> >> in the thread. Please refer to [1] for details on the questions and
> >> concerns brought up, as well as their resolutions. With no objections
> >> brought up in the discussion, we would like to proceed with the voting
> >> process.
> >>
> >> Here is the official vote for graduating Apache Pinot project as TLP.
> >>
> >> Please provide your in the following options:
> >>
> >> [ ] +1 - Recommend graduation of Apache Pinot as a TLP
> >>
> >> [ ]  0 - I don't feel strongly about it, but don't object
> >>
> >> [ ] -1 - Do not recommend the graduation of Apache Pinot because…
> >>
> >> The VOTE will remain open for at least 72 hours.
> >>
> >> To summarize a few of the community's achievements:
> >>
> >>
> >>   -
> >>
> >>   7800+ contributions from 168 contributors
> >>   -
> >>
> >>   7 releases by various release managers
> >>   -
> >>
> >>   6 new committers and 2 new PPMCs invited (all accepted)
> >>   -
> >>
> >>   Diverse committers and PPMCs (from 7 companies/institutes)
> >>   -
> >>
> >>   Apache website setup [4]
> >>   -
> >>
> >>   Dev conversations at d...@pinot.apache.org
> >>   -
> >>
> >>   Assessed ourselves against the Apache Project maturity matrix [5]
> >>   -
> >>
> >>   We have built a meritocratic and open collaborative process (the
> Apache
> >>   way)
> >>
> >>
> >>
> >> =
> >>
> >> Establish the Apache Pinot Project
> >>
> >> WHEREAS, the Board of Directors deems it to be in the best interests of
> the
> >> Foundation and consistent with the Foundation's purpose to establish a
> >> Project Management Committee charged with the creation and maintenance
> of
> >> open-source software, for distribution at no charge to the public,
> related
> >> to a distributed data integration framework that simplifies common
> aspects
> >> of big data integration such as data ingestion, replication,
> organization
> >> and lifecycle management for both streaming and batch data ecosystems.
> >>
> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC),
> >> to be known as the "Apache Pinot Project", be and hereby is established
> >> pursuant to Bylaws of the Foundation; and be it further
> >>
> >> RESOLVED, that the Apache Pinot Project be and hereby is responsible for
> >> the creation and maintenance of software related to distributed OLAP
> data
> >> store to provide Real-time Analytics to power wide variety of analytical
> >> use case; and be it further
> >>
> >> RESOLVED, that the office of "Vice President, Apache Pinot" be and
> hereby
> >> is created, the person holding such office to serve at the direction of
> the
> >> Board of Directors as the chair of the Apache Pinot Project, and to have
> >> primary responsibility for management of the projects within the scope
> of
> >> responsibility of the Apache Pinot Project; and be it further
> >>
> >> RESOLVED, that the persons listed immediately below be and hereby are
> >> appointed to serve as the initial members of the Apache Pinot Project:
> >>
> >>   -
> >>
> >>   Felix Cheung 
> >>   -
> >>
> >>   Jackie Jiang 
> >>   -
> >>
> >>   Jim Jagielski 
> >>   -
> >>
> >>   Kishore G 
> >>   -
> >>
> >>   Mayank Shrivastava 
> >>   -
> >>
> >>   Neha Pawar 
> >>   -
> >>
> >>   Olivier Lamy 
> >>   -
> >>
> >>   Seunghyun Lee 
> >>   -
> >>
> >>   Siddharth Teotia 
> >>   -
> >>
> >>   Subbu Subramaniam 
> >>   -
> >>
> >>   Xiang Fu 
> >>
> >>
> >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be
> >> appointed to the office of Vice President, Apache Pinot, to serve in
> >> accordance with and subject to the direction of the Board of Directors
> and
> >> the Bylaws of the Foundation until death, resignation, retirement,
> removal
> >> of disqualification, or until a successor is appointed; and be it
> further
> >>
> >> RESOLVED, that the Apache Pinot Project be and hereby is tasked with the
> >> migration and rationalization of the Apache Incubator Pinot podling;
> and be
> >> it further
> >>
> >> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> >> Pinot podling encumbered upon the Apache Incubator PMC are hereafter
> >> discharged.
> >>
> >>
> >> [1] general@Incubator Discuss thread
> >> <
> https://lists.apache.org/thread.html/r4421bf9517dc522a564e7453c2c87dddbf39019737dd143de57d2f49%40%3Cgeneral.incubator.apache.org%3E
> >
> >>
> >> [2] Community Discussion for Graduation
> >> <
> 

Re: [VOTE] Graduate Apache Pinot as TLP

[Xiang Fu]

+1

Xiang Fu


> On Jun 23, 2021, at 9:21 PM, Atri Sharma  wrote:
> 
> +1(binding)
> 
> On Wed, Jun 23, 2021 at 1:14 AM Mayank Shrivastava  wrote:
>> 
>> Dear Incubator Community,
>> 
>> We have discussed Apache Pinot Podling graduation in the general@incubator
>> DISCUSS thread [1], and addressed all the questions and concerns brought up
>> in the thread. Please refer to [1] for details on the questions and
>> concerns brought up, as well as their resolutions. With no objections
>> brought up in the discussion, we would like to proceed with the voting
>> process.
>> 
>> Here is the official vote for graduating Apache Pinot project as TLP.
>> 
>> Please provide your in the following options:
>> 
>> [ ] +1 - Recommend graduation of Apache Pinot as a TLP
>> 
>> [ ]  0 - I don't feel strongly about it, but don't object
>> 
>> [ ] -1 - Do not recommend the graduation of Apache Pinot because…
>> 
>> The VOTE will remain open for at least 72 hours.
>> 
>> To summarize a few of the community's achievements:
>> 
>> 
>>   -
>> 
>>   7800+ contributions from 168 contributors
>>   -
>> 
>>   7 releases by various release managers
>>   -
>> 
>>   6 new committers and 2 new PPMCs invited (all accepted)
>>   -
>> 
>>   Diverse committers and PPMCs (from 7 companies/institutes)
>>   -
>> 
>>   Apache website setup [4]
>>   -
>> 
>>   Dev conversations at d...@pinot.apache.org
>>   -
>> 
>>   Assessed ourselves against the Apache Project maturity matrix [5]
>>   -
>> 
>>   We have built a meritocratic and open collaborative process (the Apache
>>   way)
>> 
>> 
>> 
>> =
>> 
>> Establish the Apache Pinot Project
>> 
>> WHEREAS, the Board of Directors deems it to be in the best interests of the
>> Foundation and consistent with the Foundation's purpose to establish a
>> Project Management Committee charged with the creation and maintenance of
>> open-source software, for distribution at no charge to the public, related
>> to a distributed data integration framework that simplifies common aspects
>> of big data integration such as data ingestion, replication, organization
>> and lifecycle management for both streaming and batch data ecosystems.
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
>> to be known as the "Apache Pinot Project", be and hereby is established
>> pursuant to Bylaws of the Foundation; and be it further
>> 
>> RESOLVED, that the Apache Pinot Project be and hereby is responsible for
>> the creation and maintenance of software related to distributed OLAP data
>> store to provide Real-time Analytics to power wide variety of analytical
>> use case; and be it further
>> 
>> RESOLVED, that the office of "Vice President, Apache Pinot" be and hereby
>> is created, the person holding such office to serve at the direction of the
>> Board of Directors as the chair of the Apache Pinot Project, and to have
>> primary responsibility for management of the projects within the scope of
>> responsibility of the Apache Pinot Project; and be it further
>> 
>> RESOLVED, that the persons listed immediately below be and hereby are
>> appointed to serve as the initial members of the Apache Pinot Project:
>> 
>>   -
>> 
>>   Felix Cheung 
>>   -
>> 
>>   Jackie Jiang 
>>   -
>> 
>>   Jim Jagielski 
>>   -
>> 
>>   Kishore G 
>>   -
>> 
>>   Mayank Shrivastava 
>>   -
>> 
>>   Neha Pawar 
>>   -
>> 
>>   Olivier Lamy 
>>   -
>> 
>>   Seunghyun Lee 
>>   -
>> 
>>   Siddharth Teotia 
>>   -
>> 
>>   Subbu Subramaniam 
>>   -
>> 
>>   Xiang Fu 
>> 
>> 
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be
>> appointed to the office of Vice President, Apache Pinot, to serve in
>> accordance with and subject to the direction of the Board of Directors and
>> the Bylaws of the Foundation until death, resignation, retirement, removal
>> of disqualification, or until a successor is appointed; and be it further
>> 
>> RESOLVED, that the Apache Pinot Project be and hereby is tasked with the
>> migration and rationalization of the Apache Incubator Pinot podling; and be
>> it further
>> 
>> RESOLVED, that all responsibilities pertaining to the Apache Incubator
>> Pinot podling encumbered upon the Apache Incubator PMC are hereafter
>> discharged.
>> 
>> 
>> [1] general@Incubator Discuss thread
>> 
>> 
>> [2] Community Discussion for Graduation
>> 
>> 
>> [3] Voting Thread
>> 
>> 
>> [4] Voting Result
>> 
>> 
>> [5] 

Re: [VOTE] Graduate Apache Pinot as TLP

[Felix Cheung]

+1

On Wed, Jun 23, 2021 at 6:55 PM Sheng Wu  wrote:

> +1 binding, good luck
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> Justin Mclean  于2021年6月24日周四 上午9:46写道：
>
> > +1 all the best with the rest of your journey
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Graduate Apache Pinot as TLP

[Atri Sharma]

+1(binding)

On Wed, Jun 23, 2021 at 1:14 AM Mayank Shrivastava  wrote:
>
> Dear Incubator Community,
>
> We have discussed Apache Pinot Podling graduation in the general@incubator
> DISCUSS thread [1], and addressed all the questions and concerns brought up
> in the thread. Please refer to [1] for details on the questions and
> concerns brought up, as well as their resolutions. With no objections
> brought up in the discussion, we would like to proceed with the voting
> process.
>
> Here is the official vote for graduating Apache Pinot project as TLP.
>
> Please provide your in the following options:
>
> [ ] +1 - Recommend graduation of Apache Pinot as a TLP
>
> [ ]  0 - I don't feel strongly about it, but don't object
>
> [ ] -1 - Do not recommend the graduation of Apache Pinot because…
>
> The VOTE will remain open for at least 72 hours.
>
> To summarize a few of the community's achievements:
>
>
>-
>
>7800+ contributions from 168 contributors
>-
>
>7 releases by various release managers
>-
>
>6 new committers and 2 new PPMCs invited (all accepted)
>-
>
>Diverse committers and PPMCs (from 7 companies/institutes)
>-
>
>Apache website setup [4]
>-
>
>Dev conversations at d...@pinot.apache.org
>-
>
>Assessed ourselves against the Apache Project maturity matrix [5]
>-
>
>We have built a meritocratic and open collaborative process (the Apache
>way)
>
>
>
> =
>
> Establish the Apache Pinot Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of the
> Foundation and consistent with the Foundation's purpose to establish a
> Project Management Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the public, related
> to a distributed data integration framework that simplifies common aspects
> of big data integration such as data ingestion, replication, organization
> and lifecycle management for both streaming and batch data ecosystems.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache Pinot Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Pinot Project be and hereby is responsible for
> the creation and maintenance of software related to distributed OLAP data
> store to provide Real-time Analytics to power wide variety of analytical
> use case; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Pinot" be and hereby
> is created, the person holding such office to serve at the direction of the
> Board of Directors as the chair of the Apache Pinot Project, and to have
> primary responsibility for management of the projects within the scope of
> responsibility of the Apache Pinot Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Pinot Project:
>
>-
>
>Felix Cheung 
>-
>
>Jackie Jiang 
>-
>
>Jim Jagielski 
>-
>
>Kishore G 
>-
>
>Mayank Shrivastava 
>-
>
>Neha Pawar 
>-
>
>Olivier Lamy 
>-
>
>Seunghyun Lee 
>-
>
>Siddharth Teotia 
>-
>
>Subbu Subramaniam 
>-
>
>Xiang Fu 
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be
> appointed to the office of Vice President, Apache Pinot, to serve in
> accordance with and subject to the direction of the Board of Directors and
> the Bylaws of the Foundation until death, resignation, retirement, removal
> of disqualification, or until a successor is appointed; and be it further
>
> RESOLVED, that the Apache Pinot Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Pinot podling; and be
> it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pinot podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
>
> [1] general@Incubator Discuss thread
> 
>
> [2] Community Discussion for Graduation
> 
>
> [3] Voting Thread
> 
>
> [4] Voting Result
> 
>
> [5] https://pinot.incubator.apache.org/
> [6] Maturity Model Assessment
> 

-- 
Regards,

Atri
Apache Concerted

Re: [VOTE] Graduate Apache Pinot as TLP

[Sheng Wu]

+1 binding, good luck

Sheng Wu 吴晟
Twitter, wusheng1108


Justin Mclean  于2021年6月24日周四 上午9:46写道：

> +1 all the best with the rest of your journey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache Pinot as TLP

[Justin Mclean]

+1 all the best with the rest of your journey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Pinot as TLP

[kishore g]

+1

On Wed, Jun 23, 2021 at 3:10 PM Xiaotian Jiang  wrote:

> +1
>
> Jackie
>
> On Tue, Jun 22, 2021 at 12:44 PM Mayank Shrivastava 
> wrote:
>
>> Dear Incubator Community,
>>
>> We have discussed Apache Pinot Podling graduation in the general@incubator
>> DISCUSS thread [1], and addressed all the questions and concerns brought
>> up
>> in the thread. Please refer to [1] for details on the questions and
>> concerns brought up, as well as their resolutions. With no objections
>> brought up in the discussion, we would like to proceed with the voting
>> process.
>>
>> Here is the official vote for graduating Apache Pinot project as TLP.
>>
>> Please provide your in the following options:
>>
>> [ ] +1 - Recommend graduation of Apache Pinot as a TLP
>>
>> [ ]  0 - I don't feel strongly about it, but don't object
>>
>> [ ] -1 - Do not recommend the graduation of Apache Pinot because…
>>
>> The VOTE will remain open for at least 72 hours.
>>
>> To summarize a few of the community's achievements:
>>
>>
>>-
>>
>>7800+ contributions from 168 contributors
>>-
>>
>>7 releases by various release managers
>>-
>>
>>6 new committers and 2 new PPMCs invited (all accepted)
>>-
>>
>>Diverse committers and PPMCs (from 7 companies/institutes)
>>-
>>
>>Apache website setup [4]
>>-
>>
>>Dev conversations at d...@pinot.apache.org
>>-
>>
>>Assessed ourselves against the Apache Project maturity matrix [5]
>>-
>
>
>>
>>We have built a meritocratic and open collaborative process (the Apache
>>way)
>>
>>
>>
>> =
>>
>> Establish the Apache Pinot Project
>>
>> WHEREAS, the Board of Directors deems it to be in the best interests of
>> the
>> Foundation and consistent with the Foundation's purpose to establish a
>> Project Management Committee charged with the creation and maintenance of
>> open-source software, for distribution at no charge to the public, related
>> to a distributed data integration framework that simplifies common aspects
>> of big data integration such as data ingestion, replication, organization
>> and lifecycle management for both streaming and batch data ecosystems.
>>
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
>> to be known as the "Apache Pinot Project", be and hereby is established
>> pursuant to Bylaws of the Foundation; and be it further
>>
>> RESOLVED, that the Apache Pinot Project be and hereby is responsible for
>> the creation and maintenance of software related to distributed OLAP data
>> store to provide Real-time Analytics to power wide variety of analytical
>> use case; and be it further
>>
>> RESOLVED, that the office of "Vice President, Apache Pinot" be and hereby
>> is created, the person holding such office to serve at the direction of
>> the
>> Board of Directors as the chair of the Apache Pinot Project, and to have
>> primary responsibility for management of the projects within the scope of
>> responsibility of the Apache Pinot Project; and be it further
>>
>> RESOLVED, that the persons listed immediately below be and hereby are
>> appointed to serve as the initial members of the Apache Pinot Project:
>>
>>-
>>
>>Felix Cheung 
>>-
>>
>>Jackie Jiang 
>>-
>>
>>Jim Jagielski 
>>-
>>
>>Kishore G 
>>-
>>
>>Mayank Shrivastava 
>>-
>>
>>Neha Pawar 
>>-
>>
>>Olivier Lamy 
>>-
>>
>>Seunghyun Lee 
>>-
>>
>>Siddharth Teotia 
>>-
>>
>>Subbu Subramaniam 
>>-
>>
>>Xiang Fu 
>>
>>
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be
>> appointed to the office of Vice President, Apache Pinot, to serve in
>> accordance with and subject to the direction of the Board of Directors and
>> the Bylaws of the Foundation until death, resignation, retirement, removal
>> of disqualification, or until a successor is appointed; and be it further
>>
>> RESOLVED, that the Apache Pinot Project be and hereby is tasked with the
>> migration and rationalization of the Apache Incubator Pinot podling; and
>> be
>> it further
>>
>> RESOLVED, that all responsibilities pertaining to the Apache Incubator
>> Pinot podling encumbered upon the Apache Incubator PMC are hereafter
>> discharged.
>>
>>
>> [1] general@Incubator Discuss thread
>> <
>> https://lists.apache.org/thread.html/r4421bf9517dc522a564e7453c2c87dddbf39019737dd143de57d2f49%40%3Cgeneral.incubator.apache.org%3E
>> >
>>
>> [2] Community Discussion for Graduation
>> <
>> https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E
>> >
>>
>> [3] Voting Thread
>> <
>> https://lists.apache.org/thread.html/r9ca0b2ccc9b0fbdbee6a09aaf06b36ffd3a20e9cc1b810cdbe7c65d6%40%3Cdev.pinot.apache.org%3E
>> >
>>
>> [4] Voting Result
>> <
>> https://lists.apache.org/thread.html/rc371ca50ce8ff2d6c0b068165195526cfdbd08d915105573e17042d2%40%3Cdev.pinot.apache.org%3E
>> >
>>
>> [5] 

Re: [VOTE] Graduate Apache Pinot as TLP

[Xiaotian Jiang]

+1

Jackie

On Tue, Jun 22, 2021 at 12:44 PM Mayank Shrivastava 
wrote:

> Dear Incubator Community,
>
> We have discussed Apache Pinot Podling graduation in the general@incubator
> DISCUSS thread [1], and addressed all the questions and concerns brought up
> in the thread. Please refer to [1] for details on the questions and
> concerns brought up, as well as their resolutions. With no objections
> brought up in the discussion, we would like to proceed with the voting
> process.
>
> Here is the official vote for graduating Apache Pinot project as TLP.
>
> Please provide your in the following options:
>
> [ ] +1 - Recommend graduation of Apache Pinot as a TLP
>
> [ ]  0 - I don't feel strongly about it, but don't object
>
> [ ] -1 - Do not recommend the graduation of Apache Pinot because…
>
> The VOTE will remain open for at least 72 hours.
>
> To summarize a few of the community's achievements:
>
>
>-
>
>7800+ contributions from 168 contributors
>-
>
>7 releases by various release managers
>-
>
>6 new committers and 2 new PPMCs invited (all accepted)
>-
>
>Diverse committers and PPMCs (from 7 companies/institutes)
>-
>
>Apache website setup [4]
>-
>
>Dev conversations at d...@pinot.apache.org
>-
>
>Assessed ourselves against the Apache Project maturity matrix [5]
>-
>
>We have built a meritocratic and open collaborative process (the Apache
>way)
>
>
>
> =
>
> Establish the Apache Pinot Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of the
> Foundation and consistent with the Foundation's purpose to establish a
> Project Management Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the public, related
> to a distributed data integration framework that simplifies common aspects
> of big data integration such as data ingestion, replication, organization
> and lifecycle management for both streaming and batch data ecosystems.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache Pinot Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Pinot Project be and hereby is responsible for
> the creation and maintenance of software related to distributed OLAP data
> store to provide Real-time Analytics to power wide variety of analytical
> use case; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Pinot" be and hereby
> is created, the person holding such office to serve at the direction of the
> Board of Directors as the chair of the Apache Pinot Project, and to have
> primary responsibility for management of the projects within the scope of
> responsibility of the Apache Pinot Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Pinot Project:
>
>-
>
>Felix Cheung 
>-
>
>Jackie Jiang 
>-
>
>Jim Jagielski 
>-
>
>Kishore G 
>-
>
>Mayank Shrivastava 
>-
>
>Neha Pawar 
>-
>
>Olivier Lamy 
>-
>
>Seunghyun Lee 
>-
>
>Siddharth Teotia 
>-
>
>Subbu Subramaniam 
>-
>
>Xiang Fu 
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be
> appointed to the office of Vice President, Apache Pinot, to serve in
> accordance with and subject to the direction of the Board of Directors and
> the Bylaws of the Foundation until death, resignation, retirement, removal
> of disqualification, or until a successor is appointed; and be it further
>
> RESOLVED, that the Apache Pinot Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Pinot podling; and be
> it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pinot podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
>
> [1] general@Incubator Discuss thread
> <
> https://lists.apache.org/thread.html/r4421bf9517dc522a564e7453c2c87dddbf39019737dd143de57d2f49%40%3Cgeneral.incubator.apache.org%3E
> >
>
> [2] Community Discussion for Graduation
> <
> https://lists.apache.org/thread.html/r6068cae91a474e86595cc02d90701501d22c08274216301facf935cc%40%3Cdev.pinot.apache.org%3E
> >
>
> [3] Voting Thread
> <
> https://lists.apache.org/thread.html/r9ca0b2ccc9b0fbdbee6a09aaf06b36ffd3a20e9cc1b810cdbe7c65d6%40%3Cdev.pinot.apache.org%3E
> >
>
> [4] Voting Result
> <
> https://lists.apache.org/thread.html/rc371ca50ce8ff2d6c0b068165195526cfdbd08d915105573e17042d2%40%3Cdev.pinot.apache.org%3E
> >
>
> [5] https://pinot.incubator.apache.org/
> [6] Maturity Model Assessment
> <
> https://cwiki.apache.org/confluence/display/PINOT/Apache+Maturity+Model+Assessment+for+Pinot
> >
>

Re:[VOTE] Release Apache Pegasus (Incubating) 2.2.0-RC0

[Juan Pan]

Hi +1 binding, due to DISCLAIMER-WIP. 
Looks front page issue has been fixed.
Here is my check list,



[x] Download links are valid.

[x] Checksums and PGP signatures are valid.

[x] LICENSE, NOTICE and DISCLAIMER-WIP exist. (NOTICE needs updating).

[ ] All files have license headers if necessary (Some of files have no header, 
e.g., [1][2]).



[1] apache-pegasus-2.2.0-incubating-src/rdsn/include/dsn/utility/binary_reader.h
[2] apache-pegasus-2.2.0-incubating-src/rdsn/include/dsn/utility/binary_writer.h


--
Juan Pan(Trista), Apache ShardingSphere PMC, Apache brpc (Incubating) IPMC
Twitter, @trista86934690


On 06/12/2021 19:38，Yingchun Lai wrote：
Hi, all

This is a call for a vote to release Apache Pegasus (Incubating) version
2.2.0-RC0.

Pegasus is a distributed key-value storage system that is designed
to be simple, horizontally scalable, strongly consistent, and
high-performance.

The Apache Pegasus community has voted on and approved a proposal to
release Apache Pegasus 2.2.0-RC0.
Apache Pegasus community vote thread:
https://lists.apache.org/thread.html/r5f045c9f82e67c01bc23504b66960fb07afdd72875b8e1c808a05e31%40%3Cdev.pegasus.apache.org%3EVote
Result thread:
https://lists.apache.org/thread.html/r89ca7e3caf0790c9244480db6a105611b00732dd81b9da934b1fbc82%40%3Cdev.pegasus.apache.org%3E

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/pegasus/2.2.0-RC0/

It is tagged in Git as v2.2.0-RC0 and the corresponding hash is the
following:
https://gitbox.apache.org/repos/asf?p=incubator-pegasus.git;a=commit;h=a81b6c78cca29d679ae51d7cf5287334c914e3dd

KEYS file available:
https://dist.apache.org/repos/dist/dev/incubator/pegasus/KEYS

For information about the contents of this release, see:
https://docs.google.com/document/d/167M4R063FYcMXOahaInxkjJ8MBYBpzQ1ijeh0qC9SrE/edit?usp=sharing

The vote will be open for 72 hours.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Best regards,
Yingchun Lai

Re: IP clearance officer for accepting Terraform

[Justin Mclean]

Hi,

> I've been following this thread and continue to see phrases such as "major 
> contributors" and "significant contributions”.

That may be a bit nebulous depending on the exact contributions involved, but I 
would expect any one making total commits of 100s, 1,000s or more lines of code 
major/significant. You can see the stats for this repo here [1]

Thanks,
Justin

1. https://github.com/xanzy/terraform-provider-cloudstack/graphs/contributors


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: IP clearance officer for accepting Terraform

[Daniel Widdis]

I've been following this thread and continue to see phrases such as "major 
contributors" and "significant contributions".

Given the entire premise of the conversation here is on whether there are legal 
claims to IP, could you clarify, objectively, what defines "major" and/or 
"significant"?

On 6/22/21, 11:49 PM, "Justin Mclean"  wrote:

Hi,

> Alright, I'll create a Github issue as suggested in the example to track 
IP
> clearance with list of all people and will try to reach out to all
> contributors within a limited time period and see if they can agree over
> the other legal thread and submit their ICLAs.

While having an ICLA is ideal, I think a recorded agreement from the major 
contributors is probably enough given the history here. You already have that 
from most of them. If some don’t answer then just record that and continue. It 
might be possible that other IPMC members might have a different view on this.

> This however wasn't advised on the IP clearance process:
> https://incubator.apache.org/ip-clearance/ip-clearance-template.html

It does say "Either an Individual CLA or Corporate CLA is preferred to a 
Software Grant. All authors must sign an Individual CLA; or all owners of IP 
must sign one of the three documents and send to secretary “. I’m still 
slightly unclear on who the IP owners are. Sander is obviously one, but I would 
guess it’s the other 8 or so other major contributors or possibly in some cases 
their employers. Having an ICLA clears that up as the person states that any 
contributions they make they are allowed to do so and have their employers 
permission to do so.

Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: IP clearance officer for accepting Terraform

[Justin Mclean]

Hi,

> Alright, I'll create a Github issue as suggested in the example to track IP
> clearance with list of all people and will try to reach out to all
> contributors within a limited time period and see if they can agree over
> the other legal thread and submit their ICLAs.

While having an ICLA is ideal, I think a recorded agreement from the major 
contributors is probably enough given the history here. You already have that 
from most of them. If some don’t answer then just record that and continue. It 
might be possible that other IPMC members might have a different view on this.

> This however wasn't advised on the IP clearance process:
> https://incubator.apache.org/ip-clearance/ip-clearance-template.html

It does say "Either an Individual CLA or Corporate CLA is preferred to a 
Software Grant. All authors must sign an Individual CLA; or all owners of IP 
must sign one of the three documents and send to secretary “. I’m still 
slightly unclear on who the IP owners are. Sander is obviously one, but I would 
guess it’s the other 8 or so other major contributors or possibly in some cases 
their employers. Having an ICLA clears that up as the person states that any 
contributions they make they are allowed to do so and have their employers 
permission to do so.

Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: IP clearance officer for accepting Terraform

[Justin Mclean]

Hi,

Thanks for the clarifications and history it useful to know all of this.

> I started, maintained and build most of both these code bases. And as far as 
> I know I'm (still) legally both the author and the owner of the IP as the 
> company I work for (for the last 12 years) has a chapter in their contract 
> that states that any open source contributions made are "owned" by the 
> employee and not the company.

That's good to know. What about the other major contributor's contributions? I 
would assume that they or their employers would own the IP?

> Probably also imortant to know, is that I initially started both these 
> projects using the Apache License, Version 2.

The MPL license was part of a commit on 6th Jun 2017, no license file existed 
before that, that I can find from a quick search anyway. Since then eight 
versions have been released (including the first 0.1 release). So I think it's 
clear to say that any code committed after the 0.1 release was under the MPL 
license.

Kind Regards,
Justin


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: IP clearance officer for accepting Terraform

[Rohit Yadav]

Alright, I'll create a Github issue as suggested in the example to track IP
clearance with list of all people and will try to reach out to all
contributors within a limited time period and see if they can agree over
the other legal thread and submit their ICLAs. I'm not subscribed to the
legal or general@ lists so unless people copied me in or did a reply all
(incl ACS PMC) I wouldn't have got email, I'll check again what Roman may
have advised.

This however wasn't advised on the IP clearance process:
https://incubator.apache.org/ip-clearance/ip-clearance-template.html

I suggest this new approach be documented on the above or relevant page.
Thanks.

Regards.

On Wed, 23 Jun, 2021, 11:36 am Justin Mclean, 
wrote:

> Hi,
>
> Thanks for the information and history there, that was quite helpful.
>
> My understanding is the plugin was originally started as a repo or work by
> Sander (
> https://github.com/xanzy/terraform-provider-cloudstack/commits/master?after=5e7ccfea50810303a6b205084fb6f0b3eade33ca+314=master)
> who contributed it to the Hashicorp Github org like many other community
> providers and then got it eventually transferred back.
>
> From ACS PMC point of view we're going to take the risk as we've ICLA and
> grants from Sander and agreements over email from all the top contributors.
>
>
> You would be in a a better position to judge this, but I can see 8 to 10
> people (out of the 39) that have probably made significant contributions,
> some very significant. It unclear to me if these people were contacted.
>
> I've also gotten emails from other participants including Sander who
> shared their frustration, we've jumped through all the hoops and done our
> best to reach so far, I think Justin you had advised us to get all major
> contributors to agree in the other legal thread but now suddenly we are
> advised to get ICLAs too and from all the contributors.
>
>
> My very first email in that thread suggested you would need ICLAs from the
> major contributors. Having an agreement via other means is probably fine,
> but not the usual process. Roman (V.P. Legal) also suggested you contact
> these contributors.
>
> The examples you've provided don't have ICLAs or agreements from all
> contributors.
>
>
> Not all, but they have ICLAs from all major contributors. More importantly
> the information is in a form where it easy to see what has been provided
> which makes accepting the IP clearance an easy process.
>
> Kind Regard,
> Justin
>

Re: IP clearance officer for accepting Terraform

[Justin Mclean]

Hi,

Thanks for the information and history there, that was quite helpful.

> My understanding is the plugin was originally started as a repo or work by 
> Sander 
> (https://github.com/xanzy/terraform-provider-cloudstack/commits/master?after=5e7ccfea50810303a6b205084fb6f0b3eade33ca+314=master
>  
> )
>  who contributed it to the Hashicorp Github org like many other community 
> providers and then got it eventually transferred back.
> 
> From ACS PMC point of view we're going to take the risk as we've ICLA and 
> grants from Sander and agreements over email from all the top contributors.

You would be in a a better position to judge this, but I can see 8 to 10 people 
(out of the 39) that have probably made significant contributions, some very 
significant. It unclear to me if these people were contacted.

> I've also gotten emails from other participants including Sander who shared 
> their frustration, we've jumped through all the hoops and done our best to 
> reach so far, I think Justin you had advised us to get all major contributors 
> to agree in the other legal thread but now suddenly we are advised to get 
> ICLAs too and from all the contributors.

My very first email in that thread suggested you would need ICLAs from the 
major contributors. Having an agreement via other means is probably fine, but 
not the usual process. Roman (V.P. Legal) also suggested you contact these 
contributors.

> The examples you've provided don't have ICLAs or agreements from all 
> contributors.

Not all, but they have ICLAs from all major contributors. More importantly the 
information is in a form where it easy to see what has been provided which 
makes accepting the IP clearance an easy process.

Kind Regard,
Justin

Re: IP clearance officer for accepting Terraform

[Rohit Yadav]

Thanks Sander for the clarification.

Regards.

On Wed, 23 Jun, 2021, 11:22 am Sander van Harmelen, 
wrote:

> A, I just now see your message Rohit (it got in my spambox). But yes, I
> think the mail I've send just now is pretty much inline with your
> explanation in this mail...
>
> Sander
>
> On 23 Jun 2021, at 07:30, Rohit Yadav  wrote:
>
> 
> My understanding is the plugin was originally started as a repo or work by
> Sander (
> https://github.com/xanzy/terraform-provider-cloudstack/commits/master?after=5e7ccfea50810303a6b205084fb6f0b3eade33ca+314=master)
> who contributed it to the Hashicorp Github org like many other community
> providers and then got it eventually transferred back.
>
> From ACS PMC point of view we're going to take the risk as we've ICLA and
> grants from Sander and agreements over email from all the top contributors.
> I've also gotten emails from other participants including Sander who shared
> their frustration, we've jumped through all the hoops and done our best to
> reach so far, I think Justin you had advised us to get all major
> contributors to agree in the other legal thread but now suddenly we are
> advised to get ICLAs too and from all the contributors. The examples you've
> provided don't have ICLAs or agreements from all contributors.
>
> Originally I did attempt to get Hashicorp (the company, mainly a manager
> and their CTO) to do the CCLA etc but they weren't interested and didnt
> want to get involved but agreed to transfer the repo back to Sander. From
> what I understand the project wasn't Hashicorp company project but was
> started by Sander, was then under their Github org but eventually archived.
> From email exchanges I had with Hashicorp it would unlikely their CTO or
> managers be suing any parties for the initiatives and in fact offered to
> work with ACS community in publishing the Terraform provider under ACS
> official registry. As far as we had inquired Hashicorp the company has no
> interest in maintaining the project any further, but users in ACS community
> need it to be supported. Sander could you confirm if I got anything wrong?
> Thanks.
>
> Regards.
>
> On Wed, 23 Jun, 2021, 10:41 am Justin Mclean, 
> wrote:
>
>> HI,
>>
>> > Justin why do we need Hashicorp? They are not involved or are the owner
>> of the codebase/repos.
>>
>> My understanding was the work was carried out in their repo and that they
>> are probably the IP owner of the codebase. Is that correct?
>>
>> Also, currently [1] redirects to [2], I can see they host of what I
>> assume are releases of the software [3] and I can see major contributors to
>> that repo were/are Hashicorp employees.
>>
>> Kind Regards,
>> Justin
>>
>> 1. http://github.com/hashicorp/terraform-provider-cloudstack
>> 2. https://github.com/xanzy/terraform-provider-cloudstack
>> 3. https://releases.hashicorp.com/terraform-provider-cloudstack/
>
>