Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

[Alan Gates]

Henk kindly pointed me to the KEYS file that I had missed, thank you.

So, +1.  I checked the signatures, the LICENSE, NOTICE, and DISCLAIMER
files.

Alan.

On Tue, Mar 13, 2018 at 10:42 AM, Alan Gates  wrote:

> Per https://www.apache.org/dev/release-distribution#sigs-and-sums
> correctly, the KEYS file is required, hence my comment.
>
> Alan.
>
> On Tue, Mar 13, 2018 at 10:34 AM, Henk P. Penning  wrote:
>
>> On Tue, 13 Mar 2018, Alan Gates wrote:
>>
>> Date: Tue, 13 Mar 2018 18:04:08 +0100
>>> From: Alan Gates 
>>> To: general@incubator.apache.org
>>> Subject: Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release
>>>
>>> ​I can't find a KEYS file anywhere in HAWQ to check the key
>>> against.  There is also no name associated with the key, so I'm not
>>> clear how to check the signature.
>>>
>>
>>   Actually, you don't need a KEYS file to verify a .asc :
>>
>>   % gpg apache-hawq-src-2.3.0.0-incubating.tar.gz.asc
>>   gpg: Signature made Tue 27 Feb 2018 04:35:17 AM CET
>>   gpg:using RSA key CE60F90D1333092A
>>   gpg: Can't check signature: No public key
>>
>>   No public key ; so, fetch it :
>>
>>   % gpg --keyserver pgp.surfnet.nl --recv-key CE60F90D1333092A
>>   gpg: requesting key CE60F90D1333092A from hkp server pgp.surfnet.nl
>>   gpg: key CE60F90D1333092A: public key "Yi Jin "
>> imported
>>   gpg: Total number processed: 1
>>   gpg:   imported: 1  (RSA: 1)
>>
>>   ... and --verify :
>>
>>   % gpg --verify apache-hawq-src-2.3.0.0-incubating.tar.gz.asc
>>   gpg: Signature made Tue 27 Feb 2018 04:35:17 AM CET
>>   gpg:using RSA key CE60F90D1333092A
>>   gpg: Good signature from "Yi Jin "
>>   gpg: WARNING: This key is not certified with a trusted signature!
>>   gpg:  There is no indication that the signature belongs to the
>> owner.
>>   Primary key fingerprint: 41B0 0770 75DF DAFC F809  9A91 CE60 F90D 1333
>> 092A
>>
>>   % gpg --verify apache-hawq-rpm-2.3.0.0-incubating-rc2.tar.gz.asc
>>   gpg: Signature made Tue 27 Feb 2018 04:38:53 AM CET
>>   gpg:using RSA key CE60F90D1333092A
>>   gpg: Good signature from "Yi Jin "
>>   gpg: WARNING: This key is not certified with a trusted signature!
>>   gpg:  There is no indication that the signature belongs to the
>> owner.
>>   Primary key fingerprint: 41B0 0770 75DF DAFC F809  9A91 CE60 F90D 1333
>> 092A
>>
>>   Note :
>>   - Always use long (16-hex) key-id's, because short (8-hex)
>> key-id's often point (also) to fake keys.
>> In your $HOME/.gnupg/gpg.conf configure : keyid-format long
>>   - To check that CE60F90D1333092A is authorised to sign the artifacts,
>> is another matter.
>>
>>   IMHO, KEYS files serve no purpose.
>>
>>   Regards,
>>
>>   Henk Penning
>>
>>    _
>> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
>> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
>> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
>> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>>
>> On Mon, Mar 12, 2018 at 7:56 PM, Roman Shaposhnik 
>>> wrote:
>>>
>>> +1 (binding)

 * checked sigs and checksums
 * checked licenses
 * checked for archive matching git tag

 Thanks,
 Roman.


 On Mon, Mar 12, 2018 at 12:21 PM, Konstantin Boudnik 
 wrote:

> +1 [biding]
>
> - signature check [ok]
> - checksum check [ok]
> - licenses check (RAT) [ok]
>
> I haven't tried to build it because of the complexity of the build
> process and multiplicity of the environment configurations. To lower
> the entry barrier, I would recommend the community to think how to
> wrap these steps into the build system. You can go as far as to
> provide an "official" toolchain for the project. In Bigtop, we even
> provide official Docker containers were people can start working with
> the project in under 2 minutes and without any need for additional
> error prone configuration steps.
> --
>   With regards,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
>
>
> On Tue, Mar 6, 2018 at 6:56 PM, Yi JIN  wrote:
>
>> Hi IPMC members,
>>
>> The PPMC vote for the Apache HAWQ 2.3.0.0-incubating release has
>> passed.
>> So I request IPMC now to vote on this release candidate. Thank you!
>>
>> The release page is here:
>> https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.3.0.0-
>>
> incubating+Release

>
>> The PPMC vote thread is located here:
>> https://lists.apache.org/thread.html/fa5b41cd7461bd729146e10d8f7a54
>>
> 156c818f93e5a1160c42e76

Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

[Alan Gates]

Per https://www.apache.org/dev/release-distribution#sigs-and-sums
correctly, the KEYS file is required, hence my comment.

Alan.

On Tue, Mar 13, 2018 at 10:34 AM, Henk P. Penning  wrote:

> On Tue, 13 Mar 2018, Alan Gates wrote:
>
> Date: Tue, 13 Mar 2018 18:04:08 +0100
>> From: Alan Gates 
>> To: general@incubator.apache.org
>> Subject: Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release
>>
>> ​I can't find a KEYS file anywhere in HAWQ to check the key
>> against.  There is also no name associated with the key, so I'm not
>> clear how to check the signature.
>>
>
>   Actually, you don't need a KEYS file to verify a .asc :
>
>   % gpg apache-hawq-src-2.3.0.0-incubating.tar.gz.asc
>   gpg: Signature made Tue 27 Feb 2018 04:35:17 AM CET
>   gpg:using RSA key CE60F90D1333092A
>   gpg: Can't check signature: No public key
>
>   No public key ; so, fetch it :
>
>   % gpg --keyserver pgp.surfnet.nl --recv-key CE60F90D1333092A
>   gpg: requesting key CE60F90D1333092A from hkp server pgp.surfnet.nl
>   gpg: key CE60F90D1333092A: public key "Yi Jin "
> imported
>   gpg: Total number processed: 1
>   gpg:   imported: 1  (RSA: 1)
>
>   ... and --verify :
>
>   % gpg --verify apache-hawq-src-2.3.0.0-incubating.tar.gz.asc
>   gpg: Signature made Tue 27 Feb 2018 04:35:17 AM CET
>   gpg:using RSA key CE60F90D1333092A
>   gpg: Good signature from "Yi Jin "
>   gpg: WARNING: This key is not certified with a trusted signature!
>   gpg:  There is no indication that the signature belongs to the
> owner.
>   Primary key fingerprint: 41B0 0770 75DF DAFC F809  9A91 CE60 F90D 1333
> 092A
>
>   % gpg --verify apache-hawq-rpm-2.3.0.0-incubating-rc2.tar.gz.asc
>   gpg: Signature made Tue 27 Feb 2018 04:38:53 AM CET
>   gpg:using RSA key CE60F90D1333092A
>   gpg: Good signature from "Yi Jin "
>   gpg: WARNING: This key is not certified with a trusted signature!
>   gpg:  There is no indication that the signature belongs to the
> owner.
>   Primary key fingerprint: 41B0 0770 75DF DAFC F809  9A91 CE60 F90D 1333
> 092A
>
>   Note :
>   - Always use long (16-hex) key-id's, because short (8-hex)
> key-id's often point (also) to fake keys.
> In your $HOME/.gnupg/gpg.conf configure : keyid-format long
>   - To check that CE60F90D1333092A is authorised to sign the artifacts,
> is another matter.
>
>   IMHO, KEYS files serve no purpose.
>
>   Regards,
>
>   Henk Penning
>
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>
> On Mon, Mar 12, 2018 at 7:56 PM, Roman Shaposhnik 
>> wrote:
>>
>> +1 (binding)
>>>
>>> * checked sigs and checksums
>>> * checked licenses
>>> * checked for archive matching git tag
>>>
>>> Thanks,
>>> Roman.
>>>
>>>
>>> On Mon, Mar 12, 2018 at 12:21 PM, Konstantin Boudnik 
>>> wrote:
>>>
 +1 [biding]

 - signature check [ok]
 - checksum check [ok]
 - licenses check (RAT) [ok]

 I haven't tried to build it because of the complexity of the build
 process and multiplicity of the environment configurations. To lower
 the entry barrier, I would recommend the community to think how to
 wrap these steps into the build system. You can go as far as to
 provide an "official" toolchain for the project. In Bigtop, we even
 provide official Docker containers were people can start working with
 the project in under 2 minutes and without any need for additional
 error prone configuration steps.
 --
   With regards,
 Konstantin (Cos) Boudnik
 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622

 Disclaimer: Opinions expressed in this email are those of the author,
 and do not necessarily represent the views of any company the author
 might be affiliated with at the moment of writing.


 On Tue, Mar 6, 2018 at 6:56 PM, Yi JIN  wrote:

> Hi IPMC members,
>
> The PPMC vote for the Apache HAWQ 2.3.0.0-incubating release has
> passed.
> So I request IPMC now to vote on this release candidate. Thank you!
>
> The release page is here:
> https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.3.0.0-
>
 incubating+Release
>>>

> The PPMC vote thread is located here:
> https://lists.apache.org/thread.html/fa5b41cd7461bd729146e10d8f7a54
>
 156c818f93e5a1160c42e76c79@%3Cdev.hawq.apache.org%3E
>>>

> The artifacts can be downloaded here:
> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.3.0.
>
 0-incubating.RC2/
>>>
 The artifacts have been signed with Key : CE60F90D1333092A
>
> All JIRAs completed for this release are tagged with 'FixVersion
> =2.3.0.0-incubating

Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

[Henk P. Penning]

On Tue, 13 Mar 2018, Alan Gates wrote:


Date: Tue, 13 Mar 2018 18:04:08 +0100
From: Alan Gates 
To: general@incubator.apache.org
Subject: Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

​I can't find a KEYS file anywhere in HAWQ to check the key
against.  There is also no name associated with the key, so I'm not
clear how to check the signature.


  Actually, you don't need a KEYS file to verify a .asc :

  % gpg apache-hawq-src-2.3.0.0-incubating.tar.gz.asc
  gpg: Signature made Tue 27 Feb 2018 04:35:17 AM CET
  gpg:using RSA key CE60F90D1333092A
  gpg: Can't check signature: No public key

  No public key ; so, fetch it :

  % gpg --keyserver pgp.surfnet.nl --recv-key CE60F90D1333092A
  gpg: requesting key CE60F90D1333092A from hkp server pgp.surfnet.nl
  gpg: key CE60F90D1333092A: public key "Yi Jin " imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)

  ... and --verify :

  % gpg --verify apache-hawq-src-2.3.0.0-incubating.tar.gz.asc
  gpg: Signature made Tue 27 Feb 2018 04:35:17 AM CET
  gpg:using RSA key CE60F90D1333092A
  gpg: Good signature from "Yi Jin "
  gpg: WARNING: This key is not certified with a trusted signature!
  gpg:  There is no indication that the signature belongs to the owner.
  Primary key fingerprint: 41B0 0770 75DF DAFC F809  9A91 CE60 F90D 1333 092A

  % gpg --verify apache-hawq-rpm-2.3.0.0-incubating-rc2.tar.gz.asc
  gpg: Signature made Tue 27 Feb 2018 04:38:53 AM CET
  gpg:using RSA key CE60F90D1333092A
  gpg: Good signature from "Yi Jin "
  gpg: WARNING: This key is not certified with a trusted signature!
  gpg:  There is no indication that the signature belongs to the owner.
  Primary key fingerprint: 41B0 0770 75DF DAFC F809  9A91 CE60 F90D 1333 092A

  Note :
  - Always use long (16-hex) key-id's, because short (8-hex)
key-id's often point (also) to fake keys.
In your $HOME/.gnupg/gpg.conf configure : keyid-format long
  - To check that CE60F90D1333092A is authorised to sign the artifacts,
is another matter.

  IMHO, KEYS files serve no purpose.

  Regards,

  Henk Penning

   _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/


On Mon, Mar 12, 2018 at 7:56 PM, Roman Shaposhnik 
wrote:


+1 (binding)

* checked sigs and checksums
* checked licenses
* checked for archive matching git tag

Thanks,
Roman.


On Mon, Mar 12, 2018 at 12:21 PM, Konstantin Boudnik 
wrote:

+1 [biding]

- signature check [ok]
- checksum check [ok]
- licenses check (RAT) [ok]

I haven't tried to build it because of the complexity of the build
process and multiplicity of the environment configurations. To lower
the entry barrier, I would recommend the community to think how to
wrap these steps into the build system. You can go as far as to
provide an "official" toolchain for the project. In Bigtop, we even
provide official Docker containers were people can start working with
the project in under 2 minutes and without any need for additional
error prone configuration steps.
--
  With regards,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622

Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.


On Tue, Mar 6, 2018 at 6:56 PM, Yi JIN  wrote:

Hi IPMC members,

The PPMC vote for the Apache HAWQ 2.3.0.0-incubating release has passed.
So I request IPMC now to vote on this release candidate. Thank you!

The release page is here:
https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.3.0.0-

incubating+Release


The PPMC vote thread is located here:
https://lists.apache.org/thread.html/fa5b41cd7461bd729146e10d8f7a54

156c818f93e5a1160c42e76c79@%3Cdev.hawq.apache.org%3E


The artifacts can be downloaded here:
https://dist.apache.org/repos/dist/dev/incubator/hawq/2.3.0.

0-incubating.RC2/

The artifacts have been signed with Key : CE60F90D1333092A

All JIRAs completed for this release are tagged with 'FixVersion
=2.3.0.0-incubating'
https://issues.apache.org/jira/secure/ReleaseNote.jspa?

version=12340262&styleName=Html&projectId=12318826


Please vote accordingly:
[ ] +1, accept as the official Apache HAWQ 2.3.0.0-incubating release
[ ] -1, do not accept as the official Apache HAWQ 2.3.0.0-incubating

release

because...

The vote will run for at least 72 hours.

Best regards,
Yi Jin (yjin)


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

Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

[Alan Gates]

​I can't find a KEYS file anywhere in HAWQ to check the key against.  There
is also no name associated with the key, so I'm not clear how to check the
signature.

Other than that release looks fine.​

On Mon, Mar 12, 2018 at 7:56 PM, Roman Shaposhnik 
wrote:

> +1 (binding)
>
> * checked sigs and checksums
> * checked licenses
> * checked for archive matching git tag
>
> Thanks,
> Roman.
>
>
> On Mon, Mar 12, 2018 at 12:21 PM, Konstantin Boudnik 
> wrote:
> > +1 [biding]
> >
> > - signature check [ok]
> > - checksum check [ok]
> > - licenses check (RAT) [ok]
> >
> > I haven't tried to build it because of the complexity of the build
> > process and multiplicity of the environment configurations. To lower
> > the entry barrier, I would recommend the community to think how to
> > wrap these steps into the build system. You can go as far as to
> > provide an "official" toolchain for the project. In Bigtop, we even
> > provide official Docker containers were people can start working with
> > the project in under 2 minutes and without any need for additional
> > error prone configuration steps.
> > --
> >   With regards,
> > Konstantin (Cos) Boudnik
> > 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
> >
> > Disclaimer: Opinions expressed in this email are those of the author,
> > and do not necessarily represent the views of any company the author
> > might be affiliated with at the moment of writing.
> >
> >
> > On Tue, Mar 6, 2018 at 6:56 PM, Yi JIN  wrote:
> >> Hi IPMC members,
> >>
> >> The PPMC vote for the Apache HAWQ 2.3.0.0-incubating release has passed.
> >> So I request IPMC now to vote on this release candidate. Thank you!
> >>
> >> The release page is here:
> >> https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.3.0.0-
> incubating+Release
> >>
> >> The PPMC vote thread is located here:
> >> https://lists.apache.org/thread.html/fa5b41cd7461bd729146e10d8f7a54
> 156c818f93e5a1160c42e76c79@%3Cdev.hawq.apache.org%3E
> >>
> >> The artifacts can be downloaded here:
> >> https://dist.apache.org/repos/dist/dev/incubator/hawq/2.3.0.
> 0-incubating.RC2/
> >> The artifacts have been signed with Key : CE60F90D1333092A
> >>
> >> All JIRAs completed for this release are tagged with 'FixVersion
> >> =2.3.0.0-incubating'
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12340262&styleName=Html&projectId=12318826
> >>
> >> Please vote accordingly:
> >> [ ] +1, accept as the official Apache HAWQ 2.3.0.0-incubating release
> >> [ ] -1, do not accept as the official Apache HAWQ 2.3.0.0-incubating
> release
> >> because...
> >>
> >> The vote will run for at least 72 hours.
> >>
> >> Best regards,
> >> Yi Jin (yjin)
> >
> > -
> > 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: [VOTE] Accept Pinot into Apache Incubator

[Kevin A. McGrail]

+1 binding.  Apologies if this is a dupe.  I thought I voted days ago.

On Mar 9, 2018 02:11, "kishore g"  wrote:

> Hi all,
>
> I would like to call a VOTE to accept Pinot into the Apache Incubator. The
> full proposal is available on the wiki
> 
>
> Please cast your vote:
>
>   [ ] +1, bring Pinot into Incubator
>   [ ] +0, I don't care either way,
>   [ ] -1, do not bring Pinot into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> Thanks,
> Kishore G
>
> Discussion thread:
> https://lists.apache.org/thread.html/8119f9478ea1811371f1bf6685290b
> 22b57b1a3e0849d1d778d77dcb@%3Cgeneral.incubator.apache.org
>
>
> = Pinot Proposal =
>
> == Abstract ==
>
> Pinot is a distributed columnar storage engine that can ingest data in
> real-time and serve analytical queries at low latency. There are two modes
> of data ingestion - batch and/or realtime. Batch mode allows users to
> generate pinot segments externally using systems such as Hadoop. These
> segments can be uploaded into Pinot via simple curl calls. Pinot can ingest
> data in near real-time from streaming sources such as Kafka. Data ingested
> into Pinot is stored in a columnar format. Pinot provides a SQL like
> interface (PQL) that supports filters, aggregations, and group by
> operations. It does not support joins by design, in order to guarantee
> predictable latency. It leverages other Apache projects such as Zookeeper,
> Kafka, and Helix, along with many libraries from the ASF.
>
> == Proposal ==
>
> Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the
> development happens at LinkedIn with other contributions from Uber and
> Slack. We believe that being a part of Apache Software Foundation will
> improve the diversity and help form a strong community around the project.
>
> LinkedIn submits this proposal to donate the code base to Apache Software
> Foundation. The code is already under Apache License 2.0.  Code and the
> documentation are hosted on Github.
>  * Code: http://github.com/linkedin/pinot
>  * Documentation: https://github.com/linkedin/pinot/wiki
>
>
> == Background ==
>
> LinkedIn, similar to other companies, has many applications that provide
> rich real-time insights to members and customers (internal and external).
> The workload characteristics for these applications vary a lot. Some
> internal applications simply need ad-hoc query capabilities with sub-second
> to multiple seconds latency. But external site facing applications require
> strong SLA even very high workloads. Prior to Pinot, LinkedIn had multiple
> solutions depending on the workload generated by the application and this
> was inefficient. Pinot was developed to be the one single platform that
> addresses all classes of applications. Today at LinkedIn, Pinot powers more
> than 50 site facing products with workload ranging from few queries per
> second to 1000’s of queries per second while maintaining the 99th
> percentile latency which can be as low as few milliseconds. All internal
> dashboards at LinkedIn are powered by Pinot.
>
> == Rationale ==
>
> We believe that requirement to develop rich real-time analytic applications
> is applicable to other organizations. Both Pinot and the interested
> communities would benefit from this work being openly available.
>
> == Current Status ==
>
> Pinot is currently open sourced under the Apache License Version 2.0 and
> available at github.com/linkedin/pinot. All the development is done using
> GitHub Pull Requests. We cut releases on a weekly basis and deploy it at
> LinkedIn. mp-0.1.468 is the latest release tag that is deployed in
> production.
>
> == Meritocracy ==
>
> Following the Apache meritocracy model, we intend to build an open and
> diverse community around Pinot. We will encourage the community to
> contribute to discussion and codebase.
>
> == Community ==
>
> Pinot is currently used extensively at LinkedIn and Uber. Several companies
> have expressed interest in the project. We hope to extend the contributor
> base significantly by bringing Pinot into Apache.
>
> == Core Developers ==
>
> Pinot was started by engineers at LinkedIn, and now has committers from
> Uber.
>
> == Alignment ==
>
> Apache is the most natural home for taking Pinot forward. Pinot leverages
> several existing Apache Projects such as Kafka, Helix, Zookeeper, and Avro.
> As Pinot gains adoption, we plan to add support for the ORC and Parquet
> formats, as well as adding integration with Yarn and Mesos.
>
> == Known Risks ==
>
> === Orphaned Products ===
>
> The risk of the Pinot project being abandoned is minimal. The teams at
> LinkedIn and Uber are highly incentivized to continue development of Pinot
> as it is a critical part of their infrastructure.
>
> === Inexperience with Open Source ===
>
> Post open sourcing, Pinot was completely developed on GitHub. All the
> current developers on Pinot are

Re: [VOTE] Accept Pinot into Apache Incubator

[Felix Cheung]

+1

On Sun, Mar 11, 2018 at 5:34 AM Willem Jiang  wrote:

> +1 (binding)
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>   http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sun, Mar 11, 2018 at 7:51 PM, Pierre Smits 
> wrote:
>
> > +1
> >
> >
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > V.P. Apache Trafodion
> >
> > On Sun, Mar 11, 2018 at 12:59 AM, Julian Hyde  wrote:
> >
> > > +1 (binding)
> > >
> > > Ironic that Druid — a similar project — has just entered incubation
> too.
> > > But of course that is not a conflict. Both are great projects. Good
> luck!
> > >
> > > Julian
> > >
> > >
> > > > On Mar 9, 2018, at 7:37 PM, Carl Steinbach  wrote:
> > > >
> > > > +1 (binding)
> > > >
> > > > On Fri, Mar 9, 2018, 7:29 PM kishore g  wrote:
> > > >
> > > >> Added Jim Jagielski to the mentor's list.
> > > >>
> > > >> On Fri, Mar 9, 2018 at 6:35 PM, Olivier Lamy 
> > wrote:
> > > >>
> > > >>> +1
> > > >>>
> > > >>> On 9 March 2018 at 17:11, kishore g  wrote:
> > > >>>
> > >  Hi all,
> > > 
> > >  I would like to call a VOTE to accept Pinot into the Apache
> > Incubator.
> > > >>> The
> > >  full proposal is available on the wiki
> > >  
> > > 
> > >  Please cast your vote:
> > > 
> > >   [ ] +1, bring Pinot into Incubator
> > >   [ ] +0, I don't care either way,
> > >   [ ] -1, do not bring Pinot into Incubator, because...
> > > 
> > >  The vote will open at least for 72 hours and only votes from the
> > > >>> Incubator
> > >  PMC are binding.
> > > 
> > >  Thanks,
> > >  Kishore G
> > > 
> > >  Discussion thread:
> > > 
> https://lists.apache.org/thread.html/8119f9478ea1811371f1bf6685290b
> > >  22b57b1a3e0849d1d778d77dcb@%3Cgeneral.incubator.apache.org
> > > 
> > > 
> > >  = Pinot Proposal =
> > > 
> > >  == Abstract ==
> > > 
> > >  Pinot is a distributed columnar storage engine that can ingest
> data
> > in
> > >  real-time and serve analytical queries at low latency. There are
> two
> > > >>> modes
> > >  of data ingestion - batch and/or realtime. Batch mode allows users
> > to
> > >  generate pinot segments externally using systems such as Hadoop.
> > These
> > >  segments can be uploaded into Pinot via simple curl calls. Pinot
> can
> > > >>> ingest
> > >  data in near real-time from streaming sources such as Kafka. Data
> > > >>> ingested
> > >  into Pinot is stored in a columnar format. Pinot provides a SQL
> like
> > >  interface (PQL) that supports filters, aggregations, and group by
> > >  operations. It does not support joins by design, in order to
> > guarantee
> > >  predictable latency. It leverages other Apache projects such as
> > > >>> Zookeeper,
> > >  Kafka, and Helix, along with many libraries from the ASF.
> > > 
> > >  == Proposal ==
> > > 
> > >  Pinot was open sourced by LinkedIn and hosted on GitHub. Majority
> of
> > > >> the
> > >  development happens at LinkedIn with other contributions from Uber
> > and
> > >  Slack. We believe that being a part of Apache Software Foundation
> > will
> > >  improve the diversity and help form a strong community around the
> > > >>> project.
> > > 
> > >  LinkedIn submits this proposal to donate the code base to Apache
> > > >> Software
> > >  Foundation. The code is already under Apache License 2.0.  Code
> and
> > > the
> > >  documentation are hosted on Github.
> > >  * Code: http://github.com/linkedin/pinot
> > >  * Documentation: https://github.com/linkedin/pinot/wiki
> > > 
> > > 
> > >  == Background ==
> > > 
> > >  LinkedIn, similar to other companies, has many applications that
> > > >> provide
> > >  rich real-time insights to members and customers (internal and
> > > >> external).
> > >  The workload characteristics for these applications vary a lot.
> Some
> > >  internal applications simply need ad-hoc query capabilities with
> > > >>> sub-second
> > >  to multiple seconds latency. But external site facing applications
> > > >>> require
> > >  strong SLA even very high workloads. Prior to Pinot, LinkedIn had
> > > >>> multiple
> > >  solutions depending on the workload generated by the application
> and
> > > >> this
> > >  was inefficient. Pinot was developed to be the one single platform
> > > that
> > >  addresses all classes of applications. Today at LinkedIn, Pinot
> > powers
> > > >>> more
> > >  than 50 site facing products with workload ranging from few
> queries
> > > per
> > >  second to 1000’s of queries per second while maintaining the 99th
> > >  percentile latency which can be as low as few milliseconds. All
> > > >> internal
> > >  dashboards at LinkedIn are powered by Pinot.
> > > 
> > >  == Rationale ==
> > > 
> > >  We b

Re: Retiring without participation from the PPMC

[John D. Ament]

On Tue, Mar 13, 2018 at 12:31 AM lewis john mcgibbney 
wrote:

> Hi General@,
> What does a podling mentor team do in a situation where a retirement VOTE
> has been put to the podling community with no participation from the PPMC?
> PPMC VOTE's are binding. Are podling mentors considered in this same
> fashion?
> What happens if there are no VOTE's from the PPMC on a retirement VOTE?
> Thanks
> Lewis
>

Technically, the vote to retire a podling is a community vote.  Doesn't
mention PPMC, committers on the podling, etc [1].  The final decision on
retirement is the IPMC's call.  So I believe what you're doing presently is
correct, and it's OK if no PPMC members (though technically the mentors are
on the PPMC) vote.  It's probably a correct sign that retirement makes
sense.

One thing I get stuck on is when people do speak up, I tend to let it
linger too long.

[1]: https://incubator.apache.org/guides/retirement.html


>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>