Re: [VOTE] Have Amoro join the Incubator

[Paul King]

+1 binding

On Sun, Mar 3, 2024 at 11:45 AM Justin Mclean  wrote:
>
> Hi,
>
> Following on from the discussion of the Amoro proposal [1][2], let's vote on 
> having it join the Incubator.
>
> Please cast your vote:
>
> [ ] +1, have it join the Incubator as an incubating project
> [ ] +0, I have no strong opinion either way
> [ ] -1, do not have it join the Incubator because...
>
> Kind Regards,
> Justin
>
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/AmoroProposal
> 2. https://lists.apache.org/thread/7t2bm6x19zq2d79cn8jj2wqd3f2t3k00

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

Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP

[Paul King]

+1 (binding). Good luck!

On Mon, Feb 26, 2024 at 9:25 PM PJ Fanning  wrote:
>
> Hi everyone,
>
> We have positive feedback on the Pekko Vote thread [1] (result [2]).
>
> I'd like to start an official Incubator VOTE thread now.
>
> Below are some facts and project highlights from the incubation phase
> as well as the draft resolution:
>
> * All modules have at least a v1.0.0 release
> * 19 releases (across 12 modules) [3]
> * Evidence of good uptake of the Pekko releases and a large number of
> ecosystem libs now support Pekko - over 100 non Apache libraries use
> Pekko libs under the hood
> * well over 1000 PRs merged
> * 25+ code contributors
> * We've had 3 different release managers to date.
> * dozens more users who have been involved in discussions, code
> reviews, raising issues, etc.
> * We have met all maturity criteria as outlined in [4].
>
>
> Please vote on the resolution pasted below to graduate Apache Pekko
> from the Incubator to the Top Level Project.
>
>  [ ] +1 Graduate Apache Pekko from the Incubator.
>  [ ] +0 No opinion.
>  [ ] -1 Don't graduate Apache Pekko from the Incubator because ...
>
> This vote will open for at least 72 hours.
>
> I would like to thank everyone who have participated in the Apache
> Pekko community. I would also like to thank the Apache Incubator
> community as well as Apache Infrastructure team and general ASF
> community for your support.
>
>
> [1] https://lists.apache.org/thread/q7jjmp7zpcxko607v5hvj514dyf6o8bx
> [2] https://lists.apache.org/thread/tsb7b8bkgfkts1nstmj413qocztj0s5o
> [3] https://incubator.apache.org/projects/pekko.html
> [4] 
> https://cwiki.apache.org/confluence/display/PEKKO/Apache+Maturity+Model+Assessment+for+Pekko
>
>
>
>  ---
>
> Establish the Apache Pekko 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 Pekko: a toolkit and an ecosystem for building
> highly concurrent, distributed, reactive and resilient applications
> for Java and Scala.
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pekko Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
>
> RESOLVED, that the Apache Pekko Project be and hereby is responsible
> for the creation and maintenance of software related to Pekko: a
> toolkit and an ecosystem for building highly concurrent, distributed,
> reactive and resilient applications for Java and Scala.; and be it
> further
>
>
> RESOLVED, that the office of "Vice President, Apache Pekko" 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 Pekko
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Pekko
> 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 Pekko Project:
>
> Claude Warren (claude)
> Jean-Baptiste Onofré (jbonofre)
> Justin Mclean (jmclean)
> PJ Fanning (fanningpj)
> Roman Shaposhnik (rvs)
> Ryan Skraba (rskraba)
> Sheng Wu (wu-sheng)
> Alexandru Nedelcu (alexelcu)
> Arnout Engelen (engelen)
> Dani Schroeter (dsc)
> Greg Methvin (gregm)
> Guobin Li (liguobin)
> He Pin (hepin)
> Johannes Rudolph (jrudolph)
> Jonas Chapuis (jchapuis)
> Matthew de Detrich (mdedetrich)
> Nicolas Vollmar (nvollmar)
> Samuele Resca (samueler)
> Sean Glover (seanglover)
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that PJ Fanning be appointed
> to the office of Vice President, Apache Pekko, 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
> or disqualification, or until a successor is appointed; and be it
> further
>
> RESOLVED, that the Apache Pekko Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Pekko
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pekko podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
>
> Thanks,
> PJ
>
> -
> 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: [DISCUSS] Graduate Apache SDAP (Incubating) as a Top Level Project

[Paul King]

+1 (binding). Good luck!

On Fri, Feb 23, 2024 at 4:02 AM Riley Kuttruff  wrote:
>
> Hi all,
>
> Apache SDAP joined Incubator in October 2017. In the time since, we've
> made significant progress towards maturing our community and our
> project and adopting the Apache Way.
>
> After community discussion [1][2][3], the community has voted [4] that we
> would like to proceed with graduation [5]. We now call upon the Incubator
> PMC to review and discuss our progress and would appreciate any and all
> feedback towards graduation.
>
> Below are some facts and project highlights from the incubation phase as
> well as the draft resolution:
>
> - Our community consists of 21 committers, with 2 being mentors and
> the remaining 19 serving as our PPMC
> - Several pending and planned invites to bring on new committers and/or
> PPMC members from additional organizations
> - Completed 2 releases with 2 release managers - with a 3rd release run by
> a 3rd release manager in progress
> - Our software is currently being utilized by organizations such as NASA
> Jet Propulsion Laboratory, NSF National Center for Atmospheric Research,
> Florida State University, and George Mason University in support of projects
> such as the NASA Sea Level Change Portal, Estimating the Circulation and
> Climate of the Ocean (ECCO) project, GRACE/GRACE-FO, Cloud-based
> Data Match-Up Service, Integrated Digital Earth Analysis System (IDEAS),
> and many others.
> - Opened 400+ PRs across 3 main code repositories, 350+ of which are
> merged or closed (some are pending our next release)
> - Maturity model self assessment [6]
>
> We have resolved all branding issues we are aware of: logo, GitHub,
> Website, etc
>
> We’d like to also extend a sincere thank you to our mentors, current and
> former for their invaluable insight and assistance with getting us to this
> point.
>
> Thank you, Julian, Jörn, Trevor, Lewis, Suneel, and Raphael!
>
> ---
>
> Establish the Apache SDAP 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 an integrated data analytic center for Big Science problems.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache SDAP Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache SDAP Project be and hereby is responsible
> for the creation and maintenance of software related to an integrated data
> analytic center for Big Science problems; and be it further
>
> RESOLVED, that the office of "Vice President, Apache SDAP" 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 SDAP
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache SDAP
> 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 SDAP Project:
>
> - Edward M Armstrong 
> - Nga Thien Chung 
> - Thomas Cram 
> - Frank Greguska 
> - Thomas Huang 
> - Julian Hyde 
> - Joseph C. Jacob 
> - Jason Kang 
> - Riley Kuttruff 
> - Thomas G Loubrieu 
> - Kevin Marlis 
> - Stepheny Perez 
> - Wai Linn Phyo 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Nga Thien Chung
> be appointed to the office of Vice President, Apache SDAP, 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 or disqualification, or until a successor is appointed; and be it
> further
>
> RESOLVED, that the Apache SDAP Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator SDAP
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> SDAP podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> [1] https://lists.apache.org/thread/vjwjmp0h2f22dv423h262cvdg5x7jl03
> [2] https://lists.apache.org/thread/m9vqwv23jdsofwgmhgxg25f5l1v2j7nz
> [3] https://lists.apache.org/thread/4o1qjsk2cly2ppxcsmm2swzd6pcg3lxj
> [4] https://lists.apache.org/thread/qtxlxl4gj6n33wvm164vdxxnwdlppttl
> [5] https://lists.apache.org/thread/rr74c35fojc7ythmcgnoplyjllhbslj4
> [6] https://github.com/apache/incubator-sdap-website/blob/asf-site/maturity.md
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1

[Paul King]

On Wed, Nov 29, 2023 at 5:07 PM PJ Fanning  wrote:
>
> Thanks Paul. I'm not sure if the build works on Windows. The CI is
> Linux based. Most developers on the Pekko project use MacOS or Linux
> to build. I'll log an issue in the hope that someone with a Windows
> computer could look at it.

Perhaps in the "building from source" doco, just add a note that the
build has minimal testing on Windows.

> The AddThis license comes from:
> https://github.com/addthis/stream-lib/blob/master/NOTICE.txt

Okay, fair enough. I guess an entity can have any name. :-)

> This was pulled in due to this line:
> https://github.com/apache/incubator-pekko/blob/8fefca1c81e13d089ed8db85f375eb3538089c43/remote/src/main/java/org/apache/pekko/remote/artery/compress/CountMinSketch.java#L27
>
> Which has links to
> https://github.com/addthis/stream-lib/blob/master/src/main/java/com/clearspring/analytics/stream/frequency/CountMinSketch.java
>
>
> On Wed, 29 Nov 2023 at 00:59, Paul King  wrote:
> >
> > +1 (binding)
> >
> > [X] Download links are valid.
> > [X] Checksums and signatures.
> > [X] LICENSE/NOTICE files exist
> > I did notice "Copyright 2016 AddThis" in the LICENSE file wrt
> > MurmurHash3, something to fix for the next release?
> > Given the accompanying explanation in the file, I don't see this
> > as a showstopper for this release.
> > [X] No unexpected binary files
> > I didn't do an exhaustive check
> > [X] Source files have ASF headers
> > [-] Can compile from source
> > I ran "sbt compile" and "sbt package" but both had errors. A sample:
> > [error] bnd: Invalid value for Bundle-Version, HEAD+20231129-0950
> > does not match [0-9]{1,9}(\.[0-9]{1,9}(\.[0-9]{1,9}(\.[0-9A-Za-z_-]+)?)?)?
> > [error] java.util.zip.ZipException: duplicate entry: 
> > META-INF/MANIFEST.MF
> > ...
> > [error] 
> > D:\tmp\pekko102\apache-pekko-1.0.2-incubating-src-20231115\actor\src\main\java\org\apache\pekko\util\Unsafe.java:25:23:
> > not found: value sun
> > [error]   public static final sun.misc.Unsafe instance;
> > [error]   ^
> > I rarely run sbt, so this could easily be my local setup. I didn't
> > try my linux box. Maybe it would have worked there.
> >
> > I also tested the artifacts in the staging repo with a simple typed
> > actors example in Groovy:
> > https://github.com/paulk-asert/groovy-pekko-gpars/tree/main/src/main/groovy/pekko
> > I used Groovy 4.0.15, the 1.0.2-RC1 artifacts and the Scala 2.13 runtime.
> > It ran without problems.
> >
> > Cheers, Paul.
> >
> > On Sat, Nov 18, 2023 at 11:56 PM PJ Fanning  wrote:
> > >
> > > Hello Incubator Community,
> > >
> > > This is a call for a vote to release Apache Pekko(incubating)
> > > Core version 1.0.2-RC1.
> > >
> > > The discussion thread:
> > > https://lists.apache.org/thread/zy84yk5gxp54bkn81ntlj5ps5o2z9w4j
> > >
> > > Pekko Vote Thread
> > > https://lists.apache.org/thread/0ojxypkm650bhk6pf53cp7h8036jgyol
> > >
> > > Pekko Result:
> > > https://lists.apache.org/thread/mh398gtjm751fq4fhss5c0xfwxnvx2xy
> > >
> > > The release candidate:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.2-RC1/
> > >
> > > This release has been signed with a PGP key, available here:
> > >
> > > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> > >
> > > Git branch for the release:
> > >
> > > https://github.com/apache/incubator-pekko/tree/v1.0.2-RC1
> > > Git commit ID: 58fa510455190bd62d04f92a83c9506a7588d29c
> > >
> > > Release Notes:
> > >
> > > https://nightlies.apache.org/pekko/docs/pekko/1.0/docs/release-notes/index.html#1-0-2
> > >
> > > Please download, verify, and test.
> > >
> > > We have also staged jars in the Apache Nexus Repository. These were
> > > built with the same code
> > > as appears in this Source Release Candidate. We would appreciate if
> > > users could test with these too.
> > > If anyone finds any serious problems with these jars, please also
> > > notify us on this thread.
> > >
> > > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> > >
> > > In sbt, you can add this resolver.
> > >
> > > resolvers += "Apache Pekko Staging" at
> > > "https://repository.apache.org/content/groups/staging;
> > >
> > >

Re: [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1

[Paul King]

+1 (binding)

[X] Download links are valid.
[X] Checksums and signatures.
[X] LICENSE/NOTICE files exist
I did notice "Copyright 2016 AddThis" in the LICENSE file wrt
MurmurHash3, something to fix for the next release?
Given the accompanying explanation in the file, I don't see this
as a showstopper for this release.
[X] No unexpected binary files
I didn't do an exhaustive check
[X] Source files have ASF headers
[-] Can compile from source
I ran "sbt compile" and "sbt package" but both had errors. A sample:
[error] bnd: Invalid value for Bundle-Version, HEAD+20231129-0950
does not match [0-9]{1,9}(\.[0-9]{1,9}(\.[0-9]{1,9}(\.[0-9A-Za-z_-]+)?)?)?
[error] java.util.zip.ZipException: duplicate entry: META-INF/MANIFEST.MF
...
[error] 
D:\tmp\pekko102\apache-pekko-1.0.2-incubating-src-20231115\actor\src\main\java\org\apache\pekko\util\Unsafe.java:25:23:
not found: value sun
[error]   public static final sun.misc.Unsafe instance;
[error]   ^
I rarely run sbt, so this could easily be my local setup. I didn't
try my linux box. Maybe it would have worked there.

I also tested the artifacts in the staging repo with a simple typed
actors example in Groovy:
https://github.com/paulk-asert/groovy-pekko-gpars/tree/main/src/main/groovy/pekko
I used Groovy 4.0.15, the 1.0.2-RC1 artifacts and the Scala 2.13 runtime.
It ran without problems.

Cheers, Paul.

On Sat, Nov 18, 2023 at 11:56 PM PJ Fanning  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache Pekko(incubating)
> Core version 1.0.2-RC1.
>
> The discussion thread:
> https://lists.apache.org/thread/zy84yk5gxp54bkn81ntlj5ps5o2z9w4j
>
> Pekko Vote Thread
> https://lists.apache.org/thread/0ojxypkm650bhk6pf53cp7h8036jgyol
>
> Pekko Result:
> https://lists.apache.org/thread/mh398gtjm751fq4fhss5c0xfwxnvx2xy
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.2-RC1/
>
> This release has been signed with a PGP key, available here:
>
> https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
>
> Git branch for the release:
>
> https://github.com/apache/incubator-pekko/tree/v1.0.2-RC1
> Git commit ID: 58fa510455190bd62d04f92a83c9506a7588d29c
>
> Release Notes:
>
> https://nightlies.apache.org/pekko/docs/pekko/1.0/docs/release-notes/index.html#1-0-2
>
> Please download, verify, and test.
>
> We have also staged jars in the Apache Nexus Repository. These were
> built with the same code
> as appears in this Source Release Candidate. We would appreciate if
> users could test with these too.
> If anyone finds any serious problems with these jars, please also
> notify us on this thread.
>
> https://repository.apache.org/content/groups/staging/org/apache/pekko/
>
> In sbt, you can add this resolver.
>
> resolvers += "Apache Pekko Staging" at
> "https://repository.apache.org/content/groups/staging;
>
>
> The vote will be left open for at least 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about Apache Pekko, please see https://pekko.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] Source files have ASF headers
> [ ] Can compile from source
>
> To compile from the source, please refer to:
>
> https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
>
> Some notes about verifying downloads can be found at:
>
> https://pekko.apache.org/download.html#verifying-downloads
>
>
> Here is my +1 (binding).
>
> Thanks,
>
> PJ Fanning
>
> -
> 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] Release Apache Pekko(incubating) Core 1.0.2-RC1

[Paul King]

I'll take a look.

On Mon, Nov 27, 2023 at 11:46 PM PJ Fanning  wrote:
>
> Hi everyone,
>
> This RC includes a security hardening change. I am wondering if any Pekko 
> mentors or any other Incubator PMC member might have time to review the RC 
> artifacts so that we can do a release.
>
> Thanks,
> PJ
>
> On 2023/11/24 13:05:48 Matthew de Detrich wrote:
> > Carrying over my +1 from
> > https://lists.apache.org/thread/skqfzys7g32b4f4hvlby3jjj2fcct261
> >
> > Regards
> >
> > On Sat, Nov 18, 2023 at 2:56 PM PJ Fanning  wrote:
> >
> > > Hello Incubator Community,
> > >
> > > This is a call for a vote to release Apache Pekko(incubating)
> > > Core version 1.0.2-RC1.
> > >
> > > The discussion thread:
> > > https://lists.apache.org/thread/zy84yk5gxp54bkn81ntlj5ps5o2z9w4j
> > >
> > > Pekko Vote Thread
> > > https://lists.apache.org/thread/0ojxypkm650bhk6pf53cp7h8036jgyol
> > >
> > > Pekko Result:
> > > https://lists.apache.org/thread/mh398gtjm751fq4fhss5c0xfwxnvx2xy
> > >
> > > The release candidate:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.2-RC1/
> > >
> > > This release has been signed with a PGP key, available here:
> > >
> > > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> > >
> > > Git branch for the release:
> > >
> > > https://github.com/apache/incubator-pekko/tree/v1.0.2-RC1
> > > Git commit ID: 58fa510455190bd62d04f92a83c9506a7588d29c
> > >
> > > Release Notes:
> > >
> > >
> > > https://nightlies.apache.org/pekko/docs/pekko/1.0/docs/release-notes/index.html#1-0-2
> > >
> > > Please download, verify, and test.
> > >
> > > We have also staged jars in the Apache Nexus Repository. These were
> > > built with the same code
> > > as appears in this Source Release Candidate. We would appreciate if
> > > users could test with these too.
> > > If anyone finds any serious problems with these jars, please also
> > > notify us on this thread.
> > >
> > > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> > >
> > > In sbt, you can add this resolver.
> > >
> > > resolvers += "Apache Pekko Staging" at
> > > "https://repository.apache.org/content/groups/staging;
> > >
> > >
> > > The vote will be left open for at least 72 hours.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > To learn more about Apache Pekko, please see https://pekko.apache.org/
> > >
> > > Checklist for reference:
> > >
> > > [ ] Download links are valid.
> > > [ ] Checksums and signatures.
> > > [ ] LICENSE/NOTICE files exist
> > > [ ] No unexpected binary files
> > > [ ] Source files have ASF headers
> > > [ ] Can compile from source
> > >
> > > To compile from the source, please refer to:
> > >
> > >
> > > https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
> > >
> > > Some notes about verifying downloads can be found at:
> > >
> > > https://pekko.apache.org/download.html#verifying-downloads
> > >
> > >
> > > Here is my +1 (binding).
> > >
> > > Thanks,
> > >
> > > PJ Fanning
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > --
> >
> > Matthew de Detrich
> >
> > *Aiven Deutschland GmbH*
> >
> > Immanuelkirchstraße 26, 10405 Berlin
> >
> > Alexanderufer 3-7, 10117 Berlin
> >
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >
> > *m:* +491603708037
> >
> > *w:* aiven.io *e:* matthew.dedetr...@aiven.io
> >
>
> -
> 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] Retirement of the Apache DataLab

[Paul King]

+1 binding

On Wed, Aug 9, 2023 at 7:28 PM Ruslan Kulynych  wrote:
>
> Hi all,
>
> Based on discussion[1], I would like to call for a vote to retire the Apache 
> DataLab.
>
> The voting will last for at least one week to ensure that everyone has time 
> to express their opinions.
>
> Please vote accordingly:
>
> [] +1 Approve
> [] +0 No opinion
> [] -1 Disapprove with a reason
>
> [1]: https://lists.apache.org/thread/k3zsksrkd5k0147pxzqndrhgsg2o6x6j
>
> Thank you all for your participation.
>
> Best regards,
> Ruslan Kulynych
>
> -
> 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] Release Apache Wayang (Incubating) v0.7.1 RC3

[Paul King]

+1 (binding)

I checked LICENSE, NOTICE, DISCLAIMER, checksum and signature.
I see Chris has given you useful input on other aspects in the podling
vote, so I won't duplicate.
"mvn clean install" worked fine on Ubuntu but failed for me on Windows
(could be my setup).

For the vote email, you normally wouldn't have the "or" part of your
clause "at least 72 hours or until the necessary number
of votes are reached". -1 votes might come in during the 72 hours but
after 3 +1 votes.

For the NOTICE file, I suggest adding a line above the "Copyright 2016
Sebastian Kruse" entry, something like:
Some of the files under
wayang-commons/wayang-utils-profile-db/src/main/java/org/apache/wayang/commons/util/profiledb
have the following copyright:

I also checked the 0.7.1 artifacts with my Whiskey Wayang clustering
example here:
https://github.com/paulk-asert/groovy-data-science/tree/master/subprojects/WhiskeyWayang
I used Groovy 5 (alpha-1), JDK11, Wayang 0.7.1, Scala 2.12. All worked
with no issues.

Cheers, Paul.




On Sun, Sep 10, 2023 at 3:19 AM Gláucia Esppenchutz
 wrote:
>
> Hello everyone,
>
> This calls for a vote to release Release Apache Wayang (Incubating) v0.7.1
> RC3.
> The Apache Wayang voted on and approved a proposal to release Apache Wayang
> (Incubating) version v0.7.1 RC3.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/c6d59nfmjq4gs2sfhh1n5gf4c6hxy5vb
>
> Community vote result thread:
>
> https://lists.apache.org/thread/hlc0dh2mwbpwmd9oc1s1oh7l7lj7od36
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/wayang/0.7.1/rc3/
>
> Git tag for the release:
>
> https://github.com/apache/incubator-wayang/tree/wayang-0.7.1
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/wayang/KEYS
>
> How to build:
>
> https://github.com/apache/incubator-wayang/tree/wayang-0.7.1#building
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> --
> Gláucia Esppenchutz

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

Re: is it ok to modify copyright headers that have no end year?

[Paul King]

IANAL, but the advice I've been given informally by IP lawyer friends many
years ago is don't change the existing copyright.

You could instead amend to something like:

Original version:
> Copyright (C) since 2016 Lightbend Inc.
> Subsequent changes made by the Apache Pekko community:
> Copyright 2022 The Apache Software Foundation.


Also, at the time, it was commented by the same lawyer folks that in many
(but not all) jurisdictions, you can leave the year out of individual files
as long as you have a generic NOTICE file with the year range, e.g.
2022-2023 for Pekko. The date specifics for any individual file/change can
be determined "Ex Post Facto" from the version control system. But I
presume the LEGAL folks will give you further up to date info.

Cheers, Paul.


Virus-free.www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Tue, Jun 27, 2023 at 12:40 AM PJ Fanning  wrote:

> Hi everyone,
>
> The Pekko community is working on a release of our core repository. We
> have a number of other repositories that we will release later.
>
> In one of these downstream repositories, the source code has Lightbend
> copyrights that say (example [1]):
>
> Copyright (C) since 2016 Lightbend Inc.
>
> Since the Pekko forked this code at a point in September 2022, is it
> ok to change this copyright to this?
>
> Copyright (C) 2016-2022 Lightbend Inc.
>
> It doesn't seem right to leave the copyright claim open ended and
> effectively implying that any changes made this year by the Apache
> Pekko community are covered by Lightbend copyright.
>
> Generally, I wouldn't modify any headers like this but this one seems
> to require modification.
>
> Any insights would be appreciated.
>
> Regards,
> PJ
>
> [1]
> https://github.com/apache/incubator-pekko-connectors/blob/178795f6882e2d06524962f30359691889489fd5/s3/src/main/scala/org/apache/pekko/stream/connectors/s3/Utils.scala#L11
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Retire PageSpeed

[Paul King]

+1

On Tue, Mar 14, 2023 at 6:47 AM Christian Grobmeier 
wrote:

> Hello,
>
> as recently discussed, I think the PageSpeed podling is ready for
> retirement.
>
> https://lists.apache.org/thread/jxw7mqmpcfxxp0mnnx28o0k78tym507b
>
> There has been no activity for a while; there are no signs of change soon.
>
> Please vote:
>
> [ ] +1, retire
> [ ] -1 don't retire, because...
>
> Please don't hesitate to vote -1 if you feel this podling should remain.
>
> This vote will be kept open for at least the usual 72 hours.
>
> Kind regards,
> Christian
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Retire Hivemall from Incubator

[Paul King]

+1 to retire (binding)

On Sun, Aug 28, 2022 at 4:57 PM Calvin Kirs  wrote:
>
> Hi IPMC,
>
> Hivemall has been incubating since 2016-09-13.
>
> From last year, activity has been low and the chances of attracting new
> committers and building a vibrant community seem very slim at this point.
>
> The dev community vote was started by the PPMC for over a month and
> can be found here[1],[2]
>
> I therefore propose to retire Hivemall from the Incubator.
>
> I want to start this official vote.
>
> Voting will start now and will remain open for at least 72 hours.
>
> Notice: Because the dev vote didn't get enough +1's, this vote is not
> the same as usual, it's not a laze vote.
>
> [ ] +1 Retire the project
> [ ] +0 No opinion.
> [ ] -1 Do not retire the project because...
>
> [1]https://lists.apache.org/thread/3s7bjgqm7864qbwnf1ny3lszklm65sgn
> [2]https://lists.apache.org/thread/cv267tds166z7vtbzjt46nrz26xhzgvb
>
> --
> Best wishes！
> CalvinKirs
>
> -
> 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] Release Apache EventMesh(Incubating) 1.5.0-rc0

[Paul King]

Yes, the build file is using (just a little) Groovy 3 syntax (new in
Gradle 7). You could revert to older style syntax but it would
probably be better to have a bootstrap step that downloaded the gradle
wrapper and then use the wrapper in all of your instructions. The
Groovy build has such a setup. Let me know if you need a PR (for the
English instructions anyway). You could then use older Gradle versions
to bootstrap and then gradlew from then on. It would be considered
better practice in terms of reproducible builds.

I noticed also that you seem to have "gradlew.bat" in your source zip.
Is that an oversight? I couldn't see where you removed other gradle
wrapper-related artifacts in your build file - though there doesn't
seem to be any others which is usual practice currently.

Also, it seems this commit splattered over the copyright notice lines
from the gradle supplied gradlew/gradlew.bat files in the main source
repo:
https://github.com/apache/incubator-eventmesh/commit/032bb0d8b09
I didn't check if any other files are splattered in the same way in
other commits but it might be worthwhile to do a bit of an audit.

+1 (binding) but only because of the WIP disclaimer (because of the
issue mentioned above)

I checked:
- incubating in name
- signatures and hashes okay
- disclaimer exists (WIP)
- LICENSE and NOTICE seem okay
- no unexpected binary files (but I suspect gradlew.bat is an oversight)
- headers seem okay apart from gradlew.bat which shouldn't be there I suspect.


Cheers, Paul.


On Wed, Jun 29, 2022 at 7:35 PM wenjun  wrote:
>
> Hi Justin,
>
> Thanks for your check, vote, and suggestion, the build error may due
> to an incompatible version of gradle, the gradle version may need to
> be higher than 7.
>
> And I will add the build step to README soon, and modify the download
> way in EventMesh doc to use ASF release rather than github.
>
>
> Thanks,
> Wenjun
>
> On Wed, Jun 29, 2022 at 1:31 PM Justin Mclean  
> wrote:
> >
> > Hi,
> >
> > +1 (binding) if it can be built from the source release.
> >
> > I checked:
> > - incubating in name
> > - signatures and hashes are fine
> > - disclaimer exists (WIP)
> > - LICENSE and NOTICE seem fine
> > - no unexpected binary files
> > - ASF files have ASF headers
> > - Was unable to compile from source
> >
> > Can someone confirm you can build this from the source release? I’m getting 
> > an error in the gradle build file, but it may just be my setup.
> >
> > Error is:
> > Could not compile build file 
> > '/Users/justinmclean/ApacheEventMesh/apache-eventmesh-1.5.0-incubating-src/build.gradle'.
> > > startup failed:
> >   build file 
> > '/Users/justinmclean/ApacheEventMesh/apache-eventmesh-1.5.0-incubating-src/build.gradle':
> >  116: unexpected token: ) @ line 116, column 105.
> >  dist/lib").list()).orElseGet(() -> new S
> >
> > It would also be nice to include instructions on how to build in the 
> > README. On the page here [1] it states "Download and extract the source 
> > code of the latest release from GitHub releases.”. Please do not recommend 
> > this, please recommend instead that people use the offical ASF releases.
> >
> > Kind Regards,
> > Justin
> >
> > 1. 
> > https://github.com/apache/incubator-eventmesh/blob/master/docs/en/installation/01-runtime.md
> > -
> > 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
>

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

Re: [VOTE] Graduate Apache InLong(Incubating) as a TLP

[Paul King]

+1 (binding)
Best of luck going forward!

Cheers, Paul.

On Wed, May 25, 2022 at 4:33 PM Charles Zhang  wrote:
>
> Dear Apache Incubator Community,
>
>
> The InLong community has a discussion thread [1], passed the community vote
> [2], and the vote result is published [3]. We have discussed the graduation
> for InLong in the Incubator Community [4], where no issues were raised and
> lots of positive responses were received.
>
>
> I would like to start this voting thread to request graduating Apache
> InLong (incubating) from the incubator as a TLP. Please provide your vote
> as one of the following options:
>
> [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
>
> [ ] +0 No opinion.
>
> [ ] -1 No, the InLong project is not ready to graduate, because ...
>
>
> The VOTE will remain open for at least 72 hours.
>
>
> Since incubating in ASF, the project itself has become more mature and
>
> stable. The following is a brief summary of the project and community
>
> during the incubation:
>
>
> - 11 versions were released by 6 different release managers, of which 5
>
> versions are the original TubeMQ, and 6 versions are after the name was
>
> changed to InLong. The release cadence is about 2 months [5].
>
>
> - 10 new Committers and 3 PPMCs were added during incubating, they are from
>
> 4 different organizations. All PPMCs and Committers are spread across 8
>
> different organizations [6].
>
>
> - 101 unique code developers [7].
>
>
> - Closed more than 2200 issues, with an average of 200 issues per version
>
> [8].
>
>
> - All the dependencies were reviewed and ensured they do not bring any
>
> license issues [9].
>
>
> - Evaluated the InLong project and self-checked the InLong maturity model
>
> [10] and the pre-graduation Check [11].
>
>
> - Well and Complete documentation for contributors and users [12].
>
>
> - Created channels like Email, Slack, Twitter, WeChat, and GitHub
>
> Discussions to communicate, with more than 650 subscribers.
>
>
> - Actively participated in or held more than 15 meetups to increase
>
> community influence.
>
>
> Please see the proposed board resolution below and let us know what you
>
> think. The initial PMC members were passed by the discussion and invitation
>
> [13].
>
>
> [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
>
> [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
>
> [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
>
> [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
>
> [5] https://inlong.apache.org/download/main/
>
> [6] https://whimsy.apache.org/roster/ppmc/inlong
>
> [7] https://github.com/apache/incubator-inlong/graphs/contributors
>
> [8]
>
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
>
> [9] https://github.com/apache/incubator-inlong/tree/master/licenses
>
> [10]
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
>
> [11]
>
> https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
>
> [12] https://inlong.apache.org/docs/next/introduction
>
> [13] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
>
>
> --
>
> Establish the Apache InLong 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 one-stop data integration framework that provides
>
> automatic, secure, and reliable data transmission capabilities. InLong
>
> supports both batch and stream data processing at the same time, which
>
> offers great power to build data analysis, modeling, and other real-time
>
> applications based on streaming data.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache InLong Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache InLong Project be and hereby is responsible
>
> for the creation and maintenance of software related to a one-stop data
>
> integration framework that provides automatic, secure, and reliable data
>
> transmission capabilities. InLong supports both batch and stream data
>
> processing at the same time, which offers great power to build data
>
> analysis, modeling, and other real-time applications based on streaming
>
> data; and be it further
>
> RESOLVED, that the office of "Vice President, Apache InLong" 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 InLong
>
> Project, and to have primary responsibility for 

Re: [VOTE] Release Apache NLPCraft (incubating) v 0.9.0

[Paul King]

+1 (binding) carrying forward my vote and comments from PPMC vote thread.

On Sat, Jul 31, 2021 at 3:34 AM Aaron Radzinski  wrote:
>
> Hello all,
> This is a call for a vote to release Apache NLPCraft (incubating)
> version 0.9.0. Apache NLPCraft is a library for adding a natural
> language interface to any application.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft (Incubating) version 0.9.0. We would like to
> request the Incubator PMC members review and vote on this incubator
> release.
>
> Release information:
> 1. PPMC vote result thread:
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202107.mbox/%3CCACwEJt-vcEO6PO7Q2jm2JoypSduzwuVL-z1_7gCzDH24SG24mw%40mail.gmail.com%3E
> 2. Release location:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/0.9.0/
> 3. Git tag: https://github.com/apache/incubator-nlpcraft/tree/v0.9.0
> 4. JIRA issues fixed in release:
> https://issues.apache.org/jira/projects/NLPCRAFT/versions/12347778
> 5. KEYS file: 
> https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS
>
> PPMC vote has already provided a required majority approval and
> therefore this vote is a lazy consensus vote open for 72 hours.
>
> Please vote accordingly:
> +1 approve
> +0 no opinion
> -1 disapprove with the reason
>
> Thank you,
> Aaron.
> ---
> On behalf of NLPCraft community
>
> -
> 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] Graduate Apache Pinot as TLP

[Paul King]

+1 binding, good luck!

On Wed, Jun 23, 2021 at 5:44 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
> <
> 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 NLPCraft (incubating) v 0.8.0

[Paul King]

+1 (binding) carrying over my dev vote


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Jun 9, 2021 at 2:39 AM Aaron Radzinski 
wrote:

> Hello all,
> This is a call for a vote to release Apache NLPCraft (incubating)
> version 0.8.0. Apache NLPCraft is a library for adding a natural
> language interface to any application.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft (Incubating) version 0.8.0. We would like to
> request the Incubator PMC members review and vote on this incubator
> release.
>
> Release information:
> 1. PPMC vote result thread:
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202106.mbox/
> 
> 2. Release location:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/0.8.0/
> 3. Git tag: https://github.com/apache/incubator-nlpcraft/tree/v0.8.0
> 4. JIRA issues fixed in release:
> https://issues.apache.org/jira/projects/NLPCRAFT/versions/12350193
> 5. KEYS file:
> https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS
>
> PPMC vote has already provided a required majority approval and
> therefore this vote is a lazy consensus vote open for 72 hours.
>
> Please vote accordingly:
> +1 approve
> +0 no opinion
> -1 disapprove with the reason
>
> Thank you,
> Aaron.
> ---
> On behalf of NLPCraft community
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache NLPCraft - Java Client (incubating) 0.7.5

[Paul King]

+1 binding from me, carrying over my vote

On Sat, May 22, 2021 at 11:29 AM Aaron Radzinski 
wrote:

> Hello all,
> This is a call for a vote to release Apache NLPCraft - Java Client
> (incubating) version 0.7.5. Apache NLPCraft is a library for adding a
> natural language interface to any application.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft - Java Client (Incubating) version 0.7.5. We would
> like to request the Incubator PMC members review and vote on this incubator
> release.
>
> Release information:
> 1. PPMC vote result thread:
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202105.mbox/
> 
> 2. Release location:
>
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/java-client/0.7.5/
> 3. Git tag:
> https://github.com/apache/incubator-nlpcraft-java-client/tree/v0.7.5
> 4. JIRA issues fixed in release:
> https://issues.apache.org/jira/projects/NLPCRAFT/versions/12349604
> 5. KEYS file:
> https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS
>
> PPMC vote has already provided a required majority approval and hence this
> vote is a lazy consensus vote open for 72 hours.
>
> Please vote accordingly:
> +1 approve
> +0 no opinion
> -1 disapprove with the reason
>
> Thank you,
> Aaron.
> ---
> On behalf of NLPCraft community
>

Re: [VOTE] Release Apache NLPCraft (incubating) 0.7.5

[Paul King]

+1 carrying forward my dev vote after the license/notice tweaks
I don't think there is an issue with the license of the file mentioned,
just the appropriate changes to the license/notice wording to ensure the
licensing condition is properly understandable. And I think some other
tweaks to license/notice have been mentioned previously and are partly
adjusted already. In any case the WIP disclaimer accounts for the needed
changes.

On Sun, May 16, 2021 at 11:25 AM Aaron Radzinski 
wrote:

> Hello all,
> This is a call for a vote to release Apache NLPCraft (incubating)
> version 0.7.5. Apache NLPCraft is a library for adding a natural language
> interface to any application.
>
> NOTE: this is an amended release with fixes for LICENSE and NOTICE files.
> New DISCLAIMER-WIP was also added to the release. No other changes were
> made. Release version 0.7.5 has not changed.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft (Incubating) version 0.7.5. We would like to
> request the Incubator PMC members review and vote on this incubator
> release.
>
> Release information:
> 1. PPMC vote result thread:
>
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202105.mbox/%3cCALV17Qp_roGvs6jvR09zdXX0x99=mtefuax1bhtnw5cbsvk...@mail.gmail.com%3e
> 2. Release location:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/0.7.5/
> 3. Git tag: https://github.com/apache/incubator-nlpcraft/tree/v0.7.5
> 4. JIRA issues fixed in release:
> https://issues.apache.org/jira/projects/NLPCRAFT/versions/12349604
> 5. KEYS file:
> https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS
>
> The vote will be open for at least 72 hours or until a necessary number
> of votes are reached.
>
> Please vote accordingly:
> +1 approve
> +0 no opinion
> -1 disapprove with the reason
>
> Aaron,
> ---
> Thank you,
> On behalf of NLPCraft community
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc3

[Paul King]

That makes sense. I equated "Unlicense" with the informal English usage of
"unlicensed" at first glance.
A possible improvement might be to use "Public domain (unlicense.org)"
instead of "Unlicense"
but perhaps others are more aware of that reference.

Cheers, Paul.

On Wed, Mar 3, 2021 at 7:34 AM Leonard Lausen  wrote:

> Thank you Paul for voting on the release.
>
> On 2021/03/02 03:53:26, Paul King  wrote:
>
> > * LICENSE file mentions 3rdparty/tvm/3rdparty/rang as "Unlicense". It
> would
> > be good to clarify that.
>
> You can refer to line 207-211 in our LICENSE file, which state that the the
> license of each subcomponent is available at the path of the subcomponent
> as
> long as nothing else is noted in our LICENSE file. So in the case of
> 3rdparty/tvm/3rdparty/rang, we request our users to take a look at
> 3rdparty/tvm/3rdparty/rang folder and open
> 3rdparty/tvm/3rdparty/rang/LICENSE
> to find the license text of the Unlicense.
>
> Best regards
> Leonard
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.8.0.rc3

[Paul King]

+1 (binding)

Checked:
- LICENSE and NOTICE seem okay
- DISCLAIMER-WIP exists
- Incubating in name
- Checksum and signature okay
- No unexpected binary file
- Built shared library using cmake (without CUDA)
- Built Java/Scala jars (also works for Groovy)

Comments:
* As others have noted, please fix LICENSE, NOTICE and DISCLAIMER-WIP files
moving forward.
* LICENSE file mentions 3rdparty/tvm/3rdparty/rang as "Unlicense". It would
be good to clarify that.
* Also a minor thing which could be improved: "What's New" section in
README.md stops at version 1.5.1. It would be great to keep that section
updated or point to some website if that info is elsewhere.
* You reference KEYS in dev space but also have one in the release space
at: https://dist.apache.org/repos/dist/release/incubator/mxnet/. I'd
encourage you just to use the release one (keeping it updated as needed)
and delete the dev one. This would avoid having two (potentially out of
sync) sources of truth.
* I had to manually copy some .a/.so files from root directory to lib (I
could have done a step wrong)
* I had to use JDK8 to build jars (didn't see that in instructions I was
following but I could have missed it)
* Built jars had version INTERNAL, I was expecting 1.8.0.rc3 or similar
* I was planning to run my Groovy data science example against the jar but
the produced jars didn't seem complete (perhaps my lack of understanding of
steps required)

Cheers, Paul.

On Mon, Jan 25, 2021 at 12:37 AM Skalicky, Sam 
wrote:

> Dear community,
>
> This is a call for a releasing Apache MXNet (incubating) 1.8.0, release
> candidate 3.
>
> Apache MXNet (incubating) community has voted and approved the release.
>
> Vote thread:
>
> https://lists.apache.org/thread.html/r42511b3c24a6df9f07a502dd0afd9db514b2592c30c26b90ffbd36ce%40%3Cdev.mxnet.apache.org%3E
>
> Result thread:
>
> https://lists.apache.org/thread.html/r4aa42956b2a9c417e10043dd12a16e926d0a11e8b0e7befeac3fb242%40%3Cdev.mxnet.apache.org%3E
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.8.0.rc3
>
> The tag to be voted upon is 1.8.0.rc3:
> https://github.com/apache/incubator-mxnet/releases/tag/1.8.0.rc3
>
> The release hash is 2fc0706874531fdfdbe49819eae0c88f8016eee3:
>
> https://github.com/apache/incubator-mxnet/commit/2fc0706874531fdfdbe49819eae0c88f8016eee3
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
>
> For information about the contents of this release, see:
> https://cwiki.apache.org/confluence/display/MXNET/1.8.0+Release+Notes
>
> Here are the changes comparing to 1.8.0.rc2:
> * Updated LICENSE & rat checker
> * Extensions bugfixes
> * fix for R builds
> * Upgrade to oneDNN v1.7 with required bugfixes
> * Fix for testing with CUDA 11, remove cleanup on side threads
> * Fix for building CUDA 11 with Windows
> * Remove temporary fix for RNN in MKLDNN
>
> The vote will be open for 72 hours.
> [ ] +1 release this package as #
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
>
> Best regards,
> Sam Skalicky
>

Re: [DISCUSS] Graduate Apache Daffodil to a top-level project

[Paul King]

+1 (binding)

Cheers, Paul.

On Fri, Feb 5, 2021 at 5:01 AM Mike Beckerle  wrote:

> Incubator Folks,
>
> We have completed a vote on our community list d...@daffodil.apache.org as
> follows:
>
> Vote Thread:
>
> https://lists.apache.org/thread.html/r91af73ae28284945ffe881cea7877766213eaa405da21e233d85eb83%40%3Cdev.daffodil.apache.org%3E
>
> In summary, we have all +1 votes including all 3 mentors.
>
> Our maturity model can be reviewed here:
>
>
> https://cwiki.apache.org/confluence/display/DAFFODIL/Apache+Daffodil+Maturity+Model+Assesment
>
> If there is anyone in the IPMC that has any questions or concerns that
> would block our ability to graduate, please bring these issues into this
> discussion.
>
> Unless there are issues that need to be resolved, this discussion will end
> next Tuesday, Feb 8 2021. 5pm ET.US (UTC-5) (that is 72 hours of weekdays)
>
> If this discussion produces a positive consensus or no objections, I will
> proceed to a vote using lazy consensus
> https://www.apache.org/foundation/voting.html.
>
> Regards,
> Mike Beckerle
> Daffodil PPMC, Committer
>

Re: [DISCUSS] Graduate Apache DolphinScheduler (incubating) as a TLP

[Paul King]

+1 (binding)

Cheers, Paul.

On Fri, Feb 5, 2021 at 9:36 PM Gang Li  wrote:

> Hi all,
> After discussion with the community [1] and [2], and a positive vote
> result [3].
> We'd like to bring this to a discussing at the IPMC.
>
> Please see the proposed resolution below and let us know what do you think.
>
> A few status to help with the discussion:
>
> - Released 8 Apache releases, through 5 different release managers
> - Invited 14 new committers (all accepted)
> - Invited 2 new PPMC members (all accepted)
> - Apache DolphinScheduler name search has been approved [4]
> - Finished the Podling Maturity Assessment for DolphinScheduler [5], all
> items are passed
> - There are 169 contributors for now
> - There are 1904 emails sent by 197 people in dev mailing-list excepted
> GitBox forwarded
> - Resolved 1500+ issues and 2000+ pull requests during ASF incubating
>
> We've resolved all branding issues which include Logo, GitHub repo,
> document, website and others.
>
> [1]
> https://lists.apache.org/thread.html/rbef0779035c61d02ef9fa63e55175fd5896fc513258d1b2537b51604%40%3Cdev.dolphinscheduler.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/r79381a3fd38d112b5ccb0be67675547e187497135853b0fe999f813a%40%3Cdev.dolphinscheduler.apache.org%3E
> [3]
> https://lists.apache.org/thread.html/raa78e55fc511b479cae1c4faefb8ae2cb31b4fb9143a1a958ac577f0%40%3Cdev.dolphinscheduler.apache.org%3E
> [4] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-186
> [5]
> https://cwiki.apache.org/confluence/display/DOLPHINSCHEDULER/Podling+Maturity+Assessment+for+DolphinScheduler
>
> -
>
> Establish the Apache DolphinScheduler 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 and extensible workflow scheduler platform with
> powerful DAG visual interfaces.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache DolphinScheduler Project", be and
> hereby is established pursuant to Bylaws of the Foundation; and be it
> further
>
> RESOLVED, that the Apache DolphinScheduler Project be and hereby is
> responsible for the creation and maintenance of software related to a
> distributed and extensible workflow scheduler platform with powerful DAG
> visual interfaces.; and be it further
>
> RESOLVED, that the office of "Vice President, Apache DolphinScheduler"
> 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
> DolphinScheduler Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of the
> Apache DolphinScheduler 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 DolphinScheduler
> Project:
>
> * Furkan Kamaci 
> * Gang Li   
> * Guo Jiwei 
> * Guo William   
> * Jun Gao   
> * Kevin Ratnasekera 
> * Leon Bao  
> * Liang Chen
> * Lidong Dai
> * Qiao Zhanwei  
> * Shao Feng Shi 
> * Sheng Wu  
> * Wu Baoqi  
> * Xiaochun Liu  
> * ZijJian Gong  
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lidong Dai be appointed to
> the office of Vice President, Apache DolphinScheduler, 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 or disqualification, or until a successor is appointed; and be
> it further
>
> RESOLVED, that the Apache DolphinScheduler Project be and hereby is
> tasked with the migration and rationalization of the Apache Incubator
> DolphinScheduler podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> DolphinScheduler podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
>
>
> 
>
>
> Best Regards
>
> --
> DolphinScheduler(Incubator) PPMC
> Gang Li 李岗
>
> lgcar...@apache.org
>
>
>

Re: [VOTE] Release Apache NLPCraft (incubating) 0.7.4

[Paul King]

+1 carrying my dev vote forward:
https://lists.apache.org/thread.html/reb06a62c04fed54684c993e80fe01cfff849df3631d85f32e7ab1051%40%3Cdev.nlpcraft.apache.org%3E

Cheers, Paul.



Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Fri, Feb 5, 2021 at 9:03 AM Aaron Radzinski 
wrote:

> Hello all,
> This is a call for a vote to release Apache NLPCraft (incubating)
> version 0.7.4. Apache NLPCraft is a library for adding a natural language
> interface to any application.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft (Incubating) version 0.7.4. We would like to
> request the Incubator PMC members review and vote on this incubator
> release.
>
> Release information:
> 1. PPMC vote result thread:
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202102.mbox/
> 
> 2. Release location:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/0.7.4/
> 3. Git tag: https://github.com/apache/incubator-nlpcraft/tree/v0.7.4
> 4. JIRA issues fixed in release:
> https://issues.apache.org/jira/projects/NLPCRAFT/versions/12349534
> 5. KEYS file:
> https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS
>
> The vote will be open for at least 72 hours or until a necessary number
> of votes are reached.
>
> Please vote accordingly:
> +1 approve
> +0 no opinion
> -1 disapprove with the reason
>
> Thank you,
> On behalf of NLPCraft community
>

Re: [VOTE] Release Apache NLPCraft (incubating) 0.7.3

[Paul King]

+1 with caveats

Checked hashes and signatures
DISCLAIMER exists
NOTICE seems okay but possibly missing some elements (1)
LICENSE seems okay but possibly missing some elements (1)
"mvn clean verify" passes on Ubuntu
"mvn clean verify" failed for me on Windows but possibly my environment (2)
"mvn apache-rat:rat" passes
incubating in name
no unexpected binary files
I ran my groovy-data-science example. Worked after adjusting for a binary
breaking change. (3)

Cheers, Paul.

==

(1) some of the data files seem to be missing appropriate attribution
I checked only src/main/resources/moby and src/main/resources/badfilter,
perhaps worth checking all folders under resources.

moby files seem to be "Released by Grady Ward into the public
domain[1][2]". While this would allow relicensing under Apache, it isn't
clear that is what you are intending. I suspect just a reference in the
LICENSE file is intended.

swear_words.txt says licensed under Apache but seems to come from a
third-party site which seems to suggest "copyright Ryan Jones" or
"Copyright All Slang Network" is needed in NOTICE file and it might be
worth querying the author what license is applicable. From the website, it
seems public domain but not explicitly stated? Or if you have obtained from
another source, they may have already established licensing. In any case,
some mention of licensing is needed.

[1] https://en.wikipedia.org/wiki/Moby_Project
[2] http://cs.sru.edu/~ddailey/whence.html

(2) Windows errors:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.22.1:test
(integration-tests) on project nlpcraft: There are test failures.
[ERROR]
[ERROR] Please refer to
D:\tmp\nlpcraft\073\apache-nlpcraft\nlpcraft\target\surefire-reports for
the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump,
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash
or System.exit called?
[ERROR] Command was cmd.exe /X /C
"C:\Progra~1\AdoptOpenJDK\jdk-11.0.8.10-hotspot\bin\java -jar
"C:\Users\Paul
King\AppData\Local\Temp\surefire7851445059229675487\surefirebooter6212500639838130057.jar"
"C:\Users\Paul King\AppData\Local\Temp\surefire7851445059229675487"
2021-01-18T18-48-51_629-jvmRun1 surefire17512347805813647919tmp
surefire_0900453059839016198tmp"
[ERROR] Process Exit Code: 0
[ERROR] Crashed tests:
[ERROR] org.apache.nlpcraft.server.rest.NCRestAskSpec
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
forked VM terminated without properly saying goodbye. VM crash or
System.exit called?

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.22.1:test
(integration-tests) on project nlpcraft: There are test failures.
[ERROR]
[ERROR] Please refer to
D:\tmp\nlpcraft\073\apache-nlpcraft\nlpcraft\target\surefire-reports for
the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump,
[date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] The forked VM terminated without properly saying goodbye. VM crash
or System.exit called?
[ERROR] Command was cmd.exe /X /C
"C:\Progra~1\AdoptOpenJDK\jdk-11.0.8.10-hotspot\bin\java -jar
"C:\Users\Paul
King\AppData\Local\Temp\surefire3495260889293679007\surefirebooter12040527775344534193.jar"
"C:\Users\Paul King\AppData\Local\Temp\surefire3495260889293679007"
2021-01-18T18-54-27_237-jvmRun1 surefire6023894785853744471tmp
surefire_02137409296786047525tmp"
[ERROR] Process Exit Code: 0
[ERROR] Crashed tests:
[ERROR] org.apache.nlpcraft.probe.mgrs.nlp.enrichers.sort.NCEnricherSortSpec
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
forked VM terminated without properly saying goodbye. VM crash or
System.exit called?

(3) Binary breaking change:
https://github.com/apache/incubator-nlpcraft/commit/6ee9a3808
I was using NCEmbeddedProbe#start(Class) but now need to pass a null
configFile param plus Collection.
I am unsure whether you are trying to honor semantic versioning at this
point, so might be okay.



On Thu, Jan 14, 2021 at 8:28 AM Aaron Radzinski 
wrote:

> Hello all,
> This is a call for a vote to release Apache NLPCraft (incubating)
> version 0.7.3. Apache NLPCraft is a library for adding a natural language
> interface to any application.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft (Incubating) version 0.7.3. We would like to
> request the Incubator PMC members review and vote on this incubator
> release.
>
> Release information:
> 1. PPMC vote result thread: https://mail-archives.apache.org/mod_mbox/
> nlpcraft
> -dev/202011.mbox/<
> cacwejt_bjzw7vcdayws_pyywhfpaasctujyo-k4d2k8ydx6...@mail.gmail.com>
> <https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/20

Re: [VOTE] Accept Wayang into the Apache Incubator

[Paul King]

+1 (binding)



Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sat, Dec 12, 2020 at 2:33 AM Christofer Dutz 
wrote:

> Hi all,
>
> following up the [DISCUSS] thread on Wayang (
> https://lists.apache.org/thread.html/r5fc03ae014f44c7c31a509a6db4ac07faedb2e1c6245cd917b744826%40%3Cgeneral.incubator.apache.org%3E)
> I would like to call a VOTE to accept Wayang Aka Rheem into the Apache
> Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring Wayang into the Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring Wayang into the Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding, but votes from everyone are welcome.
>
> Chris
>
> -
>
> Wayang Proposal (
> https://cwiki.apache.org/confluence/display/INCUBATOR/WayangProposal)
>
> == Abstract ==
>
> Wayang is a cross-platform data processing system that aims at decoupling
> the business logic of data analytics applications from concrete data
> processing platforms, such as Apache Flink or Apache Spark. Hence, it tames
> the complexity that arises from the "Cambrian explosion" of novel data
> processing platforms that we currently witness.
>
> Note that Wayang project is the Rheem project, but we have renamed the
> project because of trademark issues.
>
> You can find the project web page at: https://rheem-ecosystem.github.io/
>
> = Proposal =
>
> Wayang is a cross-platform system that provides an abstraction over data
> processing platforms to free users from the burdens of (i) performing
> tedious and costly data migration and integration tasks to run their
> applications, and (ii) choosing the right data processing platforms for
> their applications. To achieve this, Wayang: (1) provides an abstraction on
> top of existing data processing platforms that allows users to specify
> their data analytics tasks in a form of a DAG of operators; (2) comes with
> a cross-platform optimizer for automating the selection of
> suitable/efficient platforms; and (3) and finally takes care of executing
> the optimized plan, including communication across platforms. In summary,
> Wayang has the following salient features:
>
> - Flexible Data Model - It considers a flexible and simple data model
> based on data quanta. A data quantum is an atomic processing unit in the
> system, that can represent a large spectrum of data formats, such as data
> points for a machine learning application, tuples for a database
> application, or RDF triples. Hence, Wayang is able to express a wide range
> of data analytics tasks.
> - Platform independence - It provides a simple interface (currently Java
> and Scala) that is inspired by established programming models, such as that
> of Apache Spark and Apache Flink. Users represent their data analytic tasks
> as a DAG (Wayang plan), where vertices correspond to Wayang operators and
> edges represent data flows (data quanta flowing) among these operators. A
> Wayang operator defines a particular kind of data transformation over an
> input data quantum, ranging from basic functionality (e.g.,
> transformations, filters, joins) to complex, extensible tasks (e.g.,
> PageRank).
> - Cross-platform execution - Besides running a data analytic task on any
> data processing platform, it also comes with an optimizer that can decide
> to execute a single data analytic task using multiple data processing
> platforms. This allows for exploiting the capabilities of different data
> processing platforms to perform complex data analytic tasks more
> efficiently.
> Self-tuning UDF-based cost model - Its optimizer uses a cost model fully
> based on UDFs. This not only enables Wayang to learn the cost functions of
> newly added data processing platforms, but also allows developers to tune
> the optimizer at will.
> - Extensibility - It treats data processing platforms as plugins to allow
> users (developers) to easily incorporate new data processing platforms into
> the system. This is achieved by exposing the functionalities of data
> processing platforms as operators (execution operators). The same approach
> is followed at the Wayang interface, where users can also extend Wayang
> capabilities, i.e., the operators, easily.
>
> We plan to work on the stability of all these features as well as
> extending Wayang with more advanced features. Furthermore, Wayang currently
> supports Apache Spark, Standalone Java, GraphChi, relational databases (via
> JDBC). We plan to incorporate more data processing platforms, such as
> Apache Flink and Apache Hive.
>
> === Background ===
>
> Many organizations and companies collect or produce large variety of data
> to apply data analytics over them. This is because insights from data
> rapidly allow them to make better decisions. 

Re: [VOTE] Release Apache NLPCraft - Java Client (incubating) 0.7.2

[Paul King]

+1 (binding) carrying my vote over from dev list

On Tue, Dec 15, 2020 at 12:16 PM Aaron Radzinski 
wrote:

> Hello all,
> This is a call for a vote to release Apache NLPCraft - Java Client
> (incubating)
> version 0.7.2. Apache NLPCraft is a library for adding a natural language
> interface to any application. This release includes bug fixes and necessary
> updates for NLPCraft ver. 0.7.2 (main project).
>
> NOTE: NLPCraft Java Client is a Java wrapper for NLPCraft REST APIs. It
> is contained in its own Git repository but shares the same JIRA project as
> the main NLPCraft project. Community plans to release Java Client along
> with the main project to maintain a simple compatibility matrix.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft - Java Client (Incubating) version 0.7.2. We would
> like to request the Incubator PMC members review and vote on this incubator
> release.
>
> Release information:
> 1. PPMC vote result thread: https://mail-archives.apache.org/mod_mbox/
> nlpcraft
> -dev/202011.mbox/<
> cacwejt_bjzw7vcdayws_pyywhfpaasctujyo-k4d2k8ydx6...@mail.gmail.com>
>  >
> 2. Release location:
>
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/java-client/0.7.2/
> 3. Git tag:
> https://github.com/apache/incubator-nlpcraft-java-client/tree/v0.7.2
> 4. JIRA issues fixed in release: https://issues.apache.org/jira/projects/
> NLPCRAFT/versions/12349298
> 
> 5. KEYS file:
> https://dist.apache.org/repos/dist/release/incubator/nlpcraft
> /KEYS
>
> The vote will be open for at least 72 hours or until a necessary number of
> votes are reached.
>
> Please vote accordingly:
> +1 approve
> +0 no opinion
> -1 disapprove with the reason
>
> Thank you,
> On behalf of NLPCraft community
> --
> Aaron Radzinski
>

Re: [VOTE] Release Apache NLPCraft (incubating) 0.7.2

[Paul King]

+1 (binding) carrying over my vote

On Tue, Nov 24, 2020 at 2:21 PM Aaron Radzinski 
wrote:

> Hello all,
> This is a call for a vote to release Apache NLPCraft (incubating) version
> 0.7.2. Apache NLPCraft is a library for adding a natural language interface
> to any application.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft (Incubating) version 0.7.2. We would like to
> request the Incubator PMC members review and vote on this incubator
> release.
>
> Release information:
> 1. PPMC vote result thread:
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202011.mbox/<
> cacwejt_bjzw7vcdayws_pyywhfpaasctujyo-k4d2k8ydx6...@mail.gmail.com>
> 2. Release location:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/0.7.2/
> 3. Git tag: https://github.com/apache/incubator-nlpcraft/tree/v0.7.2
> 4. JIRA issues fixed in release:
> https://issues.apache.org/jira/projects/NLPCRAFT/versions/12349298
> 5. KEYS file:
> https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS
>
> The vote will be open for at least 72 hours or until a necessary number of
> votes are reached.
>
> Please vote accordingly:
> +1 approve
> +0 no opinion
> -1 disapprove with the reason
>
> Thank you,
> On behalf of NLPCraft community
>

Re: [VOTE] Hop proposal

[Paul King]

+1 (binding)


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Sep 16, 2020 at 11:29 PM Matt Casters
 wrote:

> Hi Apache,
>
> I'd like to call a vote on accepting Hop into the Apache Incubator.
> Please see the discussion thread [1].
>
> Please see the full proposal:
> https://cwiki.apache.org/confluence/display/INCUBATOR/HopProposal
> Please cast your vote
>
> [ ] +1 Accept Hop into the Incubator
> [ ] +0 Indifferent to the acceptance of Hop
> [ ] -1 Do not accept Hop because …
>
> The vote will be open at least for 72 hours.
>
> Incubator PMC member votes are binding. Everyone else is welcomed to vote
> too
> (mark them as non-binding if you can)!
>
> Thanks in advance for your time.
>
> Regards,
> Matt
>
> [1]
>
> http://apache-incubator-general.996316.n3.nabble.com/DISCUSS-Hop-proposal-td68232.html
>

Re: [VOTE] Release Apache NLPCraft (incubating) 0.7.0

[Paul King]

+1, carrying my vote over from dev list


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Thu, Oct 1, 2020 at 5:34 AM Aaron Radzinski 
wrote:

> Hello all,
> This is a call for a vote to release Apache NLPCraft (incubating) version
> 0.7.0. Apache NLPCraft is a library for adding a natural language interface
> to any application.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft (Incubating) version 0.7.0. We would like to
> request the Incubator PMC members review and vote on this incubator
> release.
>
> Release information:
> 1. PPMC vote result thread:
>
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202009.mbox/%3ccacwejt8ova52cxczs74ri3ascqskz3gcduh+acd3i2mczyk...@mail.gmail.com%3E
> 2. Release location:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/0.7.0/
> 3. Git tag: https://github.com/apache/incubator-nlpcraft/tree/v0.7.0
> 4. JIRA issues fixed in release:
> https://issues.apache.org/jira/projects/NLPCRAFT/versions/12347776
> 5. KEYS file:
> https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS
>
> NOTES:
> - Please re-import KEYS file before checking signatures.
> - Remove local ${USER_HOME}/.nlpcraft file before running 'mvn verify' if
> you had previous NLPCraft installation.
>
> The vote will be open for at least 72 hours or until a necessary number of
> votes are reached.
>
> Please vote accordingly:
> +1 approve
> +0 no opinion
> -1 disapprove with the reason
>
> Thank you,
> --
> Aaron Radzinski
> On behalf of NLPCraft community
>

Re: [VOTE] Distribution guidelines for platforms

[Paul King]

+1

On Mon, Jul 6, 2020 at 11:23 AM Justin Mclean 
wrote:

> Hi,
>
> This vote is to make this official [1] and move the guidelines to the
> website. The guidelines will be placed under the podling guides menu and
> linked to from the release section in the Incubator policy page [2]
>
> The last sentence in that section will be changed to say this (where
> "here" links to the web version of the guidelines):
>
> "Also, the Podling MAY choose to distribute approved releases through
> other channels by following the guidelines here."
>
> This vote will be open for 72 hours or as long as is needed and IPMC votes
> are binding.
>
> Please vote:
> +1 [ ] Let's make this official
> +0 [ ] Not sure this is needed
> -1 [ ] No way because...
>
> Thanks,
> Justin
>
> 1.
> https://cwiki.apache.org/confluence/display/INCUBATOR/Distribution+Guidelines
> 2. https://incubator.apache.org/policy/incubation.html#releases
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache NLPCraft (Incubating) 0.6.2

[Paul King]

+1 carrying my vote over from the dev list

Checked hashes and signatures.
"maven clean verify" passes (fails for me on Windows JDK8 as per
NLPCRAFT-76, passes on Linux JDK11)
"maven apache-rat:rat" passes (but it is configured to ignore failures, you
can change numUnapprovedLicenses in the pom from 100 to 0 and it still
currently passes) UPDATE: fixed in master
incubating in name
DISCLAIMER exists
NOTICE seems okay
LICENSE seems okay
no unexpected binary files
licensing issues found by Justin last time seem sorted


On Fri, Jul 17, 2020 at 3:54 PM Konstantin Boudnik  wrote:

> +1 [binding]
>
> - DISCLAIMER exists
> - LICENSE and NOTICE as expected
> - No binary files
> - Signatures and checksums are ok
>
> --
> With regards,
>Cos
>
> On 2020-07-16 00:23, Aaron Radzinski wrote:
> > Hello all,
> > This is a call for a vote to release Apache NLPCraft (incubating) version
> > 0.6.2. Apache NLPCraft is a library for adding a natural language
> interface
> > to any application.
> >
> > The Apache NLPCraft community has voted on and approved a proposal to
> > release Apache NLPCraft (Incubating) version 0.6.2. We would like to
> > request the Incubator PMC members review and vote on this incubator
> release.
> >
> > Release information:
> > 1. PPMC vote result thread:
> >
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202007.mbox/%3CCACwEJt8UFyDacVOa-MpwYj8s-c8vfFXbhmR%3DL1XBdtA4RKyJ7g%40mail.gmail.com%3E
> > 2. Release location:
> >
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/0.6.2/
> > 3. Git tag: https://github.com/apache/incubator-nlpcraft/tree/v0.6.2
> > 4. JIRA issues fixed in release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323722=12347775
> > 5. KEYS file:
> > https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS
> >
> > The vote will be open for at least 72 hours or until a necessary number
> of
> > votes are reached.
> >
> > Please vote accordingly:
> > +1 approve
> > +0 no opinion
> > -1 disapprove with the reason
> >
> > Thank you,
> > --
> > Aaron Radzinski
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Distribution guidelines for platforms

[Paul King]

My reading of the wording is that there is now more wiggle room for
podlings rather than more restrictions.

Cheers, Paul.

On Mon, Jul 13, 2020 at 5:51 PM Justin Mclean 
wrote:

> Hi,
>
> > I think all of these situations can occur with or without the new
> incubator policy.
>
> It possibles yes, but they would be less likely to occur.
>
> > his can only be more restrictive than the original ASF policies.
>
> These are not more restrictive than current policy. I really don’t
> understand why you think that they are. Please point out where that is the
> case and I’ll correct it.
>
> > If there’s consensus on the guideline among the TLPs
>
> There probably is not consensus among TLP on this and different projects
> will do it in different ways. That is fine as long as it complies, but
> working that does can be difficult.  Some TLP projects may not be complying
> with policy and not be aware of it, which may become a future issue. Even
> worse podlings may copy them rather that actually reading and understanding
> ASF policy or the intent behind it.
>
> This document allows for a variety of interpretation - "All of the above
> SHOULD be followed. The podling can ask the IPMC for permission to do
> otherwise.” Note the use of the word SHOULD rather than MUST. SHOULD means
> unless you have a good reason to do otherwise.
>
> > and everyone agrees with your assessment, why would it take ASF years to
> reach consensus on them?
>
> It taken years to get to this point and these issues and the like have
> been discussed for over a decade without resolution and that’s why policy
> don’t exist. The current board is trying to address that but it’s likely to
> be a slow process.
>
> The fact that once again this discussion has got derailed leaves me with
> very little hope that this will get resolved. A large amount of work has
> been put into this by many people, and it's unfortunate that these
> objections were brought up so late in the process.
>
> Thanks,
> Justin
> -
> 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

[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

Re: [VOTE] Release Apache NLPCraft (Incubating) 0.6.1

[Paul King]

+1 (binding) carrying my dev vote forward.
I'll note here for anyone running the test suite under Windows - there
seems to be some issues on some systems that are being looked at in
parallel and testing using WSL2 seems to avoid the problem.

Cheers, Paul.


On Sat, Jun 13, 2020 at 4:30 AM Aaron Radzinski 
wrote:

> Hello all,
> This is a call for a vote to release Apache NLPCraft (incubating) version
> 0.6.1. Apache NLPCraft is a library for adding a natural language interface
> to any application.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft (Incubating) version 0.6.1. We would like to
> request the Incubator PMC members review and vote on this incubator
> release.
>
> Release information:
> 1. PPMC vote result thread:
>
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202006.mbox/%3ccacwejt91kdfkqntbb9msekqo4sky5_vsqwyobft57eeibap...@mail.gmail.com%3e
> 2. Release location:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/0.6.1/
> 3. Git tag: https://github.com/apache/incubator-nlpcraft/tree/v0.6.1
> 4. JIRA issues fixed in release:
> https://issues.apache.org/jira/projects/NLPCRAFT/versions/12347775
> 5. KEYS file:
> https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS
>
> The vote will be open for at least 72 hours or until a necessary number of
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thank you,
> --
> Aaron Radzinski
>

Re: [VOTE] Accept Apache BlueMarlin in the incubator

[Paul King]

+1 (binding)


On Mon, May 25, 2020 at 4:27 PM Jean-Baptiste Onofre 
wrote:

> Hi everyone,
>
> Following the discussion about BlueMarlin, I would like to start a formal
> vote to accept BlueMarlin into the incubator.
>
> As reminder, here’s the proposal:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Apache+BlueMarlin <
> https://cwiki.apache.org/confluence/display/INCUBATOR/Apache+BlueMarlin>
>
> Please vote to accept BlueMarlin in the incubator:
>
>   [ ] +1, accept BlueMarlin into Incubator
>   [ ] -1, don’t accept BlueMarlin into Incubator (please provide a reason)
>
> The vote is open for 72 hours.
>
> Thanks,
> Regards
> JB

Re: [VOTE] Release Apache NLPCraft - Java Client (Incubating) 0.5.0

[Paul King]

+1 binding (carrying forward my earlier vote)

On Mon, May 25, 2020 at 9:53 AM Aaron Radzinski 
wrote:

> Hello all,
> This is a call for a vote to release Apache NLPCraft - Java Client
> (incubating) version 0.5.0.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft - Java Client (Incubating) version 0.5.0. We would
> like to request the Incubator PMC members review and vote on this incubator
> release.
>
> Apache NLPCraft is a Java-based library for adding a natural language
> interface to any applications. Notice that this is a first ASF release for
> the NLPCraft community. Java Client is a native JVM client for NLPCraft
> REST API.
>
> Release information:
> 1. Vote result thread:
>
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202005.mbox/%3CCACwEJt-vW4%2B7wUy1XoBYEdUVrT56LZuqDX0KRBvF7HO%3DU0KMGA%40mail.gmail.com%3E
> 2. Release (ZIP, PGP, SHA256) location:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/java-client/
> 3. Git tag:
> https://github.com/apache/incubator-nlpcraft-java-client/tree/v0.5.0
> 4. KEYS file:
> https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS
>
> The vote will be open for at least 72 hours or until a necessary number of
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thank you,
> --
> Aaron Radzinski
>

Re: [VOTE] Release Apache NLPCraft (Incubating) 0.5.0

[Paul King]

+1 (binding)

Checked:
+ DISCLAIMER exists
+ incubating in name
+ no unexpected binary files
+ signature okay (from
https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS)
+ checksum okay
+ LICENSE okay
+ NOTICE lines 1-5 correct (remove lines 6-95 for next release, they aren't
appropriate for the src release just binary)
+ mvn verify PASSES on JDK8 (checks for invalid JDK version - nice)
+ mvn apache-rat:check -Prelease PASSES (excludes look good; possibly
"javadoc" no longer required?)
+ mvn package PASSES (still a few warnings creating javadoc; NOTICE file
doesn't appear in created all-deps jar, this would be a full bindist
variant with current content)

On Thu, Apr 23, 2020 at 3:52 PM Aaron Radzinski 
wrote:

> Hello all,
> This is a call for a vote to release Apache NLPCraft (incubating) version
> 0.5.0.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft (Incubating) version 0.5.0. We would like to
> request the Incubator PMC members review and vote on this incubator
> release.
>
> Apache NLPCraft is a Java-based library for adding a natural language
> interface to any applications. Notice that this is a first ASF release for
> the NLPCraft community.
>
> Release information:
> 1. Vote result thread:
>
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202004.mbox/%3CCACwEJt9LEqEJw7gVxS%3D56d%2BA%3DZewjBBEbQQJY%3D%2B6o7N7P-%3D0Ag%40mail.gmail.com%3E
> 2. Release location:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/
> 3. Git tag:
>
> https://gitbox.apache.org/repos/asf?p=incubator-nlpcraft.git;a=tag;h=refs/tags/v0.5.0
> 4. JIRA issues fixed in release:
> https://issues.apache.org/jira/projects/NLPCRAFT/versions/12347774
>
> Quick links:
> 1. ZIP archive:
>
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip
> 2. PGP signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip.asc
> 3. SHA256 signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip.sha256
> 4. KEYS file:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/KEYS
>
> NOTE: the 'dist' location has double 'nlpcraft' folders which may look
> suspicious. First 'nlpcraft' is a root for the project, while the second
> denotes core project name. Note that we'll be releasing our sub-projects
> (i.e. java client) under the root 'nlpcraft' folder so the dist location
> will eventually have structure like this:
> -- nlpcraft
>   |-- nlpcraft
>   |-- nlpcraft-java-client
>   |-- nlpcraft-web-ui
>
> The vote will be open for at least 72 hours or until a necessary number of
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thank you,
> --
> Aaron Radzinski
>

Re: [VOTE] Release Apache NLPCraft (Incubating) 0.5.0

[Paul King]

Okay, I didn't know that wording was there. Standard practice is to always
wait at least 72hrs unless there are exceptional circumstances such as:
* cancelling the vote early when it needs an obvious fix
* when there is a security issue in the release which needs prompt releasing
* the entire PMC (IPMC in this case) has voted (this won't ever happen for
the IPMC)
The 72hrs allows folks from different time zones and different work
commitments to participate in the vote.

Cheers, Paul.


On Fri, Apr 24, 2020 at 4:31 AM Nikita Ivanov  wrote:

>
> Paul - this is the language that's proposed as a template in
> https://incubator.apache.org/policy/incubation.html#releases
>
> Thanks,
> --
> Nikita Ivanov
>
>
>
> On Thu, Apr 23, 2020 at 1:04 AM Paul King  wrote:
>
>> Just on process, the "or until a necessary number of votes are reached"
>> won't apply. You might get 3 +1s straight away and a -1 a couple of days
>> later. If that was the total votes, that would still be counted as a
>> failing vote.
>>
>> Cheers, Paul.
>>
>> On Thu, Apr 23, 2020 at 3:52 PM Aaron Radzinski <
>> aradzin...@datalingvo.com>
>> wrote:
>>
>> > Hello all,
>> > This is a call for a vote to release Apache NLPCraft (incubating)
>> version
>> > 0.5.0.
>> >
>> > The Apache NLPCraft community has voted on and approved a proposal to
>> > release Apache NLPCraft (Incubating) version 0.5.0. We would like to
>> > request the Incubator PMC members review and vote on this incubator
>> > release.
>> >
>> > Apache NLPCraft is a Java-based library for adding a natural language
>> > interface to any applications. Notice that this is a first ASF release
>> for
>> > the NLPCraft community.
>> >
>> > Release information:
>> > 1. Vote result thread:
>> >
>> >
>> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202004.mbox/%3CCACwEJt9LEqEJw7gVxS%3D56d%2BA%3DZewjBBEbQQJY%3D%2B6o7N7P-%3D0Ag%40mail.gmail.com%3E
>> > 2. Release location:
>> > https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/
>> > 3. Git tag:
>> >
>> >
>> https://gitbox.apache.org/repos/asf?p=incubator-nlpcraft.git;a=tag;h=refs/tags/v0.5.0
>> > 4. JIRA issues fixed in release:
>> > https://issues.apache.org/jira/projects/NLPCRAFT/versions/12347774
>> >
>> > Quick links:
>> > 1. ZIP archive:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip
>> > 2. PGP signature:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip.asc
>> > 3. SHA256 signature:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip.sha256
>> > 4. KEYS file:
>> > https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/KEYS
>> >
>> > NOTE: the 'dist' location has double 'nlpcraft' folders which may look
>> > suspicious. First 'nlpcraft' is a root for the project, while the second
>> > denotes core project name. Note that we'll be releasing our sub-projects
>> > (i.e. java client) under the root 'nlpcraft' folder so the dist location
>> > will eventually have structure like this:
>> > -- nlpcraft
>> >   |-- nlpcraft
>> >   |-- nlpcraft-java-client
>> >   |-- nlpcraft-web-ui
>> >
>> > The vote will be open for at least 72 hours or until a necessary number
>> of
>> > votes are reached.
>> >
>> > Please vote accordingly:
>> > [ ] +1 approve
>> > [ ] +0 no opinion
>> > [ ] -1 disapprove with the reason
>> >
>> > Thank you,
>> > --
>> > Aaron Radzinski
>> >
>>
>

Re: [VOTE] Release Apache NLPCraft (Incubating) 0.5.0

[Paul King]

Just on process, the "or until a necessary number of votes are reached"
won't apply. You might get 3 +1s straight away and a -1 a couple of days
later. If that was the total votes, that would still be counted as a
failing vote.

Cheers, Paul.

On Thu, Apr 23, 2020 at 3:52 PM Aaron Radzinski 
wrote:

> Hello all,
> This is a call for a vote to release Apache NLPCraft (incubating) version
> 0.5.0.
>
> The Apache NLPCraft community has voted on and approved a proposal to
> release Apache NLPCraft (Incubating) version 0.5.0. We would like to
> request the Incubator PMC members review and vote on this incubator
> release.
>
> Apache NLPCraft is a Java-based library for adding a natural language
> interface to any applications. Notice that this is a first ASF release for
> the NLPCraft community.
>
> Release information:
> 1. Vote result thread:
>
> https://mail-archives.apache.org/mod_mbox/nlpcraft-dev/202004.mbox/%3CCACwEJt9LEqEJw7gVxS%3D56d%2BA%3DZewjBBEbQQJY%3D%2B6o7N7P-%3D0Ag%40mail.gmail.com%3E
> 2. Release location:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/
> 3. Git tag:
>
> https://gitbox.apache.org/repos/asf?p=incubator-nlpcraft.git;a=tag;h=refs/tags/v0.5.0
> 4. JIRA issues fixed in release:
> https://issues.apache.org/jira/projects/NLPCRAFT/versions/12347774
>
> Quick links:
> 1. ZIP archive:
>
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip
> 2. PGP signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip.asc
> 3. SHA256 signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/apache-nlpcraft-incubating-0.5.0.zip.sha256
> 4. KEYS file:
> https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/nlpcraft/KEYS
>
> NOTE: the 'dist' location has double 'nlpcraft' folders which may look
> suspicious. First 'nlpcraft' is a root for the project, while the second
> denotes core project name. Note that we'll be releasing our sub-projects
> (i.e. java client) under the root 'nlpcraft' folder so the dist location
> will eventually have structure like this:
> -- nlpcraft
>   |-- nlpcraft
>   |-- nlpcraft-java-client
>   |-- nlpcraft-web-ui
>
> The vote will be open for at least 72 hours or until a necessary number of
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thank you,
> --
> Aaron Radzinski
>

Re: [VOTE] Release Apache Daffodil (incubating) 2.6.0-rc2

[Paul King]

+1 (but I had some issues noted below which I presume are minor oversights
or due to my environment)

Checked:
- signatures and hashes for src zip okay
- incubating in name
- DISCLAIMER exists
- LICENSE and NOTICE files (root and daffodil-cli variants seem okay)
- source files have ASF or compatible headers
- builds from source
- rat check found 9 files[1] which seem like other .bin files but maybe
aren't mentioned in your excludes list; otherwise no unexpected binary
files.
  I presume you have somewhere documented how the .bin/.dat are generated.
- test suite runs but I had some errors[2] Environmental? I was using
Windows.
- as an experiment, I ran the tutorial from Java and Groovy and seemed to
get the same result with both though I wasn't sure what to expect (round
tripping dateTimeTest from tdmlTutorial.tdml.xml?)

Cheers, Paul.

[1] Files with unapproved licenses:


daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_13b.bin

daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_13a.bin

daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_02.bin

daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_13c.bin

daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_03.bin

daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_13d.bin

daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_07.bin

daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_04.bin

daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_01.bin

[2] Numerous tests failed, e.g.:
[error] Test
org.apache.daffodil.section07.discriminators.TestDiscriminators.test_choiceBranchDiscrim
failed: org.apache.daffodil.exceptions.Abort: Invariant broken.
Runtime.scala - Leaked exception: java.lang.OutOfMemoryError: Java heap
space
[error] java.lang.OutOfMemoryError: Java heap space
[error]
[error] org.apache.daffodil.exceptions.Assert$.abort(Assert.scala:120)
[error]
org.apache.daffodil.exceptions.Assert$.invariantFailed(Assert.scala:166)
[error] ...
[error] at
org.apache.daffodil.section07.discriminators.TestDiscriminators.test_choiceBranchDiscrim(TestDiscriminators3.scala:52)

[error] Test
org.apache.daffodil.section07.assertions.TestAssertions.test_assertPatternMatch2
failed: org.apache.daffodil.exceptions.Abort: Invariant broken. Pool
MarkPool leaked 1 instance(s).
[error] poolDebugLabel = ElementParserBase2
[error] org.apache.daffodil.exceptions.Assert$.abort(Assert.scala:120)
[error]
org.apache.daffodil.exceptions.Assert$.invariantFailed(Assert.scala:166)
[error] org.apache.daffodil.util.Pool.finalCheck(Pool.scala:103)
[error] ...
[error] at
org.apache.daffodil.section07.assertions.TestAssertions.test_assertPatternMatch2(TestAssertions.scala:69)



Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Tue, Apr 14, 2020 at 10:47 PM Olabusayo Kilo  wrote:

> The Apache Daffodil community has voted and approved the proposed
> release of Apache Daffodil (incubating) 2.6.0-rc2
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Daffodil is an open source implementation of the DFDL specification that
> uses DFDL schemas to parse fixed format data into an infoset, which is
> most commonly represented as either XML or JSON. This allows the use of
> well-established XML or JSON technologies and libraries to consume,
> inspect, and manipulate fixed format data in existing solutions.
> Daffodil is also capable of the reverse by serializing or "unparsing" an
> XML or JSON infoset back to the original data format.
>
> Vote thread:
>
> https://lists.apache.org/thread.html/r25781e7da23f4d0318ca6fa316c8d4bfb244e441fa4d722be4010be2%40%3Cdev.daffodil.apache.org%3E
>
> Result thread:
>
> https://lists.apache.org/thread.html/rcf5b2c6961179205262fbd03605f3bd09f34d3946808880f0a487fa1%40%3Cdev.daffodil.apache.org%3E
> --
> Best Regards
> Lola K.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Daffodil (incubating) 2.6.0-rc2

[Paul King]

should have noted (binding) with my +1

<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Thu, Apr 23, 2020 at 5:18 PM Paul King  wrote:

> +1 (but I had some issues noted below which I presume are minor oversights
> or due to my environment)
>
> Checked:
> - signatures and hashes for src zip okay
> - incubating in name
> - DISCLAIMER exists
> - LICENSE and NOTICE files (root and daffodil-cli variants seem okay)
> - source files have ASF or compatible headers
> - builds from source
> - rat check found 9 files[1] which seem like other .bin files but maybe
> aren't mentioned in your excludes list; otherwise no unexpected binary
> files.
>   I presume you have somewhere documented how the .bin/.dat are generated.
> - test suite runs but I had some errors[2] Environmental? I was using
> Windows.
> - as an experiment, I ran the tutorial from Java and Groovy and seemed to
> get the same result with both though I wasn't sure what to expect (round
> tripping dateTimeTest from tdmlTutorial.tdml.xml?)
>
> Cheers, Paul.
>
> [1] Files with unapproved licenses:
>
>
> daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_13b.bin
>
> daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_13a.bin
>
> daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_02.bin
>
> daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_13c.bin
>
> daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_03.bin
>
> daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_13d.bin
>
> daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_07.bin
>
> daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_04.bin
>
> daffodil-test/src/test/resources/org/apache/daffodil/section05/simple_types/blobs/blob_01.bin
>
> [2] Numerous tests failed, e.g.:
> [error] Test
> org.apache.daffodil.section07.discriminators.TestDiscriminators.test_choiceBranchDiscrim
> failed: org.apache.daffodil.exceptions.Abort: Invariant broken.
> Runtime.scala - Leaked exception: java.lang.OutOfMemoryError: Java heap
> space
> [error] java.lang.OutOfMemoryError: Java heap space
> [error]
> [error] org.apache.daffodil.exceptions.Assert$.abort(Assert.scala:120)
> [error]
> org.apache.daffodil.exceptions.Assert$.invariantFailed(Assert.scala:166)
> [error] ...
> [error] at
> org.apache.daffodil.section07.discriminators.TestDiscriminators.test_choiceBranchDiscrim(TestDiscriminators3.scala:52)
>
> [error] Test
> org.apache.daffodil.section07.assertions.TestAssertions.test_assertPatternMatch2
> failed: org.apache.daffodil.exceptions.Abort: Invariant broken. Pool
> MarkPool leaked 1 instance(s).
> [error] poolDebugLabel = ElementParserBase2
> [error] org.apache.daffodil.exceptions.Assert$.abort(Assert.scala:120)
> [error]
> org.apache.daffodil.exceptions.Assert$.invariantFailed(Assert.scala:166)
> [error] org.apache.daffodil.util.Pool.finalCheck(Pool.scala:103)
> [error] ...
> [error] at
> org.apache.daffodil.section07.assertions.TestAssertions.test_assertPatternMatch2(TestAssertions.scala:69)
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>  Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> <#m_-3941925250562357311_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Tue, Apr 14, 2020 at 10:47 PM Olabusayo Kilo  wrote:
>
>> The Apache Daffodil community has voted and approved the proposed
>> release of Apache Daffodil (incubating) 2.6.0-rc2
>>
>> We now kindly request the Incubator PMC members review and vote on this
>> incubator release.
>>
>> Daffodil is an open source implementation of the DFDL specification that
>> uses DFDL schemas to parse fixed format data into an infoset, which is
>> most commonly represented as either XML or JSON. This allows the use of
>> well-established XML or JSON technologies and libraries to consume,
>> inspect, and manipulate fixed format data in existing solutions.
>> Daffodil is also capable of the reverse by serializing or "unparsing" an
>> XML or JSON infoset back to the original data format.
>>
>> Vote thread:
>>
>> https://lists.apache.org/thread.html/r2578

Re: [VOTE] Release Apache Superset (incubating) version 0.36.0

[Paul King]

+1 (binding)

Checked:
- signature okay
- checksum okay
- incubating in name
- DISCLAIMER exists
- LICENSE and NOTICE seem okay
- didn't appear to have any binary files within tarball (apart from images)
- builds from source (using RELEASING/test_run_tarball.sh)

Comments:
- The instructions in RELEASING/README.md hinted what to do for the "builds
from source" step above but might be good to mention some clearer
instructions in the root README.md or INSTALL.md for next release for how
you'd typically expect new users to try your project deliverables

Cheers, Paul.

On Tue, Apr 7, 2020 at 8:02 PM Ville Brofeldt 
wrote:

> Hello IPMC,
>
> The Apache Superset (incubating) community has voted on and approved a
> proposal to
> release Apache Superset (incubating) version 0.36.0.
> The voting thread can be found here:
>
> https://lists.apache.org/thread.html/r7a46394a72577d9663c90b22fa35756a4cdd67d44825aaf8ecee42e5%40%3Cdev.superset.apache.org%3E
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Superset (incubating) is a modern, enterprise-ready business
> intelligence web application
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/superset/0.36.0rc3/
>
> Git tag for the release:
> https://github.com/apache/incubator-superset/tree/0.36.0rc3
>
> The Change Log for the release:
> https://github.com/apache/incubator-superset/blob/0.36.0rc3/CHANGELOG.md
>
> public keys are available at:
>
> https://www.apache.org/dist/incubator/superset/KEYS
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Superset (Incubating) Team
>

wiki permissions

[Paul King]

I don't seem to have wiki permissions. Can someone please enable me?
ApacheID: paulk

Thanks, Paul.

Re: "Fork Me" on GitHub (was Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP)

[Paul King]

I would think it is almost ubiquitous now for developers to know that the
easiest way for them to create a PR for instance is to fork the project
(the source code if you like) on Github.

It seems sensible to encourage the use of "Fork me on Github" as it
substantially lowers the barrier of newcomers to our projects but it would
seem prudent to ensure that the links are made low key so as not to appear
like banner ads. Other ways to contribute should be given equal prominence.

Just my 2c.

Cheers, Paul.



On Fri, Mar 27, 2020 at 7:27 PM Harbs  wrote:

> Thanks for the link to the board@ list. I agree with you that it’s a
> shame the discussion was on a private list.
>
> Yes. It seems that the concern of some is that link is an “ad”.
>
> It seems to me that the primary purpose for the link is to make
> contributing easier and the “advertisement” is secondary.
>
> I don’t really see the concern for using unreleased code any more than
> having a link to the Apache repos.
>
> The fact is that GitHub has become the defacto place where much of the
> development is being done on many projects.
>
> The compromise which seemed acceptable to most in that thread seems to be
> to remove “GitHub” from the link.
>
> I also wonder if opinions might have changed in the 5 years since that
> discussion. In that time, GitHub has only become more ubiquitous and more
> adopted by many Apache projects.
>
> Thanks,
> Harbs
>
> > On Mar 27, 2020, at 12:03 PM, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> > If you can, I suggest people read this board@ thread [1]. It a pity
> that conversation didn’t happen in more public space. Also note the board
> action item that resulted from this and that the “Fork me on Github” ribbon
> is no longer on the front page of the project in question.
> >
> > Also consider the language choice of “Fork me on GitHub” may cause some
> confusion to new user re the ownership of a project and make it unclear if
> this is an ASF project or a GitHub one when displayed prominently on the
> front page.
> >
> > Thanks,
> > Justin
> >
> > 1.
> https://lists.apache.org/thread.html/1d5f9aaf7919608d80d1cf288092ba406c763f1ada850c5130412b4b%401417896365%40%3Cboard.apache.org%3E
> > -
> > 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: [DISCUSS] Project proposal - Apache Rainbow

[Paul King]

I'm probably leaning towards accepting. Given that the closest fit to me
seems the DLAB project, I would be keen to see if anyone in that project
has an interest in keeping abreast of developments in Rainbow. DLAB is
itself also incubating so we wouldn't want to burden them with too many
more official responsibilities, so just informal interest would be all I
would hope we could encourage.

Cheers, Paul.

On Wed, Mar 25, 2020 at 3:31 PM Justin Mclean 
wrote:

> Hi,
>
> Really up to the project on what process would fit them best. If it ends
> up an Incubator project that  may mean more work for the mentors. I think
> as long as they are committed to the project we could accept it, but I’d
> like to hear what other IPMC members think.
>
> Thanks,
> justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release SAMOA 0.5.0 (incubating) RC3

[Paul King]

Looks like under "The developer's version artifacts" you have the sha512
hashes, but under the staging repo you just have sha1/md5.


On Wed, Mar 18, 2020 at 7:58 AM Justin Mclean 
wrote:

> HI,
>
> -1 (binding) because of hash issue - but this is easily fixed without
> stopping the vote and there’s no need for a revote. Once change I check and
> change my vote to +1
>
> I checked:
> - incubating in name
> - signature is fine (although it would be good to sigh with an apache
> email address)
> - hash needs to be sha256 or sha512 [1]
> - DISCLAIMER exits
> - LICENSE is OKish
> - NOTICE year is out of date (2016!) Please fix.
> - No unexpected binary files
> - Can compile from source
>
> License mentions "This product includes software developed at Yahoo! Inc.”
> but doesn’t say how that is licensed I think this needs to be in NOTICE not
> LICENSE as teh copyright headers have been relocated right? It also unclear
> where the code for MOA is bundled.
>
> Thanks,
> Justin
>
> 1. https://infra.apache.org/release-distribution-policy.html
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release SAMOA 0.5.0 (incubating) RC3

[Paul King]

+1 (binding) with some caveats.

I checked:
* Incubating in name
* DISCLAIMER exists
* LICENSE and NOTICE okay (copyright end year in NOTICE needs a bump I
would suspect)
* Signatures okay
* Checksums okay

My understanding is that the KEYS file for your project is expected in:
  https://dist.apache.org/repos/dist/release/incubator/samoa/KEYS (or via
the external URL https://downloads.apache.org/incubator/samoa/KEYS)
It would normally contain the keys for all release managers. I believe you
can just copy your file there now - please do.

Rat indicates that the following files need headers or an exclusion (if
generated or header can't be there for some technical reason):
  sign.sh
  DEPENDENCIES
  CONTRIBUTING.md
  checkstyle/header.regexp
  bin/samza-kryo
  src/main/resources/kafka.avsc (samoa-api)
  src/main/resources/META-INF/services/org.apache.hadoop.fs.FileSystem
(samoa-api)
[None of these seem like critical IP to me, so not worth cancelling but
this should be easy to fix up for next release.]

The following test failed on Ubuntu and WSL:
  Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.384 sec
<<< FAILURE! - in
org.apache.samoa.topology.impl.SimpleEntranceProcessingItemTest

testStartSendingEvents(org.apache.samoa.topology.impl.SimpleEntranceProcessingItemTest)
 Time elapsed: 0.31 sec  <<< ERROR!
  java.lang.IllegalStateException: Missing invocation to mocked type at
this point; please make sure there is an associated mock field or mock
parameter in scope
  at
org.apache.samoa.topology.impl.SimpleEntranceProcessingItemTest$4.(SimpleEntranceProcessingItemTest.java:158)...

Additional tests failed under Windows, e.g.:
  Tests run: 10, Failures: 0, Errors: 10, Skipped: 0, Time elapsed: 8.097
sec <<< FAILURE! - in org.apache.samoa.streams.fs.HDFSFileStreamSourceTest

testGetNextInputStream(org.apache.samoa.streams.fs.HDFSFileStreamSourceTest)
 Time elapsed: 6.661 sec  <<< ERROR!
  java.lang.UnsatisfiedLinkError:
org.apache.hadoop.io.nativeio.NativeIO$Windows.access0(Ljava/lang/String;I)Z...

Attempting to test under Windows with JDK 11.0.5 gave:
  [ERROR] Caused by: java.lang.IllegalStateException: JMockit requires a
Java 6+ VM
  [ERROR] at
mockit.internal.startup.AgentInitialization.loadAgentFromLocalJarFile(AgentInitialization.java:25)
[I am assuming there is something I don't have set up correctly in my
environment but would be good for you to list recommended JDK
versions/platforms in your vote email (and release email) if there are
restrictions, or point to some doco where such info is available]

I could build from source using `mvn -Dmaven.test.skip=true package` and
was then able to run the classifiers.ensemble.Bagging example from the
project home page.
[After printing out what looked like the results, bin/samoa didn't return
to the command prompt. I didn't know if that is expected behavior.]

Cheers, Paul.



On Mon, Mar 16, 2020 at 7:40 AM Corey Sterling 
wrote:

> Hi all,
>
> The SAMOA community has voted to promote a release candidate to a
> full-release.
>
> The vote thread can be found at:
>
> https://lists.apache.org/thread.html/r9ee34c67da99269915485635ae9c86e158fb9e149727e699d3990e23%40%3Cdev.samoa.apache.org%3E
>
> and the result thread at:
>
> https://lists.apache.org/thread.html/r066a4c6334e155887f6ab199fb9f52e0b7798a9a1940cae69a29671d%40%3Cdev.samoa.apache.org%3E
>
> We now invite the general incubator community to vote on releasing the same
> release candidate as Apache SAMOA (incubating) version 0.5.0.
>
> Release candidate 2 was skipped as during it's creation the Github mirror
> of the branch became out-of-sync with the Apache source repository.
>
> This release will be the third release for SAMOA in the incubator.
>
> -
> The commit to be voted on is in the branch "releases/0.5.0-incubating-RC3"
> (commit 9fe3b5582b7c697a00151902bd7e945aaf07506f):
> https://git-wip-us.apache.org/repos/asf?p=incubator-samoa
> .git;a=commit;h=9fe3b5582b7c697a00151902bd7e945aaf07506f
>
> Tag v0.5.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-samoa
> .git;a=commit;h=856a16920f7c19f94c43c3cdd287a86f52087c15
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/csterling
>
> The staging repository for this release can be found at:
>
> https://repository.apache.org/content/repositories/staging/org/apache/samoa/
> samoa/0.5.0-incubating/
> 
>
> The developer's version artifacts:
>
> https://dist.apache.org/repos/dist/dev/incubator/samoa/0.5.0-incubating-rc3/
>
> -
>
> Please vote on releasing this package as Apache SAMOA 0.5.0 (incubating).
>
> [ ] +1 Release this package as Apache SAMOA 0.5.0 (incubating)
> [ ] -1 Do not release this package because ...
>
> Cheers,
>
> Corey.
>

Re: [VOTE] Apache Tuweni 1.0.0-incubating release

[Paul King]

I had the same questions Justin mentioned wrt  gossip and relayer but
forgot to mention that.
One approach could be to have your artifacts split into sources and
distributions subdirectories (or similar names).

Cheers, Paul.

On Sun, Mar 15, 2020 at 5:37 PM Justin Mclean 
wrote:

> Hi,
>
> +1 (binding)
>
> I checked only the source release:
> - incubating in name
> - signature and hashes good
> - DISCLAIMER exists
> - LICENSE and NOTICE are good
> - No unexpected binary files
> - Hard to tell if any files are missing headers due to large number of
> Json files
> - Didn’t compile from source
>
> It a little unclear from the names if if gossip and relayer are binary or
> source artefacts, you might want to correct that.
>
> Also you might want consider  removing the large amount of test resource
> form the source release, IMO users generally want to build the release not
> test it ands it on the rather large size with some test file being over 1Mb.
>
> Thanks,
> Justin
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Tuweni 1.0.0-incubating release

[Paul King]

+1 (binding)

I checked:
* Incubating in name
* DISCLAIMER exists
* LICENSE and NOTICE okay
* Signatures okay
* Checksums okay
* Rat checks okay (hacked to make work without .git dir)

I noticed two copies of many files within the tgz and zip source archives
but this didn't seem to impact extraction bar some warnings.
E.g.:

> $ tar tvf tuweni-src-1.0.0-incubating.tar | grep toml/build.gradle
> -rw-r--r-- 0/01523 1970-01-01 10:00
> tuweni-src-1.0.0/toml/build.gradle
> -rw-r--r-- 0/01523 1970-01-01 10:00
> tuweni-src-1.0.0/toml/build.gradle


I checked for unexpected binary files. There were many *.ssz test files. I
understand why you might have them and see you have excluded them in e.g.
rat checks.
I am assuming you have discussed using them in your build and have some
doco somewhere to explain how to work with/create such files.

I ran gradle test under Windows 10 and JDK 11.05 (there seemed to be issues
on that platform in the voting thread so I thought I would give it a try).
I had 5 errors as listed below which I assume are platform glitches and
which can hopefully can be addressed for some future release:

> Task :hobbits:test
> org.apache.tuweni.hobbits.UDPTest > testTwoEndpoints(Vertx) FAILED
> Caused by: java.net.BindException
> org.apache.tuweni.hobbits.UDPTest > testTwoUDPConnections(Vertx) FAILED
> Caused by: java.net.BindException
> org.apache.tuweni.hobbits.RelayerTest > testUDPRelay(Vertx) FAILED
> java.lang.NullPointerException at RelayerTest.kt:101
> 17 tests completed, 3 failed, 1 skipped
> > Task :io:test
> org.apache.tuweni.io.ResourcesTest >
> shouldIterateResourcesOnFileSystemAndInJars(Path) FAILED
> java.lang.RuntimeException at ResourcesTest.java:96
> Caused by: java.net.URISyntaxException at ResourcesTest.java:96
> 19 tests completed, 1 failed
> > Task :kv:test
> org.apache.tuweni.kv.MapDBKeyValueStoreSpec > describe a MapDB-backed key
> value store FAILED
> java.nio.file.FileSystemException at KeyValueStoreSpec.kt:202
> 55 tests completed, 1 failed


Cheers, Paul.


On Mon, Mar 9, 2020 at 6:14 PM Antoine Toulme  wrote:

> Hi all,
>
> We're voting on the distributions available here:
> https://dist.apache.org/repos/dist/dev/incubator/tuweni/1.0.0-incubating/
>  >
> The release tag is present here:
> https://github.com/apache/incubator-tuweni/releases/tag/v1.0.0-incubating
>  >
>
> This release includes the following changes:
> * Moved to JDK11 support by default. 1.0.0 drops support for JDK8.
> * Added ethnetstats library.
> * Added key-value store functionalities: proxy store, stores are now
> generic, not just bytes, and have the ability to iterate over keys or clear
> their contents.
> * Added support for JPA-backed key value stores
> * Added eth2 reference tests repository. This repository is checked out as
> a submodule, and will be used to test SSZ going forward.
> * Fix TUWENI-30: expose key for GenericHash
> * Allow CN as option when generating the self-signed certs (used to be
> example.com )
> * Move Jenkins build to Jenkinsfile inside the repo.
>
> Here is the release thread on the dev list of Apache Tuweni:
>
> https://lists.apache.org/thread.html/rfa465f37916648e1decb7a60e89fb5cd7c6d128fa53523fdff8c6427%40%3Cdev.tuweni.apache.org%3E
> <
> https://lists.apache.org/thread.html/rfa465f37916648e1decb7a60e89fb5cd7c6d128fa53523fdff8c6427@%3Cdev.tuweni.apache.org%3E
> >
>
> Here is the result of the vote:
>
> https://lists.apache.org/thread.html/r752b4c407e5e89c0ba5a28cbe85e4784b728992731e845364e8c915a%40%3Cdev.tuweni.apache.org%3E
> <
> https://lists.apache.org/thread.html/r752b4c407e5e89c0ba5a28cbe85e4784b728992731e845364e8c915a@%3Cdev.tuweni.apache.org%3E
> >
>
> The vote for Apache Tuweni 1.0.0 has concluded:
> +1s: 5
> Antoine Toulme
> Steven Schroeder
> Furkan Kamacı (mentor)
> Larry McCay (mentor)
> Jonny Rhea
> +0: 0
> -1: 0
>
> The vote has passed. We have 2 mentor votes, and will require a new vote
> on the general incubator list.
>
> Cheers,
>
> Antoine

Re: [VOTE] Release Apache Annotator (incubating) version 0.1.0 (-rc.1)

[Paul King]

Hi Annotator dev team. Congrats on getting to this exciting stage!

I am just checking up on process. Are you following the traditional podling
release process:
https://incubator.apache.org/policy/incubation.html#releases
I.e. first a vote on dev mailing list followed by a subsequent vote from
incubator general list?
Looks like this is the first round and once the 72 hour window closes
shortly you are all good to go for round 2, but I just wanted to check
expectations - doesn't seem you had a lot of feedback on that part of your
proposed process from a few weeks back.
There has been talk of a more streamlined process that might collapse the
two rounds but I wasn't aware that it had been enacted just yet - happy to
be told differently if that is the case.

Cheers, Paul.


On Sat, Feb 29, 2020 at 1:33 AM Randall Leeds  wrote:

> Dear community,
>
> I would like to propose we release Apache Annotator (incubating) 0.1.0.
>
> This is the first release of Apache Annotator and represents a modest but
> exciting step for the community. We encourage everyone to help us verify
> that the release is proper and help identify and fix any critical issues
> with the project's packaging or the proper functioning of the build.
>
> The release artifacts are available here:
>
>
>
> https://dist.apache.org/repos/dist/dev/incubator/annotator/source/0.1.0/rc.1
>
> There you will find a tarball, a GPG signature, and SHA256/SHA512
> checksums.
>
> A KEYS file for checking the signatures can be found here:
>
> https://dist.apache.org/repos/dist/release/incubator/annotator/KEYS
>
> Please verify that the build is from commit
> b3d671796422e5583f4ee3cd8ad7bbaa90bc3ffc, tagged as v0.1.0-rc.1, by
> checking out the source tree and running `make dist`, verifying that it
> produces an identical tarball with the same checksums as the uploaded
> artifacts.
>
> Please validate the build by checking that the signature and checksums are
> valid for the uploaded tarball and then unpacking it and ensuring that
> `make && make check` exits cleanly.
>
> If you would like to further validate the packaging, the repository is set
> up for Apache Rat to check for proper license headers and notifications. As
> this is our first release, it is important to us that we get these
> processes correctly in place.
>
> If the vote passes, these artifacts will be released as Apache Annotator
> (incubating) 0.1.0.
>
> The vote will be open for 72 hours.
>
> Voting:
> +1 - release this package as 0.1.0
> +0 - no opinion
> -1 - do not release this package
>
> Regards,
> Randall Leeds
>

Double entry for FreeMarker

[Paul King]

Hi all,

I noticed under Apache Projects:
https://projects.apache.org/projects.html

That FreeMarker is listed twice (even though they graduated in 2018):

   -  Apache FreeMarker
   
   -  Apache FreeMarker (Incubating)
   

Is that something we clean up on our end (Incubator) or do we leave that up
to FreeMarker? If it's our end, can someone remind me what's involved and
I'll kick it off. I'm not sure if it's just an Infra ticket or if there is
some self-service way to do it. (Or feel free to jump in if you know what's
involved.)

Cheers, Paul.

Re: [DISCUSS] Project proposal - Apache Rainbow

[Paul King]

Indeed, it does sound interesting.

I would find it useful if the "existing Apache projects" bit of "Rainbow is
in development, leveraging existing Apache projects." could be expanded in
any way. I know there is a list of external dependencies later but  any
further description of how those technologies are used would be helpful.

Also, I'd be interested in knowing how the proposal relates to DLAB:
https://dlab.apache.org/

Nice work.

Cheers, Paul.



On Sat, Feb 22, 2020 at 2:34 AM larry mccay  wrote:

> This seems like an interesting proposal.
>
> Couple points/questions:
>
> * The existing source is not available for viewing as it is still in
> private repos?
> * Is it a primarily java project?
> * It seems the intent of Rainbow is to not compete or overlap with the
> Hadoop ecosystem projects but rather to provide an efficient interface
> above them - correct?
>
>
> On Fri, Feb 21, 2020 at 8:51 AM Aviem Zur  wrote:
>
> > Hi,
> >
> > We would like to propose Rainbow as an Apache incubator project. Rainbow
> is
> > an end-to-end platform for data engineers & scientists, allowing them to
> > build, train and deploy machine learning models in a robust and agile
> way.
> > The project's goal is to operationalize the machine learning process,
> > allowing data scientists to quickly transition from a successful
> experiment
> > to an automated pipeline in production.
> >
> > The proposal can be found here:
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Apache+Rainbow
> >
> > We would appreciate your feedback and thoughts on the proposal.
> >
> > Thanks,
> > Aviem
> >
>

Re: [VOTE] Accept NLPCraft into Apache Incubator

[Paul King]

+1 (binding)


On Mon, Feb 10, 2020 at 7:54 AM Konstantin Boudnik  wrote:

> Hello.
>
> As the discussion of NLPCraft proposal [1] has been wrapped up [2] I would
> like
> to call a VOTE to accept this project into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring NLPCraft into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring NLPCraft into Incubator, because...
>
> The vote will open for at least 72 hours until midnight PDT Wednesday, Feb
> 13,
> 2020. As a reminder: only votes from the IPMC members are considered
> binding,
> but other votes are welcome!
>
>
> [1] https://cwiki.apache.org/confluence/display/INCUBATOR/NLPCraftProposal
> [2] https://s.apache.org/me4ut
>
> Thank you,
>   Cos
>
>
>

Re: [DISCUSS] NLPCraft Proposal

[Paul King]

All sounds good to me.

On Tue, Feb 4, 2020 at 4:30 PM Nikita Ivanov  wrote:

> Hi Paul,
> I'm one of the NLPCraft project members, let me chime in here.
>
> 1. The project is very interested in native Groovy/Kotlin/Scala model
> APIs. It is a bit unclear for now how much work needs to be done
> specifically for these languages given that NLPCraft provides a very plain
> (and Scala-friendly) Java APIs. I think it deserves a separate deep
> conversation.
> 2. The topic of Commons Clause (with ALV2) is very clear - if and when the
> project enters the ASF Incubator the license will change to plain Apache
> License, v2.0. There's no disagreement on this among project members.
> Thanks!
> --
> Nikita Ivanov
>
>
> On Mon, Feb 3, 2020 at 9:35 PM Paul King  wrote:
>
>> Looks like you have close to a full house for mentors. I could certainly
>> put my hat in the ring if you need another, otherwise I will certainly be
>> an interested community member. It seems like an interesting project. I
>> would have a particular interest in Groovy/Micronaut integration.
>>
>> I did notice in the current repo, usage of the Commons Clause (with ALV2).
>> The usage by Redis of something similar, albeit with notable differences,
>> was controversial a little while back but seemed to die down as per
>> LEGAL-402. As someone who hasn't been following this lately, is that
>> something the project needs to manage expectations for?
>>
>> Cheers, Paul.
>>
>>
>> On Tue, Feb 4, 2020 at 10:43 AM Konstantin Boudnik 
>> wrote:
>>
>> > Good time of the time to all!
>> >
>> > I'd like to bring this new interesting project for the discussion,
>> comments
>> > and feedback with the aim of starting a formal [VOTE] of its acceptance
>> > into
>> > Incubator.
>> >
>> > People behind this project aren't new to Apache: some of them were
>> behind
>> > the
>> > Apache Ignite incubation, which I consider a huge success as the
>> community
>> > is
>> > literally thriving almost 5 years after the graduation.
>> >
>> > I have been involved a little bit with this project when it just started
>> > privately a few years ago. And I'd like to emphasize that the community
>> > however small it might look so far, has been aligned with Apache ways of
>> > doing
>> > things. Nikita Ivanov (from Ignite PMC) is very instrumental in
>> tirelessly
>> > helping this group to learn what it means to be a truly open source
>> > project.
>> >
>> > The code is already under ALv2 and is publicly available. As you will
>> see
>> > it
>> > has a lot of organic connections with the rest of Apache ecosystem and
>> IMO
>> > will fit very well here and continue to grow the community.
>> >
>> > The project's proposal is available at [1].
>> >
>> > Thank you very much for the feedback you're willing to provide!
>> > --
>> >   With best regards,
>> > Cos
>> >
>> > [1]
>> https://cwiki.apache.org/confluence/display/INCUBATOR/NLPCraftProposal
>> >
>>
>

Re: [DISCUSS] NLPCraft Proposal

[Paul King]

Looks like you have close to a full house for mentors. I could certainly
put my hat in the ring if you need another, otherwise I will certainly be
an interested community member. It seems like an interesting project. I
would have a particular interest in Groovy/Micronaut integration.

I did notice in the current repo, usage of the Commons Clause (with ALV2).
The usage by Redis of something similar, albeit with notable differences,
was controversial a little while back but seemed to die down as per
LEGAL-402. As someone who hasn't been following this lately, is that
something the project needs to manage expectations for?

Cheers, Paul.


On Tue, Feb 4, 2020 at 10:43 AM Konstantin Boudnik  wrote:

> Good time of the time to all!
>
> I'd like to bring this new interesting project for the discussion, comments
> and feedback with the aim of starting a formal [VOTE] of its acceptance
> into
> Incubator.
>
> People behind this project aren't new to Apache: some of them were behind
> the
> Apache Ignite incubation, which I consider a huge success as the community
> is
> literally thriving almost 5 years after the graduation.
>
> I have been involved a little bit with this project when it just started
> privately a few years ago. And I'd like to emphasize that the community
> however small it might look so far, has been aligned with Apache ways of
> doing
> things. Nikita Ivanov (from Ignite PMC) is very instrumental in tirelessly
> helping this group to learn what it means to be a truly open source
> project.
>
> The code is already under ALv2 and is publicly available. As you will see
> it
> has a lot of organic connections with the rest of Apache ecosystem and IMO
> will fit very well here and continue to grow the community.
>
> The project's proposal is available at [1].
>
> Thank you very much for the feedback you're willing to provide!
> --
>   With best regards,
> Cos
>
> [1] https://cwiki.apache.org/confluence/display/INCUBATOR/NLPCraftProposal
>

Re: [VOTE] Release Apache DataSketches-java 1.2.0-incubating-RC2

[Paul King]

IANAL, but I think for an individual file your analysis is correct, i.e. no
change required if no substantive change to the file.
For the NOTICE file, my understanding is that it represents a summary for
the entire release, so best to change.
I don't have a definitive reference to give you though to confirm that
understanding.
Someone with more knowledge might correct me or be able to provide such a
reference.
I agree that it isn't implemented consistently.

 Cheers, Paul.

On Mon, Jan 27, 2020 at 5:19 AM leerho  wrote:

> Paul,
>
> WRT the year bump on Copyright notices.
>
> It is my understanding that if a file has not been substantially changed,
> that it is not necessary to change the year on a Copyright notice every
> time the year rolls over.
>
> As for the NOTICE file, it has not changed at all.  So it should not be
> necessary to change the year, unless, somehow, the NOTICE file is special.
>
> If you look at these NOTICE files: for Hadoop, it is still dated 2006;
> Spark is dated 2014;  Beam is 2016-2018, PDFBox is 2014.
> Clearly this rule, if it is truly legally required, is not consistently
> implemented.
>
> Is my understanding correct?
>
> Lee.
>
>
>
>
>
> On Sat, Jan 25, 2020 at 3:19 PM Paul King  wrote:
>
>> +1 (binding) with one minor comment
>>
>> Checked:
>> * incubating in name
>> * DISCLAIMER-WIP exists
>> * LICENSE
>> * NOTICE (year bump needed 2019 => 2019-2020 as already noted by Justin)
>> * no unexpected binary files
>> * signatures
>> * hash
>> * mvn clean install (1)
>> * mvn apache-rat:check
>>
>> (1) Works on Linux. On Windows, some tests fail with:
>> java.nio.file.InvalidPathException: Illegal char <:> at index 2 ...
>> I note your comment in the install/test guide about "path elements must
>> not
>> have any non-Java identifier characters"
>> but it wasn't clear to me that it would impact the test suite on Windows
>> or
>> whether I could do anything to avoid the problem.
>>
>> Cheers, Paul.
>>
>>
>> On Thu, Jan 23, 2020 at 11:56 AM leerho  wrote:
>>
>> > Hello IPMC and Apache DataSketches Community,
>> >
>> > 1. This is a call for vote to release Apache DataSketches-java version:
>> >  1.2.0-incubating-RC2
>> >
>> > NOTE 1: This is the core Java component of the DataSketches library
>> > that includes all the sketch algorithms in production-ready packages.
>> These
>> > sketches can be called directly from this component or used in
>> conjunction
>> > with the adaptor components such as Hadoop Pig, Hadoop Hive, or the
>> > aggregator adaptors built into Apache Druid.
>> >
>> > NOTE 2: This release contains some signifiant merge speed
>> performance
>> > improvements. See datasketches.apache.org web site for more details.
>> >
>> >   A. Results from the PPMC vote:
>> >
>> >  - 1 (+1 binding) vote, 2 (+1 non-binding) votes
>> >
>> >  - The vote thread can be found at the Permalink:
>> >
>> >
>> >
>> https://lists.apache.org/thread.html/rcd938a0dcc74e5284cf2cb6d4eca268aafb143840f52ed7ac4bd6956%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:
>> >   - verified signature and sha512 hash
>> >   - mvn install
>> >
>> > - Jon Malkin (+1 non-binding)
>> >   - verified signature and shasum
>> >   - ran tests successfully
>> >   - mvn install successfully
>> >
>> > - 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
>> >
>> > 2. Source repository:
>> > - https://github.com/apache/incubator-datasketches-java
>> >
>> > Git Tag for this release:
>> > -
>> >
>> >
>> https://github.com/apache/incubator-datasketches-java/tree/1.2.0-incubating-RC2
>> > on branch 1.2.X-incubating
>> >
>> > Git HashId for this release starts with: 97552af
>> >
>> > 3. The Release Candidate / Dist (Zip Repository):
>> > -
>> >
>&g

Re: [VOTE] Release Apache DataSketches-java 1.2.0-incubating-RC2

[Paul King]

+1 (binding) with one minor comment

Checked:
* incubating in name
* DISCLAIMER-WIP exists
* LICENSE
* NOTICE (year bump needed 2019 => 2019-2020 as already noted by Justin)
* no unexpected binary files
* signatures
* hash
* mvn clean install (1)
* mvn apache-rat:check

(1) Works on Linux. On Windows, some tests fail with:
java.nio.file.InvalidPathException: Illegal char <:> at index 2 ...
I note your comment in the install/test guide about "path elements must not
have any non-Java identifier characters"
but it wasn't clear to me that it would impact the test suite on Windows or
whether I could do anything to avoid the problem.

Cheers, Paul.


On Thu, Jan 23, 2020 at 11:56 AM leerho  wrote:

> Hello IPMC and Apache DataSketches Community,
>
> 1. This is a call for vote to release Apache DataSketches-java version:
>  1.2.0-incubating-RC2
>
> NOTE 1: This is the core Java component of the DataSketches library
> that includes all the sketch algorithms in production-ready packages. These
> sketches can be called directly from this component or used in conjunction
> with the adaptor components such as Hadoop Pig, Hadoop Hive, or the
> aggregator adaptors built into Apache Druid.
>
> NOTE 2: This release contains some signifiant merge speed performance
> improvements. See datasketches.apache.org web site for more details.
>
>   A. Results from the PPMC vote:
>
>  - 1 (+1 binding) vote, 2 (+1 non-binding) votes
>
>  - The vote thread can be found at the Permalink:
>
>
> https://lists.apache.org/thread.html/rcd938a0dcc74e5284cf2cb6d4eca268aafb143840f52ed7ac4bd6956%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:
>   - verified signature and sha512 hash
>   - mvn install
>
> - Jon Malkin (+1 non-binding)
>   - verified signature and shasum
>   - ran tests successfully
>   - mvn install successfully
>
> - 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
>
> 2. Source repository:
> - https://github.com/apache/incubator-datasketches-java
>
> Git Tag for this release:
> -
>
> https://github.com/apache/incubator-datasketches-java/tree/1.2.0-incubating-RC2
> on branch 1.2.X-incubating
>
> Git HashId for this release starts with: 97552af
>
> 3. The Release Candidate / Dist (Zip Repository):
> -
>
> https://dist.apache.org/repos/dist/dev/incubator/datasketches/java/1.2.0-incubating-RC2/
>
> 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: [Nexus](http://repository.apache.org) (Jar Artifacts):
> -
>
> https://repository.apache.org/content/groups/staging/org/apache/datasketches/datasketches-java/1.2.0-incubating/
>
> 5. Build & Test Guide:
> -
>
> https://github.com/apache/incubator-datasketches-java/blob/1.2.0-incubating-RC2/README.md
>
> 6. This vote 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
>

Re: [VOTE] Myriad retirement

[Paul King]

+1 (binding)

Cheers, Paul.

On Fri, Jan 24, 2020 at 1:14 AM Javi Roman  wrote:

> Unfortunately, despite an effort to reboot the project about more than one
> year, we weren't successful in keeping the existing committers active. At
> this point, a decision to retire the podling was taken, and a vote was done
> on the PPMC:
>
> Discussion:
>
> https://lists.apache.org/thread.html/ea7567bede20e2c0fc9d0c3ea2713e2b2a7442897ceafdeb1aa95b05%40%3Cdev.myriad.apache.org%3E
>
> Result:
>
> https://lists.apache.org/thread.html/r5d8a123ad051f748379904066cde17b93974ed2628593ebd69dee028%40%3Cdev.myriad.apache.org%3E
>
> According to https://incubator.apache.org/guides/retirement.html I'm
> starting a vote on the incubator mailing list to be ratified the
> retirement.
>
>
> [ ] +1   : retire Myriad
> [ ] +/-0 : No opinion
> [ ] -1   : Don't retire Myriad.
>
>
> Many thanks.
>
> --
> Javi Roman
>
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
> Apache Id: javiroman
>

Re: [VOTE] Accept YuniKorn into Apache Incubator

[Paul King]

+1 (binding)


On Sat, Jan 11, 2020 at 3:47 AM Vinod Kumar Vavilapalli 
wrote:

> Hi,
>
> I'd like to call a vote on accepting YuniKorn into the Apache Incubator.
>
> Please see the discussion thread [1].
>
> Please see the full proposal:
> https://cwiki.apache.org/confluence/display/INCUBATOR/YuniKornProposal
>
> Please cast your vote
>
> [ ] +1 Accept YuniKorn into the Incubator
> [ ] +0 Indifferent to the acceptance of YuniKorn
> [ ] -1 Do not accept YuniKorn because …
>
> The vote will be open at least for 72 hours.
>
> Incubator PMC member votes are binding. Everyone else is welcomed to vote
> too (mark them as non-binding if you can)!
>
> Thanks
> +Vinod
>
> [1] [DISCUSS] YuniKorn Proposal
> https://lists.apache.org/thread.html/59a3fc019119352f06e75a2bae5c25cd1b652282d7a59b85ed2188cf%40%3Cgeneral.incubator.apache.org%3E
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Superset (incubating) version 0.35.2

[Paul King]

+1 (binding) with some minor comments below

Checked:
- incubating in name
- checksum
- signature
- didn't appear to have any binary files within tarball (apart from images)
- builds from source (with version change)

Comments:
- I followed the instructions in RELEASING/README.md to build from source
but it wasn't clear whether there was an alternative way; perhaps mention
some clearer instructions on building from source in the root README.md or
INSTALL.md for next release
- the root README.md seems to have an old link wrt contributing which
should be fixed when you get a chance
- RELEASING/README.md has a 0.33.xx version which should be 0.35.xx. It
seems to be either a typo or a hard-coded value which should be automated
at some point. I don't regard it as a showstopper since it seems an obvious
typo to me.

Cheers, Paul.


On Fri, Jan 10, 2020 at 5:14 AM Ville Brofeldt 
wrote:

> Hello IPMC,
>
>
> The Apache Superset (incubating) community has voted on and approved a
> proposal to
>
> release Apache Superset (incubating) version 0.35.2.
>
> The voting thread can be found here:
>
> https://lists.apache.org/thread.html/rf8b1cbe6c880d408583448e5a96e08b90da1258c7cdaf4658836%40%3Cdev.superset.apache.org%3E
>
>
> We now kindly request the Incubator PMC members review and vote on this
>
> incubator release.
>
>
> Apache Superset (incubating) is a modern, enterprise-ready business
> intelligence web application.
>
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/superset/0.35.2rc2/
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-superset/tree/0.35.2rc2
>
>
> The Change Log for the release:
>
> https://github.com/apache/incubator-superset/blob/0.35.2rc2/CHANGELOG.md
>
>
> public keys are available at:
>
>
> https://www.apache.org/dist/incubator/superset/KEYS
>
>
> The vote will be open for at least 72 hours or until the necessary number
>
> of votes are reached.
>
>
> Please vote accordingly:
>
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
>
> Thanks,
>
> The Apache Superset (Incubating) Team
>

Re: [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

[Paul King]

+1 binding
Cheers, Paul.

On Sun, Dec 8, 2019 at 7:55 AM Gian Merlino  wrote:

> Earlier this year, Druid voted to graduate to a top level project. The vote
> passed in the Druid community and the Incubator, and a resolution was
> submitted to the Board, but needed to be shelved at the last minute. We are
> now ready to proceed to graduation once again, and so I would like to call
> another vote. The Druid project has re-voted and has notified the Board of
> these developments. We now seek consent from the Incubator community to
> propose a graduation resolution for the Dec 18 board meeting.
>
> The proposed graduation resolution is nearly the same as last time; the
> only changes are the addition of four new initial members (fokko, furkan,
> qmm, and vogievetsky).
>
> For reference,
>
> 1) The Druid vote that was just held:
>
> https://lists.apache.org/thread.html/3b1432780b8d841fffce3033cd5cc39fe1fe0f46feccb96f036dbf01%40%3Cdev.druid.apache.org%3E
>
> 2) Our prior Incubator graduation vote, which passed earlier this year:
>
> https://lists.apache.org/thread.html/19b703fdf192ddf8e31bda57264e03113c7e44b5954a56886e05@%3Cgeneral.incubator.apache.org%3E
>
> Please take a minute to vote on whether or not Apache Druid should graduate
> to a Top Level Project by responding with one of the following:
>
> [ ] +1 Apache Druid should graduate
> [ ]  0 No opinion
> [ ] -1 Apache Druid should not graduate because...
>
> The VOTE is open for a minimum of 72 hours.
>
> ---
>
> Establish Apache Druid 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 analytical database
> software, for distribution at no charge to the public.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "The Apache Druid Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that The Apache Druid Project be and hereby is
> responsible for the creation and maintenance of an analytical
> database software project; and be it further
>
> RESOLVED, that the office of "Vice President, Druid" 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
> Druid Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of
> The Apache Druid 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 Druid Project:
>
>   * Benedict Jin (asdf2...@apache.org)
>   * Charles Allen(cral...@apache.org)
>   * Clint Wylie  (cwy...@apache.org)
>   * David Lim(david...@apache.org)
>   * Dylan Wylie  (dylanwy...@apache.org)
>   * Eric Tschetter   (ched...@apache.org)
>   * Fangjin Yang (f...@apache.org)
>   * Fokko Driesprong (fo...@apache.org)
>   * Furkan Kamaci(kam...@apache.org)
>   * Gian Merlino (g...@apache.org)
>   * Himanshu Gupta   (himans...@apache.org)
>   * Jihoon Son   (jihoon...@apache.org)
>   * Jonathan Wei (jon...@apache.org)
>   * Julian Hyde  (jh...@apache.org)
>   * Kurt Young   (k...@apache.org)
>   * Lijin Bin(binli...@apache.org)
>   * Maxime Beauchemin(maximebeauche...@apache.org)
>   * Mingming Qiu (q...@apache.org)
>   * Niketh Sabbineni (nik...@apache.org)
>   * Nishant Bangarwa (nish...@apache.org)
>   * P. Taylor Goetz  (ptgo...@apache.org)
>   * Parag Jain   (pja...@apache.org)
>   * Roman Leventov   (leven...@apache.org)
>   * Slim Bouguerra   (bs...@apache.org)
>   * Surekha Saharan  (sure...@apache.org)
>   * Xavier Léauté(x...@apache.org)
>   * Vadim Ogievetsky (vogievet...@apache.org)
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gian Merlino
> be and hereby is appointed to the office of Vice President,
> Druid, 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 or disqualification, or
> until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Druid Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Druid podling; and be it further
>
> RESOLVED, that all responsibility pertaining to the Apache
> Incubator Druid podling encumbered upon the Apache Incubator
> PMC are hereafter discharged.
>

Re: [VOTE] Apache BatchEE leaving the incubator

[Paul King]

+1  to join Apache Geronimo

On Fri., 6 Dec. 2019, 5:51 pm Romain Manni-Bucau, 
wrote:

> Hi everyone,
>
> BatchEE community voted to leave the incubator to join Apache Geronimo as a
> subproject.
>
> Here is the vote thread:
> http://mail-archives.apache.org/mod_mbox/batchee-dev/201912.mbox/browser
>
> Please vote:
>
>  [ ] +1 to retire Sirona
>  [ ] -1 to retire Sirona ${cause}
>
> Vote will be opened for 3 days or until 3 +1 bindings are reached as usual
>
> Here is my +1
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>

Re: [VOTE] Accept NuttX into the Apache Incubator

[Paul King]

+1 binding

On Wed, Dec 4, 2019 at 3:30 PM 俊平堵  wrote:

> Hi folks,
>
>
> The [DISCUSS] thread on NuttX has died down.
>
>
> Accordingly, I would like to call a VOTE to accept NuttX into the
>
> Apache Incubator.
>
>
> Please cast your vote:
>
>
>   [ ] +1, bring NuttX into the Incubator
>
>   [ ] +0, I don't care either way
>
>   [ ] -1, do not bring NuttX into the Incubator, because...
>
>
> The vote will open at least for 72 hours and only votes from the
>
> Incubator PMC are binding, but votes from everyone are welcome.
>
>
> =Abstract=
>
> NuttX is a mature, real-time embedded operating system (RTOS).  It has wide
> usage in IoT projects, control systems, robotics, drones, and many other
> systems.  Unique properties of NuttX are its strict adherence to standards
> and its scalability. NuttX follows the Unix standards as defined
> by OpenGroup.org (POSIX, ANSI, and others).  This allows for a high degree
> of portability. Scalability is supported through a configuration system
> that allows NuttX to run on the smallest embedded platforms and through
> high end single board computers.
>
>
> =Proposal=
>
> NuttX was released under a BSD 3-Clause license on February 17, 2007.  From
> that time until now it has been managed by a single person, Gregory Nutt.
> The user base of NuttX has grown to probably thousands of projects and
> perhaps a hundred active developments at any time.  The code base has grown
> to around 1.5 million lines of code (according to OpenHub.com).
>
> NuttX has benefited from this single person management because this has
> resulted in a consistent architecture and controlled growth.  But now it is
> time to open this project to the participation of others because this
> consistent architecture assures solid future growth, and because the
> magnitude of effort required to support the RTOS exceeds the capability of
> a single person, but also because users of NuttX require a stable road map
> going forward that does not depend on a single person.
>
> For these reasons, I propose that NuttX enter the Apache Incubator as a
> first step in opening the project to wider participation.
>
>
> =Initial Goals=
>
> The initial goal will be to move the existing BSD code base to Apache and
> integrate with the Apache development process and infrastructure. A primary
> goal of incubation will be to grow and diversify the NuttX community. We
> will convert that code base to the Apache license during incubation.
>
>
> =Current Status=
>
> As previously mentioned, NuttX is a mature, stable product in wide use in
> embedded products.
>
>
> ==Meritocracy==
>
> We value meritocracy and we understand that it is the basis for an open
> community that encourages multiple companies and individuals to contribute
> and be invested in the project’s future. We will encourage and monitor
> participation and make sure to extend privileges and responsibilities to
> all contributors.
>
> Being a mature project, NuttX already has an extensive user base with many
> people who understand the software, who have committed hundreds of changes,
> and are happy to participate in the project.  I believe that with a little
> guidance and formalization, a PMC and a large group of experienced
> committers can quickly be established.
>
>
> ==Community==
>
> NuttX has a large, active community.  Communication is via a Google group
> at https://groups.google.com/forum/#!forum/nuttx where there are 395
> members as of this writing.  Code is currently maintained
> at Bitbucket.org at https://bitbucket.org/nuttx/.  Other communications
> are
> through Bitbucket issues and also via Slack for focused, interactive
> discussions.
>
> Keeping up with the communications, requests for help, issues, and
> contributions is more than a full time job at this time.
>
>
> ==Core Developers==
>
> NuttX was initially developed by Gregory Nutt, released as an open source
> project on February 17, 2007, and is still under active development.  There
> are several dozen, active, frequent contributors involved with the project.
> The core OS can be considered finished at this point, but development
> continues in specialized areas of networking, IoT, cryptography, tools, and
> other more specialized functions.
>
>
> =Alignment=
>
> NuttX is an original development with some small percentage of ported
> code.  It stands alone depends on no other projects.
>
>
> =Known Risks=
>
> ==Orphaned Products==
>
> We are committed to the future development of NuttX and understand that
> graduation to a TLP, while preferable, is not the only positive outcome of
> incubation.
>
> Should the NuttX project be accepted by the Incubator, the prospective PPMC
> would be willing to agree to a target incubation period of 2 years or less,
> knowing that every Incubator project incurs a certain cost in terms of ASF
> infrastructure and volunteer time.
>
>
> ==Inexperience with Open Source==
>
> None of the initial committers are Apache members and we will need some
> help 

Re: Remove PMC incubator page

[Paul King]

+1

On Fri, Oct 18, 2019 at 6:59 PM Justin Mclean 
wrote:

> Hi,
>
> The page here [1] doesn’t really add anything that is not written out
> elsewhere and seems redundant. If no-one objects I’ll remove it.
>
> Thanks,
> Justin
>
>
> 1. https://incubator.apache.org/guides/pmc.html
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Recommend Apache Rya graduation to Top Level Project resolution to the Board

[Paul King]

+1

On Fri., 6 Sep. 2019, 6:29 pm Adina Crainiceanu,  wrote:

> The Apache Rya (incubating) community is bringing the attached resolution
> to graduate to a Top Level Project up for a formal IPMC VOTE.
>
> -We completed all the tasks documented in the status file [1]
> -The name Apache Rya was approved by the Brand Management Committee [2]
> -We had four Apache releases with three different release managers
> -Our community grew during incubation and we learned to function following
> the Apache Way
> -We discussed on the dev@ list about our readiness for graduation [3], we
> voted [4], and the result of the vote was positive [5]
> -We went through the process of assessing our project against the Apache
> Maturity model [6] and we believe we are ready to graduate and continue to
> grow as a Top Level Project.
> -We worked on creating a graduation resolution and we selected a Chair [7].
>
> Please take a minute to vote on whether or not the IPMC should recommend
> the resolution below to the Board by responding with one of the following:
>
> [ ] +1 Apache Rya should graduate
> [ ]  0 No opinion
> [ ] -1 Apache Rya should not graduate because...
>
> The VOTE is open for a minimum of 72 hours.
>
> Thank you,
> Adina, on behalf of Apache Rya (incubating) community
>
> [1] https://incubator.apache.org/projects/rya.html
> [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-135
> [3]
>
> https://lists.apache.org/thread.html/dd09c2060a754e69e093404e0d57239a555ab5e7d702cf76fd02f820@%3Cdev.rya.apache.org%3E
> [4]
>
> https://lists.apache.org/thread.html/10f04a55e0f6d4c09d3ffeac487b0bf309eb8e5058f950778214faeb@%3Cdev.rya.apache.org%3E
> [5]
>
> https://lists.apache.org/thread.html/d1664b17d8a6bf3d3e4e5f28382bc360fe974f1db8f880c6d97ff278@%3Cdev.rya.apache.org%3E
> [6]
>
> https://cwiki.apache.org/confluence/display/RYA/Apache+Maturity+Evaluation+for+Rya
> [7]
>
> https://lists.apache.org/thread.html/3007163bc654df45109c38b4d9a53c7b2137ad0fef660429938a282b@%3Cprivate.rya.apache.org%3E
>
> _
> Proposed graduation resolution:
>
> Establish the Apache Rya 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 scalable storage, retrieval, and analysis of RDF data.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Rya Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Rya Project be and hereby is responsible for
> the creation and maintenance of software related to scalable storage,
> retrieval, and analysis of RDF data; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Rya" 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 Rya Project, and to
> have primary responsibility for management of the projects within the
> scope of responsibility of the Apache Rya 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 Rya Project:
>
>  * Aaron Mihalik 
>  * Adina Crainiceanu 
>  * Billie Rinaldi
>  * Caleb Meier   
>  * David Lotts   
>  * David Rapp
>  * Jennifer Brown
>  * Josh Elser
>  * Puja Valiyil  
>  * Roshan Punnoose   
>  * Steve R Wagner
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Adina Crainiceanu be
> appointed to the office of Vice President, Apache Rya, 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 or disqualification, or until a successor is appointed; and be
> it further
>
> RESOLVED, that the Apache Rya Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Rya podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Rya podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>

Re: [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

[Paul King]

+1 (binding)

Good luck!
Cheers, Paul.

On Tue, Aug 13, 2019 at 5:03 PM Gian Merlino  wrote:

> The Apache Druid community has recently discussed our readiness for
> graduation [1] and voted on it affirmatively [2, 3]. We've also assessed
> ourselves against the maturity model [4] and collaborated on a resolution
> for graduation including PMC membership and PMC chair.
>
> The community's achievements since entering the Incubator in early 2018
> include the following:
>
> - Accepted 1240 patches from 142 contributors
> - Performed 5 releases with 4 different release managers
> - Invited 10 new committers
> - Some time later on, invited all 10 of those new committers to join the
> PMC (those that have accepted are named in the resolution below)
> - Migrated development to Apache's GitHub org:
> https://github.com/apache/incubator-druid
> - Migrated our web site to https://druid.apache.org/
> - Migrated developer conversations to the list at d...@druid.apache.org
>
> Now the Druid community is bringing the attached resolution up for a formal
> IPMC VOTE.
>
> Please take a minute to vote on whether or not Apache Druid should graduate
> to a Top Level Project by responding with one of the following:
>
> [ ] +1 Apache Druid should graduate
> [ ]  0 No opinion
> [ ] -1 Apache Druid should not graduate because...
>
> The VOTE is open for a minimum of 72 hours.
>
> [1]
>
> https://lists.apache.org/thread.html/68fcc3d2fc66c7f559e2c9dd02478d17f195565fecdb07ed53bc965e@%3Cdev.druid.apache.org%3E
> [2]
>
> https://lists.apache.org/thread.html/10c615a7648db14a268759be91f4b1eff448960f5338e0d416c7373a@%3Cdev.druid.apache.org%3E
> [3]
>
> https://lists.apache.org/thread.html/7517dd38fbeb28978b1188bed1d69e91445927d13d520a4c71ae9fcf@%3Cdev.druid.apache.org%3E
> [4] https://gist.github.com/gianm/33ae4d61ebaa8b8714d9e2f51a11e7f7
>
> --
>
> Establish Apache Druid 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 analytical database
> software, for distribution at no charge to the public.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "The Apache Druid Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that The Apache Druid Project be and hereby is
> responsible for the creation and maintenance of an analytical
> database software project; and be it further
>
> RESOLVED, that the office of "Vice President, Druid" 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
> Druid Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of
> The Apache Druid 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 Druid Project:
>
>   * Benedict Jin (asdf2...@apache.org)
>   * Charles Allen(cral...@apache.org)
>   * Clint Wylie  (cwy...@apache.org)
>   * David Lim(david...@apache.org)
>   * Dylan Wylie  (dylanwy...@apache.org)
>   * Eric Tschetter   (ched...@apache.org)
>   * Fangjin Yang (f...@apache.org)
>   * Gian Merlino (g...@apache.org)
>   * Himanshu Gupta   (himans...@apache.org)
>   * Jihoon Son   (jihoon...@apache.org)
>   * Jonathan Wei (jon...@apache.org)
>   * Julian Hyde  (jh...@apache.org)
>   * Kurt Young   (k...@apache.org)
>   * Lijin Bin(binli...@apache.org)
>   * Maxime Beauchemin(maximebeauche...@apache.org)
>   * Niketh Sabbineni (nik...@apache.org)
>   * Nishant Bangarwa (nish...@apache.org)
>   * P. Taylor Goetz  (ptgo...@apache.org)
>   * Parag Jain   (pja...@apache.org)
>   * Roman Leventov   (leven...@apache.org)
>   * Slim Bouguerra   (bs...@apache.org)
>   * Surekha Saharan  (sure...@apache.org)
>   * Xavier Léauté(x...@apache.org)
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gian Merlino
> be and hereby is appointed to the office of Vice President,
> Druid, 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 or disqualification, or
> until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Druid Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Druid podling; and be it further
>
> RESOLVED, that all responsibility pertaining to the Apache
> Incubator Druid podling encumbered upon the Apache Incubator
> PMC are hereafter discharged.
>

Re: [DISCUSS] IPMC votes on releases

[Paul King]

Another variation/option for those using the WIP disclaimer might be that
since the WIP disclaimer kind of says this release doesn't have "full
official" status from an ASF point of view then one way of thinking about
it is that perhaps full official IPMC endorsement is less of a requirement
so IPMC voting could be 3 days but lazy. If you don't get more -1 votes
than +1 votes after 3 days, you can go ahead and publish. Outside WIP
disclaimer projects, if there are projects which are repeatedly not getting
enough IPMC votes, then IPMC membership by an experienced PPMC member could
be considered as an option, so +1 for your (D) I believe.

I have no problem giving +1 to (E) at all but in reality, it is almost no
effort for the 3 mentioned IPMC members on the dev list to just +1 the IPMC
vote, so are we picking up the real problem podlings?

On Fri, Aug 9, 2019 at 3:04 PM Justin Mclean 
wrote:

> Hi,
>
> One of the incubator pain points is the double voting on releases first by
> the podling and then by the IPMC.
>
> Historically there been a lot of discussion about this and a couple of
> proposals to try and change it, but none have been accepted. There have
> been proposals on alternative ways to vote and to ask for guidances which
> have been accepted, but podlings don’t seem to take these options up. I’m
> hoping the recent DISCLAIMER-WIP is one that is used more by podlings, and
> go some way to helping podling get releases out, but time will tell.
>
> When consider what to do about this, please keep this in mind:
> 1. Only PMC members can have binding votes on releases (it’s in our
> bylaws) so a minimum of 3 IPMC votes are require to make a release.
> 2. Podlings are not TLP and don’t have a PMC and PPMC members votes are
> not binding on releases.
> 3. The IPMC picks up some serious issues in (about 1 in 5) releases by
> checking this way. This is mostly, but not always, on the early releases.
>
> So option (A) would be to get the Bylaws changed and treat podlings as
> TLPs.
>
> Another option (B) is to get all mentors to vote on every release. We’ve
> tried this via various means and it seems only a couple of podlings can
> manage this.
>
> One (perhaps not carefully considered) option (C) would be to vote in all
> PPMC members as IPMC and make PPMC members IPMC members when projects are
> first created rather than incubator committers. If we did this we could
> optionally gate graduation on a review of a podlings releases but that may
> be unpopular. There have also been complaints in the past that he IPMC is
> too large, so increasing the IPMC size this way may also not be popular.
>
> A variation on (C) let call it option (D) would be to vote in podling
> release mangers into the IPMC after they have done a number of releases
> along with podling committers that provide good feedback on a number of
> release candidates. That way when starting out a podling is likely to need
> the IPMC help, but one they have a few releases under their belts they will
> have enough IPMC votes without having to reply on mentors or other IPMC
> members. It would also encourage more careful voting on releases, If you
> just go +1 with giving some detail you’re not going to be voted into the
> IPMC. This wouldn't require any bylaws or policy change, we could just go
> ahead and do it. It would require the mentors help in identifying good
> candidates.
>
> One further idea I have is (E) is that if a podling does have 3 IPMC votes
> on it dev list and are using the DISCLAIMER-WIP disclaimer, they can just
> notify the IPMC that they are making a release, the IPMC can review it and
> and any issues or feedback found can incorporated into the next release or
> before graduation as per [1]. This may mean that there’s a risk that a
> release has to be taken down and redone - (see issues that are blockers in
> that ticket), but most issues found over the notification it would be
> business as usual.
>
> So IMO options (A) and (C) above seem unlikely to happen, and (B) isn’t
> really working, but option (D) combined with (E) along with the recent
> DISCLAIMER-WIP I think could would improve the situation.
>
> Does anyone have any other ideas they care to share?
>
> Thanks,
> Justin
>
> 1. https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-469
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [MENTORS] IPMC Policy change work in progress disclaimer

[Paul King]

Kudos for progressing this idea. I really like it. It should allow
improvements from the perspective of both podlings and reviewers.

Cheers, Paul.

On Fri, Aug 2, 2019 at 12:25 PM Justin Mclean 
wrote:

> Hi,
>
> The work in progress progress disclaimer (DISCLAIMER-WIP) has been added
> to the IPMC policy page. [1]
>
> Podlings can now select which disclaimer they want to use. If they want to
> use the standard disclaimer then their releases must comply with all ASF
> policy. If they want the incubator to be more lenient in voting on their
> release or know that the release has some issues not in line with ASF
> policy then the work in progress disclaimer can be used.
>
> Unless the release is simple and straightforward, I would recommend that a
> podling uses the work in progress disclaimer for the first couple of
> releases.
>
> For what is allowed under the work in progress disclaimer please see this
> legal JIRA [2]. This allows a lot more in a release but not everything.
> Certain things are required like having a LICENSE, NOTICE and
> DISCLAIMER-WIP, and while it would be OK to include compiled code you still
> need to comply with any licensing for that code.
>
> By the time a podling graduates it's expected that they are making
> releases with the standard disclaimer.
>
> Here is the text of the DISCLAIMER-WIP where the Incubator is the sponsor:
> 
> Apache  #Podling-Name# is an effort
> undergoing incubation at The Apache Software Foundation (ASF),
> sponsored by the Apache Incubator. Incubation is required of all
> newly accepted projects until a further review indicates that the
> infrastructure, communications, and decision making process have
> stabilized in a manner consistent with other successful ASF projects.
> While incubation status is not necessarily a reflection of the
> completeness or stability of the code, it does indicate that the
> project has yet to be fully endorsed by the ASF.
>
> Some of the incubating project's releases may not be fully compliant
> with ASF policy. For example, releases may have incomplete or
> un-reviewed licensing conditions. What follows is a list of known
> issues the project is currently aware of (note that this list, by
> definition, is likely to be incomplete):
> #List of known issues go here#
>
> If you are planning to incorporate this work into your
> product/project, please be aware that you will need to conduct a
> thorough licensing review to determine the overall implications of
> including this work. For the current status of this project through the
> Apache
> Incubator visit:
> http://incubator.apache.org/project/#Podling-Name#.html
> 
>
> Just fill in #Podling-Name# with your podling name and list the known
> issues in the correct place.
>
> Thanks,
> Justin
>
> 1. https://incubator.apache.org/policy/incubation.html#disclaimers
> 2. https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-469
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Heron Release 0.20.1-incubating Release Candidate 3

[Paul King]

+1 (binding)

I checked:
- incubating in name
- DISCLAIMER present
- Signature and hashes okay
- LICENSE is missing a number of permissive licenses (I didn't check ones
Justin had already covered but third_party\python\semver seems to be
missing from list of BSD licensed software though it does appear in your
rat excludes - please add for next release)
- NOTICE has incorrect year (please update for next time)
- No unexpected binary files
- All ASF files have correct headers
- didn’t compile from source

Cheers, Paul.



On Fri, Jul 26, 2019 at 12:02 PM Justin Mclean 
wrote:

> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signature and hashes fine
> - LICENSE is missing a number of permissive licenses (see below)
> - NOTICE has incorrect year (please update)
> - No unexpected binary files
> - All ASF file have correct headers
> - didn’t compile form source
>
> Licence is misisng
> -  MIT licensed software copyright  Facebook [1][2][3][4][5][6]
> - ALv2 files [7][8]
> - ALv2 files [9][10][11][12][13][14][15][16]
> - this ALv2 file [17]
> - this  ALv2 file [18]
> - this ALv2 file [19]
> - this file [20] includes Sizzle (MIT, BSD, and GPL Licenses)
> - this file [21] includes modernizr (MIT licensed)
>
> (I just did a search for the word copyright and match what was listed in
> the LICENSE file if you’re wondering how I found these)
>
> Thanks,
> Justin
>
> 1. ./website2/website/core/Footer.js
> 2. ./website2/website/siteConfig.js
> 3. ./website2/website/pages/en/users.js
> 4. ./website2/website/pages/en/index.js
> 5. ./website2/website/pages/en/help.js
> 6. ./website2/website/pages/en/versions.js
> 7. ./tools/rules/pex/pex_rules.bzl
> 8. ./tools/rules/pex/wrapper/pex_wrapper.py
> 9. ./scripts/setup-eclipse.sh
> 10. ./scripts/detect_os_type.sh
> 11. ./scripts/get_all_heron_paths.sh
> 12. ./scripts/packages/template_bin.sh
> 13. ./scripts/packages/self_extract_binary.bzl
> 14. ./scripts/packages/package_info_generator.sh
> 15. ./scripts/packages/tests_template_bin.sh
> 16. ./scripts/packages/bin_common.sh
> 17. ../heron/shell/src/python/handlers/healthhandler.py
> 18. ./third_party/java/bazel/extra_actions_base.proto
> 19.
> ./third_party/java/jarjar/src/main/resources/com/tonicsystems/jarjar/help.txt
>
> 20. ./heron/shell/assets/jquery.js
> 21 ./heron/tools/ui/resources/static/js/bootstrap.js
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Rya (Incubating) version 4.0.0 RC1

[Paul King]

+1 (binding)

I checked:
- incubating in name
- signatures and hashes okay
- DISCLAIMER exists
- NOTICE year needs updating as previously noted (fix next release)
- LICENSE is okay
- No unexpected binary files
- Al files have ASF headers
- `mvn -DskipTests clean install` passes
- `mvn clean install` fails (probably my machine)



On Tue, Jul 23, 2019 at 8:24 AM Aaron D. Mihalik 
wrote:

> The Apache Rya community has voted and approved the proposed release of
> Apache Rya 4.0.0 (Incubating) RC1.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
> supports SPARQL queries. Rya is a scalable RDF data management system built
> on top of Apache Accumulo®. Rya uses novel storage methods, indexing
> schemes, and query processing techniques that scale to billions of triples
> across multiple nodes. Rya provides fast and easy access to the data
> through SPARQL, a conventional query mechanism for RDF data. More
> information can be found at http://rya.incubator.apache.org/
>
> [VOTE] Thread:
>
> https://lists.apache.org/thread.html/e4ac6e5908dd61912d9f6423d6eab794fc07a77db5a3606b583bef60@%3Cdev.rya.apache.org%3E
>
> [VOTE][RESULT] Email:
>
> https://lists.apache.org/thread.html/a26193173404558eec762a39dd8ab87890c9fd536c37a8f6d1ae0f85@%3Cdev.rya.apache.org%3E
>
> The source zip, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-incubating-4.0.0-rc1/
>
> Ancillary artifacts such as poms, jars, wars, ect. can be found here:
>
> https://repository.apache.org/content/repositories/orgapacherya-1011/org/apache/rya/
>
> The Git tag is rya-incubating-4.0.0-rc1
> The Git commit ID is 824090ac1b33c3b4ba52bfb8a67abfdc4f0ceea3
>
> https://gitbox.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=824090ac1b33c3b4ba52bfb8a67abfdc4f0ceea3
>
> Checksums of rya-project-4.0.0-source-release.zip:
> SHA1: e5e91b19abddbdf3c9f0e18469433e730bef7957
> MD5: 1d46620a37df803c3ba0b1b383c1da10
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/mihalik.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>
> Issues that were closed/resolved for this release are here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319020=12341289
>
>
> The vote will be open for 72 hours and close at 6:30 PM Thursday, July 25,
> 2019 (EDT).
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.  Then
> please vote:
>
> [ ] +1 Release this package as rya-project-4.0.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>

Re: DLab needs help

[Paul King]

I've jumped on their dev list as well and can try to help out informally.
Let's see how it goes with Furkan helping and I consider a more formal role
if they still need help.

Cheers, Paul.

On Wed, Jul 24, 2019 at 8:37 PM Furkan KAMACI 
wrote:

> Hi,
>
> Thanks Justin! I've just started to write an email.
>
> Kind Regards,
> Furkan KAMACI
>
> On Wed, Jul 24, 2019 at 1:23 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > I am volunteer to be a mentor for Apache DLab.
> >
> > Thanks a lot for volunteering, I’ve added you as mentor, please go and
> > introduce yourself on their list and help where you can.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: Cookbook and duplication of content on incubator site

[Paul King]

All sounds good to me too! +1

On Wed, Jul 24, 2019 at 6:26 PM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi Justin,
>
> Thank you for addressing this, I was planning to work on this
> duplication of content but didn't get to it yet.
>
> On Wed, Jul 24, 2019 at 8:44 AM Justin Mclean 
> wrote:
> > With the cookbook added [1] I suggest that we remove this page:
> > https://incubator.apache.org/policy/process.html
>
> +1
>
> > And move this page:
> > https://incubator.apache.org/policy/roles_and_responsibilities.html
> > To:
> > https://incubator.apache.org/guides/roles_and_responsibilities.html
>
> +1
>
> > And heavily cut down this page:
> > https://incubator.apache.org/policy/incubation.html
> > to remove anything that not actually IPMC policy.
>
> +1 as you suggest.
>
> > ...And that leaves:
> > - Podling Constraints and sub headings
>
> Note that the branding constraints are already pointed to by
> http://incubator.apache.org/cookbook/#publicity_and_announcements
>
> >
> > We should add the section under "Podling Website Requirements” from:
> > https://incubator.apache.org/guides/sites.html
> > to this policy page with a few adjustments, like the need a disclaimer
> on the podling web site.
>
> +1
>
> > What do other IPMC members think?..
>
> +1 and thank you!
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: DataSketches needs some help

[Paul King]

I have subscribed to their dev list. I'll try to help out a bit informally
if I can. If needed I might be able to assist with Mentoring but I don't
have a lot of cycles free at the moment.

Cheers, Paul.

On Wed, Jul 24, 2019 at 10:57 AM Justin Mclean 
wrote:

> Hi,
>
> DataSketches seems to be having some issues getting started and needs some
> extra mentor help.  Is anyone willing to help out by mentoring the project?
>
> DataSketches [1] is an open source, high-performance library of stochastic
> streaming algorithms commonly called "sketches" in the data sciences.
> Sketches are small, stateful programs that process massive data as a stream
> and can provide approximate answers, with mathematical guarantees, to
> computationally difficult queries orders-of-magnitude faster than
> traditional, exact methods.
>
> Thanks,
> Justin
>
> 1. http://datasketches.apache.org
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: New disclaimer text

[Paul King]

+1 for:
DISCLAIMER-PERMISSIVE or DISCLAIMER-WIP


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Jul 17, 2019 at 5:05 PM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi,
>
> On Wed, Jul 17, 2019 at 8:06 AM Justin Mclean 
> wrote:
> > - Keep the existing one called as it is...
>
> And have it mention the possible additional disclaimers, as DISCLAIMER-*
> maybe.
>
> >... Name the new one something like DISCLAIMER-PERMISSIVE,
> DISCLAIMER-ISSUES,
> > DISCLAIMER-INITIAL, or DISCLAIMER-PROGRESS...
>
> I suggest DISCLAIMER-WIP as in Work In Progress.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.5.0.rc2

[Paul King]

+1 binding

checked signature/checksum/disclaimer
license seems very thorough but two possible clarifications are suggested
below (*)
ran `make lib/libmxnet.so` successfully (opencv was listed as an optional
dependency but it seemed to be needed for this to work)
ran `make scalapkg` to generate Scala/Java jars (seemed to need to set
LD_LIBRARY_PATH for this to work)
ran `make ratcheck`
ran some Groovy/MXNet examples with the new jars - all worked

Cheers, Paul.


(*) I can't be sure without understanding the history but it seems like
there is possibly scope
to improve clarity for these two files for future releases:

10. ONNX Export module (python/mxnet/contrib/onnx/mx2onnx/LICENSE)
14. cmake/Modules/FindJeMalloc.cmake

It looks like both are based on some original but have been modified but
there are just two
different copyright notices with Apache License just pasted above the
previous one.
Hard to tell just from that what the history is. It might be clearer with
some additional wording, e.g.

--.8---
Originally based on code with the following license:

  Original license text

And has been modified by the Apache MXNet project. Modifications have the
following license:

Apache License text
--.8---

But maybe there is further history behind those files, so hard to tell for
sure.



On Wed, Jul 10, 2019 at 7:34 PM Lai Wei  wrote:

> Dear community,
>
> This is a call for a releasing Apache MXNet (incubating) 1.5.0, release
> candidate 2.
>
> Apache MXNet (incubating) community has voted and approved the release.
>
> Vote thread:
>
> https://lists.apache.org/thread.html/50fe473a3e03c891caccb8cae8e5195bb740a4758f7688790dff70df@%3Cdev.mxnet.apache.org%3E
>
> Result thread:
>
> https://lists.apache.org/thread.html/641cf0fddce623ff352ba9c7655938c0d16337bae4a8d290956ea130@%3Cdev.mxnet.apache.org%3E
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.5.0.rc2/
>
> The tag to be voted upon is 1.5.0.rc2:
> https://github.com/apache/incubator-mxnet/releases/tag/1.5.0.rc2
>
> The release hash is 75a9e18:
>
> https://github.com/apache/incubator-mxnet/commit/75a9e187d00a8b7ebc71412a02ed0e3ae489d91f
>
> Release artifacts are signed with the following key, KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
>
> For information about the contents of this release, see:
> https://cwiki.apache.org/confluence/display/MXNET/1.5.0+Release+Notes
>
> The vote will be open for 72 hours.
>
> [ ] +1 release this package as ...
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
>
>
> Best Regards
>
> Lai
>

Re: New disclaimer text

[Paul King]

+1

On Sat, Jul 13, 2019 at 10:44 AM Sheng Wu  wrote:

> +1 from me to have two disclaimers, chosen by podings.
>
> Also, +1 from me, the one they chosen should stay in website and
> announcement.
>
> Sheng
>
> Justin Mclean 于2019年7月13日 周六上午9:37写道：
>
> > Hi,
> >
> > +1 Works for me.
> >
> > It will need to be made very clear to podlings that different rules apply
> > depending on what disclaimer they have.
> >
> > Would this also please to the disclaimer on their web site and in
> > announcement emails?
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > --
> Sheng Wu
> SkyWalking, Shardingsphere and Zipkin
>

Re: [Discuss] Graduate Apache OpenWhisk (incubating) as a TLP

[Paul King]

I have been following some of the OpenWhisk traffic on the mailing list but
mostly at arms length, so I thought I would have my first play writing a
Groovy action this evening to see if the process would shed any light on
the project's graduation readiness. The result (with kudos to Markus
Thömmes whose repo I plagiarised):

https://github.com/paulk-asert/openwhisk-groovy

[As an aside: perhaps it belongs in devtools? It seems very similar to the
maven-java example contained in there - let me know if you want a PR.]

Anyway, everything seemed as expected or close to expected in terms of
branding/what I could download/disclaimers etc. With all of your repos and
moving parts on the server side of things, you will no doubt have an
on-going effort in terms of working out what and how to package things
going forward - since things will no doubt keep changing. I don't see any
reason why that on-going effort needs to be done any further within
incubation. There are still things which seem like they might need more
work, like the CLI releases page on github but I see discussions indicating
that folks seem to understand the issues involved.

So from my point of view you seem ready for graduation.

Cheers, Paul.



On Tue, Jul 2, 2019 at 11:45 AM David P Grove  wrote:

>
>
> Hi all,
>
> In the two and a half years that Apache OpenWhisk (incubating) has
> been a part of the Apache incubator, the community has grown, diversified,
> and adapted to the Apache Way. We believe that the project is ready to
> graduate to a TLP.
>
> As a community, we have discussed [1] and voted [2] to graduate to
> a
> TLP, we have worked through the maturity model [3], notified the IPMC that
> we have the intention to graduate [4], discussed our resolution [5, 6] and
> proposed PMC chair [7].
>
> Please see the draft resolution appended below and provide any
> comments or feedback you have on it.
>
> We would like to continue the graduation process and hereby ask you
> all for your opinion on this. The discussion is open for 72 hours, after
> which we will start a [VOTE] on graduation here.
>
> thanks,
>
> --dave
> on behalf of the Apache OpenWhisk PPMC
>
> [1]
>
> https://lists.apache.org/thread.html/8daa3a05148f54ca82458777e2b2b5e25ba99d39dcf8ce7dd85d0188@%3Cdev.openwhisk.apache.org%3E
> [2]
>
> https://lists.apache.org/thread.html/34e5740cdf1ce5f74c9468d9f9b222ba8994f0c63a82777b020cdf10@%3Cdev.openwhisk.apache.org%3E
> [3] https://cwiki.apache.org/confluence/display/OPENWHISK/Project+Maturity
> +Model
> [4]
>
> https://lists.apache.org/thread.html/02dd71dcc6b2f326015954388c61d06d12f982fd64f34ee40e076171@%3Cgeneral.incubator.apache.org%3E
> [5]
>
> https://lists.apache.org/thread.html/5b52f89c9af99fc79c7d466db83be1b299a441f258b8419285359ac5@%3Cdev.openwhisk.apache.org%3E
> [6]
>
> https://lists.apache.org/thread.html/5a44e377f3292a24de13c3a23f82735b82364c6419fab13e997bd91a@%3Cdev.openwhisk.apache.org%3E
> [7]
>
> https://lists.apache.org/thread.html/1c0366181b6812de7ae8f68cb546bb3a4512b53dc4e89edba7b27075@%3Cdev.openwhisk.apache.org%3E
> [8]
>
> https://lists.apache.org/thread.html/1c0366181b6812de7ae8f68cb546bb3a4512b53dc4e89edba7b27075@%3Cdev.openwhisk.apache.org%3E
>
>
> Proposed Resolution for the Apache OpenWhisk project for the ASF Board:
>
> X. Establish the Apache OpenWhisk 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 platform for building serverless applications with functions.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache OpenWhisk Project",
> be and hereby is established pursuant to Bylaws of the Foundation; and be
> it further
>
> RESOLVED, that the Apache OpenWhisk Project be and hereby is responsible
> for the creation and maintenance of software
> related to a platform for building serverless applications with functions;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache OpenWhisk" 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
> OpenWhisk Project, and to have primary responsibility
> for management of the projects within the scope of responsibility of the
> Apache OpenWhisk 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 OpenWhisk Project:
> Bertrand Delacretaz, bdelacre...@apache.org
> Carlos Santana, csantan...@apache.org
> Chetan Mehrotra, chet...@apache.org
> Dave Grove, dgr...@apache.org
> Dominic Kim, styl...@apache.org
> Dragos Dascalita Haut, dra...@apache.org
> James Dubee, du...@apache.org

Re: [VOTE] Release Apache Flagon (Incubating) v2.0.0

[Paul King]

Yes, when I say "probably worth correcting" I mean for future builds if
possible. Good luck with the release.

Cheers, Paul.


<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Tue, Jul 2, 2019 at 2:05 AM Joshua Poore 
wrote:

> Thanks, Paul.
>
> Yes, some of our webextension files are build from a few other source
> files. The best way we could manage to get headers in those these build
> files resulted in some repetition of headers from various arc files. We’ll
> see if we can’t find a better way, but at present we’re leaning on
> compliance and functional soundness.
>
> Joshua Poore
>
>
> > On Jul 1, 2019, at 10:01 AM, Paul King  wrote:
> >
> > +1 (binding)
> >
> > Checked:
> > * incubator in name
> > * LICENSE/NOTICE files
> > * checksums
> > * ASF headers in files (though a few js files in UserAleWebExtension have
> > the header repeated multiple times - not a big deal but probably worth
> > correcting unless these files are generated that way)
> >
> > Cheers, Paul.
> >
> >
> > <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> > Virus-free.
> > www.avast.com
> > <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> > On Mon, Jul 1, 2019 at 11:24 PM Joshua Poore 
> > wrote:
> >
> >> Hi Folks,
> >>
> >> 72 hours has passed on our VOTE on general@ to Release Apache Flagon
> >> v2.0.0.
> >>
> >> We are missing one binding VOTE from IPMC to release. Please review and
> >> VOTE.
> >>
> >> We presently have +4 community votes & +2  binding votes. No one has
> voted
> >> +0 or -1.
> >>
> >> Thanks!
> >>
> >> Joshua Poore
> >>
> >>
> >>> On Jun 29, 2019, at 8:06 PM, Justin Mclean 
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> +1 (binding)
> >>>
> >>> I checked:
> >>> - incubating in name
> >>> - signature and hashes fine
> >>> - DISCLAIMER exists
> >>> - LICENSE has minor issue (see below)
> >>> - NOTICE is fine
> >>> - all ASF files have correct headers
> >>>
> >>> As noted above the LICENSE file has incorrect copyright line in the
> >> license appendix.
> >>>
> >>> Thanks,
> >>> 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
> >>
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Flagon (Incubating) v2.0.0

[Paul King]

+1 (binding)

Checked:
* incubator in name
* LICENSE/NOTICE files
* checksums
* ASF headers in files (though a few js files in UserAleWebExtension have
the header repeated multiple times - not a big deal but probably worth
correcting unless these files are generated that way)

Cheers, Paul.



Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Jul 1, 2019 at 11:24 PM Joshua Poore 
wrote:

> Hi Folks,
>
> 72 hours has passed on our VOTE on general@ to Release Apache Flagon
> v2.0.0.
>
> We are missing one binding VOTE from IPMC to release. Please review and
> VOTE.
>
> We presently have +4 community votes & +2  binding votes. No one has voted
> +0 or -1.
>
> Thanks!
>
> Joshua Poore
>
>
> > On Jun 29, 2019, at 8:06 PM, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> > +1 (binding)
> >
> > I checked:
> > - incubating in name
> > - signature and hashes fine
> > - DISCLAIMER exists
> > - LICENSE has minor issue (see below)
> > - NOTICE is fine
> > - all ASF files have correct headers
> >
> > As noted above the LICENSE file has incorrect copyright line in the
> license appendix.
> >
> > Thanks,
> > 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: Podlings, the Incubator, relationships and Apache

[Paul King]

My +1 to the 2nd camp. For me it's about transparency.

I don't see an issue if a podling release has some significant flaws. For
me, the ideal would be if it is easy for podling members, reviewers, and
downstream users to easily determine whether such flaws are known and what
they are. It can be as simple as a line in the release notes or release
email and/or an easily findable issue or two.

On Mon, Jun 24, 2019 at 9:01 PM Jim Jagielski  wrote:

> ++1. I agree w/ Rich and Roman
>
> > On Jun 23, 2019, at 11:25 PM, Roman Shaposhnik 
> wrote:
> >
> > On Sat, Jun 22, 2019 at 3:31 PM Rich Bowen  rbo...@rcbowen.com>> wrote:
> >>
> >> A couple of thoughts:
> >
> > And a couple of thoughts on top of that.
> >
> >> Podlings are not permitted to call themselves "Apache Foo" because they
> are
> >> not yet full Apache projects.
> >
> > Correct. The I way I see this thread is this: *when it comes to
> > releases*, there's
> > always been two camps in Incubator. One thinks that Incubator is a TLP
> just
> > like Apache Commons that happens to produce release artifacts that have
> > nothing in common (just like Apache Commons'  JXPath has very little to
> do
> > with Compress and). A second camp thinks that Incubator is actually a
> special
> > construct within a foundation (after all, if it was just like Apache
> Commons why
> > would we make them put DISCLAIMER into release tarballs?).
> >
> > It seems that David is closer to the 1st camp, and Rich and I are
> > closer to the 2nd.
> >
> > Looking at the community benefits, I really think we should acknowledge
> that
> > Incubator is a special construct and optimize that special construct
> > for a particular
> > outcome: which is effectiveness of the graduation process.
> >
> >> While in the incubator we should expect podlibgs to fail at the rules.
> >> They're new to them and many of them feel arbitrary, even capricious, to
> >> those coming in from outside. We should make it safe to fail until they
> are
> >> ready to graduate. We should nurture them as long as they are moving
> >> towards that goal.
> >
> > Yup.
> >
> >> I cannot disagree with your reading of our resolutions. But I wonder if
> >> that reality is producing good citizen projects or a bunch of resentful
> >> people following rules they don't understand or embrace because they
> know
> >> they have to.
> >>
> >> Zipkin is only the latest project which clearly didn't get it and has
> left
> >> angry. I would rather a project realize that they don't fit and be able
> to
> >> leave with their dignity without having also to leave hating what we
> stand
> >> for.
> >>
> >> I want our new graduates to love and understand the ASF not merely
> tolerate
> >> it.
> >>
> >> I want the incubator to respond to failure with gentle correction rather
> >> than scoldings.
> >>
> >> Specifically I think podlings should be able to produce releases that
> are
> >> not asf complient and have them clearly labeled as such. Because they
> are
> >> not TLPs yet and so cannot be held to the same standard. This must be
> >> accompanied by a movement towards being a TLP, not some eternal
> incubation.
> >
> > With my IPMC member hat on -- huge +1 to the above.
> >
> > With my VP Legal hat on: I have no dog in this race. The IPMC needs to
> make
> > a *business* (well, community in this case) decision and then we can work
> > with a risk profile of that decision.
> >
> > Like I said -- the decision to make is: 1st vs. 2nd camp.
> >
> > Thanks,
> > Roman.
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> 
> > For additional commands, e-mail: general-h...@incubator.apache.org
> 
>

Re: Podling releases and release policy

[Paul King]

Perhaps one approach is to maintain a list of "release issues" which are
deemed "minor offences". As long as there are bugs raised against such
"release issues", then no further permission would be required. Anything
outside the "minor offences" would require explicit permission.

As others have mentioned, such release bugs would be labelled as blocking
for graduation. Ideally the bug ticket numbers would be listed in a
disclaimer file within the release. This would make it easier for reviewers
and act as a reminder for project members and users. IANAL, but I think it
would help too in terms of legal shield etc. to have such a file within the
release not just a generic disclaimer "on some web site at one point in
time".

Cheers, Paul.

On Tue, Jun 4, 2019 at 7:16 PM Justin Mclean  wrote:

> Hi,
>
> > Historically, demonstrably, we have applied a different policy to
> "podling
> > releases" that is a bit more lenient. Once the podling graduates, it must
> > conform to the formal Apache release guidelines.
>
> 1. There is no seperate incubator release policy for podling/IPMC
> releases, well no formal written down one anyway.
> 2. The IPMC does currenly give podlings a lot of leeway and treats IPMC
> releases differently to TLP releases. A look at recent IPMC release votes
> will find +1 votes on issues that would probably be -1 on a TLP release.
>
> Perhaps read what going in the board report [1] (still draft) as I think
> that captures it well.
>
> Thanks,
> Justin
>
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/June2019

Re: [VOTE] Release Apache Zipkin (incubating) version 2.14.0

[Paul King]

I'd second Geertjan's comments about how helpful (even though it probably
seemed painful at the time) Justin's comments were for Apache Groovy during
our incubation.

Perhaps it is worth re-reading some of the reasons why The ASF values
highly the provenance behind all of the software in its builds (probably
3rd para is the most relevant):

http://www.apache.org/legal/release-policy.html#why

I have also found Justin's ApacheCon talks very interesting. I couldn't
find the most relevant one but one with additional tools for looking at
large code bases can be found here:

https://static.sched.com/hosted_files/apachecon2016/75/CodeAnalysis_ApacheCon2016.pdf

Cheers, Paul.


On Sun, May 19, 2019 at 8:57 AM Justin Mclean 
wrote:

> HI,
>
> > maybe you can open source the tools you use justin.
>
> I spoken about it at many ApacheCons and provided "them" here on this
> list. Calling them tools is probably an exaggeration, It’s nothing complex.
>
> Here’s the tool I used:
>
> search copyright | sort -u
>
> (Where search is "find . -type f -exec grep -i "$1" {} \;“)
>
> I then look at the files it finds to see if they match with what is listed
> in LICENSE.
>
> Sometime I might do a few more searches like "search BSD" or "search MIT”
> or “search general public license”. I didn’t in this case.
>
> Do note that this will not catch the case where a header had moved or
> altered or code been minified. Tools are there to just help and will not
> find everything. If you want something more comprehensive I suggest you
> setup Fossology [1].
>
> > you seem uncanny ability to find glitches, yet also have an ability to
> > ignore note in the vote request mentioning known issues.
>
> None of the issue I mentioned where mentioned in the vote as from what I
> can see?
>
> > start helping instead of finding faults. you are the reason incubator is
> > not something anyone wants to go through
>
> I am helping, you’ll note a) I voted +1 b) provided feedback that will
> improve your next release.
>
> The incubator is here to help, if you want things checked in a release
> before you vote on it then just ask here. If you want to try out a new
> process or change how you vote on something then you can discuss it here.
>
> Thanks,
> Justin
>
> 1. https://www.fossology.org
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Recommend 'Apache NetBeans graduation to Top Level Project' resolution to board

[Paul King]

+1 (binding)

Cheers, Paul.


On Tue, Apr 9, 2019 at 8:41 PM Geertjan Wielenga
 wrote:

> Hi all,
>
> The Apache NetBeans podling community brings the resolution, after
> discussion[1], to become a top level Apache project up for the IPMC vote.
> The PPMC community vote[2] resulted in 64 +1 votes and no 0 or -1 votes,
> further details about the project and what has been done is found in the
> related discussion thread[1].
>
> We have had a long and eventful incubation period and are looking forward
> to graduating and continuing our development and community work with and
> around Apache NetBeans.
>
> The vote is open for 72 hours, assuming that at that stage there are at
> least 3 +1 votes and nothing left open for discussion.
>
> Thanks,
>
> Geertjan
> on behalf of Apache NetBeans PPMC
>
> 1.
>
> https://lists.apache.org/thread.html/648834cdb10ce55aff2c6c8dd3c32454a74711c6289f385e456b74d8@%3Cgeneral.incubator.apache.org%3E
> 2.
>
> https://lists.apache.org/thread.html/72e59c722580fef2cbaa637735691a549756aeaa72c4cbf52265fbe0@%3Cdev.netbeans.apache.org%3E
>
> -
>
> Establish the Apache NetBeans 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 providing a development environment, tooling platform, and application
> framework.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache NetBeans Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache NetBeans Project be and hereby is responsible for
> the creation and maintenance of software related to providing a development
> environment, tooling platform, and application framework; and be it further
>
> RESOLVED, that the office of "Vice President, Apache NetBeans" 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 NetBeans Project, and
> to have primary responsibility for management of the projects within the
> scope of responsibility of the Apache NetBeans 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 NetBeans Project:
>
> * Anton Epple 
> * Antonio Vieiro 
> * Aristides Villarreal 
> * Arunava Sinha 
> * Ate Douma 
> * Attila Kelemen 
> * Bertrand Delacretaz 
> * Bruno Flávio 
> * Bruno Souza 
> * Christian Lenz 
> * Constantin Drabo 
> * David Heffelfinger 
> * Daniel Gruno 
> * Dusan Balek 
> * Eirik Bakke 
> * Emilian Bold 
> * Emmanuel Hugonnet 
> * Eric Barboni 
> * Florian Vogler 
> * Geertjan Wielenga 
> * Glenn Holmer 
> * Ivar Grimstad 
> * James Gosling 
> * Jan Lahoda 
> * Jan Pirek 
> * Jaroslav Tulach 
> * Jean-Marc Borer 
> * Jiří Kovalský 
> * Joerg Michelberger 
> * Johan Vos 
> * John Kostaras 
> * John McDonnell 
> * Josh Juneau 
> * José Pereda 
> * Junichi Yamamoto 
> * Kirk Pepperdine 
> * Lars Bruun-Hansen 
> * Laszlo Kishalmi 
> * Leonardo Zanivan 
> * Mark Stephens 
> * Mark Struberg 
> * Martin Entlicher 
> * Martin Klähn 
> * Matthias Bläsing 
> * Michael Müller 
> * Michael Nascimento 
> * Michel Graciano 
> * Neil C Smith 
> * Ralph Benjamin Ruijs 
> * Reema Taneja 
> * Shai Almog 
> * Simon Phipps 
> * Svatopluk Dedic 
> * Sven Reimers 
> * Thilina Ranathunga 
> * Timon Veenstra 
> * Tomas Mysik 
> * Tomas Zezula 
> * Tushar Joshi 
> * Vladimir Voskresensky 
> * Wade Chandler 
> * Zoran Sevarac 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Geertjan Wielenga be appointed
> to the office of Vice President, Apache NetBeans, 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 or
> disqualification, or until a successor is appointed; and be it further
>
> RESOLVED, that the Apache NetBeans Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator NetBeans podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> NetBeans podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>

Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top Level Project' resolution to board

[Paul King]

+1 binding

Regards, Paul.

On Tue, Mar 19, 2019 at 3:21 PM Mick Semb Wever  wrote:

>
>
> After the latest discussion amongst this dev community on this dev mailing
> list[1],  presenting Sheng Wu as the PMC Chair and the maturity model[2],
> and then the discussion again on the incubator list[3],  a vote for Apache
> SkyWalking graduating to a top level project was called and has passed[4].
> From the past incubator discussions the PPMC altered the draft graduation
> proposal, specifically the proposed PMC list: removing some inactive people
> and adding all the podling Committers.
>
>
> Apache SkyWalking entered the incubator on December of 2017.  SkyWalking
> has delivered 8 releases so far in total, and now shows a good cadence of
> successful releases.
>
> During the podling's time in the Apache Incubator there has been
>  3200+ commits on development of the project,
>   378 Issues tagged as question in GitHub created, 373 resolved,
>   850+ Pull request created and resolved,
>   97 different contributors,
> 9 elected new committers, and
> 3 elected new PPMC members.
>
> And the dev ML has had 72 participants:
> https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019
>
> Attached is the draft Resolution for the PPMC and IPMC to vote upon.
>
> Please take a minute to vote on whether or not Apache SkyWalking should
> graduate to a Top Level Project by responding with one of the following:
>
> [ ] +1 Apache SkyWalking should graduate.
> [ ] +0 No opinion
> [ ] -1 Apache SkyWalking should not graduate (please provide the reason)
>
> The VOTE is open for a minimum of 72 hours. As there has been previous
> discussions on past versions of this proposal, I have not preluded the vote
> with a DISCUSS email. If feedback arises the vote period will be extended
> in good faith.
>
> regards,
> Mick
>
>
> [1]
> https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E
> [2]
> https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking
> [3]
> https://lists.apache.org/thread.html/68b06b2efdcd4f519cd9aa3df55d46bf0dade28002065fbad75d4195@%3Cdev.skywalking.apache.org%3E
> [4]
> https://lists.apache.org/thread.html/9f05862dffb40a967f867ba0fee4ab8549b08736cde27571e303ab30@%3Cdev.skywalking.apache.org%3E
>
> 
>
>
> Establish the Apache SkyWalking 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 application performance management and monitoring (APM).
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache SkyWalking Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache SkyWalking Project be and hereby is
> responsible for the creation and maintenance of software related to
> application performance management and monitoring (APM); and
> be it further
>
> RESOLVED, that the office of "Vice President, Apache SkyWalking" 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
> SkyWalking Project, and to have primary responsibility for management of
> the projects within the scope of responsibility of the Apache SkyWalking
> 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 SkyWalking
> Project:
>
>   * Haoyang Liu  (刘浩杨)  
>   * Hongtao Gao  (高洪涛)  
>   * Ignasi Barrera  
>   * Mick Semb Wever 
>   * Sheng Wu  (吴晟)  
>   * Shinn Zhang  (张鑫)   
>   * Willem Ning Jiang  (姜宁)
>   * Yongsheng Peng  (彭勇升)   
>   * DongXue Si (司冬雪)
>   * Jian Tan (谭建)   
>   * Kai Wang (王凯)   
>   * Yang Bai (柏杨)   
>   * Yao Wang (王垚)   
>   * Zhang Kewei (张科伟)  
>  * Can Li (李璨)  
>  * Jiaqi Lin (林嘉绮)  
>  * Jinlin Fu (付金林)  
>  * Lang Li (李浪)   
>  * Wenbin Wang (王文斌)
>  * Yixiong Cao (曹奕雄)
>
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sheng Wu (吴晟) be
> appointed to the office of Vice President, Apache SkyWalking, 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
> or disqualification, or until a successor is appointed; and be it 

Re: [VOTE] Accept DataSketches into the Apache Incubator

[Paul King]

+1 (binding)


On Sat, Mar 16, 2019 at 4:30 PM Liang Chen  wrote:

> Hi
>
> +1(binding)
>
> Regards
> Liang
>
>
> Kenneth Knowles wrote
> > Hi all,
> >
> > We've discussed the proposal for the DataSketches project in [1] and [2].
> > The
> > proposal itself has been put on the wiki [3].
> >
> > Per incubator rules [4] I'd like to call a vote to accept the new
> > "DataSketches" project as a podling in the Apache Incubator.
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote.
> > Everyone is welcome to vote, only Incubator PMC member votes are binding.
> > It would be helpful (but not required) if you could add a comment stating
> > whether your vote is binding or non-binding.
> >
> > This vote will run for at least 72 hours (but I expect to keep it open
> for
> > longer). Please VOTE as follows:
> >
> > [ ] +1 Accept DataSketches into the Apache Incubator
> > [ ] +0 Abstain
> > [ ] -1 Do not accept DataSketches into the Apache Incubator because ...
> >
> > Thanks to everyone who contributed to the proposal and discussions.
> >
> > Kenn
> >
> > [1]
> >
> https://lists.apache.org/thread.html/329354bd6a463dab56c2539972cfa2d6c6da7c75900216d785db4e3b@%3Cgeneral.incubator.apache.org%3E
> > [2]
> >
> https://lists.apache.org/thread.html/c9873cd4fcdc6367bcf530d8fa1ef09f3035f38e7c435e1a79a93885@%3Cgeneral.incubator.apache.org%3E
> > [3] https://wiki.apache.org/incubator/DataSketchesProposal
> > [4] https://incubator.apache.org/guides/proposal.html#the_vote
>
>
>
>
>
> --
> Sent from: http://apache-incubator-general.996316.n3.nabble.com/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Training into the Apache Incubator

[Paul King]

+1

On Wed, Feb 13, 2019 at 5:58 PM Lars Francke  wrote:

> Hi everyone,
>
> we've discussed the proposal for the Training project in [1] and [2]. The
> proposal itself can be found on the wiki[3].
>
> According to the Incubator rules[4] I'd like to call a vote to accept the
> new "Training" project as a podling in the Apache Incubator.
>
> A vote for accepting a new Apache Incubator podling is a majority vote.
> Everyone is welcome to vote, only Incubator PMC member votes are binding.
> It would be helpful (but not required) if you could add a comment stating
> whether your vote is binding or non-binding.
>
> This vote will run for at least 72 hours (but I expect to keep it open for
> longer). Please VOTE as follows:
>
> [ ] +1 Accept Training into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept Training into the Apache Incubator because ...
>
> Thank you for everyone who decided to join in in the past discussions!
> Lars
>
> [1] <
>
> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
> >
>
> [2] <
>
> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
> >
>
> [3] 
>
> [4] <
>
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> >
>

Re: the case of the maven wrapper

[Paul King]

For anyone who is interested from the Gradle side of things, you can look
at what we do for the Groovy project. We do include the (Gradle) wrapper
files in our git repo but NOT in our source distribution zip. There is one
extra step in our build process/line in our README that explains how to
populate the correct wrapper files using an existing gradle install and
after which the wrapper can then be used. I don't know if something similar
is currently possible with the Maven wrapper. Great if so, but if not, it
might prove to be a useful direction to head.

Cheers, Paul.

On Tue, Feb 19, 2019 at 10:54 AM Adrian Cole 
wrote:

> The request to donate the wrapper was closed won't fix (they did
> adjust the license headers)
>
> I've made a comment on a 3+ year old issue on maven itself, which had
> excluded the wrapper due to perceived problems in performing change
> inside the ASF
>
>
> https://issues.apache.org/jira/browse/MNG-5937?focusedCommentId=16771456=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16771456
>
> On Thu, Feb 14, 2019 at 4:18 PM Adrian Cole 
> wrote:
> >
> > FYI I've asked takari to donate the wrapper to the ASF. It is
> > important but tiny
> > https://github.com/takari/takari-maven-plugin/issues/18
> >
> > Meanwhile, we will remove the wrapper from the source distribution as
> > putting it in the NOTICE file is something off-putting to a few of our
> > contributors. We can build without the wrapper and it isn't worth
> > making a commitment to the NOTICE file for what seems not thought
> > through.
> >
> > If the enforcement rules loosen back to where we don't need to do
> > this, or the plugin or a copy of it is donated to the ASF, we'll
> > likely put it back into the source distribution.
> >
> > On Thu, Feb 14, 2019 at 3:29 PM Justin Mclean 
> wrote:
> > >
> > > Hi,
> > >
> > > > If we all say fine.. let's just throw more paperwork at it, I would
> ask you
> > > > to help draft a line for the NOTICE of what we would do. suppose we
> would
> > > > also have to do this for gradle etc.
> > >
> > > You would need to do this for any 3rd party file bundled with a
> release and yes sometimes this is complex and takes time. See for example
> Apache Newt. [1]
> > >
> > > > So basically if we accept that the new norm is this level of detail
> on
> > > > incidental files,
> > >
> > > It’s a 3rd party file not an incidental file and the ASF has policy
> around what to do when including 3rd party files which a (P)PMC and
> releases need to comply with. [2][3]
> > >
> > > To comply however is a simple change that needs to be made once to
> clearly inculcate the IP province and license of that file to users of the
> projects.
> > >
> > > > would it be "this includes source generated by the takari maven
> plugin"?
> > > > and of course if we say this, the next cruft is explaining gradle
> etc.
> > >
> > > If you don’t know what to do ask you mentors or the IPMC for help. If
> you disagree with advice given then clarify on legal-discuss.
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. https://github.com/apache/mynewt-newt/blob/master/LICENSE
> > > 2. http://www.apache.org/dev/release-publishing.html#goal
> > > 3. http://www.apache.org/dev/release-publishing.html#valid
> > >
> > >
> > > -
> > > 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] Shut down unused/inactive incubator lists

[Paul King]

+1

On Mon, Jan 21, 2019 at 10:12 AM sebb  wrote:

> The following lists are all but inactive:
>
> announce@ Last post Jan 2008
> android-interest@ Last post Mar 2011
> dev@ - only general circulars
> jaxws-tck@ (private) Last post 2012
> projects@ Last post Jul 2011
> user@ - only general circulars
>
> I think they should be shut down.
>
> Please vote so an Infra Jira can be raised to shut them down.
> They can have a bounce message added to direct posters to
> general@/private@ as appropriate
>
> [  ] +1
> [  ] -1 - give a reason please
>
> Please vote by end January 2019
>
> Sebb.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

[Paul King]

+1

On Tue, Dec 11, 2018 at 6:56 AM Roy Lenferink  wrote:

> Hi all,
>
> The Apache Incubator is still having a repository on git-wip-us as well
> [1].
>
> Does anyone have a problem with moving over the incubator repository to
> gitbox voluntarily?
> This means integrated access and easy PRs (write access to the GitHub
> repo).
>
> We need to document support for the decision from a mailing list post, so
> here it is.
>
> - Roy
>
> [1] https://git-wip-us.apache.org/repos/asf/incubator.git
>
> -- Forwarded message -
> From: Daniel Gruno 
> Date: vr 7 dec. 2018 om 17:53
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: us...@infra.apache.org 
>
> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
>   DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
>
> Hello Apache projects,
>
> I am writing to you because you may have git repositories on the
> git-wip-us server, which is slated to be decommissioned in the coming
> months. All repositories will be moved to the new gitbox service which
> includes direct write access on github as well as the standard ASF
> commit access via gitbox.apache.org.
>
> ## Why this move? ##
> The move comes as a result of retiring the git-wip service, as the
> hardware it runs on is longing for retirement. In lieu of this, we
> have decided to consolidate the two services (git-wip and gitbox), to
> ease the management of our repository systems and future-proof the
> underlying hardware. The move is fully automated, and ideally, nothing
> will change in your workflow other than added features and access to
> GitHub.
>
> ## Timeframe for relocation ##
> Initially, we are asking that projects voluntarily request to move
> their repositories to gitbox, hence this email. The voluntary
> timeframe is between now and January 9th 2019, during which projects
> are free to either move over to gitbox or stay put on git-wip. After
> this phase, we will be requiring the remaining projects to move within
> one month, after which we will move the remaining projects over.
>
> To have your project moved in this initial phase, you will need:
>
> - Consensus in the project (documented via the mailing list)
> - File a JIRA ticket with INFRA to voluntarily move your project repos
>over to gitbox (as stated, this is highly automated and will take
>between a minute and an hour, depending on the size and number of
>your repositories)
>
> To sum up the preliminary timeline;
>
> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
>relocation
> - January 9th -> February 6th: Mandated (coordinated) relocation
> - February 7th: All remaining repositories are mass migrated.
>
> This timeline may change to accommodate various scenarios.
>
> ## Using GitHub with ASF repositories ##
> When your project has moved, you are free to use either the ASF
> repository system (gitbox.apache.org) OR GitHub for your development
> and code pushes. To be able to use GitHub, please follow the primer
> at: https://reference.apache.org/committer/github
>
>
> We appreciate your understanding of this issue, and hope that your
> project can coordinate voluntarily moving your repositories in a
> timely manner.
>
> All settings, such as commit mail targets, issue linking, PR
> notification schemes etc will automatically be migrated to gitbox as
> well.
>
> With regards, Daniel on behalf of ASF Infra.
>
> PS:For inquiries, please reply to us...@infra.apache.org, not your
> project's dev list :-).
>

Re: [VOTE] Retire ODF Toolkit

[Paul King]

+1

On Sat, Nov 17, 2018 at 5:54 AM Dave Fisher  wrote:

> The ODF Toolkit community has VOTEd to Retire.
>
> The thread:
> https://lists.apache.org/thread.html/6de81dc33cb8311a38e38b927bfa1df7290c47ba7e7b39311cd06ce6@%3Codf-dev.incubator.apache.org%3E
>
> The results:
> https://lists.apache.org/thread.html/d4b4b33470a7bc3e70dc6192527168bb5907810045df5453c784cc93@%3Codf-dev.incubator.apache.org%3E
>
> Note that of the 6 VOTES there were 5 from IPMC members including the
> current Mentor and two original Mentors.
>
> This Vote will continue with the IPMC votes at 5 +1 and will be open for
> the next week.
>
> [ ] +1 - Retire ODF Toolkit.
> [ ] -1 - Do not retire ODF Toolkit. I intend to become a Mentor and try to
> make the community happen.
>
> Regards,
> Dave
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [PROPOSAL] Changing requirements for IPMC

[Paul King]

+1 to both from me too!


On Sun, Nov 11, 2018 at 12:22 PM Roman Shaposhnik 
wrote:

> On Wed, Nov 7, 2018 at 1:28 AM Bertrand Delacretaz
>  wrote:
> >
> > Hi,
> >
> > On Tue, Nov 6, 2018 at 9:20 AM Justin Mclean 
> wrote:
> > > ...I propose this:
> > >
> > > If someone has done several of the following:
> > > - has been involved in an incubating project from start to finish
> > > - has been a release manager
> > > - has assembled LICENSE and NOTICE files
> > > - has reviewed and voted on releases
> > > - has proposed or accepted committers/PPMC members
> > >
> > > Then they can ask the IPMC to join to IPMC by sending an email to
> private@ listing what they have been involved in...
> >
> > I like that, +1
> >
> > And maybe we should make sure each podling has at least one
> > experienced mentor, that is one who has successfully brought other
> > podlings to graduation, or a long-time ASF Member.
>
> I like both the original idea (after all I, myself, was one such case --
> an IPMC
> member before an ASF member) and this idea of a mentor-in-training
> for podlings.
>
> +1 to both!
>
> Thanks,
> Roman.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: How to review so-called "binary releases"?

[Paul King]

I also agree that moving to a different URL would be disruptive. In Apache
Groovy, we have a separate directory for the official (source) release as
distinct from the convenience binaries which are in a separate directory. I
think we copied the approach from Apache Ant. Our release notes stress the
official nature of the source release. IANAL, but I'd think such an
approach could be argued as providing a clear distinction between the
artifacts in terms of any potential liability.

Cheers, Paul.


On Thu, Nov 8, 2018 at 1:24 AM Dave Fisher  wrote:

> Hi -
>
> There are some projects where the binary is all the users want. For
> example, Apache OpenOffice. In that case these binaries are an exception
> and while on dist they are not mirrored and instead we distribute through
> SourceForge.
>
> I think if binaries are kept in a separate folder from source then
> DISCLAIMERs could be required to be added.
>
> To move to a new url would be very disruptive. To tell projects that they
> can no longer distribute binaries for community convenience would not be a
> small, reversible change.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Nov 7, 2018, at 5:14 AM, Carlos Santana  wrote:
> >
> > Jim
> >
> > What do you think now?
> > Was that a good or bad thing?
> >
> > TLDR; I’m in favor of convenient binaries is just the how they are
> handled.
> >
> > Sorry for my brevity, what I meant is that binaries should not be beside
> next to the source release seating on the same server and giving the same
> guarantees for both type of artifacts (source vs binary).
> >
> > Now in terms of convenience :-)
> > ASF should not block a project of making binaries available to their
> community for what ever purpose they think appropriate (ie nightly, binary
> of a RC, binary of final RC)
> >
> > ASF should provide guidance to the projects to make sure they make their
> communities aware that a source artifact is different from a binary
> artifact.
> > A project for example can put warnings and bold text on the location (ie
> directory, readme, inside the binary, download webpage, wiki etc) where the
> community downloads a copy of the binary.
> > The warning can say this is not a release of the ASF, is just a
> convenient binary “download on your own risk”, we provide sha256 sum and
> maybe the binary is even signed, but best practice is for you to download
> the source and be in control of building the binary.
> >
> >
> >
> > - Carlos Santana
> > @csantanapr
> >
> >> On Nov 7, 2018, at 7:04 AM, Jim Jagielski  wrote:
> >>
> >> Just a FYI that in the early days of the ASF (and the httpd project),
> community binaries were a common offering...
> >> -
> >> 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
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Binary file inclusion (was [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0)

[Paul King]

Just FYI, Groovy had numerous such "test" jars and wrapper files and
such initially. It turned out to only be a couple of hours work to
remove them and build them on the fly within the build files. While I
certainly see both sides of the argument about whether some
"binary-like" artifacts might be considered as special and okay to
include, I actually think what we ended up with does make it clearer
exactly what is going on.

Cheers, Paul.

On Tue, Jan 24, 2017 at 3:51 AM, John D. Ament  wrote:
> On Mon, Jan 23, 2017 at 8:04 AM Marvin Humphrey 
> wrote:
>
>> On Mon, Jan 23, 2017 at 4:35 AM, John D. Ament 
>> wrote:
>>
>> > What I'm trying to make sure we're agreeing to is
>> > that the problem isn't that there is a JAR to .tar.gz file in the
>> > distribution.  Its that the original source is missing.
>>
>> No.  Bundling jar files is not OK in general and it is definitely the
>> intent of the policy to exclude them.  (Source: I led the redrafting
>> effort for the official policy.) Among other reasons, they are
>> potential trojan horses, because they cannot be audited by a PMC.
>>
>> We might choose to make exceptions in some edge cases, like when the
>> jar files are used as data for tests. That does not invalidate the
>> policy.
>>
>>
> I'm thinking then we need to explicitly call this out.  Perhaps we need to
> add a section next to
> http://www.apache.org/legal/release-policy.html#what-must-every-release-contain
> that
> says "What must each release archive explicitly not contain" and list out
> what's being called out.  By only saying what it must contain, we don't say
> what is not allowed.
>
> Sorry if my thick headedness is getting frustrating, as it seems like there
> is a big gap between what expectations are and what's actually written
> down.  My goal is simply to get written down what the true expectations are.
>
>
>> > I'm personally in favor of
>> > having the gradle wrapper (and maven wrapper) present since it helps
>> build
>> > the code.
>>
>> The gradle wrapper and similar are also not permitted. Build processes
>> need to bootstrap it.
>>
>>
> I would like to understand why, from a legal standpoint, these are not
> allowed.
>
>
>> This isn't a big deal in practice because most people don't care about
>> the security implications of consuming the convenience binary and just
>> use that.
>>
>> Marvin Humphrey
>>
>> -
>> 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: [DISCUSS] Significance of Artifact Names

[Paul King]

+1  from me too.

For Groovy, we had a discussion internally and with our mentors. The
src archive and website disclaimer seemed to be the things that were
cared about from a legal point of view and so that is what we renamed.

For us, "convenience binaries" were something that should be
convenient for our users, otherwise they'd be called "inconvenience
binaries". :-)

For us, this seemed to be the right way to treat our community while
still keeping the legal audit/requirements there for anyone caring
about the official release. From where I sit it seems to be a "have
your cake and eat it too" situation to say that you don't care about
"convenience binaries" but "kind of" do care about some technical
aspects of there naming.

Cheers, Paul.


On Thu, Jan 5, 2017 at 12:19 PM, Roman Shaposhnik  wrote:
> Huge +1 to what Cédric has said.
>
> Thanks,
> Roman.
>
> On Wed, Jan 4, 2017 at 6:20 AM, Cédric Champeau
>  wrote:
>> Cross-posting since I missed this topic in the first place. My apologies
>> for the duplicate:
>>
>> I would argue that one of the Foundation mottos is "community first". In
>> that sense, enforcing a policy like that is not thinking about users. It's
>> adding a burden they don't care about. I am strongly against anything that
>> enforces technical requirements where there shouldn't be. Enforcing Maven
>> coordinates, or enforcing a _version string_ is going too far into the
>> technical details. There's branding and there's technical. Maven already
>> makes the mistake of mixing how you build the project and how you consume
>> it, which is the root of a lot of pain. Let's not make the error again at
>> the policy level, it's a total non sense.
>>
>> The Foundation can host a variety of different projects, from new ones
>> written in C to "old" ones written in Java, and all the different things we
>> can see in our ecosystem: Javascript, Go, ... Enforcing a rule about _how_
>> you consume a project, by Maven coordinates or version string is an
>> implementation detail. Branding the project is not. In other words, as long
>> as your package name, maven artifacts, Docker images, ... do not infringe
>> copyright, it's a no brainer. However, the project page *must* state about
>> incubating status and *explain* what it means. A *lot* of people don't care
>> what *incubating* means in the Foundation sense (and even worse, podling
>> can have very negative image). It would have been terrible for Groovy to
>> change the way people consume the artifacts, making them think of low
>> quality software, because they don't understand what "incubating" mean. To
>> me it sounds even worse than "alpha". Since "incubating" is meant towards
>> *incubating project in the sense of the Apache community*, it should *only*
>> appear where it makes sense: DISCLAIMER, web site, ... That is to say
>> everywhere you can give an explanation about its meaning. It should also
>> appear in the source package name, because that is what we legally care
>> about. But the version *string*, inside the package, is purely, again,
>> internal details, just like package name, Maven coordinates, NPM
>> coordinates, ... Why would you force me to use a version pattern if what I
>> want is the revision hash as the version number? The policy should NOT
>> impact how we design software or how we want the design to be. There are
>> potential technical issues with putting such a label in a version string
>> (OSGi, Jigsaw, dependency resolution with Maven, Ivy or Gradle, ... just to
>> name the Java ecosystem), so to me enforcing the policy here is just an
>> error.
>>
>> As for Groovy and the Codehaus package and Maven coordinates, we plan to
>> change this in a major, breaking, 3.0 release, not before. Because it would
>> be a breaking change, and some dependency management engines, typically,
>> are very poor when it comes to dependency substitution, which would add too
>> much burden for people to upgrade. We had an agreement with Ben from
>> Codehaus to use the name when we joined the ASF.
>>
>>
>>
>> 2017-01-04 6:24 GMT+01:00 Alex Harui :
>>
>>> Sorry for top-posting.
>>>
>>> It's always been interesting to me that the ASF says that it only releases
>>> source code, but still has policy about the contents of convenience
>>> binaries such as [6].  So, I suppose the ASF could dictate naming of
>>> binary packages.
>>>
>>> I know very little about Maven, but in my mind, the -incubating suffix is
>>> supposed to help warn the customer or cover the ASFs butt or both.  I
>>> don't know if anybody actually points to a source artifact from Maven, but
>>> if the downstream user is being careful enough to work from sources, it
>>> makes sense to me to put in an additional warning by adding the
>>> -incubating suffix to the source package. It says that these source
>>> packages are not like other ASF source packages without having to open the
>>> package.
>>>
>>> But for a 

Re: [DISCUSS] Proposing Griffin for Apache incubator

[Paul King]

Just the name worries me a little bit if the griffon project ever wanted to
move to Apache but they don't have any plans to do so at the moment.

http://griffon-framework.org

Cheers Paul

On 29 Nov 2016 9:35 PM, "Henry Saputra"  wrote:

> Seemed like the discussion is calming down
> Will send VOTE thread end of day tomorrow.
>
> Thanks,
>
> Henry
>
> On Wed, Nov 23, 2016 at 3:30 PM Henry Saputra 
> wrote:
>
> > Hi All,
> >
> > As the champion for Griffin, I would like to bring up discussion to
> > bring the project as Apache incubator podling.
> >
> > Here is the direct quote from the abstract:
> >
> > "
> > Griffin is a Data Quality Service platform built on Apache Hadoop and
> > Apache Spark. It provides a framework process for defining data
> > quality model, executing data quality measurement, automating data
> > profiling and validation, as well as a unified data quality
> > visualization across multiple data systems. It tries to address the
> > data quality challenges in big data and streaming context.
> > "
> >
> > Here is the link to the proposal:
> > https://wiki.apache.org/incubator/GriffinProposal
> >
> > I have copied the proposal below for easy access
> >
> >
> > Thanks,
> >
> > - Henry
> >
> >
> > Griffin Proposal
> >
> > Abstract
> >
> > Griffin is a Data Quality Service platform built on Apache Hadoop and
> > Apache Spark. It provides a framework process for defining data
> > quality model, executing data quality measurement, automating data
> > profiling and validation, as well as a unified data quality
> > visualization across multiple data systems. It tries to address the
> > data quality challenges in big data and streaming context.
> >
> > Proposal
> >
> > Griffin is a open source Data Quality solution for distributed data
> > systems at any scale in both streaming or batch data context. When
> > people use open source products (e.g. Apache Hadoop, Apache Spark,
> > Apache Kafka, Apache Storm), they always need a data quality service
> > to build his/her confidence on data quality processed by those
> > platforms. Griffin creates a unified process to define and construct
> > data quality measurement pipeline across multiple data systems to
> > provide:
> >
> > Automatic quality validation of the data
> > Data profiling and anomaly detection
> > Data quality lineage from upstream to downstream data systems.
> > Data quality health monitoring visualization
> > Shared infrastructure resource management
> >
> > Overview of Griffin
> >
> > Griffin has been deployed in production at eBay serving major data
> > systems, it takes a platform approach to provide generic features to
> > solve common data quality validation pain points. Firstly, user can
> > register the data asset which user wants to do data quality check. The
> > data asset can be batch data in RDBMS (e.g.Teradata), Apache Hadoop
> > system or near real-time streaming data from Apache Kafka, Apache
> > Storm and other real time data platforms. Secondly, user can create
> > data quality model to define the data quality rule and metadata.
> > Thirdly, the model or rule will be executed automatically (by the
> > model engine) to get the sample data quality validation results in a
> > few seconds for streaming data. Finally, user can analyze the data
> > quality results through built-in visualization tool to take actions.
> >
> > Griffin includes:
> >
> > Data Quality Model Engine
> >
> > Griffin is model driven solution, user can choose various data quality
> > dimension to execute his/her data quality validation based on selected
> > target data-set or source data-set ( as the golden reference data). It
> > has a corresponding library supporting it in back-end for the
> > following measurement:
> >
> > Accuracy - Does data reflect the real-world objects or a verifiable
> source
> > Completeness - Is all necessary data present
> > Validity - Are all data values within the data domains specified by the
> > business
> > Timeliness - Is the data available at the time needed
> > Anomaly detection - Pre-built algorithm functions for the
> > identification of items, events or observations which do not conform
> > to an expected pattern or other items in a dataset
> > Data Profiling - Apply statistical analysis and assessment of data
> > values within a dataset for consistency, uniqueness and logic.
> >
> > Data Collection Layer
> >
> > We support two kinds of data sources, batch data and real time data.
> >
> > For batch mode, we can collect data source from Apache Hadoop based
> > platform by various data connectors.
> >
> > For real time mode, we can connect with messaging system like Kafka to
> > near real time analysis.
> >
> > Data Process and Storage Layer
> >
> > For batch analysis, our data quality model will compute data quality
> > metrics in our spark cluster based on data source in Apache Hadoop.
> >
> > For near real time analysis, we consume data from messaging system,
> > 

Re: [VOTE] Graduate Groovy from the Incubator

[Paul King]

I certainly don't want to limit discussion but if anyone hasn't seen it
yet,  here is the direct link to our self assessment against the maturity
metrics (completed with the assistance of our mentors in particular
Bertrand):
https://github.com/apache/incubator-groovy/blob/master/MATURITY.adoc
On 2 Nov 2015 5:30 am, "Rich Bowen" <rbo...@rcbowen.com> wrote:

> On Oct 28, 2015 4:26 PM, "Konstantin Boudnik" <c...@apache.org> wrote:
> >
> > Following discussions [1] about its current status, the Groovy community
> > has voted [2] to graduate from the Incubator. The vote passed [3] with 12
> +1s
> > total, 5 are binding:
> >
> > Guillaume Laforge
> > Cédric Champeau
> > Paul King
> > Jochen Theodorou
> > Pascal Schumacher
> > Emmanuel Lécharny (binding)
> > Bertrand Delacretaz (binding)
> > Andrew Bayer (binding)
> > Jim Jagielski (binding)
> > Konstantin Boudnik (binding)
> > Russel Winder
> > Guillaume Alleon
> >
> > The Groovy community has:
> > * completed all required paperwork:
> > https://incubator.apache.org/projects/groovy.html
> > * completed multiple releases (2.4.4, 2.4.5, 2.4.6 is in the works)
> > * completed the name check procedure:
> > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-88
> > * addressed 50+ JIRAs:
> > http://is.gd/1tACON
> > * voted in multiple new committers/PPMC members
> >
> > Therefore, I'm calling a VOTE to graduate Groovy with the following Board
> > resolution. The VOTE will run for at least 72 hours, ending
> > Saturday, October 31st 8 PM PST.
>
> I recognize that I have missed the vote and thus my response is moot. I
> have been traveling, but i don't expect preferential treatment.
>
> However, as useful as these other measures are, as a member, and as a
> director who will need to vote on this resolution, I'd like to know if you,
> as a mentor, feel that this project had attainded maturity as described in
> the maturity metric document, and will operate according to the Apache way?
>
> >
> > [ ] +1 Graduate Apache Groovy from the Incubator.
> > [ ] +0 Don't care.
> > [ ] -1 Don't graduate Apache Groovy from the Incubator because ...
> >
> > Regards,
> > Cos
> >
> > [1] http://is.gd/DX41lO
> > [2] http://is.gd/pPweq3
> > [3] http://is.gd/VTLiqO
> >
> >  Apache Groovy graduation resolution draft
> >
> > Establish the Apache Groovy Top-Level 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 evolution
> > and maintenance of the Groovy programming language,
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Groovy Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Groovy Project be and hereby is responsible
> > for the evolution and maintenance of the Groovy programming language;
> > and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Groovy" 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 Groovy
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache Groovy
> > 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 Groovy Project
> > PMC:
> >
> > Cédric Champeau <cedric.champ...@gmail.com>
> > Paul King <pa...@asert.com.au>
> > Guillaume Laforge <glafo...@gmail.com>
> > Pascal Schumacher <pascalschumac...@gmx.net>
> > Jochen Theodorou <blackd...@gmx.org>
> > Andrew Bayer <andrew.ba...@gmail.com>
> > Konstantin Boudnik <c...@apache.org>
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Guillaume Laforge be
> > appointed to the office of Vice President, Apache Groovy, 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 or disqualification, or until a successor is appointed; and be
> > it further
> >
> > RESOLVED, that the Apache Groovy Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator Groovy
> > podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > Groovy podling encumbered upon the Apache Incubator Project are
> > hereafter discharged.
>

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

[Paul King]

I thought I'd comment from Groovy's point of view, being on the
"receiving" end of the audit.

I felt that the structure the audit provided to discussions about "Are
we there yet?" was very valuable. It didn't feel to me like the audit
was imposing any new requirement or policy that I hadn't heard about
before - just presenting a structured checklist to make sure we hadn't
forgotten anything and to avoid going over ground multiple times for
things which had been decided/discussed previously.

It was also presented to us as a guideline. I think this is a very
healthy way to view it. Most of our mentors seemed to have had a "gut
feel" for when projects are ready for graduation. A guideline doesn't
preclude that human aspect but does assist with focusing the
discussion around the important points and making it less subjective
in many areas. Also, as a guideline it would leave open the ability
for us to make a case for why a particular audit item may not apply or
might apply differently to us. We didn't end up having any such
requirement but if we did and we found an acceptable compromise, then
it would be recorded for future reference.

So, I'd certainly recommend any project adopting the maturity model as
a guideline.

Cheers, Paul.


On Fri, Oct 16, 2015 at 12:40 AM, Jim Jagielski  wrote:
>
>> On Oct 15, 2015, at 10:03 AM, Rich Bowen  wrote:
>>
>>
>>
>> On 10/15/2015 08:21 AM, Jim Jagielski wrote:
>>> If we are to use the maturity model as the guideline regarding podling
>>> graduation, then certainly the model should be voted on and approved
>>> by the membership as *the* model for the ASF, right?
>>>
>>> Basically, it looks to me that the model is proposing and creating policy,
>>> and this is something that needs to be done 'correctly', if you get my
>>> meaning.
>>
>> +1
>>
>> This is why, in that other thread, I suggested that mentors voluntarily 
>> evaluate their podlings based on these guidelines, but didn't suggest any 
>> kind of actual policy change or requirement.
>>
>
> My only concern is that if it becomes a de-facto 'standard' w/o
> being vetted and approved by the membership/board/incubator/etc...
>
>
> -
> 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] Release Apache Groovy 2.4.5-incubating

[Paul King]

On Mon, Sep 21, 2015 at 6:05 PM, Bertrand Delacretaz  wrote:
>
>
> Two files do not have the standard Apache license header, changing
> those would make future checks easier:
>
> ./config/codenarc/codenarc.groovy
> ./src/spec/test/PrimitiveTest.groovy
>
>
Fixed (for the next release).

Re: [VOTE] Release Apache Groovy 2.4.5-incubating

[Paul King]

On Mon, Sep 21, 2015 at 3:37 PM, Jochen Theodorou  wrote:

> Am 21.09.2015 01:17, schrieb Justin Mclean:
> [...]
>
>> - The file LineColumnCheck.txt looks like it's source code and is missing
>> an header. Is it Apache licensed or generated?
>>
>
> The file provides test data. It contains sample scripts which are compiled
> and the line/column information that the test will check against. In the
> repository the file has a header, but using == as comment marker. I have no
> idea what in our build is removing the header. We have to investigate this
>
> bye Jochen


The  header is in master but not 2.4.5 though it looks like it is set
up for manual running - so we'll have to check it still works with such a
header in place and doesn't muck up the line/column information that the
test needs.
.

Re: [VOTE] Release Apache Groovy 2.4.4-incubating

[Paul King]

On 14/07/2015 7:00 AM, Justin Mclean wrote:

Hi,


We don't bundle the source from any of those libraries true, but we do generate 
sources as part of our build using ANTLR and we do bundle the class files from 
the ANLTR and ASM projects in some of our jars and we do bundle the jars from 
some of those projects in some of our binary zips. So, only use of source files 
is important for NOTICE/LICENSE or would we need slightly different versions of 
those files in different places?


Yes only refer to what is bundled [1] and yes the NOTICE/LICENSE files would 
need to be different [2].


We ended up needing ten different NOTICE (and respectively LICENSE) variants 
but we should be good now for another release. We might try to get someone to 
do a pre-check on a snapshot before we attempt a formal release.

Cheers, Paul.


1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
2. http://www.apache.org/dev/licensing-howto.html#binary

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





---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


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