Re: [VOTE] Release Apache DataSketches-cpp 2.0.0-incubating-rc4

2020-06-22 Thread Evans Ye 
+1 (binding)

What I checked:
* PGP signiture
* checksum
* C++ test tested
* Python wrapper tested

- Evans

leerho  於 2020年6月18日 週四 下午12:31寫道：

> Folks, Please!  We need one more IPMC member to vote on our C++ release,
> which was posted 9 days ago.
> Permalink
> 
> :
>
> We do have customers that are waiting on this release.
>
> Only one of our 5 mentors has voted, (Thank you Furkan!)
>
> Please help us.
>
> Thank you!
>
> Lee.
>
>
>
> On Sat, Jun 13, 2020 at 6:42 PM Justin Mclean 
> wrote:
>
>> Hi
>>
>> +1 (binding)
>>
>> I checked:
>> - incubating in name
>> - signatures and hashes are fine
>> - LICENSE and NOTICE are fine
>> - No unexpected binary files
>> - All source files have ASF headers
>> - Don't have a suitable environment setup to compile
>>
>> Thanks,
>> Justin
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

[VOTE] Release Apache DataSketches-hive 1.1.0-incubating-RC1

2020-06-22 Thread leerho 
Hello IPMC and Apache DataSketches Community,

1. This is a call for vote to release Apache DataSketches-hive version:
 1.1.0-incubating-RC1

NOTE 1: This is the Java Hive adaptor component of the DataSketches
library that enables Apache Hive access to the key sketch algorithms in
production-ready packages: Sketches Included: CPC, FrequentItems, HLL, KLL,
Quantiles, Theta and Tuple.

  A. Results from the PPMC vote:

 - 2 (+1 binding) vote, 2 (+1 non-binding) votes

 - The vote thread can be found at the Permalink:

https://lists.apache.org/thread.html/r38b33a8553e94fabaa71db6dedbc06f7f294aa7bb0ab0d334fb61817%40%3Cdev.datasketches.apache.org%3E

  B. Testing/actions/votes performed by the voters in the PPMC Stage 1:

- Alexander Saydakov (+1 non-binding)
  Checked:
  - gpg signature
  - shasum
  - mvn test
  - mvn install
  - copied resulting .jar to a Hive cluster (with datasketches-java
1.3.0) and run a few example scripts (available on the web site)

- Jon Malkin (+1 non-binding)
  I checked:
  - signature and checksum
  - mvn test and mvn package both work properly
  - no extra binaries or other unexpected files
  - incubating in name
  - LICENSE and NOTICE present, although I don't know enough to
validate content

- Furkan Kamachi (+1 binding)
  I checked:
  - Incubating in name
  - DISCLAIMER-WIP exists
  - LICENSE and NOTICE are fine
  - No unexpected binary files
  - Checked PGP signatures
  - Checked Checksums
  - Code compiles and tests successfully run
  - Apache rat checks are OK

- Evans Ye  (+1 binding)
  Checked:
  - gpg signature
  - sha512 sum
  - maven tests
  - disclaimer, notice, licence look good

2. Source repository:
- https://github.com/apache/incubator-datasketches-hive

Git Tag for this release:
-
https://github.com/apache/incubator-datasketches-hive/tree/1.1.0-incubating-RC1

Git HashId for this release starts with: 22bfbc2

3. The Release Candidate / Zip Repository:
-
https://dist.apache.org/repos/dist/dev/incubator/datasketches/hive/1.1.0-incubating-RC1/

The public signing key can be found in the KEYS file:
- https://dist.apache.org/repos/dist/dev/incubator/datasketches/KEYS

The artifacts have been signed with --keyid-format SHORT : 8CD4A902

4. Repository: Maven Central [Nexus](http://repository.apache.org) (Jar
Artifacts):
-
https://repository.apache.org/content/groups/staging/org/apache/datasketches/datasketches-hive/1.1.0-incubating/

5. Build & Test Guide:
-
https://github.com/apache/incubator-datasketches-hive/blob/1.1.0-incubating-RC1/README.md

6. This is the 2nd stage vote:
   - This voting process will remain open for at least 72 hours
 and until at least 3 (+1) IPMC votes or a majority of (+1) are
acquired.

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks,
Lee Rhodes
lee...@apache.org

[jira] [Comment Edited] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-22 Thread Sheng Zha (Jira) 


[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142496#comment-17142496
 ] 

Sheng Zha edited comment on INCUBATOR-253 at 6/23/20, 12:09 AM:


> Anyone including PPMC members (with hat off) can build a third party artifact 
>but it needs to be clear to potential downloaders/users that said artifact is 
>a third party artifact.

> 3rd party distribution also have different branding and trademark policies 
>they need to comply with.

This makes sense. We plan to make a proposal on how our community will provide 
pre-built binary as third-party releases and review its adherence to the 
branding and trademark policies.

> In general they would also need to be based on released code.

I don't think the incubator has the right to require this given that the apache 
license v2 allows redistribution with or without modification as long as the 
conditions are met.

> in short if it a channel controlled by the (P)PMC then it would not be 
>considered an 3rd party release.

The definition of "control" is ambiguous. As long as the PPMC hat can be on or 
off at will, any declaration of "controlled by the (P)PMC" can be true and 
false at the same time.


was (Author: zhasheng):
> Anyone including PPMC members (with hat off) can build a third party artifact 
>but it needs to be clear to potential downloaders/users that said artifact is 
>a third party artifact.

> 3rd party distribution also have different branding and trademark policies 
>they need to comply with.

This makes sense. We plan to make a proposal on how our community will provide 
pre-built binary as third-party releases that adhere to the branding and 
trademark policies.

> In general they would also need to be based on released code.

I don't think the incubator has the right to require this given that the apache 
license v2 allows redistribution with or without modification as long as the 
conditions are met.

> in short if it a channel controlled by the (P)PMC then it would not be 
>considered an 3rd party release.

The definition of "control" is ambiguous. As long as the PPMC hat can be on or 
off at will, any declaration of "controlled by the (P)PMC" can be true and 
false at the same time.

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-22 Thread Sheng Zha (Jira) 


[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142496#comment-17142496
 ] 

Sheng Zha commented on INCUBATOR-253:
-

> Anyone including PPMC members (with hat off) can build a third party artifact 
>but it needs to be clear to potential downloaders/users that said artifact is 
>a third party artifact.

> 3rd party distribution also have different branding and trademark policies 
>they need to comply with.

This makes sense. We plan to make a proposal on how our community will provide 
pre-built binary as third-party releases that adhere to the branding and 
trademark policies.

> In general they would also need to be based on released code.

I don't think the incubator has the right to require this given that the apache 
license v2 allows redistribution with or without modification as long as the 
conditions are met.

> in short if it a channel controlled by the (P)PMC then it would not be 
>considered an 3rd party release.

The definition of "control" is ambiguous. As long as the PPMC hat can be on or 
off at will, any declaration of "controlled by the (P)PMC" can be true and 
false at the same time.

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-22 Thread Justin Mclean (Jira) 


[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142473#comment-17142473
 ] 

Justin Mclean commented on INCUBATOR-253:
-

See https://issues.apache.org/jira/browse/LEGAL-515 for more info, but in short 
if it a channel controlled by the (P)PMC then it would not be considered an 3rd 
party release.

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-22 Thread Justin Mclean (Jira) 


[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142464#comment-17142464
 ] 

Justin Mclean commented on INCUBATOR-253:
-

3rd party distribution also have different branding and trademark policies they 
need to comply with. In general they would also need to be based on released 
code.

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-22 Thread Paul King (Jira) 


[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142439#comment-17142439
 ] 

Paul King commented on INCUBATOR-253:
-

Anyone including PPMC members (with hat off) can build a third party artifact 
but it needs to be clear to potential downloaders/users that said artifact is a 
third party artifact. You would typically need special arrangements/permission 
for such an artifact to be stored on Apache infrastructure for instance.

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

2020-06-22 Thread Sheng Zha (Jira) 


[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142357#comment-17142357
 ] 

Sheng Zha commented on INCUBATOR-253:
-

> I would be of the opinion that nightly builds (or in fact any build) created 
> by the PPMC are NOT allowed to have category X licensed code.

I'd like to clarify on this. What's the definition of a build that's created by 
the PPMC? Can I, a PPMC member, take my PPMC hat off and make a build? If not, 
does it mean that making a build as an independent individual is a right that 
one waives when joining an apache project as a committer/PPMC?

The viability of the growth of MXNet ecosystem hinges on this point so I'd 
appreciate clear answers on the my questions.

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[RESULT][VOTE] Accept Pegasus into The Apache Incubation

2020-06-22 Thread Gosling Von 
Hi,

Thanks for reviewing and voting for Pegasus into Apache Incubation, I am happy 
to announce the release voting has passed with 7 +1 binding votes, no +0 or -1 
votes. Details are as follows, the voting thread is here[1].


[Binding]

- Justin Mclean
- Duo Zhang
- Gosling Von
- Byung-Gon Chun
- Michael Wall
- Furkan KAMACI
- Kevin A. McGrail


[Not binding]

- Yingchun Lai
- lidong dai
- Guangxu Cheng
- agile6v
- Yu Li
- zhangliang
- Ming Wen


Many thanks for everyone. Pegasus is a very promising project in distributed kv 
storage, and welcome to be involved in the community. Next, we will be working 
on Podling Infrastructure Setup :-)


[1] 
https://lists.apache.org/thread.html/r8930baccc2a55bb2ddd56d7539708dc7f8053ec965b640e5460c4688%40%3Cgeneral.incubator.apache.org%3E
 



Best Regards,
Von Gosling