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

[Suneel Marthi]

+1 binding

On Fri, May 15, 2020 at 10:01 PM Vinoth Chandar  wrote:

> +1 (non-binding)
>
> On 2020/05/16 01:50:03, Vinoth Chandar  wrote:
> > Hello all,
> >
> > I would like to call for a VOTE for graduating Apache Hudi (Incubating),
> as
> > a top level project.
> >
> > Please vote on the resolution pasted below to graduate Apache Hudi from
> the
> > incubator to a Top Level Project.
> >
> > [ ] +1 Graduate Apache Hudi from the Incubator.
> > [ ] +0
> > [ ] -1 Don't graduate Apache Hudi from the Incubator because ...
> >
> > This vote will open for at least 72 hours.
> >
> > Apache Hudi (Incubating) entered the incubator in Jan 2019, the community
> > has grown vibrantly since, with all the design, development happening on
> > the Apache infrastructure, the "Apache way".
> >
> > To list a few of the community's achievements,
> >
> > - Accepted > 500 patches from 90 contributors, including 15+ new  design
> > proposals
> > - Performed 3 releases with 3 different release managers [5]
> > - Invited 5 new committers (all of them accepted)
> > - invited 3 of those new committers to join the PMC (all of them
> accepted)
> > - Migrated our web site to ASF infrastructure [1]
> > - Migrated developer conversations to the list at d...@hudi.apache.org
> > - Migrated all issue tracking to JIRA [2]
> > - Apache Hudi name search has been approved [3]
> > - Assessed ourselves against the Apache Project maturity matrix [4]
> > - We have built a meritocratic, open collaborative process, the Apache
> way
> > - Our proposed PMC is diverse and consists of members from ~10
> organizations
> >
> > We discussed our readiness for graduation as a community [6] and voted
> > unanimously in favor [7] (results summarized in [8]).  We have
> collaborated
> > on a resolution for graduation, including PMC membership and PMC chair.
> We
> > have also addressed the issues raised on the general@incubator DISCUSS
> > thread [9].
> >
> >
> > [1] https://hudi.apache.org
> >
> > [2] https://issues.apache.org/jira/projects/HUDI/
> >
> > [3] https://jira.apache.org/jira/browse/PODLINGNAMESEARCH-162
> >
> > [4]
> >
> https://cwiki.apache.org/confluence/display/HUDI/Apache+Hudi+Maturity+Matrix
> >
> >
> > [5] https://hudi.apache.org/releases.html
> > [6]
> >
> https://lists.apache.org/thread.html/rc98303d9f09665af90ab517ea0baeb7c374e9a5478d8424311e285cd%40%3Cdev.hudi.apache.org%3E
> > [7]
> >
> https://lists.apache.org/thread.html/rc19cedf6bb423cfc24efea27d8952a2224370a7679bab74d05de19b2%40%3Cdev.hudi.apache.org%3E
> > [8]
> >
> https://lists.apache.org/thread.html/r7b5c169c1bc3a1acaa35f43ff5388f5fc8b60746d423043464fcf5df%40%3Cdev.hudi.apache.org%3E
> > [9]
> >
> https://lists.apache.org/thread.html/r10d8c2038f1131c4da3e0cc2759da3554fab846bd623830251327b27%40%3Cgeneral.incubator.apache.org%3E
> >
> > Establish the Apache Hudi 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 atomic upserts and incremental data streams on Big Data.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC),
> > to be known as the "Apache Hudi Project", be and hereby is established
> > pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Hudi Project be and hereby is responsible for
> the
> > creation and maintenance of software related to providing atomic upserts
> > and incremental data streams on Big Data; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Hudi" 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 Hudi Project, and to have
> > primary responsibility for management of the projects within the scope of
> > responsibility of the Apache Hudi 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 Hudi Project:
> >
> >  * Anbu Cheeralan   
> >
> >  * Balaji Varadarajan
> >
> >  * Bhavan

Re: [DISCUSS] Graduate Apache Hudi (Incubating) as a TLP

[Suneel Marthi]

On Mon, May 11, 2020 at 11:10 PM Justin Mclean 
wrote:

> Hi,
>
> One thing I think may need some explanation. I notice a person who has
> been recently added (not voted) to the project is part of the proposed PMC.
> As far as I can tell they have had no involvement in the project. I can see
> a couple of other PMC members who has also had no noticeable involvement in
> the project. Now having inactive PMC members is not a big deal, but I
> curious why these people are on the proposed PMC list.
>

Why having inactive PMC members is not a big deal now?  What's the point of
keeping them if they r inactive and do nothing or have no interest in the
project?  There is an inactive IPMC member on the proposed PMC - who didn't
have time, or bandwidth to help in any way on the project but yet chose to
be part of and expressed his intent to be on the proposed PMC.  Mind you
there was no merit earned here, the fact that one is an IPMC member lets u
be a mentor - and then a free ride to be part of PMC without performing the
mentor's role.

Not trying to challenge your statement here - but just trying to understand
as to how having inactive/disinterested PMC members is not a big deal ?


> Some other very minor things:
> - it seems a little odd that you have 90+ contributors but have only
> invited 5 committers. Looks like a few have made sizeable contributions as
> well.
> - links on download page need fixing (https://www.apache.org/dist/ has
> been deprecated)
> - logos of other companies on front page
> - There exists some 3rd party branding issues e.g [1][2] Were you aware of
> these?
>
> Thanks,
> Justin
>
> 1.
> https://databricks.com/session/hudi-near-real-time-spark-pipelines-at-petabyte-scale
> 2. https://ondataengineering.net/technologies/hudi/
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Hudi (incubating) 0.5.2 RC2

[Suneel Marthi]

Transferring my vote from dev@hudi

+1 binding

On Sun, Mar 22, 2020 at 12:28 PM Thomas Weise  wrote:

> +1 (binding)
>
> * mvn clean package from downloaded source successfully
> * checked signature and hash
> * checked LICENSE/NOTICE - there is a minor issue which should be corrected
> in the next release
>
> According to [1], LICENSE should mention the version of included
> dependencies, since their license can also change.
>
> "NOTE: It's also possible to include the text of the 3rd party license
> within the LICENSE file. This is best reserved for short licenses. It's
> important to specify the version of the dependency as licenses are
> sometimes changed."
>
> The NOTICE file now has the bundled dependencies bubbled up. I'm not sure
> if there was a need to add all of these (though there is no harm). There
> appears to be conflicting information in [1].
>
> "Under normal circumstances, there is no need to modify NOTICE."
>
> "If the dependency supplies a NOTICE file, its contents must be analyzed
> and the relevant portions bubbled up into the top-level NOTICE file."
>
> Thanks,
> Thomas
>
> [1] http://www.apache.org/dev/licensing-howto.html#alv2-dep
>
>
>
> On Sun, Mar 22, 2020 at 12:22 AM vino yang  wrote:
>
> > Dear IPMC,
> >
> > Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts
> > Deletes and Incrementals. Apache Hudi (incubating) manages storage of
> > large analytical datasets on DFS (Cloud stores, HDFS or any Hadoop
> > FileSystem compatible storage) and provide ability to query them.
> >
> > The Apache Hudi (incubating) community has voted on the release candidate
> > and approved. The new source release candidate version is
> > 0.5.2-incubating-rc2
> >
> > Results: 6 binding +1 votes
> >
> > Here is the voting
> > thread:
> >
> https://lists.apache.org/thread.html/r7d8b4831666446bdf19fb6365090ad8c5975b5221e66184ccb24b7e2%40%3Cdev.hudi.apache.org%3E
> >
> > Here is the voting result
> > email:
> >
> https://lists.apache.org/thread.html/rf4a43dbb6171b9e1db236246afbc49979e4dcca87b8a09f3de19a2b8%40%3Cdev.hudi.apache.org%3E
> >
> > The Apache Hudi community had verified the following aspects of release:
> > - verified checksums and signatures [SUCCESS]
> > - license header check [SUCCESS]
> > - No binaries in source release [SUCCESS]
> > - verified RAT check [SUCCESS]
> > - built from source release (mvn clean install -DskipTests) [SUCCESS]
> > - mvn test from source release [SUCCESS]
> >
> > I'd like to call a vote in general to approve the release of Apache Hudi
> > (incubating). Please review and vote on the release candidate #2 for the
> > version 0.5.2, as follows:
> > [ ] +1,  Approve the release
> > [ ]  0,  I don't feel strongly about it, but I'm okay with the release
> > [ ] -1,  Do not approve the release (please provide specific comments)
> >
> >
> > The complete staging area is available for your review, which includes:
> > * JIRA release notes [1],
> > * the official Apache source release and binary convenience releases to
> be
> > deployed to dist.apache.org [2], which are signed with the key with
> > fingerprint C3A96EC77149571AE89F82764C86684D047DE03C [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "release-0.5.2-incubating-rc2" [5],
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12346606
> >
> > [2]
> >
> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.2-incubating-rc2/
> >
> > [3] https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
> >
> > [4]
> https://repository.apache.org/content/repositories/orgapachehudi-1019
> >
> > [5]
> >
> https://github.com/apache/incubator-hudi/tree/release-0.5.2-incubating-rc2
> >
> >
> > A release validation script is available in master for running usual
> > checks. To run this
> >
> >   - git clone g...@github.com:apache/incubator-hudi.git
> >   - cd incubator-hudi/scripts
> >   - ./release/validate_staged_release.sh --release=0.5.2 --rc_num=2
> >
> > The vote will be open for at least 72 hours. The vote will pass if a
> > majority of at least three +1 IPMC votes are cast.
> >
> > Best,
> >
> > vino
> >
>

Re: [VOTE] Apache Hudi (incubating) 0.5.2 RC1

[Suneel Marthi]

transferring my vote from dev@hudi

+1 binding



On Sun, Mar 15, 2020 at 10:58 PM vino yang  wrote:

> Dear IPMC,
>
> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts
> Deletes and Incrementals. Apache Hudi (incubating) manages storage of
> large analytical datasets on DFS (Cloud stores, HDFS or any Hadoop
> FileSystem compatible storage) and provide ability to query them.
>
> The Apache Hudi (incubating) community has voted on the release candidate
> and approved. The new source release candidate version is
> 0.5.2-incubating-rc1
>
> Results: 6 binding +1 votes
>
> Here is the voting
> thread:
> https://lists.apache.org/thread.html/rf687b44fb8d5e9073c2918a0c366352379ddf01632832adcbfcc060e%40%3Cdev.hudi.apache.org%3E
>
> Here is the voting result
> email:
> https://lists.apache.org/thread.html/rfaad30944d931d07c7a3f8b143b810891d9d80ad61fc6a1f5b7c0dcf%40%3Cdev.hudi.apache.org%3E
>
> The Apache Hudi community had verified the following aspects of release:
> - verified checksums and signatures [SUCCESS]
> - license header check [SUCCESS]
> - No binaries in source release [SUCCESS]
> - verified RAT check [SUCCESS]
> - built from source release (mvn clean install -DskipTests) [SUCCESS]
> - mvn test from source release [SUCCESS]
>
> I'd like to call a vote in general to approve the release of Apache Hudi
> (incubating). Please review and vote on the release candidate #1 for the
> version 0.5.2, as follows:
> [ ] +1,  Approve the release
> [ ]  0,  I don't feel strongly about it, but I'm okay with the release
> [ ] -1,  Do not approve the release (please provide specific comments)
>
>
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint C3A96EC77149571AE89F82764C86684D047DE03C [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-0.5.2-incubating-rc1" [5],
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12346606
>
> [2]
> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.2-incubating-rc1/
>
> [3] https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
>
> [4] https://repository.apache.org/content/repositories/orgapachehudi-1018/
>
> [5]
> https://github.com/apache/incubator-hudi/tree/release-0.5.2-incubating-rc1
>
>
> A release validation script is available in master for running usual
> checks. To run this
>
>   - git clone g...@github.com:apache/incubator-hudi.git
>   - cd incubator-hudi/scripts
>   - ./release/validate_staged_release.sh --release=0.5.2 --rc_num=1
>
> The vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
>
> Best,
>
> vino
>

Re: [VOTE] Apache Hudi (incubating) 0.5.1 RC1

[Suneel Marthi]

+1 binding

Transferring my vote from dev@hudi



On Sat, Jan 25, 2020 at 9:27 PM leesf  wrote:

> Dear IPMC,
>
> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts anD
> Incrementals. Apache Hudi (incubating) manages storage of large analytical
> datasets on DFS (Cloud stores, HDFS or any Hadoop FileSystem compatible
> storage) and provide ability to query them.
>
> The Apache Hudi (incubating) community has voted on the release candidate
> and approved. The new source release candidate version is
> 0.5.1-incubating-rc1
>
> Results: 3 binding +1 votes
>
> Here is the voting thread:
>
> https://lists.apache.org/thread.html/r8af8fb482991c6f8ab1c54069bab129fc76f97f3a2244bc809d9b914%40%3Cdev.hudi.apache.org%3E
>
>
> Here is the voting result email:
>
> https://lists.apache.org/thread.html/r75c603201701b5cd6697ddb6b69bf4d940c089a1e61ddfa8e68e07b1%40%3Cdev.hudi.apache.org%3E
>
>
> The Apache Hudi community had verified the following aspects of release:
> - verified checksums and signatures [SUCCESS]
> - license header check [SUCCESS]
> - No binaries in source release [SUCCESS]
> - verified RAT check [SUCCESS]
> - built from source release (mvn clean install -DskipTests) [SUCCESS]
> - mvn test from source release [SUCCESS]
>
> I'd like to call a vote in general to approve the release of Apache Hudi
> (incubating). Please review and vote on the release candidate #1 for the
> version 0.5.1, as follows:
> [ ] +1,  Approve the release
> [ ]  0,  I don't feel strongly about it, but I'm okay with the release
> [ ] -1,  Do not approve the release (please provide specific comments)
>
>
> The complete staging area is available for your review, which includes:
>
>   - JIRA release notes [1]
>   - The official Apache source release and binary convenience releases to
> be deployed to dist.apache.org [2], which are signed with the key with
> fingerprint 623E08E06DB376684FB9599A3F5953147903948A   [3],
>   - all artifacts to be deployed to the Maven Central Repository [4]
>   - source code tag "release-0.5.1-incubating-rc1" [5]
>
> [1]
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12346183
> [2]
>
> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.1-incubating-rc1/
> [3] https://dist.apache.org/repos/dist/dev/incubator/hudi//KEYS
> [4] https://repository.apache.org/content/repositories/orgapachehudi-1014
> [5]
> https://github.com/apache/incubator-hudi/tree/release-0.5.1-incubating-rc1
>
> A release validation script is available in master for running usual
> checks. To run this
>
>   - git clone g...@github.com:apache/incubator-hudi.git
>   - cd incubator-hudi/scripts
>   - ./release/validate_staged_release.sh --release=0.5.1 --rc_num=1
>
> The vote will be open for at least 72 hours. Please cast your votes before
> *Jan. 29th 2020, 23:59 UTC*(End on Wednesday). The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
>
> Thanks,
> Leesf
>

Re: [VOTE] Myriad retirement

[Suneel Marthi]

+1 to retire

On Thu, Jan 23, 2020 at 11:33 AM Ted Dunning  wrote:

> +1
>
> It was a good effort (and a good reboot effort). But the world changes.
>
> Thanks to Javi for working hard on this.
>
>
> On Thu, Jan 23, 2020 at 7: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} Apache Hudi (incubating) 0.5.0 RC6

[Suneel Marthi]

+1 binding

On 2019/10/19 22:04:19, vbal...@apache.org wrote: 
> Dear IPMC,
> 
> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts anD 
> Incrementals. Apache Hudi (incubating) manages storage of large analytical 
> datasets on DFS (Cloud stores, HDFS or any Hadoop FileSystem compatible 
> storage) and provide ability to query them.
> 
> The previous source release candidate 0.5.0-incubating-rc5 had licensing 
> concerns (Please see 
> https://lists.apache.org/thread.html/02d40e3dbababc069c5210928aa4dd335c41ab1837d5a894954f5c9f@%3Cgeneral.incubator.apache.org%3E)
>  .
> 
> We have addressed them in the new source release candidate (RC#6). The Apache 
> Hudi (incubating) community has voted on this new release candidate and 
> approved. The new source release candidate version is 0.5.0-incubating-rc6
> 
> Results: 4 binding +1 votes
> 
> Here is the voting thread:  
> https://lists.apache.org/thread.html/617cad3116308821f845d3be5d71e135fdcbb82b4533c53941a0fda8@%3Cdev.hudi.apache.org%3E
> Here is the voting result email:  
> https://lists.apache.org/thread.html/1587f3d766f6b3536d32630f89ba53b86cb09178d744fce05ae93a03@%3Cdev.hudi.apache.org%3E
> 
> The Apache Hudi community had verified the following aspects of release:
> - verified checksums and signatures [SUCCESS]
> - license header check [SUCCESS]
> - No binaries in source release [SUCCESS]
> - verified RAT check [SUCCESS]
> - built from source release (mvn clean install -DskipTests) [SUCCESS]
> - mvn test from source release [SUCCESS]
> 
> I'd like to call a vote in general to approve the first release of Apache 
> Hudi (incubating). Please review and vote on the release candidate #5 for the 
> version 0.5.0, as follows:
> [ ] +1,  Approve the release
> [ ]  0,  I don't feel strongly about it, but I'm okay with the release
> [ ] -1,  Do not approve the release (please provide specific comments)
> 
> 
> The complete staging area is available for your review, which includes:
> 
>   - JIRA release notes [1]
>   - The official Apache source release and binary convenience releases to be 
> deployed to dist.apache.org [2], which are signed with the key with 
> fingerprint AF9BAF79D311A3D3288E583F24A499037262AAA4  [3],
>   - all artifacts to be deployed to the Maven Central Repository [4]
>   - source code tag "release-0.5.0-incubating-rc6" [5]
> 
>   [1]  
> https://jira.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12346087
>   [2]  
> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.0-incubating-rc6/
>   [3]  https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
>   [4]  https://repository.apache.org/content/repositories/orgapachehudi-1006/
>   [5]  
> https://github.com/apache/incubator-hudi/tree/release-0.5.0-incubating-rc6
> 
> A release validation script is available in master for running usual checks. 
> To run this
> 
>   - git clone g...@github.com:apache/incubator-hudi.git
>   - cd incubator-hudi/scripts
>   - ./release/validate_staged_release.sh --release=0.5.0 --rc_num=6
> 
> The vote will be open for at least 72 hours. The vote will pass if a majority 
> of at least three +1 IPMC votes are cast
> 
> Thanks,
> Balaji.V
> (on behalf of Apache Hudi PPMC)
> 
> -
> 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} Apache Hudi (incubating) 0.5.0 RC5

[Suneel Marthi]

+1 binding

On Thu, Oct 10, 2019 at 6:31 PM vbal...@apache.org 
wrote:

> Dear IPMC,
> Apache Hudi (incubating) (pronounced Hoodie) stands for Hadoop Upserts anD
> Incrementals. Apache Hudi (incubating) manages storage of large analytical
> datasets on DFS (Cloud stores, HDFS or any Hadoop FileSystem compatible
> storage) and provide ability to query them. Apache Hudi (incubating)
> community has voted on and approved the first source release. The source
> release version is 0.5.0-incubating-rc5
> Results: 3 binding +1 votes
> One -0 vote with the note that "NOTICE needs to include (incubating)"
> This NOTICE file inconsistency is also seen in other incubating projects.
> We have fixed the inconsistency subsequently in the NOTICE file in our
> master branch :
> https://github.com/apache/incubator-hudi/commit/834c591955cfa8a9c5f286967d693932564b6764
> .
> Here is the voting thread:
>
> https://lists.apache.org/thread.html/7eac27261a475dfda25ea711e93d93e7305af38866f38e0dac80ad1f@%3Cdev.hudi.apache.org%3E
> Here is the voting result email:
>
> https://lists.apache.org/thread.html/053dc9462759b7db9a60e4fd651dfe207f20d317c7ae195c390c2a55@%3Cdev.hudi.apache.org%3E
> The Apache Hudi community had verified the following aspects of release:
> - verified checksums and signatures [SUCCESS]- license header check
> [SUCCESS]- No binaries in source release [SUCCESS]
> - verified RAT check [SUCCESS]
> - built from source release (mvn clean install -DskipTests) [SUCCESS]
> - mvn test from source release [SUCCESS]
>
> I'd like to call a vote in general to approve the first release of Apache
> Hudi (incubating). Please review and vote on the release candidate #5 for
> the version 0.5.0, as follows:
> [ ] +1, Approve the release [ ]   0 I don't feel strongly about it, but
> I'm okay with the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
>
> The complete staging area is available for your review, which includes:
>- JIRA release notes [1]
>- The official Apache source release to be deployed to dist.apache.org
> [2], which are signed with the key with fingerprint
> AF9BAF79D311A3D3288E583F24A499037262AAA4 [3],
>- all artifacts to be deployed to the Maven Central Repository [4]
>- source code tag "release-0.5.0-incubating-rc5" [5]
>
>-
> https://jira.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822&version=12346087
>
>
>-
> https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.0-incubating-rc5/
>- https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
>-
> https://repository.apache.org/content/repositories/orgapachehudi-1005/
>-
> https://github.com/apache/incubator-hudi/tree/release-0.5.0-incubating-rc5
>
>
>
> We also have a new release validation script available in master to
> automate the usual checks. To run this
>
>- git clone g...@github.com:apache/incubator-hudi.git
>
>- cd incubator-hudi/scripts
>- ./release/validate_staged_release.sh --release=0.5.0 --rc_num=5
>
> The vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast
> Thanks,
> Balaji.V(on behalf of Apache Hudi PPMC)
>

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

[Suneel Marthi]

+1 binding

Congrats !!

On Tue, Aug 13, 2019 at 3:06 PM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> +1 (binding)
>
> Congratulations!
>
> Julian
>
>
>  Ursprüngliche Nachricht 
> Betreff: Re: [VOTE] Recommend 'Apache Druid graduation to Top Level
> Project' resolution to the board
> Von: Julian Hyde
> An: general@incubator.apache.org
> Cc:
>
> +1
>
> Good luck! It has been great mentoring you guys.
>
> On Tue, Aug 13, 2019 at 10:40 AM Andrei Savu  wrote:
> >
> > +1 (binding)
> >
> > Congrats! Great to see such an active community.
> >
> > -- Andrei Savu
> >
> > On Tue, Aug 13, 2019 at 12:03 AM 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

Re: [VOTE] Accept Hudi into the Apache Incubator

[Suneel Marthi]

, we have an
> active set of early contributors/collaborators from Shopify, DoubleVerify
> and Vungle, that we hope will increase the diversity going forward. Once
> again, a primary motivation for incubation is to facilitate this in the
> Apache way.
> 
> === Reliance on Salaried Developers ===
> 
> Both the current committers & early contributors have several years of core
> expertise around data systems. Current committers are very passionate about
> the project and have already invested hundreds of hours towards helping &
> building the community. Thus, even with employer changes, we expect they
> will be able to actively engage in the project either because they will be
> working in similar areas even with newer employers or out of belief in the
> project.
> 
> === Relationships with Other Apache Products ===
> 
> To the best of our knowledge, there are no direct competing projects with
> Hudi that offer all of the feature set namely - upserts, incremental
> streams, efficient storage/file management, snapshot isolation/rollbacks -
> in a coherent way. However, some projects share common goals and technical
> elements and we will highlight them here. Hive ACID/Kudu both offer upsert
> capabilities without storage management/incremental streams. The recent
> Iceberg project offers similar snapshot isolation/rollbacks, but not
> upserts or other data plane features. A detailed comparison with their
> trade-offs can be found at https://uber.github.io/hudi/comparison.html.
> 
> We are committed to open collaboration with such Apache projects and
> incorporate changes to Hudi or contribute patches to other projects, with
> the goal of making it easier for the community at large, to adopt these
> open source technologies.
> 
> === Excessive Fascination with the Apache Brand ===
> 
> This proposal is not for the purpose of generating publicity. We have
> already been doing talks/meetups independently that have helped us build
> our community. We are drawn towards Apache as a potential way of ensuring
> that our open source community management is successful early on so  hudi
> can evolve into a broadly accepted--and used--method of managing data on
> Hadoop.
> 
> == Documentation ==
> [1] Detailed documentation can be found at https://uber.github.io/hudi/
> 
> == Initial Source ==
> 
> The codebase is currently hosted on Github: https://github.com/uber/hudi .
> During incubation, the codebase will be migrated to an Apache
> infrastructure. The source code already has an Apache 2.0 licensed.
> 
> == Source and Intellectual Property Submission Plan ==
> 
> Current code is Apache 2.0 licensed and the copyright is assigned to Uber.
> If the project enters incubator, Uber will transfer the source code &
> trademark ownership to ASF via a Software Grant Agreement
> 
> == External Dependencies ==
> 
> Non apache dependencies are listed below
> 
> * JCommander (1.48) Apache-2.0
> * Kryo (4.0.0) BSD-2-Clause
> * Kryo (2.21) BSD-3-Clause
> * Jackson-annotations (2.6.4) Apache-2.0
> * Jackson-annotations (2.6.5) Apache-2.0
> * jackson-databind (2.6.4) Apache-2.0
> * jackson-databind (2.6.5) Apache-2.0
> * Jackson datatype: Guava (2.9.4) Apache-2.0
> * docker-java (3.1.0-rc-3) Apache-2.0
> * Guava: Google Core Libraries for Java (20.0) Apache-2.0
> * bijection-avro (0.9.2) Apache-2.0
> * com.twitter.common:objectsize (0.0.12) Apache-2.0
> * Ascii Table (0.2.5) Apache-2.0
> * config (3.0.0) Apache-2.0
> * utils (3.0.0) Apache-2.0
> * kafka-avro-serializer (3.0.0) Apache-2.0
> * kafka-schema-registry-client (3.0.0) Apache-2.0
> * Metrics Core (3.1.1) Apache-2.0
> * Graphite Integration for Metrics (3.1.1) Apache-2.0
> * Joda-Time (2.9.6) Apache-2.0
> * JUnit CPL-1.0
> * Awaitility (3.1.2) Apache-2.0
> * jersey-connectors-apache (2.17) GPL-2.0-only CDDL-1.0
> * jersey-container-servlet-core (2.17) GPL-2.0-only CDDL-1.0
> * jersey-core-server (2.17) GPL-2.0-only CDDL-1.0
> * htrace-core (3.0.4) Apache-2.0
> * Mockito (1.10.19) MIT
> * scalatest (3.0.1) Apache-2.0
> * Spring Shell (1.2.0.RELEASE) Apache-2.0
> 
> All of them are Apache compatible
> 
> == Cryptography ==
> 
> No cryptographic libraries used
> 
> == Required Resources ==
> 
> === Mailing lists ===
> 
> * priv...@hudi.incubator.apache.org (with moderated subscriptions)
> * d...@hudi.incubator.apache.org
> * comm...@hudi.incubator.apache.org
> * u...@hudi.incubator.apache.org
> 
> === Git Repositories ===
> 
> Git is the preferred source control system: git://
> git.apache.org/incubator-hudi
> 
> === Issue Tracking ===
> 
> We prefer to use the Apache gitbox integration to sync Github & Apache
> infrastructure, and r

Re: [VOTE] Graduate Apache Airflow to TLP

[Suneel Marthi]

+1 binding

On Wed, Dec 5, 2018 at 6:57 PM Julian Hyde  wrote:

> +1 (binding)
>
>
> > On Dec 5, 2018, at 3:31 PM, Jakob Homan  wrote:
> >
> > Hello-
> >
> > The Airflow podling community has VOTEd[0] to graduate, following a
> > very successful DISCUSS[1].  Accordingly I'm bringing the resolution
> > up for an IPMC VOTE.
> >
> > The podling result was:
> > Overall: 21 x +1 votes, 0 x -1 votes
> >
> > Binding +1 x 11: Kaxil, Tao, Bolke, Fokko, Maxime, Arthur, Hitesh,
> > Chris, Sid, Ash, Jakob.
> > Non-binding +1 x 10: Daniel, Shah, Stefan, Kevin, Marc, Sunil,
> > Adityan, Deng, Neelesh, Sai
> >
> > Since entering the Incubator in 2016, the Airflow community has:
> >   * successfully produced 7 releases
> >   * added 9 new committers/PPMC members
> >   * built a diverse group of committers from multiple different employers
> >   * had more than 3,300 JIRA tickets opened
> >   * completed the project maturity model with positive responses[2]
> >
> > Here's my binding +1.  The VOTE will run for at least 72 hours.
> >
> > Thanks,
> > Jakob
> >
> > [0]
> https://mail-archives.apache.org/mod_mbox/airflow-dev/201812.mbox/%3c115b1380-619d-41d7-a30e-9c041cd4d...@gmail.com%3E
> > [1]
> https://lists.apache.org/thread.html/%3c0a763b0b-7d0d-4353-979a-ac6769eb0...@gmail.com%3E
> > [2]
> https://cwiki.apache.org/confluence/display/AIRFLOW/Maturity+Evaluation
> >
> > 
> >
> > Establish the Apache Airflow 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 workflow automation and scheduling
> > that can be used to author and manage data pipelines.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "Apache Airflow Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that the Apache Airflow Project be and hereby is
> > responsible for the creation and maintenance of software
> > related to workflow automation and scheduling that can be
> > used to author and manage data pipelines; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Airflow" 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 Airflow Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache Airflow 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 Airflow Project:
> >
> > * Alex Guziel 
> > * Alex Van Boxel 
> > * Arthur Wiedmer 
> > * Ash Berlin-Taylor 
> > * Bolke de Bruin 
> > * Chris Riccomini 
> > * Dan Davydov 
> > * Fokko Driesprong 
> > * Hitesh Shah 
> > * Jakob Homan 
> > * Jeremiah Lowin 
> > * Joy Gao 
> > * Kaxil Naik 
> > * Maxime Beauchemin 
> > * Siddharth Anand 
> > * Sumit Maheshwari 
> > * Tao Feng 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Bolke de Bruin
> > be appointed to the office of Vice President, Apache Airflow, 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 Airflow PMC be and hereby is
> > tasked with the creation of a set of bylaws intended to
> > encourage open development and increased participation in the
> > Apache Airflow Project; and be it further
> >
> > RESOLVED, that the Apache Airflow Project be and hereby
> > is tasked with the migration and rationalization of the Apache
> > Incubator Airflow podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache
> > Incubator Airflow podling encumbered upon the Apache Incubator
> > Project are hereafter discharged.
> >
> > -
> > 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] Retire Gearpump podling

[Suneel Marthi]

+1 to retire

Very sad to see this retire - initially conceived by the former Intel
Hadoop Engg core team back in the day

On Sun, Sep 16, 2018 at 5:45 PM Ted Dunning  wrote:

> +1 from here as well.
>
> Good luck to the project participants.
>
>
> On Sun, Sep 16, 2018, 16:32 John D. Ament  wrote:
>
> > +1 to retire
> >
> > Like all podlings, the source code will continue to be available in a
> read
> > only fashion, if others ever want to pick it back up or restart a podling
> > with the name.  Best of luck to all.
> >
> > On Sun, Sep 16, 2018 at 5:32 AM Manu Zhang 
> > wrote:
> >
> > > Hi mentors,
> > >
> > > The Gearpump podling has voted to retire from incubation. Here are the
> > > relevant discussion and vote threads from the dev list. The vote passed
> > > unanimously with 6 +1s.
> > >
> > > DISCUSS:
> > >
> > >
> >
> https://lists.apache.org/thread.html/77946cfff4557cf10c13c2d35fc165223583e58c2f7705319acabcf4@%3Cdev.gearpump.apache.org%3E
> > > VOTE:
> > >
> > >
> >
> https://lists.apache.org/thread.html/03fc0421bb425f79d623863335bc2b81e4b6c77a169f508aadce7785@%3Cdev.gearpump.apache.org%3E
> > >
> > > Please vote to ratify this request for retirement. It will be open for
> at
> > > least 72 hours.
> > >
> > > Thanks,
> > > Manu Zhang
> > >
> >
>

Re: [VOTE] Graduate Apache HAWQ (incubating)

[Suneel Marthi]

+1 binding

Sent from my iPhone

> On Jul 27, 2018, at 9:56 PM, yang.hao  wrote:
> 
> +1 (non-binding)
> 
> 
> 
> 
> On Jul 27, 2018, at 7:13 PM, Roman Shaposhnik r...@apache.org wrote:
> 
> Hi!
> 
> after a very positive discussion in the HAWQ community
> and at the IPMC level:
> https://lists.apache.org/thread.html/67a2d52ef29cbf9e93d8050ed0193cc110a919962dd92f8436b343b7@%3Cdev.hawq.apache.org%3E
> https://lists.apache.org/thread.html/3a142d758ef5ae119e421071893615992ea5ee937b5d02007f5e@%3Cgeneral.incubator.apache.org%3E
> 
> I'd like to bring the following resolution for a formal vote.
> 
> Please vote on the resolution pasted below to graduate
> Apache HAWQ from the incubator to top level project.
> 
> [ ] +1 Graduate Apache HAWQ from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache HAWQ from the Incubator because...
> 
> This vote will be open for at least 72 hours.
> 
> Many thanks to our mentors and everyone else for the support,
> Roman (on behalf of the Apache HAWQ PPMC).
> 
> ## Resolution to create a TLP from graduating Incubator podling
> 
> X. Establish the Apache HAWQ 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 Hadoop native SQL query engine that
>  combines the key technological advantages of MPP database
>  with the scalability and convenience of Hadoop.
> 
>  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>  Committee (PMC), to be known as the "Apache HAWQ Project",
>  be and hereby is established pursuant to Bylaws of the
>  Foundation; and be it further
> 
>  RESOLVED, that the Apache HAWQ Project be and hereby is
>  responsible for the creation and maintenance of software
>  related to Hadoop native SQL query engine that
>  combines the key technological advantages of MPP database
>  with the scalability and convenience of Hadoop;
>  and be it further
> 
>  RESOLVED, that the office of "Vice President, Apache HAWQ" 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 HAWQ Project, and to have primary responsibility
>  for management of the projects within the scope of
>  responsibility of the Apache HAWQ 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 HAWQ Project:
> 
>   * Alan Gatesga...@apache.org
>   * Alexander denissovadenis...@apache.org
>   * Amy Bai  a...@apache.org
>   * Atri Sharmaa...@apache.org
>   * Bhuvnesh chaudharybhuvnesh2...@apache.org
>   * Bosco   bo...@apache.org
>   * Chunling Wang   wangchunl...@apache.org
>   * David Yozieyo...@apache.org
>   * Ed Espino esp...@apache.org
>   * Entong Shenent...@apache.org
>   * Foyzur Rahman   foy...@apache.org
>   * Goden Yao goden...@apache.org
>   * Gregory Chase   gregch...@apache.org
>   * Hong Wu  xunzh...@apache.org
>   * Hongxu Ma inte...@apache.org
>   * Hubert Zhang   hubertzh...@apache.org
>   * Ivan Weng iw...@apache.org
>   * Jesse Zhangj...@apache.org
>   * Jiali Yao j...@apache.org
>   * Jun Aoki ja...@apache.org
>   * Kavinder Dhaliwal kavin...@apache.org
>   * Lav Jain lavj...@apache.org
>   * Lei Chang lei_ch...@apache.org
>   * Lili Ma  lil...@apache.org
>   * Lirong Jianj...@apache.org
>   * Lisa Owen li...@apache.org
>   * Ming Li  m...@apache.org
>   * Mohamed Soliman  msoli...@apache.org
>   * Newton Alexna...@apache.org
>   * Noa Horn nh...@apache.org
>   * Oleksandr diachenkoodiache...@apache.org
>   * Paul Guo paul...@apache.org
>   * Radar Da Lei   r...@apache.org
>   * Roman Shaposhnik r...@apache.org
>   * Ruilong Huoh...@apache.org
>   * Shivram Mani   shiv...@apache.org
>   * Shubham Sharma  outofmem...@apache.org
>   * Tushar Pednekar  tushar_pedne...@apache.org
>   * Venkatesh raghavanvraghava...@apache.org
>   * Vineet Goelvvin...@apache.org
>   * Wen Lin  w...@apache.org
>   * Xiang Shengxsh...@apache.org
>   * Yi Jin  y...@apache.org
>   * Zhanwei Wang   wan...@apache.org
>   * Zhenglin Tao   ztao1...@apache.org
> 
>  NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lei Chang
>  be appointed to the office of Vice President, Apache HAWQ, 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 HAWQ PMC be and hereby is
>  tasked with the creation of a set of bylaws intended to
>  encourage open development and increased participation in the
>  A

[RESULT] [VOTE] Retire AriaTosca podling

[Suneel Marthi]

The Vote to retire AriaTosca podling has passed with 7 +1 binding votes and
no -1s.

Results:

+1 - Ted Dunning, John Ament, Jakob Homan, Dave Fisher, Philip Rhodes,
Stian, Suneel Marthi

Thanks all.

Re: [VOTE] Retire AriaTosca podling

[Suneel Marthi]

The code stays put and wouldn't implode.

Example is Apache Pirk which retired early 2017 -
https://github.com/apache/incubator-pirk

On Thu, Jun 28, 2018 at 5:34 PM, Phillip Rhodes 
wrote:

> Wait, does that mean that the source for all retired podlings
> disappears from all ASF repos (no archive) when a podling is retired??
>
> If that's the case, I vote -1 for this retirement, and all future such
> votes.  If that's not the case, then sure.  But I'm against anything
> that potentially results in a loss of available code.
>
>
> Phil
>
> This message optimized for indexing by NSA PRISM
>
>
> On Thu, Jun 28, 2018 at 3:18 PM, Dave Fisher 
> wrote:
> > Hi -
> >
> > Podlings do not retire to the Attic. The Attic is for TLPs. Any
> interested party should be sure to make their fork shortly.
> >
> > +1 (binding)
> >
> > Regards,
> > Dave
> >
> >> On Jun 28, 2018, at 12:07 PM, Suneel Marthi  wrote:
> >>
> >> The AriaTosca podling has decided to retire the project - see [1] [2]
> >>
> >> The Voting results from dev@ had:
> >>
> >> 6 +1 to retire the project
> >> 1 -1
> >>
> >> This is a call for Vote to retire/attic the podling and will run for 72
> hrs
> >> ending on Saturday - June 30 2018.
> >>
> >> Please Vote:
> >>
> >> +1 - Yes, Retire the podling
> >> -1  - What ya thinking? Don't do it because ..
> >>
> >> Here's my +1 binding
> >>
> >> [1]
> >> https://lists.apache.org/thread.html/a1a671cb061ad7ff2b724f4fd09720
> 295add90a45902c4cdcc2114f7@%3Cdev.ariatosca.apache.org%3E
> >>
> >> [2]
> >> https://lists.apache.org/thread.html/b8522a4ab613e95517df645d6cacd5
> 02cc73064b60fb41a18b4ea4fb@%3Cdev.ariatosca.apache.org%3E
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Retire AriaTosca podling

[Suneel Marthi]

Yes we did clarify that with ECI

Sent from my iPhone

> On Jun 28, 2018, at 4:21 PM, Ted Dunning  wrote:
> 
> +1 to retire
> 
> Somebody should reach out to the ECI Telecom person for voted -1 to let
> them know that the project isn't necessarily dying with this step and to
> let them know that they can fork the project and revive it (outside of the
> Incubator for now)
> 
> 
> 
>> On Thu, Jun 28, 2018 at 12:18 PM Dave Fisher  wrote:
>> 
>> Hi -
>> 
>> Podlings do not retire to the Attic. The Attic is for TLPs. Any interested
>> party should be sure to make their fork shortly.
>> 
>> +1 (binding)
>> 
>> Regards,
>> Dave
>> 
>>> On Jun 28, 2018, at 12:07 PM, Suneel Marthi  wrote:
>>> 
>>> The AriaTosca podling has decided to retire the project - see [1] [2]
>>> 
>>> The Voting results from dev@ had:
>>> 
>>> 6 +1 to retire the project
>>> 1 -1
>>> 
>>> This is a call for Vote to retire/attic the podling and will run for 72
>> hrs
>>> ending on Saturday - June 30 2018.
>>> 
>>> Please Vote:
>>> 
>>> +1 - Yes, Retire the podling
>>> -1  - What ya thinking? Don't do it because ..
>>> 
>>> Here's my +1 binding
>>> 
>>> [1]
>>> 
>> https://lists.apache.org/thread.html/a1a671cb061ad7ff2b724f4fd09720295add90a45902c4cdcc2114f7@%3Cdev.ariatosca.apache.org%3E
>>> 
>>> [2]
>>> 
>> https://lists.apache.org/thread.html/b8522a4ab613e95517df645d6cacd502cc73064b60fb41a18b4ea4fb@%3Cdev.ariatosca.apache.org%3E
>> 
>> 

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

[VOTE] Retire AriaTosca podling

[Suneel Marthi]

The AriaTosca podling has decided to retire the project - see [1] [2]

The Voting results from dev@ had:

6 +1 to retire the project
1 -1

This is a call for Vote to retire/attic the podling and will run for 72 hrs
ending on Saturday - June 30 2018.

Please Vote:

+1 - Yes, Retire the podling
-1  - What ya thinking? Don't do it because ..

Here's my +1 binding

[1]
https://lists.apache.org/thread.html/a1a671cb061ad7ff2b724f4fd09720295add90a45902c4cdcc2114f7@%3Cdev.ariatosca.apache.org%3E

[2]
https://lists.apache.org/thread.html/b8522a4ab613e95517df645d6cacd502cc73064b60fb41a18b4ea4fb@%3Cdev.ariatosca.apache.org%3E

Re: [VOTE] Apache Crail 1.0-incubating (RC3)

[Suneel Marthi]

+1 binding

1. Verified sigs and hashes
2. Built from source
3. incubating in artifacts name

On Thu, May 24, 2018 at 7:08 PM, Julian Hyde  wrote:

> Willem,
>
> You didn’t cast a vote on the release.
>
> I don’t think test failures is a blocker because README.md tells people to
> skip tests.
>
> IPMC,
>
> We still need one more +1, please.
>
> Julian
>
>
> > On May 23, 2018, at 12:23 AM, Jonas Pfefferle  wrote:
> >
> > Hi,
> >
> > At the moment there is no way to run the tests without setting up a
> configuration for your system (Crail needs hugepage mountpoint, network
> interfaces etc).
> > For that reason we instruct people in the README to build with
> "-DskipTests".
> >
> > If you want to deploy/configure Crail to run the tests you need to setup
> the CRAIL_HOME environment variable and adapt the Crail configuration with
> your network settings etc. Check the README for more detailed instructions.
> >
> > Thanks,
> > Jonas
> >
> > On Wed, 23 May 2018 10:33:09 +0800
> > Willem Jiang  wrote:
> >> Hi,
> >> I just tried to build from the source kit and got the test error due to
> >> missing crail-site.conf.
> >> I checked the README and cannot find any note for solving this problem.
> >> testRenameFile(org.apache.crail.ClientTest): null/conf/crail-site.conf
> (No
> >> such file or directory)
> >> testRenameFile(org.apache.crail.ClientTest)
> >> testlookupDirectory(org.apache.crail.ClientTest):
> >> null/conf/crail-site.conf (No such file or directory)
> >> Willem Jiang
> >> Blog: http://willemjiang.blogspot.com (English)
> >> http://jnn.iteye.com  (Chinese)
> >> Twitter: willemjiang
> >> Weibo: 姜宁willem
> >> On Tue, May 22, 2018 at 3:28 PM, Jonas Pfefferle 
> wrote:
> >>> Please vote to approve the source release of Apache Crail
> 1.0-incubating
> >>> (RC3).
> >>> This release candidate fixes all issues raised in the last IPMC vote:
> >>> - Add DISCLAIMER
> >>> - Move IBM copyright from NOTICE file to CREDITS file and fix
> formatting
> >>> of Apache copyright
> >>> - Leading directory name in tar/zip file is now
> >>> "apache-crail-1.0-incubating-src"
> >>>
> >>> The podling dev vote thread:
> >>>
> >>> https://www.mail-archive.com/dev@crail.apache.org/msg00268.html
> >>>
> >>> The result:
> >>>
> >>> https://www.mail-archive.com/dev@crail.apache.org/msg00274.html
> >>>
> >>> Commit hash: 0db64fddad52044eab75ee73e1857c7bcf6fae7d
> >>>
> >>> https://git1-us-west.apache.org/repos/asf?p=incubator-crail.
> >>> git;a=commit;h=0db64fddad52044eab75ee73e1857c7bcf6fae7d
> >>>
> >>> Release files can be found at:
> >>> https://dist.apache.org/repos/dist/dev/incubator/crail/1.0-rc3/
> >>>
> >>> The vote is open for at least 72 hours and passes if a majority of at
> least
> >>> 3 +1 PMC votes are cast.
> >>>
> >>> [ ] +1 Release this package as Apache Crail 1.0-incubating
> >>> [ ] -1 Do not release this package because ...
> >>>
> >>> Thanks,
> >>> Jonas
> >>>
> >>>
> >>> -
> >>> 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
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Wiki conflict for March report

[Suneel Marthi]

...and I am the culprit... apologies Mark.

On Tue, Mar 6, 2018 at 8:55 PM, John D. Ament  wrote:

> Thanks Mark.  I went through the changes from when the conflict was
> introduced to now, I don't see anything missing.  I also privately pinged
> the culprit.
>
> On Tue, Mar 6, 2018 at 7:34 PM Mark Thomas  wrote:
>
> > All,
> >
> > I have just spent rather longer than I would have liked cleaning up a
> > conflicted edit in this month's report.
> >
> > I have two requests.
> >
> > 1. If you have submitted your report, please check I didn't accidentally
> > remove content. I tried hard not to but the report was a mess and
> > something might have slipped through the net.
> >
> > 2. If you are editing the report please, please, please take care not to
> > create edit conflicts and if you do manage to create please clean up
> > your own mess rather than leaving it for others to do it for you.
> >
> > Mark
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Accept Druid into the Apache Incubator

[Suneel Marthi]

+1 - its great to see Druid coming to Apache

On Mon, Feb 26, 2018 at 9:23 PM, Bolke de Bruin  wrote:

> +1 (non-binding)
>
> > On 26 Feb 2018, at 20:53, Ashutosh Chauhan  wrote:
> >
> > +1
> >
> > On Sun, Feb 25, 2018 at 11:51 PM, Hao Chen  wrote:
> >
> >> +1 (non-binding)
> >>
> >> Hao Chen
> >>
> >> *PMC & Committer, Apache Eagle*
> >>
> >> On Mon, Feb 26, 2018 at 3:02 PM, ShaoFeng Shi 
> >> wrote:
> >>
> >>> +1 (non-binding)
> >>>
> >>> 2018-02-26 14:16 GMT+08:00 Zhanhui Li :
> >>>
>  +1 (non-binding)
> 
>  Glad to see Druid in Apache community.
> 
> > 在 2018年2月26日，下午1:45，Bhupesh Chawda  写道：
> >
> > +1 (non-binding)
> >
> > ~ Bhupesh
> >
> >
> > ___
> >
> > Bhupesh Chawda
> >
> > E: bhup...@datatorrent.com  |
> >> Twitter:
>  @bhupeshsc
> >
> > www.datatorrent.com   |
> >> apex.apache.org
> >>> <
>  http://apex.apache.org/>
> >
> >
> >
> > On Mon, Feb 26, 2018 at 11:12 AM, Chinmay Kolhatkar <
> >>> chin...@apache.org
>  >
> > wrote:
> >
> >> +1
> >>
> >> On 2018/02/24 09:02:41, Ted Dunning  wrote:
> >>> +1
> >>>
> >>>
> >>>
> >>> On Thu, Feb 22, 2018 at 11:03 AM, Julian Hyde 
>  wrote:
> >>>
>  Hi all,
> 
>  After some discussion on the Druid proposal[1], I'd like to
>  start a vote on accepting Druid into the Apache Incubator,
>  per the ASF policy[2] and voting rules[3].
> 
>  A vote for accepting a new Apache Incubator podling is a
>  majority vote for which only Incubator PMC member votes are
>  binding. Votes from other people are also welcome as an
>  indication of people's enthusiasm (or lack thereof).
> 
>  Please do not use this VOTE thread for discussions.  If
>  needed, start a new thread instead.
> 
>  This vote will run for at least 72 hours. Please VOTE as
>  follows:
>  [ ] +1 Accept Druid into the Apache Incubator
>  [ ] +0 Abstain
>  [ ] -1 Do not accept Druid into the Apache Incubator
>    because ...
> 
>  The proposal is listed below, but you can also access it on
>  the wiki[4].
> 
>  Julian
> 
>  [1] https://lists.apache.org/thread.html/
> >> b95f90a30b6e8587e9b108f368b07c
>  1b3e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E
> 
>  [2] https://incubator.apache.org/policy/incubation.html#
>  approval_of_proposal_by_sponsor
> 
>  [3] http://www.apache.org/foundation/voting.html
> 
>  [4] https://wiki.apache.org/incubator/DruidProposal
> 
> 
> 
> 
> 
>  = Druid Proposal =
> 
>  == Abstract ==
> 
>  Druid is a high-performance, column-oriented, distributed
>  data store.
> 
>  == Proposal ==
> 
>  Druid is an open source data store designed for real-time
>  exploratory analytics on large data sets. Druid's key
>  features are a column-oriented storage layout, a distributed
>  shared-nothing architecture, and ability to generate and
>  leverage indexing and caching structures. Druid is typically
>  deployed in clusters of tens to hundreds of nodes, and has
>  the ability to load data from Apache Kafka and Apache
>  Hadoop, among other data sources. Druid offers two query
>  languages: a SQL dialect (powered by Apache Calcite) and a
>  JSON-over-HTTP API.
> 
>  Druid was originally developed to power a slice-and-dice
>  analytical UI built on top of large event streams. The
>  original use case for Druid targeted ingest rates of
>  millions of records/sec, retention of over a year of data,
>  and query latencies of sub-second to a few seconds. Many
>  people can benefit from such capability, and many already
>  have (see http://druid.io/druid-powered.html). In addition,
>  new use cases have emerged since Druid's original
>  development, such as OLAP acceleration of data warehouse
>  tables and more highly concurrent applications operating
>  with relatively narrower queries.
> 
>  == Background ==
> 
>  Druid is a data store designed for fast analytics. It would
>  typically be used in lieu of more general purpose query
>  systems like Hadoop MapReduce or Spark when query latency is
>  of the utmost importance. Druid is often used as a data
>  store for powering GUI analytical applications.
> 
>  The buzzwordy description of Druid is a high-performa

Re: [VOTE] Apache AriaTosca Release 0.2.0

[Suneel Marthi]

+1 binding

On Thu, Jan 11, 2018 at 11:14 PM, Justin Mclean 
wrote:

> Hi,
>
> Seems reasonable. Changing my vote to +1 (binding)
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache MXNet (incubating) 1.0.0 release RC1

[Suneel Marthi]

+1 binding

On Sat, Dec 2, 2017 at 12:57 PM, Sergio Fernández  wrote:

> +1 (binding)
>
> Most of the minor issues I've seen so far are already reported by Justin.
> So let's address them for the next release. Good luck at NIPS!
>
>
>
> On Nov 30, 2017 4:45 PM, "Chris Olivier"  wrote:
>
> Hello All,
>
>
> This is a call for releasing Apache MXNet (incubating) 1.0.0, release
> candidate 1.
>
>
> Apache MXNet community has voted and approved the release.
>
>
> *Vote thread:*
>
> https://lists.apache.org/thread.html/568bf0c9960f14640b753a5fb6766c
> 7b0074339d286f405c04ffec96@%3Cdev.mxnet.apache.org%3E
>
>
> *Result thread:*
>
> https://lists.apache.org/thread.html/558a60f4d0c16b0311c96afd059082
> ebde0f773c56a03cb9e00bc19f@%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.0.0.rc1/
>
>
>
> *The release tag can be found here: *
>
> https://github.com/apache/incubator-mxnet/tree/1.0.0.rc1
>
>
>
> *The release hash is *25720d0e3c29232a37e2650f3ba3a2454f9367bb* and can be
> found here:*
>
>  25720d0e3c29232a37e2650f3ba3a2454f9367bb>
>
>
>
> *Release artifacts are signed with the following key:*
>
> 16DD B2E2 FE0C 3925 CB13  38D7 21F3 F9AB C622 DF82
>
>
>
> *KEY files are available here:*
>
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
>
>
>
> *For information about the contents of this release, see:*
>
>  Apache+MXNet+%28incubating%29+1.0+Release+Notes>
>
>
>
> The vote will be open for at least 72 hours.
>
>
> [ ] +1 Release this package as 1.0.0
>
> [ ] +0 no opinion
>
> [ ] -1 Do not release this package because...
>
>
> Thanks,
>
>
> -Chris Olivier
>
> cjolivie...@apache.org
>

Re: [VOTE] Graduate the Apache Trafodion Project from Incubator to a TLP

[Suneel Marthi]

+1 binding

On Tue, Nov 28, 2017 at 6:47 PM, Ted Dunning  wrote:

> +1 (binding)
>
>
>
> On Tue, Nov 28, 2017 at 2:52 PM, Sean Broeder 
> wrote:
>
> > +1 (non-binding)
> >
> > -Original Message-
> > From: Gunnar Tapper [mailto:tapper.gun...@gmail.com]
> > Sent: Tuesday, November 28, 2017 1:11 PM
> > To: general@incubator.apache.org
> > Subject: Re: [VOTE] Graduate the Apache Trafodion Project from Incubator
> > to a TLP
> >
> > +1 (non-binding)
> >
> > On Tue, Nov 28, 2017 at 2:36 PM, Suresh Subbiah <
> > suresh.subbia...@gmail.com>
> > wrote:
> >
> > > +1 (non-binding)
> > >
> > > On Tue, Nov 28, 2017 at 2:08 PM, Eric Owhadi 
> > > wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > -Original Message-
> > > > From: Dave Birdsall [mailto:dave.birds...@esgyn.com]
> > > > Sent: Tuesday, November 28, 2017 2:03 PM
> > > > To: general@incubator.apache.org
> > > > Subject: RE: [VOTE] Graduate the Apache Trafodion Project from
> > Incubator
> > > > to a TLP
> > > >
> > > > +1 (non-binding)
> > > >
> > > > -Original Message-
> > > > From: Pierre Smits [mailto:pierre.sm...@gmail.com]
> > > > Sent: Tuesday, November 28, 2017 12:01 PM
> > > > To: general@incubator.apache.org
> > > > Subject: [VOTE] Graduate the Apache Trafodion Project from Incubator
> > to a
> > > > TLP
> > > >
> > > > Hi all,
> > > >
> > > > The Trafodion community started an initial discussion graduating from
> > the
> > > > Incubator (see [1]) and had a consensus that the project is good to
> > > > graduate. The community proceeded to draft the graduation resolution,
> > > > discussed it [2], and voted on it [3]. The community vote passed with
> > 42
> > > +1
> > > > votes (40 advisory, 2 binding votes), no -1 votes or  +0 (abstains)
> > > votes.
> > > >
> > > > The discussion on the graduation of the Apache Trafodion project and
> > the
> > > > proposed draft resolution proceeded to the general mailing list of
> the
> > > > Apache Incubator project [4], and advice was provided about some
> > wording
> > > in
> > > > the draft resolution. The proposed changes to that draft are
> > incorporated
> > > > into the graduation resolution shown below. I would now like to call
> > for
> > > a
> > > > recommendation vote to present the Board of The Apache Software
> > > Foundation
> > > > with the resolution solution to graduate from incubation and
> establish
> > > > Apache Trafodion as a top-level project.
> > > >
> > > > Apache Trafodion entered incubation in May 2015. Since then the
> project
> > > > has produced several releases and has grown the community, the
> > committer
> > > > pool and the PPMC. For each release source artefacts have been voted
> on
> > > and
> > > > made available to the public on the Apache Distribution Network.
> Given
> > > all
> > > > the feedback provided in various discussions about our progress and
> > > > graduation, we feel confident that the project is ready to graduate
> > from
> > > > incubation.
> > > >
> > > > Please vote on whether to graduate Apache Trafodion from incubation
> and
> > > > recommend the graduation resolution below to the ASF Board.
> > > >
> > > > [  ] +1 Graduate the Apache Trafodion Project from the Incubator [  ]
> > +0
> > > > Abstain [  ] -1 Don't graduate the Apache Trafodion Project from the
> > > > Incubator because...
> > > >
> > > > This vote will be open for at least 72 hours. Thanks to all Trafodion
> > > > Mentors, all Trafodion Contributors for their support and
> contributions
> > > and
> > > > all in the Apache Incubator Project who took the time to provide
> their
> > > > insights and support.
> > > >
> > > > The full text of the resolution from [5] is below. The resolution
> will
> > be
> > > > submitted to the Board of Directors of The Apache Software Foundation
> > for
> > > > their consideration upon approval by the Apache Incubator PMC
> members.
> > > >
> > > > [1] [DISCUSSION] Graduation of The (incubating) Apache Trafodion
> > Project
> > > <
> > > > https://lists.apache.org/thread.html/8e00251a72a5e3f667fbcfc319c021
> > > > 3ad86ff21839e98e0ae68520e3@%3Cdev.trafodion.apache.org%3E>
> > > > [2] [VOTE] Graduate from Incubator and become a top-level project <
> > > > https://lists.apache.org/thread.html/86fc81f780840d5392b161572281f8
> > > > 03a1585d398d7820b26be9a255@%3Cdev.trafodion.apache.org%3E>
> > > > [3]  [RESULT][VOTE] Graduate from Incubator and become a top-level
> > > project
> > > >  > > > 56302cf98fe212909fefb8e76f@%3Cdev.trafodion.apache.org%3E>
> > > > [4] [DISCUSS] Resolution to graduate the incubating Apache Trafodion
> > > > Project  > > > 67b3704ea71aee2c7c1ff35579761f69b9e08b6e4cc69fafdc21531e@%
> > > > 3Cgeneral.incubator.apache.org%3E>
> > > >
> > > >
> > > > Best Regards,
> > > >
> > > > Pierre Smits
> > > >
> > > > -
> > > >
> > > > Establish the Apache Trafodion Project
> > > >
> > > >
> > > > WHEREAS, 

Re: [VOTE] Apache MXNet (incubating) 0.12.1 release RC0

[Suneel Marthi]

+1 binding

On Sat, Nov 11, 2017 at 4:07 AM, Meghna Baijal 
wrote:

> Hello All,
>
>
> This is a call for releasing Apache MXNet (incubating) 0.12.1, release
> candidate 0.
>
>
> Apache MXNet community has voted and approved the release.
>
>
> *Vote thread:*
>
> https://lists.apache.org/thread.html/254d533bf9b2df9ac2de960ba6303d
> 89d5d39a783573b4c6e47e4e08@%3Cdev.mxnet.apache.org%3E
>
>
> *Result thread:*
>
> https://lists.apache.org/thread.html/2027f372ebff981ea2e585f6215d8a
> 6a844058e7628a1f16ebd351c9@%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/0.12.1.rc0/
>
>
>
> *The release tag can be found here: *
>
> https://github.com/apache/incubator-mxnet/tree/0.12.1.rc0
>
>
>
> *The release hash is *e0c7906693f0c79b0ce34a4d777c26a6bf1903c1* and can be
> found here:*
>
> https://github.com/apache/incubator-mxnet/commit/
> e0c7906693f0c79b0ce34a4d777c26a6bf1903c1
>
>
>
> *Release artifacts are signed with the following key:*
>
> 69FF E8D6 1051 FFE7 E61B 02C2 80FD 81D7 703D F31B
>
>
>
> *KEY files are available here:*
>
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.12.1.rc0/
>
>
>
> *For information about the contents of this release, see:*
>
> https://cwiki.apache.org/confluence/display/MXNET/
> MXNet+0.12.1+Release+Notes
>
>
>
> The vote will be open for at least 72 hours.
>
>
> [ ] +1 Release this package as 0.12.1
>
> [ ] +0 no opinion
>
> [ ] -1 Do not release this package because...
>
>
> Thanks,
>
> Meghna Baijal
>

Re: [VOTE] Graduate the Apache Juneau podling from Incubator to a TLP

[Suneel Marthi]

+1

On Tue, Oct 10, 2017 at 2:29 PM, Pierre Smits 
wrote:

> +1
>
> Best regards
>
> Pierre
>
> On Tue, 10 Oct 2017 at 03:23 John D. Ament  wrote:
>
> > Hi,
> >
> > Actually my real affiliation would be Sparta Systems, Inc.  I believe
> Craig
> > would be something along the lines of "Enjoying Retirement" :-)
> >
> > Steve's affiliation is People Pattern Inc.
> >
> > John
> >
> > On Mon, Oct 9, 2017 at 4:39 PM James Bognar 
> > wrote:
> >
> > > Hi Raphael,
> > >
> > > The affiliations for the initial members are as follows:
> > >
> > > John D. Ament, Apache
> > > Steve Blackmon, Apache Streams
> > > James Bognar, Salesforce
> > > Peter Haumer, IBM
> > > David M Goddard, IBM
> > > Raphi D Lee, No affiliation
> > > Craig L Russell, Apache
> > > Stian Soiland-Reyes, Apache
> > >
> > >
> > > On Mon, Oct 9, 2017 at 4:22 PM, Raphael Bircher <
> > rbircherapa...@gmail.com>
> > > wrote:
> > >
> > > > -0 (binding)
> > > >
> > > > I don't give a -1 here, but I want to know, what the affiliations of
> > the
> > > > PMC's are. As I read older reports, i saw that diversity was a
> topic. I
> > > > know, I'm a bit picky about diversity. Can someone provide
> informations
> > > > there. And is the community grow issue really resolved? The Podling
> > > report
> > > > from July looks not very promising.
> > > >
> > > > I'm honest, if there where not long standing IPMC Members on the
> list,
> > I
> > > > would vote -1. So please clarify
> > > > - Community grow
> > > > - Diversity
> > > >
> > > > Thanks a load.
> > > >
> > > > Regards, Raphael
> > > >
> > > >
> > > > Am .10.2017, 16:11 Uhr, schrieb James Bognar  >:
> > > >
> > > > Hi everyone,
> > > >>
> > > >> The Apache Juneau PPMC held a vote on the readiness for graduation
> of
> > > >> Apache Juneau as a Top Level Project and came to a consensus to
> > proceed
> > > >> with graduation.  The vote was 7 +1s (5 binding) and no 0s or -1s.
> > > >>
> > > >> The vote thread can be found here:
> > > >> https://lists.apache.org/thread.html/d8eab3f75ca4c2f18477acbdf33726
> > > >> 113eed505a7457b8db289c41ab@%3Cdev.juneau.apache.org%3E
> > > >>
> > > >> Our Whimsy page can be found here:
> > > >> https://whimsy.apache.org/roster/ppmc/juneau
> > > >>
> > > >> Our status file can be found here:
> > > >> http://incubator.apache.org/projects/juneau.html
> > > >>
> > > >> Note that we are still waiting for the results of the Podling
> Suitable
> > > >> Names Search, but we do not anticipate any issues.
> > > >> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-134
> > > >>
> > > >> We have been in the incubator since June 24, 2016.  Since then we
> have
> > > >> proven our ability to produce Apache releases with the following:
> > > >> - 2016-10-25 - Juneau 6.0.0
> > > >> - 2017-01-03 - Juneau 6.0.1
> > > >> - 2017-02-25 - Juneau 6.1.0
> > > >> - 2017-04-28 - Juneau 6.2.0
> > > >> - 2017-06-28 - Juneau 6.3.0
> > > >> - 2017-08-01 - Juneau 6.3.1
> > > >> - 2017-10-06 - Juneau 6.4.0
> > > >>
> > > >> Our community consists of a mixture of corporate (IBM, Salesforce),
> > > Apache
> > > >> (Streams), and external committers.  We have a healthy and
> successful
> > > >> ongoing collaboration with the Apache Streams project.  Our
> community
> > is
> > > >> healthy, open, and respectful.
> > > >>
> > > >> Our source code is mature and heavily documented with many examples
> > and
> > > >> tutorials.
> > > >>
> > > >> Please vote on whether to graduate Juneau from the Incubator and
> > > recommend
> > > >> the graduation resolution below to the ASF Board.
> > > >>
> > > >> [  ] +1 Graduate Apache Juneau podling from the Incubator
> > > >> [  ] +0 Don't care
> > > >> [  ] -1 Don't graduate Apache Juneau podling from the Incubator
> > > because...
> > > >>
> > > >> This vote will be open for at least 72 hours. Thanks to all the
> > mentors
> > > >> and
> > > >> PPMC members of the Juneau community for your help in getting this
> > > project
> > > >> off the ground.
> > > >>
> > > >> The full text of the resolution is below. The resolution will be
> > > submitted
> > > >> to the Board of Directors for their consideration upon approval by
> the
> > > >> Apache Incubator PMC members.
> > > >>
> > > >> --
> > > >>
> > > >> Establish the Apache Juneau 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 toolkit for marshalling POJOs to a wide variety of
> > content
> > > >> types using a common framework, and for creating sophisticated
> > > >> self-documenting REST interfaces and microservices using VERY little
> > > >> code.
> > > >>
> > > >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > >> (PMC), to be known as the "Apache Juneau Pro

Re: [VOTE] Graduate the Apache Juneau podling from Incubator to a TLP

[Suneel Marthi]

+1 ipmc binding

On Mon, Oct 9, 2017 at 2:47 PM, Craig Russell  wrote:

> +1 (IPMC binding)
>
> Good job.
>
> Craig
>
> > On Oct 9, 2017, at 7:11 AM, James Bognar  wrote:
> >
> > Hi everyone,
> >
> > The Apache Juneau PPMC held a vote on the readiness for graduation of
> > Apache Juneau as a Top Level Project and came to a consensus to proceed
> > with graduation.  The vote was 7 +1s (5 binding) and no 0s or -1s.
> >
> > The vote thread can be found here:
> > https://lists.apache.org/thread.html/d8eab3f75ca4c2f18477acbdf33726
> > 113eed505a7457b8db289c41ab@%3Cdev.juneau.apache.org%3E
> >
> > Our Whimsy page can be found here:
> > https://whimsy.apache.org/roster/ppmc/juneau
> >
> > Our status file can be found here:
> > http://incubator.apache.org/projects/juneau.html
> >
> > Note that we are still waiting for the results of the Podling Suitable
> > Names Search, but we do not anticipate any issues.
> > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-134
> >
> > We have been in the incubator since June 24, 2016.  Since then we have
> > proven our ability to produce Apache releases with the following:
> > - 2016-10-25 - Juneau 6.0.0
> > - 2017-01-03 - Juneau 6.0.1
> > - 2017-02-25 - Juneau 6.1.0
> > - 2017-04-28 - Juneau 6.2.0
> > - 2017-06-28 - Juneau 6.3.0
> > - 2017-08-01 - Juneau 6.3.1
> > - 2017-10-06 - Juneau 6.4.0
> >
> > Our community consists of a mixture of corporate (IBM, Salesforce),
> Apache
> > (Streams), and external committers.  We have a healthy and successful
> > ongoing collaboration with the Apache Streams project.  Our community is
> > healthy, open, and respectful.
> >
> > Our source code is mature and heavily documented with many examples and
> > tutorials.
> >
> > Please vote on whether to graduate Juneau from the Incubator and
> recommend
> > the graduation resolution below to the ASF Board.
> >
> > [  ] +1 Graduate Apache Juneau podling from the Incubator
> > [  ] +0 Don't care
> > [  ] -1 Don't graduate Apache Juneau podling from the Incubator
> because...
> >
> > This vote will be open for at least 72 hours. Thanks to all the mentors
> and
> > PPMC members of the Juneau community for your help in getting this
> project
> > off the ground.
> >
> > The full text of the resolution is below. The resolution will be
> submitted
> > to the Board of Directors for their consideration upon approval by the
> > Apache Incubator PMC members.
> >
> > --
> >
> > Establish the Apache Juneau 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 toolkit for marshalling POJOs to a wide variety of content
> > types using a common framework, and for creating sophisticated
> > self-documenting REST interfaces and microservices using VERY little
> > code.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Juneau Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Juneau Project be and hereby is responsible
> > for the creation and maintenance of software related to a toolkit for
> > marshalling POJOs to a wide variety of content types using a common
> > framework, and for creating sophisticated self-documenting REST
> > interfaces and microservices using VERY little code; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Juneau" 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 Juneau
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache Juneau
> > 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 Juneau Project:
> >
> > * Craig L Russell 
> > * David Goddard   
> > * James Bognar
> > * Jochen Wiedmann 
> > * John D. Ament   
> > * Peter Haumer
> > * Raphi D Lee 
> > * Steve Blackmon  
> > * Stian Soiland-Reyes 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that James Bognar be appointed
> > to the office of Vice President, Apache Juneau, 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 Juneau PMC be and hereby is tasked
> > with the creation of a set of bylaws intended to encourage open
> > development and increased participation in the Apache Juneau Project;
> > and be it fu

Re: [VOTE] Graduate the Apache PredictionIO podling from Incubator to a TLP

[Suneel Marthi]

+1 binding 

On 2017-10-05 00:55, Donald Szeto wrote: 
> Hi all,> 
> 
> The PredictionIO community started an initial discussion on graduation> 
> [1], evaluated the maturity model [2], and had a consensus that the podling> 
> is good to graduate. The community proceeded to draft a> 
> resolution, discussed it [3], and voted on it [4]. The vote passed with 9> 
> +1 votes (8 binding) and no -1 votes.> 
> 
> The discussion proceeded to the general incubator list, and had gained> 
> support [5]. I would now like to call for a recommendation vote to present> 
> the ASF Board with the resolution to graduate from incubation and establish> 
> Apache PredictionIO as a top-level project.> 
> 
> Apache PredictionIO entered incubation in May 2016. Since then the podling> 
> has made 3 releases and added 8 PPMC members. For each release, source> 
> artifacts have been voted on and made available to the public on the Apache> 
> distribution network. Based on the maturity model evaluation [2], we> 
> believe that the project is ready to graduate from the Incubator.> 
> 
> Please vote on whether to graduate PredictionIO from the Incubator and> 
> recommend the graduation resolution below to the ASF Board.> 
> 
> [ ] +1 Graduate Apache PredictionIO podling from the Incubator> 
> [ ] +0 Don't care> 
> [ ] -1 Don't graduate Apache PredictionIO podling from the Incubator> 
> because...> 
> 
> This vote will be open for at least 72 hours. Thanks to all mentors and> 
> Apache PredictionIO project members and community for their support and> 
> contribution.> 
> 
> The full text of the resolution from [5] is below. The resolution will be> 
> submitted to the Board of Directors for their consideration upon approval> 
> by the Apache Incubator PMC members.> 
> 
> Best Regards,> 
> Donald> 
> 
> --> 
> 
> Establish the Apache PredictionIO 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 machine learning server built on top of state-of-the-art> 
> open source stack, that enables developers to manage and deploy> 
> production-ready predictive services for various kinds of machine> 
> learning tasks.> 
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee> 
> (PMC), to be known as the "Apache PredictionIO Project", be and hereby> 
> is established pursuant to Bylaws of the Foundation; and be it further> 
> 
> RESOLVED, that the Apache PredictionIO Project be and hereby is> 
> responsible for the creation and maintenance of software related to a> 
> machine learning server built on top of state-of-the-art open source> 
> stack, that enables developers to manage and deploy production-ready> 
> predictive services for various kinds of machine learning tasks; and be> 
> it further> 
> 
> RESOLVED, that the office of "Vice President, Apache PredictionIO" 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> 
> PredictionIO Project, and to have primary responsibility for management> 
> of the projects within the scope of responsibility of the Apache> 
> PredictionIO 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 PredictionIO> 
> Project:> 
> 
> * Alex Merritt > 
> * Andrew Kyle Purtell > 
> * Chan Lee > 
> * Donald Szeto > 
> * Felipe Oliveira > 
> * James Taylor > 
> * Justin Yip > 
> * Kenneth Chan > 
> * Lars Hofhansl > 
> * Lee Moon Soo > 
> * Luciano Resende > 
> * Marcin Ziemi%u0144ski > 
> * Marco Vivero > 
> * Mars Hall > 
> * Matthew Tovbin > 
> * Naoki Takezoe > 
> * Pat Ferrel > 
> * Paul Li > 
> * Shinsuke Sugaya > 
> * Simon Chan > 
> * Takahiro Hagino > 
> * Takako Shimamoto > 
> * Tamas Jambor > 
> * Tom Chan > 
> * Vitaly Gordon > 
> * Xiangrui Meng > 
> * Xusen Yin > 
> * Yevgeny Khodorkovsky > 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Donald Szeto be appointed> 
> to the office of Vice President, Apache PredictionIO, 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 PredictionIO PMC be and hereby is> 
> tasked with the creation of a set of bylaws intended to encourage open> 
> development and increased participation in the Apache PredictionIO> 
> Project; and be it further> 
> 
> RESOLVED, that the Apache PredictionIO Project be and hereby is tasked> 
> with the migration and rationalization of the Apache Incubator> 
> PredictionIO podling; and be it further> 
> 
> R

[jira] [Commented] (INCUBATOR-205) Marking the master branch of "incubator-mxnet" protected

[Suneel Marthi (JIRA)]

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

Suneel Marthi commented on INCUBATOR-205:
-

[~gautamkumar] have u read John's previous comment? This is not an incubator 
jira but should have been an infra jira. Close this one now and let's talk on 
slack. 

> Marking the master branch of "incubator-mxnet" protected
> 
>
> Key: INCUBATOR-205
> URL: https://issues.apache.org/jira/browse/INCUBATOR-205
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Gautam Kumar
>
> Hi,
>   Community has decided to mark the master branch of incubator-mxnet repo to 
> be protected. 
> We all agreed on protected branch  feature mentioned in 
> https://help.github.com/articles/about-protected-branches/.
> Appreciate your help.
> Regards,
> Gautam 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Re: [VOTE] Release Apache Juneau 6.3.1-incubating-RC1

[Suneel Marthi]

+1 binding

1. checked NOTICE, License
2. Verified sigs and hashes


On Mon, Jul 31, 2017 at 1:31 PM, John D. Ament 
wrote:

> +1 to release
>
> On 2017-07-25 09:41 (-0400), James Bognar  wrote:
> > The Apache Juneau Incubator PPMC has voted +3 to release Apache Juneau
> > 6.3.1-incubating RC1. This vote carries over +2 binding votes from IPMC
> > members.
> >
> > Steve Blackmon, +1
> > Jochen Wiedmann, +1
> >
> > Incubator PMC members please review and vote on this incubator release.
> >
> > Apache Juneau is...
> >
> > - A universal toolkit for marshalling POJOs to a wide variety of content
> > types using a common framework.
> > - A REST server API for creating universal self-documenting REST
> interfaces
> > using POJOs.
> > - A REST client API for interacting with REST interfaces using POJOs.
> > - A REST microservice API that combines all the features above for
> creating
> > lightweight standalone REST interfaces that start up in milliseconds.
> >
> > Please see original [VOTE] thread:
> > https://lists.apache.org/thread.html/e4c46719d8787fd45c362ca7e9eec4
> 4c47c4a45f02335dee6665ab2e@%3Cdev.juneau.apache.org%3E
> >
> > The binaries are available at:
> > https://dist.apache.org/repos/dist/dev/incubator/juneau/
> binaries/juneau-6.3.1-incubating-RC1/
> >
> > The release candidate to be voted over is available at:
> > https://dist.apache.org/repos/dist/dev/incubator/juneau/
> source/juneau-6.3.1-incubating-RC1/
> >
> > Build the release candidate using:
> > mvn clean install
> >
> > The release candidate is signed with a GPG key available at:
> > https://dist.apache.org/repos/dist/release/incubator/juneau/KEYS
> >
> > A staged Maven repository is available for review at:
> > https://repository.apache.org/content/repositories/orgapachejuneau-1013/
> >
> > Please vote on releasing these packages as:
> > Apache Juneau 6.3.1-incubating
> >
> > This vote will be open until 28-July-2017 10:00am.
> > [ ] +1 Release this package
> > [ ] 0 I don't feel strongly about it, but don't object
> > [ ] -1 Do not release this package because...
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Podlings & Gitbox Usage

[Suneel Marthi]

+1

On Fri, Jul 28, 2017 at 11:48 AM, John D. Ament 
wrote:

> All,
>
> As many are aware, Infra has been rolling out a new service that allows
> projects to leverage git repositories dually hosted on github and ASF git
> repositories, commonly known as gitbox.  This effectively allows a project
> to commit directly to Github and have those commits reflect back on the ASF
> side.
>
> This has been especially useful to a number of projects, since the github
> interface gives many options for managing repositories.  I've recently also
> asked infra to open it up to allow any IPMC member to request a gitbox
> repository for any approved podling that is using gitbox.  Podlings I think
> have found this useful, since many of them come from a github background.
> They like using the tool and having it available for all to use.
>
> So with that said, I want to propose some broad incubator wide policies for
> gitbox.  I'd like to propose that gitbox usage is approved for all
> podlings, there is nothing to inhibit a podling to request a gitbox
> repository and as long as a podling feels the need to use gitbox, like they
> would any other tool that we can integrate with, they should be free to use
> it without any additional approvals required.
>
> So please let me know your thoughts.  If I don't hear any -1's I plan to
> submit an infra ticket early next week to enable the access for all
> approved podlings.  Please note that your first conversion may need some
> lead time with infra.
>
> Regards,
>
> John
>

Re: [VOTE] Release Apache Tamaya Extensions 0.3-incubating

[Suneel Marthi]

+1 binding

1. Verified Sigs and Hashes
2.  Verified the DISCLAIMER, LICENSE and NOTICE
3.  Ran a clean {src} build and all tests pass.

On Mon, Jul 24, 2017 at 8:21 PM, John D. Ament 
wrote:

> Oliver,
>
> No, please leave the current vote open.  People will vote, just give them
> some time (summer holidays has everyone a bit sluggish to respond).
>
> You have 5 +1's on the dev list, 1 of which is binding, so you'll be fine
> :-)
>
> John
>
> On Mon, Jul 24, 2017 at 3:36 PM Oliver B. Fischer <
> o.b.fisc...@swe-blog.net>
> wrote:
>
> > Dear all,
> >
> > our vote is now running for more then a week. Should I close the vote
> > and start it again? I am not sure what is missing to get enough positive
> > (or even negative) votes on our release.
> >
> > Oliver
> >
> > Am 16.07.17 um 23:38 schrieb Oliver B. Fischer:
> > > Dear all,
> > >
> > > The Apache Tamaya team would like to release version 0.3-incubating of
> > > Apache Tamaya Extensions.
> > >
> > > The new release of our extensions as it uses the new 0.3 release of
> > > Apache Tamya API&Core.
> > >
> > > The source distribution has been deployed to [1] and the Maven
> > > artefacts are available at [2].
> > >
> > > The full release notes are available at [3].
> > >
> > > The project vote has been passed with
> > >
> > > 5 binding +1 votes (pmc):
> > >
> > > 0 non-binding +1
> > >
> > > 0 -1 vote
> > >
> > > The vote thread can be found at [4].
> > >
> > > Please note:
> > > This vote is a "majority approval" with a minimum of three +1 votes and
> > > no -1’s (see [5]).
> > >
> > > 
> > > [ ] +1 for community members who have reviewed the bits
> > > [ ] +0
> > > [ ] -1 for fatal flaws that should cause these bits not to be
> > > released, and why..
> > > 
> > >
> > > [1] https://s.apache.org/NA8w
> > > [2] https://s.apache.org/79Jw
> > > [3] https://s.apache.org/SSYr
> > > [4] https://s.apache.org/vyST
> > > [5] http://www.apache.org/foundation/voting.html#ReleaseVotes
> > >
> > >
> >
> > --
> > N Oliver B. Fischer
> > A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> > P +49 30 44793251 <+49%2030%2044793251>
> > M +49 178 7903538 <+49%20178%207903538>
> > E o.b.fisc...@swe-blog.net
> > S oliver.b.fischer
> > J oliver.b.fisc...@jabber.org
> > X http://xing.to/obf
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] publish ariatosca 0.1.1

[Suneel Marthi]

moving my +1 binding from dev@

On Thu, Jul 13, 2017 at 2:09 PM, John D. Ament 
wrote:

> +1 release contents look good, signatures fine.
>
> Minor nit: don't send to both general@ and dev@.  It confuses the vote.
>
> On Thu, Jul 13, 2017 at 10:33 AM Ran Ziv  wrote:
>
> > The ariatosca community voted on and has approved a proposal to release
> > ariatosca 0.1.1.
> > Pursuant to the Releases section of the Incubation Policy and with the
> > endorsement of our mentors, we would now like to request the permission
> of
> > the Incubator PMC to publish the tarball on Apache's /dist/release.
> >
> >
> > Proposal:
> > https://lists.apache.org/thread.html/b0571ee44c5f5bb325cc7f4
> > 9e475e3219c5ca89d78d22a3ac203a77c@%3Cdev.ariatosca.apache.org%3E
> >
> >
> > Vote result:
> >
> > https://lists.apache.org/thread.html/a2271fa86a2d0d9926a53c165b9a8a
> 50218d12ca01a651bdd0af5122@%3Cdev.ariatosca.apache.org%3E
> >
> >
> > Release candidate package may be found at:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> 0.1.1-incubating/
> > The "source" directory contains the actual source snapshot as required
> per
> > an Apache release.
> > the "sdist" and "bdist" directories are Pythonic source and binary
> > distributions, to be uploaded on PyPI upon a successful vote.
> >
> > See more information about the package in the original proposal thread.
> >
> >
> >
> > Please vote by Sunday, July 16th, at 14:00 UTC.
> >
> >
> > Thanks,
> > Ran
> >
>

Re: [VOTE] Graduate Apache Streams project from Incubator

[Suneel Marthi]

+1 binding

On Mon, Jul 10, 2017 at 11:09 AM, sblackmon  wrote:

>
> In concert with the discussion started last week [1], please vote on the
> draft resolution which establishes Apache Streams as a new top-level
> project at the Apache Software Foundation, as follows:
>
> [ ] +1, Graduate Apache Streams from the Incubator.
> [ ] +0, Don't care.
> [ ] -1, Don't graduate Apache Streams from the Incubator (provide details)
>
> The full text of the resolution is below.
>
> If approved by the Apache Incubator PMC members, the proposed resolution
> will be submitted to the Board of Directors for their consideration.
>
> Thanks !
>
> [1] https://lists.apache.org/thread.html/60d676ad7b190323f8479bccff8ae9
> 96f98bf5fcd0d0ff4d54b71006@
>
> Establish the Apache Streams 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 interoperability of online profiles and activity feeds.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache Streams Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Streams Project be and hereby is responsible for
> the creation and maintenance of software related to interoperability of
> online profiles and activity feeds; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Streams" 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 Streams Project, and
> to have primary responsibility for management of the projects within the
> scope of responsibility of the Apache Streams 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 Streams Project:
>
>  * Stephen D Blackmon   
>  * Robert Baker Douglas 
>  * Ate Douma
>  * Ryan Edward Ebanks   
>  * Matt Franklin
>  * Joey Frazee  
>  * Trevor Grant 
>  * Suneel Marthi
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephen D Blackmon be
> appointed to the office of Vice President, Apache Streams, 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 Streams PMC be and hereby is tasked with
> the creation of a set of bylaws intended to encourage open development and
> increased participation in the Apache Streams Project; and be it further
>
> RESOLVED, that the Apache Streams Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Streams podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Streams podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Retire HORN

[Suneel Marthi]

+1

On Sun, Jul 9, 2017 at 8:53 AM, John D. Ament  wrote:

> All,
>
> After a few discussions on list, its been agreed to retire the HORN
> podling.
>
> - The podling recently voted to retire [1]
> - Back in April I asked for their status, where a public discussion
> occurred with others stating they had no time for the project.
> - Recently started a discussion, where it was agreed [3]
>
> At this point, I am asking the IPMC to vote to retire HORN.
>
> [ ] +1 to retire
> [ ] -1 don't retire because...
>
> Here is my own +1.
>
> [1]:
> https://lists.apache.org/thread.html/9cec83d3a648c7746f5df0936798b4
> e533fe74ded7bc4eead8611d30@%3Cdev.horn.apache.org%3E
> [2]:
> https://lists.apache.org/thread.html/200eba59f8de9e0df220ef7c3d1c65
> e877d2cc8f480d6e89279fd810@%3Cdev.horn.apache.org%3E
> [3]:
> https://lists.apache.org/list.html?d...@horn.apache.org:gte=
> 1d:discuss%20retire%20horn
>

Re: [VOTE] publish ariatosca 0.1.0

[Suneel Marthi]

Copying my +1 from dev@ariatosca


On Wed, Jul 5, 2017 at 9:57 AM, John D. Ament  wrote:

> Copying my +1 from the dev list.
>
> - Builds from source
> - Signed
> - Clearly separated source, sdist and bdist files
>
> John
>
> On Wed, Jul 5, 2017 at 9:52 AM Ran Ziv  wrote:
>
> > The ariatosca community voted on and has approved a proposal to release
> > ariatosca 0.1.0.
> > Pursuant to the Releases section of the Incubation Policy and with the
> > endorsement of two of our mentors we would now like to request the
> > permission of the Incubator PMC to publish the tarball Apache's
> > /dist/release.
> >
> >
> > Proposal:
> >
> > https://lists.apache.org/thread.html/ab4979e21893389a97f57d0b182360
> 8a0933f27fcc4e7e0805cbc583@%3Cdev.ariatosca.apache.org%3E
> >
> >
> > Vote result:
> >
> > https://lists.apache.org/thread.html/24420783e5bb09db4246819d31c9b7
> 806edc57013e0838ec4790c06b@%3Cdev.ariatosca.apache.org%3E
> >
> >
> > Release candidate package may be found at:
> > *
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> 0.1.0-incubating/
> > <
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> 0.1.0-incubating/
> > >*
> > The "source" directory contains the actual source snapshot as required
> per
> > an Apache release.
> > the "sdist" and "bdist" directories are Pythonic source and binary
> > distributions, to be uploaded on PyPI upon a successful vote.
> >
> > See more information about the package in the original proposal thread.
> >
> >
> >
> > Please vote by Saturday, July 8th, at 14:00 UTC.
> >
> >
> > Thanks,
> > Ran
> >
>

Re: [DISCUSS] Migrating to the New Incubator Website

[Suneel Marthi]

FWIW, the Apache OpenNLP project recently moved to a new website using
JBake - http://opennlp.apache.org

On Mon, Jun 19, 2017 at 2:04 PM, John D. Ament 
wrote:

> On Mon, Jun 19, 2017 at 7:15 AM Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
>
> > Hi,
> >
> > On Sat, Jun 17, 2017 at 2:35 PM, John D. Ament 
> > wrote:
> > > ...The git repository for the site can be seen here:
> > >
> > https://git-wip-us.apache.org/repos/asf?p=incubator.git;a=
> shortlog;h=refs/heads/jbake-site
> > ...
> >
> > Just one detail, I'm also working on converting the Sling site to
> > JBake [1] and like the Tamaya podling website did I have included
> > JBake in a ./bin folder to make it easier for everybody to use the
> > same version.
> >
> >
> I ended up working with Gav to get 2.5.1 installed on jenkins slaves,
> buildbot slaves are coming next.  Not sure if that's of interest to you.
> The Tamaya guys are who introduced me to JBake.
>
>
> > -Bertrand
> >
> > [1] https://issues.apache.org/jira/browse/SLING-6955 - repo will be at
> > https://git-wip-us.apache.org/repos/asf?p=sling-sling-site.git soon
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Graduate Apache Atlas Project from Incubator

[Suneel Marthi]

+1 binding

On Tue, Jun 6, 2017 at 9:53 PM, John D. Ament  wrote:

> +1
>
> On Tue, Jun 6, 2017 at 4:06 PM Suma Shivaprasad 
> wrote:
>
> > Dear Incubator members,
> >
> > Following the discussion in Atlas community on graduating Apache Atlas
> from
> > incubation to a Top Level Project, starting this voting thread within
> > the incubator
> > community. Apache Atlas entered into incubation during May 2015 and has
> > come a long way since its incubation - features like classification based
> > security for Hive/HDFS/HBase/Kafka, LDAP based authentication, Knox SSO,
> >  re-designed/simplified UI and APIs, HA support, Graph abstraction,
> > addition of Sqoop/Storm/Falcon connectors have made Apache Atlas  a core
> > platform for Data governance.
> >
> > There has been a consistent growth in the Atlas community since
> incubation:
> > - PPMC has elected 15 individuals as committers of which 3 were also
> > included in PPMC
> > - PMC/committers are spread across 12 organizations
> > - more than 62 contributors were added to the project
> >
> > PPMC also has done 5 successful releases under the guidance of mentors
> > demonstrating their knowledge of ASF's IP policies.
> >
> > Voting was conducted within Apache Atlas Community to graduate
> >  to a Top Level Project and has passed with 12 +1 binding votes , no 0
> > or -­1 votes - https://s.apache.org/94xI.
> >
> > Apache Atlas has shown great progress and prospect to become a true TLP.
> > Following project summary reflects its accomplishments.
> >
> > Please vote on the Project resolution that is found in bottom to graduate
> > Apache Atlas from Incubator to Top Level Project.
> >
> > [ ] +1 Graduate Apache Atlas from the Incubator.
> > [ ] +0 No opinion
> > [ ] -1 Don't graduate Apache Atlas from the Incubator ( please provide
> > the reason)
> >
> > This VOTE will be opened for next 72 hours.
> >
> > Thanks all Mentors and Apache Atlas Project members for their support and
> > contributions.
> >
> > Here is my vote +1 (binding)
> >
> > Project Summary:
> >
> > =
> > http://incubator.apache.org/projects/atlas.html
> >
> > Project website:
> > =
> >
> > http://atlas.incubator.apache.org
> >
> > Project Documentation:
> > ===
> >
> > Home - http://atlas.incubator.apache.org/index.html
> > Architecture - http://atlas.incubator.apache.org/Architecture.html
> > Installation guide - http://atlas.incubator.apach
> > e.org/InstallationSteps.html
> > QuickStart Guide- http://atlas.incubator.apache.org/QuickStart.html
> > REST API - http://atlas.incubator.apache.org/api/v2/index.html
> > Atlas Release Guide - https://cwiki.apache.org/con
> > fluence/display/ATLAS/Developer+Resources
> >
> > Project maturity Assessment:
> > ===
> >
> > https://cwiki.apache.org/confluence/display/ATLAS/Apache+
> > Atlas+Project+Maturity+Model
> >
> > Proposed PMC size: 33
> >
> > Total number of committers  : 33 members
> > Total number of contributors : 62 members
> >
> > PMC affiliation (* indicated chair)
> >
> > * Hortonworks (13)
> >IBM (3)
> >Aetna(4)
> >Freestone (3)
> >Oracle(2)
> >Target (1)
> >Dataguise(1)
> >Inmobi(1)
> >JPMC(1)
> >MPR(1)
> >SAP(1)
> >SparklineData(1)
> >Others(1)
> >
> > 1676 commits on master
> > 80 contributors across all branches
> > Dev list averaged ~500-800 msgs/month in 2017
> > User list was created recently in April 2017. Hence not considering stats
> > for this.
> > 1859 issues created
> >
> > Committer¹s affiliation:
> > ===
> > * Hortonworks (13)
> >IBM (3)
> >Aetna(4)
> >Freestone (3)
> >Oracle(2)
> >Target (1)
> >Dataguise(1)
> >Inmobi(1)
> >JPMC(1)
> >MPR(1)
> >SAP(1)
> >SparklineData(1)
> >Others(1)
> >
> >
> > Apache Atlas Top Level Project Resolution:
> > 
> >
> > Establish the Apache Atlas 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 data management platform That provides real-time, consistent access
> > to data-intensive applications throughout widely distributed cloud
> > architectures.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Atlas Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> > RESOLVED,that the Apache Atlas Project be and hereby is responsible for
> > the creation and maintenance of software related to a data management
> > platform that provides real-time, consistent access to data-intensive
> > applications throughout widely distributed cloud architectures.
> >
> > RESOLVED, that the office of "Vice President, Apac

Re: private list subscriptions

[Suneel Marthi]

+1 to use @apache.org addresses only.

On Sat, May 20, 2017 at 7:05 PM, Henri Yandell  wrote:

> Dumb question time.
>
> Should we encourage that @apache.org addresses are used when subscribing
> to
> a private PMC list; and if not all PMC members have subscribed on a
> podling, can one subscribe their @apache.org addresses for them?
>
> Or should we mandate that @apache are used?
>
> Does anything automatic happen that ensures that only committers'
> addresses, or one of their preferred alternative addresses, are being used?
> I'm suspecting not.
>
> Thanks,
>
> Hen
>

Re: [VOTE] Retire the Pirk podling

[Suneel Marthi]

+1 binding

On Fri, Apr 14, 2017 at 1:43 PM, Markus Weimer  wrote:

> +1 (binding)
>
>
> On 2017-04-14 10:18 AM, Tim Ellison wrote:
>
>> +1 (binding)
>>
>> On 14/04/17 04:25, Josh Elser wrote:
>>
>>> Folks,
>>>
>>> The Pirk PPMC have recently voted unanimously to retire the podling.
>>> This decision, while heavy-hearted, comes on the tails of months of no
>>> development with no change on the horizon.
>>>
>>> Context for those interesting in reading: DISCUSS [1], VOTE [2], RESULT
>>> [3].
>>>
>>> [ ] +1: Retire Pirk
>>> [ ] -1: Do not retire Pirk because
>>>
>>> Here's my +1 (binding)
>>>
>>> - Josh
>>>
>>> [1] https://lists.apache.org/thread.html/c0a2bcc6271d71efb60c688
>>> ad83c4c3e1aeffb8851e01f675135b0c5@%3Cdev.pirk.apache.org%3E
>>> [2] https://lists.apache.org/thread.html/447f04840531c439250ca6b
>>> 05e3592ea3159d2e982b5bb75320ec427@%3Cdev.pirk.apache.org%3E
>>> [3] https://lists.apache.org/thread.html/ef4699debd5fe0441e94c8f
>>> 68e40e63d8a20d249a241bb50cf5341a6@%3Cdev.pirk.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
>>
>>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Metron podling Graduation

[Suneel Marthi]

+1 binding

On Thu, Mar 30, 2017 at 12:19 AM, Debo Dutta (dedutta) 
wrote:

> +1
>
> Sent from my iPhone
>
> > On Mar 29, 2017, at 7:53 PM, Julian Hyde  wrote:
> >
> > +1 (binding)
> >
> >> On Mar 29, 2017, at 6:55 PM, John D. Ament 
> wrote:
> >>
> >> +1
> >>
> >> When you submit the resolution to the board, the breakdown of PMC by
> >> affiliation (and make sure you use PMC not PPMC) can just be replaced
> with
> >> the proposed PMC members.   My question asking for it is a pure sanity
> >> check to make sure there is no dominance.
> >>
> >> John
> >>
> >>> On Wed, Mar 29, 2017 at 10:39 AM Casey Stella 
> wrote:
> >>>
> >>> Hi Everyone,
> >>>
> >>> I propose that we graduate Apache Metron (incubating) from the
> incubator.
> >>> The full text of the proposal is below, with requisite modifications
> >>> applied from the discussion thread.
> >>>
> >>> The discuss thread can be found at
> >>>
> >>> https://lists.apache.org/thread.html/e5d106456b28562bdc947624c6f33e
> 3281297dfd3803aab3d171bbad@%3Cgeneral.incubator.apache.org%3E
> >>>
> >>>
> >>> Best,
> >>>
> >>> Casey
> >>>
> >>> Resolution:
> >>>
> >>> Establish the Apache Metron 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 security analytics platform for big data use
> cases.
> >>>
> >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >>> Committee (PMC), to be known as the "Apache Metron Project",
> >>> be and hereby is established pursuant to Bylaws of the
> >>> Foundation; and be it further
> >>>
> >>> RESOLVED, that the Apache Metron Project be and hereby is
> >>> responsible for the creation and maintenance of software
> >>> related to:
> >>> (a) A mechanism to capture, store, and normalize any type of security
> >>> telemetry at extremely high rates.
> >>> (b) Real time processing and application of enrichments
> >>> (c) Efficient information storage
> >>> (d) An interface that gives a security investigator a centralized view
> >>> of data and alerts passed through the system.
> >>>
> >>> RESOLVED, that the office of "Vice President, Apache Metron" 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 Metron Project, and to have primary responsibility
> >>> for management of the projects within the scope of
> >>> responsibility of the Apache Metron 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 Metron Project:
> >>>
> >>>
> >>> PPMC by Affiliation:
> >>>
> >>> Hortonworks:
> >>> Sheetal Dolas (sheetal_dolas)
> >>> Ryan Merriman (rmerriman)
> >>> Larry McCay (lmccay)
> >>> P. Taylor Goetz (ptgoetz)
> >>> Nick Allen (nickallen)
> >>> David Lyle (lyle)
> >>> George Vetticaden (gvetticaden)
> >>> James Sirota (jsirota)
> >>> Casey Stella (cstella)
> >>> Michael Perez (mperez)
> >>> Kiran Komaravolu (kirankom)
> >>> Vinod Kumar Vavilapalli (vinodkv)
> >>>
> >>> Cisco:
> >>> Debo Dutta (ddutta)
> >>> Discovery Gerdes (discovery)
> >>>
> >>> Rackspace:
> >>> Oskar Zabik (smogg)
> >>> Andrew Hartnett (dev_warlord)
> >>> Paul Kehrer (reaperhulk)
> >>> Sean Schulte (sirsean)
> >>>
> >>> B23:
> >>> Mark Bittmann (mbittmann)
> >>> Dave Hirko (dbhirko)
> >>> Brad Kolarov (bjkolly)
> >>>
> >>> Mantech:
> >>> Charles Porter (cporter)
> >>> Ray Urciuoli (rurcioli)
> >>>
> >>> Fogbeam Labs:
> >>> Phillip Rhodes (prhodes)
> >>>
> >>>
> >>>
> >>>
> >>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Casey Stella
> >>> be appointed to the office of Vice President, Apache Metron, 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 Metron PMC be and hereby is
> >>> tasked with the creation of a set of bylaws intended to
> >>> encourage open development and increased participation in the
> >>> Apache Metron Project; and be it further
> >>>
> >>> RESOLVED, that the Apache Metron Project be and hereby
> >>> is tasked with the migration and rationalization of the Apache
> >>> Incubator Metron podling; and be it further
> >>>
> >>> RESOLVED, that all responsibilities pertaining to the Apache
> >>> Incubator Metron podling encumbered upon the Apache Incubator
> >>> Project are hereafter discharged.
> >>>
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: gen

Re: [DISCUSS] Apache Metron podling Graduation

[Suneel Marthi]

+1 binding

On Thu, Mar 23, 2017 at 8:05 PM, Niclas Hedhman  wrote:

> +1 (binding)
>
> On Fri, Mar 24, 2017 at 2:32 AM, Casey Stella  wrote:
>
> > Hi Everyone,
> >
> > The incubating Apache Metron community believes it is time to graduate
> > to TLP.
> >
> > Apache Metron entered incubation in December of 2015. Since then, we've
> > overcome technical challenges to remove Category X dependencies, and
> > made 3 releases. Our most recent release contains binary convenience
> > artifacts. We are a very helpful and engaged community, ready to answer
> > all questions and feedback directed to us via the user list. Through our
> > time in incubation we've added a number of committers and promoted some
> > of them to PPMC membership. We are actively pursuing others. While we do
> > still have issues to address raised by means of the maturity model, all
> > projects are ongoing processes, and we believe we no longer need the
> > incubator to continue addressing these issues.
> >
> > To inform the discussion, here is some basic project information:
> >
> > Project status:
> >   http://incubator.apache.org/projects/metron.html
> >
> > Project website:
> >   https://metron.incubator.apache.org/
> >
> > Project documentation:
> >https://cwiki.apache.org/confluence/display/METRON/Documentation
> >
> > Maturity assessment:
> >
> > https://cwiki.apache.org/confluence/display/METRON/
> > Apache+Project+Maturity+Model
> >
> > Community Vote to Graduate:
> >
> > https://lists.apache.org/thread.html/540378e2773b1b2ce2af498e56a643
> > 5e547c04948a6b496b9a4ffc71@%3Cdev.metron.apache.org%3E
> >
> > DRAFT of the board resolution is at the bottom of this email
> >
> > Proposed PMC size: 24 members
> >
> > Total number of committers: 6 members
> >
> >
> > 516 commits on develop
> > 34 contributors across all branches
> >
> > dev list averaged ~650 msgs/month for the last 3 months
> >
> >
> > Resolution:
> >
> > Establish the Apache Metron 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 security analytics platform for big data use cases.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "Apache Metron Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that the Apache Metron Project be and hereby is
> > responsible for the creation and maintenance of software
> > related to:
> > (a) A mechanism to capture, store, and normalize any type of security
> > telemetry at extremely high rates.
> > (b) Real time processing and application of enrichments
> > (c) Efficient information storage
> > (d) An interface that gives a security investigator a centralized view
> > of data and alerts passed through the system.
> >
> > RESOLVED, that the office of "Vice President, Apache Metron" 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 Metron Project, and to have primary responsibility
> > for management of the projects within the scope of
> > responsibility of the Apache Metron 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 Metron Project:
> >
> >
> > PPMC:
> > Mark Bittmann (mbittmann)
> > Sheetal Dolas (sheetal_dolas)
> > Debo Dutta (ddutta)
> > Discovery Gerdes (discovery)
> > Andrew Hartnett (dev_warlord)
> > Dave Hirko (dbhirko)
> > Paul Kehrer (reaperhulk)
> > Brad Kolarov (bjkolly)
> > Kiran Komaravolu (kirankom)
> > Larry McCay (lmccay)
> > P. Taylor Goetz (ptgoetz)
> > Ryan Merriman (rmerriman)
> > Michael Perez (mperez)
> > Charles Porter (cporter)
> > Phillip Rhodes (prhodes)
> > Sean Schulte (sirsean)
> > James Sirota (jsirota)
> > Casey Stella (cstella)
> > Ray Urciuoli(rurcioli)
> > Vinod Kumar Vavilapalli (vinodkv)
> > George Vetticaden (gvetticaden)
> > Oskar Zabik (smogg)
> > David Lyle (lyle)
> > Nick Allen (nickallen)
> >
> >
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Casey Stella
> > be appointed to the office of Vice President, Apache Metron, 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 Metron PMC be and hereby is
> > tasked with the creation of a set of bylaws intended to
> > encourage open development and increased participation in the
> > Apache Metron Project; and be it further
> >
> > RESOLVED, that the Apache Metron Project be and hereby

Re: [VOTE] Apache DataFu 1.3.2 release RC0

[Suneel Marthi]

+1 binding

1. Checked License Notice Disclaimer in Source Tar ball
2. Ran RAT check
3. Checked the hashes and signatures
4. Ran complete build and unit tests


> -- Forwarded message --
> From: Jakob Homan 
> Date: Mon, Mar 6, 2017 at 2:23 PM
> Subject: Re: [VOTE] Apache DataFu 1.3.2 release RC0
> To: DataFu 
> Cc: "general@incubator.apache.org" 
>
>
> +1 (binding)
>
> * Built jar, ran tests, checked MD5, checked N/L/D files, spot checked
> for headers
>
> -Jakob
>
>
> On 5 March 2017 at 19:57, Roman Shaposhnik  wrote:
> > On Thu, Mar 2, 2017 at 12:31 PM, Matthew Hayes 
> wrote:
> >> The Apache DataFu community has voted on and approved the release of
> Apache
> >> DataFu 1.3.2 (incubating):
> >>
> >> http://mail-archives.apache.org/mod_mbox/incubator-datafu-de
> v/201703.mbox/browser
> >>
> >> Results:
> >> 3 binding +1 votes
> >> No 0 votes
> >> No -1 votes
> >>
> >> I'd like to call a vote in general to approve the release.
> >>
> >> The source release candidate RC0 can be downloaded here:
> >>
> >> https://dist.apache.org/repos/dist/dev/incubator/datafu/apache-datafu
> >> -incubating-1.3.2-rc0/
> >>
> >> The artifacts (i.e. JARs) built from 1.3.2 RC0 can be found here:
> >>
> >> https://repository.apache.org/content/repositories/orgapache
> datafu-1004/
> >>
> >> These have been signed with PGP key 7BA4C7DF, corresponding to
> >> mha...@apache.org, which is included in the repository's KEYS file.
> This
> >> key can be found on keyservers, such as:
> >>
> >> *http://pgp.mit.edu/pks/lookup?op=get&search=0x7BA4C7DF
> >> *
> >>
> >> The key is also listed here:
> >>
> >> https://people.apache.org/keys/group/datafu.asc
> >>
> >> The release candidate has been tagged in git with release-1.3.2-rc0,
> which
> >> has been signed with the same key.  I've also created a branch 1.3.2.
> >>
> >> For reference, here is a list of all closed JIRAs tagged with 1.3.2:
> >>
> >> https://issues.apache.org/jira/issues/?jql=project%20%
> >> 3D%20DATAFU%20AND%20status%20%3D%20Closed%20AND%20fixVersion
> %20%3D%201.3.2%
> >> 20ORDER%20BY%20updated%20DESC%2C%20created%20DESC%2C%
> >> 20status%20DESC%2C%20priority%20DESC
> >>
> >> For a summary of the changes in this release, see:
> >>
> >> https://github.com/apache/incubator-datafu/blob/1.3.2/changes.md
> >>
> >> Note that starting with this release, LICENSE, NOTICE, and DISCLAIMER
> files
> >> are included in the META-INF of the JARs.  These differ from the source
> >> release versions as they reflect what is bundled in the JARs.
> >>
> >> Please download the release candidate, check the hashes, check the
> >> signatures, test it, and vote.  The vote will be open for 72 hours.
> >>
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> [ ] -1 disapprove (and reason why)
> >
> > +1 (binding)
> >
> > * Checked Maven artifacts (jars) to have the right LICENSE, NOTICE and
> > DISCLAIMER
> > * Checked source tarball for LICENSE, NOTICE and DISCLAIMER
> > * Checked the keyfile
> > * Checked the hashes and signatures
> > * Compared content of the tarball to the tag
> > * Run RAT check
> > * Built the project
> >
> > Thanks,
> > Roman.
>

Re: Podling Graduation Rally

[Suneel Marthi]

Streams was also called as 'Ready to graduate' in the December report.

Since Oct 2016, the podling has had 3 releases and another release is
planned for this weekend.

There have been discussions on the podIing mail lists about graduation
following the next planned release. I can help push forward Streams
graduation and the podling has satisfied most of the Apache Maturity
Assessment -  see
https://cwiki.apache.org/confluence/display/STREAMS/Apache+Maturity+Model+Assessment+for+Streams




On Mon, Feb 13, 2017 at 7:51 AM, Pierre Smits 
wrote:

> Hi John,
>
> Thank you for bringing this to our attention. I guess it should be brought
> back regularly so that participants here stay on the ball.
>
> That being said, I believe Trafodion should also be considered to be ready.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM 
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Mon, Feb 13, 2017 at 1:28 PM, John D. Ament 
> wrote:
>
> > All,
> >
> > As mentioned in this month's report, there are 63 active podlings.  While
> > I've been chasing retiring podlings, I think it would be good for the
> > community as a whole to look closely as podlings and see what we can do
> to
> > graduate podlings that seem to be doing well.
> >
> > Take a look at the last two reports:
> >
> > https://wiki.apache.org/incubator/February2017
> > https://wiki.apache.org/incubator/January2017
> >
> > Last month, I listed 4 podlings that appear to have completed all
> > graduation requirements, but remain in the incubator (Airflow, BatchEE,
> > Freemarker, Metron).  I didn't include that in February, but if I had to
> > list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> > PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my POV/opinion
> > unless others want to chime in).
> >
> > So I'm curious, what can others do to help these 12 podlings get past the
> > finish line?
> >
> > John
> >
>

Re: [VOTE] MXNet to enter the Incubator

[Suneel Marthi]

+1 binding

On Fri, Jan 20, 2017 at 12:16 PM, Stian Soiland-Reyes 
wrote:

> +1 (binding)
>
> On 17 Jan 2017 4:20 am, "Henri Yandell"  wrote:
>
> > Hi Incubator folk,
> >
> >I would like to call a vote for accepting "MXNet" for incubation in
> the
> > Apache Incubator.
> >
> > The full proposal is available at this wiki link:
> >
> > https://wiki.apache.org/incubator/MXNetProposal?action=recall&rev=19
> >
> > I will reply to this email with a copy of the proposal.
> >
> > MXNet already has a broad community, which I think is clear from the
> > interest from many contributors in being a part of the project at Apache.
> > There are four mentors signed up, along with 2 or 3 other Apache
> committers
> > looking to be involved in the project.
> >
> > Please cast your vote:
> >
> >   [ ] +1, bring MXNet into the Incubator
> >   [ ] -1, MXNet should not enter the Incubator, because...
> >
> >  The vote will be open for at least 72 hours, and only votes from the
> > Incubator PMC are binding.
> >
> > As the proposer, I consider my vote already cast in favour (and binding
> as
> > I'm a PMC member).
> >
> > Thanks all,
> >
> > Hen
> >
>

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Suneel Marthi]

I would like to sign up as mentor for MxNet.

On Fri, Jan 6, 2017 at 12:12 AM, Henri Yandell  wrote:

> Hello Incubator,
>
> I'd like to propose a new incubator Apache MXNet podling.
>
> The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> committers,
> 200 contributors) is very interested in joining Apache. MXNet is an
> open-source deep learning framework that allows you to define, train, and
> deploy deep neural networks on a wide array of devices, from cloud
> infrastructure to mobile devices.
>
> The wiki proposal page is located here:
>
>   https://wiki.apache.org/incubator/MXNetProposal
>
> I've included the text below in case anyone wants to focus on parts of it
> in a reply.
>
> Looking forward to your thoughts, and for lots of interested Apache members
> to volunteer to mentor the project in addition to Sebastian and myself.
>
> Currently the list of committers is based on the current active coders, so
> we're also very interested in hearing from anyone else who is interested in
> working on the project, be they current or future contributor!
>
> Thanks,
>
> Hen
> On behalf of the MXNet project
>
> -
>
> = MXNet: Apache Incubator Proposal =
>
> == Abstract ==
>
> MXNet is a Flexible and Efficient Library for Deep Learning
>
> == Proposal ==
>
> MXNet is an open-source deep learning framework that allows you to define,
> train, and deploy deep neural networks on a wide array of devices, from
> cloud infrastructure to mobile devices. It is highly scalable, allowing for
> fast model training, and supports a flexible programming model and multiple
> languages. MXNet allows you to mix symbolic and imperative programming
> flavors to maximize both efficiency and productivity. MXNet is built on a
> dynamic dependency scheduler that automatically parallelizes both symbolic
> and imperative operations on the fly. A graph optimization layer on top of
> that makes symbolic execution fast and memory efficient. The MXNet library
> is portable and lightweight, and it scales to multiple GPUs and multiple
> machines.
>
> == Background ==
>
> Deep learning is a subset of Machine learning and refers to a class of
> algorithms that use a hierarchical approach with non-linearities to
> discover and learn representations within data. Deep Learning has recently
> become very popular due to its applicability and advancement of domains
> such as Computer Vision, Speech Recognition, Natural Language Understanding
> and Recommender Systems. With pervasive and cost effective cloud computing,
> large labeled datasets and continued algorithmic innovation, Deep Learning
> has become the one of the most popular classes of algorithms for machine
> learning practitioners in recent years.
>
> == Rational ==
>
> The adoption of deep learning is quickly expanding from initial deep domain
> experts rooted in academia to data scientists and developers working to
> deploy intelligent services and products. Deep learning however has many
> challenges.  These include model training time (which can take days to
> weeks), programmability (not everyone writes Python or C++ and like
> symbolic programming) and balancing production readiness (support for
> things like failover) with development flexibility (ability to program
> different ways, support for new operators and model types) and speed of
> execution (fast and scalable model training).  Other frameworks excel on
> some but not all of these aspects.
>
>
> == Initial Goals ==
>
> MXNet is a fairly established project on GitHub with its first code
> contribution in April 2015 and roughly 200 contributors. It is used by
> several large companies and some of the top research institutions on the
> planet. Initial goals would be the following:
>
>  1. Move the existing codebase(s) to Apache
>  1. Integrate with the Apache development process/sign CLAs
>  1. Ensure all dependencies are compliant with Apache License version 2.0
>  1. Incremental development and releases per Apache guidelines
>  1. Establish engineering discipline and a predictable release cadence of
> high quality releases
>  1. Expand the community beyond the current base of expert level users
>  1. Improve usability and the overall developer/user experience
>  1. Add additional functionality to address newer problem types and
> algorithms
>
>
> == Current Status ==
>
> === Meritocracy ===
>
> The MXNet project already operates on meritocratic principles. Today, MXNet
> has developers worldwide and has accepted multiple major patches from a
> diverse set of contributors within both industry and academia. We would
> like to follow ASF meritocratic principles to encourage more developers to
> contribute in this project. We know that only active and committed
> developers from a diverse set of backgrounds can make MXNet a successful
> project.  We are also improving the documentation and code to help new
> developers get started quickly.
>
> === Community ===
>
> Acceptance into the Apache foundation woul

Re: [VOTE] Graduate Apache Ranger Project from the Incubator - Resending with additional mail distro

[Suneel Marthi]

+1 binding

On Wed, Jan 4, 2017 at 5:48 PM, Ramesh Mani  wrote:

> Dear Incubator members,
>
> Apache Ranger Project community has successfully released 0.6.2 version
> and with it there had been a lot of discussion within Apache Ranger
> community to consider graduation to TLP. Apache Ranger entered into
> incubation on 24th July 2014 and from this welcoming community had done a
> tremendous job in resolving various technical hurdles like refactoring the
> project core model to  be service based, adding more Apache Hadoop
> components like Apache YARN, Apache Storm, Apache Kafka, Apache Nifi,
> Apache Ranger KMS into Ranger Authorizing  model for security and making it
> into a core product in the Apache Hadoop security space. PPMC has exhibited
> a clear understanding of this growing apache community by electing  4
> individuals as committers  and  inculding 22 individuals as contributors to
> the Apache Ranger project. PPMC also has done 8 successful releases under
> the guidance of mentors demonstrating their mastery over AFS’s IP policies.
>
> An voting was conducted within Apache Ranger Community to graduate Apache
> Ranger Project to Top Level Project. Vote passed with 16 +1 votes , no 0 or
> –1 votes.
> http://mail-archives.apache.org/mod_mbox/incubator-ranger-
> dev/201612.mbox/%3CD479D4C8.11E4E%25rmani%40hortonworks.com%3E
>
> Apache Ranger Project has shown a great perspective to become a true TLP.
> Following summary on the project reflects its accomplishment.
>
> Please vote on the Project resolution that is found in bottom to graduate
> Apache Ranger Project from Incubator to Top Level Project.
>
> [ ] +1 Graduate Apache Ranger from the Incubator.
> [ ] +0 No opinion
> [ ] -1 Don't graduate Apache Ranger from the Incubator ( please provide
> the reason)
>
> This VOTE will be opened for next 72 hours.
>
> Thanks all Mentors and Apache Ranger Project members for their support and
> contributions.
>
> Here is my vote +1 (binding)
>
> Project Summary:
> =
>
> http://incubator.apache.org/projects/ranger.html
>
> Project website:
> =
>
> http://ranger.incubator.apache.org
>
> Project Documentation:
> ===
>
> http://ranger.incubator.apache.org/index.html
> http://ranger.incubator.apache.org/quick_start_guide.html
> https://cwiki.apache.org/confluence/display/RANGER/Release+Folders
>
> Project maturity Assessment:
> ===
>
> https://cwiki.apache.org/confluence/display/RANGER/
> Apache+Ranger+Project+Ma
> turity+Model
>
> Proposed PMC size: 17
>
> Total number of committers   : 14 members
> Total number of contributors : 22 members
>
> PMC affiliation (* indicated chair)
>
> * Hortonworks (9)
>Privacera (2)
>BlueTalon (1)
>Others(1)
>
> 1802 commits on develop
> 22 contributors across all branches
> Dev list averaged ~50 msgs/month in 2016
> User list averaged ~40 msgs/month in 2016
> 1208 issues created
> 997 issues resolved
>
> Committer’s affiliation:
> ===
> Active:
> Hortonworks
> Talend
> Freestone infotech
> BlueTalon
> eBay
> Others
>
>
> Apache Ranger Top Level Project Resolution:
> 
>
> Establish the Apache Ranger 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 data management platform That provides real-time, consistent access
> to data-intensive applications throughout widely distributed cloud
> architectures.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Ranger Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED,that the Apache Ranger Project be and hereby is responsible for
> the creation and maintenance of software related to a data management
> platform that provides real-time, consistent access to data-intensive
> applications throughout widely distributed cloud architectures.
>
> RESOLVED, that the office of "Vice President, Apache Ranger" 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 Ranger
> Project, and to have primary responsibility for management of the projects
> within the scope of responsibility of the Apache Ranger 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 Ranger Project:
>
> Alok La
> la...@apache.org
> Alan Gates
> ga...@apache.org
> Balaji Ganesan
> bgane...@apache.org

[ANNOUNCE] Apache Streams 0.4.1-incubating release

[Suneel Marthi]

The Apache Streams team is pleased to announce the release of Apache
Streams 0.4.1-incubating.

Sources are now available from Apache mirrors (
http://www.apache.org/dyn/closer.cgi/incubator/streams/relea
ses/0.4.1-incubating/ ) and binaries are now available from the apache
maven repository ( http://repository.apache.org/ ) and maven central (
http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache
.streams%22%20v%3A%220.4.1-incubating%22 )

Apache Streams (incubating) unifies a diverse world of digital profiles and
online activities into common formats and vocabularies, and makes these
datasets accessible across a variety of databases, devices, and platforms
for streaming, browsing, search, sharing, and analytics use-cases.

The project aims to provide simple two-way data interchange with popular
REST APIs in activity streams formats using a universal protocol. Streams
compatibility with multiple storage back-ends and ability to be embedded
within any java-based real-time or batch data processing platform ensures
that its interoperability features come with little technical baggage.

0.4.1-incubating is a maintenance release focused on code, documentation,
style and test improvements. Several highlights include adoption of the
google java code style and databricks scala code style, switch from JUnit
to TestNG for integration tests, elimination of guava transitive dependency
from most modules, and removal of non-apache hadoop dependencies from all
modules.

0.4.1-incubating also contains bug fixes and additional flexibility in the
facebook, instagram, twitter, and youtube provider modules.

More details on Apache Streams can be found at:

http://streams.incubator.apache.org/

Thanks to all the contributors who made the release possible, and encourage
anyone interested in using or contributing to the project to join the dev
mailing list ( mailto:dev-subscr...@streams.incubator.apache.org )


Regards,

Apache Streams (incubating) Community



DISCLAIMER

Apache Streams is an effort undergoing incubation at the Apache

Software Foundation (ASF), sponsored by the Apache Incubator PMC.

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.

Re: [VOTE] Release Apache Streams (incubating) 0.4.1

[Suneel Marthi]

Moving my vote from dev@streams

+1 binding

On Thu, Dec 22, 2016 at 4:27 PM, sblackmon  wrote:

> Hi Incubator PMC,
>
> The Apache Streams community has voted and approved the proposal to
> release Apache Streams 0.4.1 (incubating).
>
> We now kindly request the Incubator PMC members to review and vote on this
> incubator release.
>
> 0.4.1-incubating is a maintenance release focused on code, documentation,
> style and test improvements. Several highlights include adoption of the
> google java code style and databricks scala code style, switch from JUnit
> to TestNG for integration tests, elimination of guava transitive dependency
> from most modules, and removal of non-apache hadoop dependencies from all
> modules.
>
> 0.4.1-incubating also contains bug fixes and additional flexibility in the
> facebook, instagram, twitter, and youtube provider modules.
>
> Thread [VOTE] :
> https://lists.apache.org/thread.html/f27488e6a5d2355651b0aeb9dd6d82
> 891e20d802ee3c58a0cc4a6533@%3Cdev.streams.apache.org%3E
>
> Thread [VOTE] [RESULT] :
> https://lists.apache.org/thread.html/2bd0aef6ed78bdbceb222770b39d0e
> 92e3ffbaab53c7da2d56fff6c6@%3Cdev.streams.apache.org%3E
>
> The Release candidate to be voted upon is 0.4.1-incubating (rc1), with the
> following artifacts up for a vote:
>
> incubator-streams-master source tag (0.4.1-incubating):
> https://git-wip-us.apache.org/repos/asf?p=incubator-streams-master.git;h=
> 8b99488333700d2ff91bf846f656df28f90ef2fc
> incubator-streams source tag (0.4.1-incubating):
> https://git-wip-us.apache.org/repos/asf?p=incubator-streams.git;h=
> 0ab58845d4006ca49c935c1010e080b1aed32c8a
> incubator-streams-examples source tag (0.4.1-incubating):
> https://git-wip-us.apache.org/repos/asf?p=incubator-streams-
> examples.git;h=298d639ea0e9cae0280970a81ac992f8e2481923
>
> Maven staging repos:
> https://repository.apache.org/content/repositories/orgapachestreams-1020
> https://repository.apache.org/content/repositories/orgapachestreams-1021
> https://repository.apache.org/content/repositories/orgapachestreams-1022
>
> Source releases:
> https://dist.apache.org/repos/dist/dev/incubator/streams/0.
> 4.1-incubating/streams-master-0.4.1-incubating-source-release.zip
> https://dist.apache.org/repos/dist/dev/incubator/streams/0.
> 4.1-incubating/streams-project-0.4.1-incubating-source-release.zip
> https://dist.apache.org/repos/dist/dev/incubator/streams/0.
> 4.1-incubating/streams-examples-0.4.1-incubating-source-release.zip
>
> Checksums of streams-master-0.4.1-incubating-source-release.zip:
> MD5: f34b5799f7852756ee3be6af742c8b11
> SHA1: 596346b53b66d4a7878a8443c3c3a1766c325442
> Checksums of streams-project-0.4.1-incubating-source-release.zip:
> MD5: a5d548ee32b856da7ecdeb7c5c6de124
> SHA1: d5be5990200d05f408d13e5061fcc2bed112cbda
> Checksums of streams-examples-0.4.1-incubating-source-release.zip:
> MD5: 55151873d89c7c1f09e6a6f5916dc2ac
> SHA1: 72921be981f739a2962e9a1363115377d86d3ac8
>
> Release artifacts are signed with the following keys:
> https://people.apache.org/keys/committer/smarthi.asc
> https://people.apache.org/keys/committer/sblackmon.asc
>
> Please take the time to verify these artifacts before casting your vote.
>
> Note that Maven 3.3.9 and JDK 1.8+ are now required, and that MAVEN_OPTS
> should set the java heap to at least 2G for best results.
>
> These repositories must be verified (mvn clean verify) in the right order:
> first streams-master, then streams-project, finally streams-examples.
>
> Note that to execute the full suite of integration tests, one must first
> prepare a testing environment with docker databases and working credentials
> to all providers.
>
> Vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Ratis to enter Apache Incubator

[Suneel Marthi]

+1 binding

On Fri, Dec 16, 2016 at 8:32 PM, Roman Shaposhnik 
wrote:

> On Fri, Dec 16, 2016 at 3:41 PM, Jitendra Pandey
>  wrote:
> > Dear All,
> >I would like to call a vote for accepting "Ratis" for incubation in
> the Apache Incubator.
> > The full proposal is available below, and is also available at this wiki
> link.
> >https://wiki.apache.org/incubator/RatisProposal
> > There are two discussion threads for this proposal, because the project
> was renamed from Concur to Ratis based on feedback. Please look for both
> Concur and Ratis in the archives.
> >
> > Please cast your vote:
> >
> >   [ ] +1, bring Ratis into Incubator
> >   [ ] +0, I don't care either way,
> >   [ ] -1, do not bring Ratis into Incubator, because...
>
> +1 (binding) Super excited to see RAFT Java implementation community
> development effort!
>
> Thanks,
> Roman.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Streams 0.4-incubating

[Suneel Marthi]

Here's the Build Order:

1.  Streams-master
2.  Streams-Project
3.  Streams-examples

And the project needs Java 8 and Maven >= 3.3.9


On Wed, Nov 9, 2016 at 9:10 PM, John D. Ament  wrote:

> In addition, can you provide build instructions?
>
> Johns-MBP-2:streams-project-0.4-incubating johnament$ mvn clean install
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for
> org.apache.streams:streams-project:0.4-incubating: Failure to find
> org.apache.streams:streams-master:pom:0.4-incubating in
> http://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of
> central-repo has elapsed or updates are forced and 'parent.relativePath'
> points at wrong local POM @ line 23, column 13
>  @
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR]   The project org.apache.streams:streams-project:0.4-incubating
> (/Users/johnament/Downloads/streams-project-0.4-incubating/pom.xml) has 1
> error
> [ERROR] Non-resolvable parent POM for
> org.apache.streams:streams-project:0.4-incubating: Failure to find
> org.apache.streams:streams-master:pom:0.4-incubating in
> http://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of
> central-repo has elapsed or updates are forced and 'parent.relativePath'
> points at wrong local POM @ line 23, column 13 -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/
> UnresolvableModelException
> Johns-MBP-2:streams-project-0.4-incubating johnament$
>
>
> On Wed, Nov 9, 2016 at 9:08 PM John D. Ament 
> wrote:
>
> > On Mon, Nov 7, 2016 at 11:51 AM sblackmon  wrote:
> >
> > Hi Incubator PMC,
> >
> > The Apache Streams community has voted and approved the proposal to
> > release Apache Streams 0.4 (incubating).
> >
> > We now kindly request the Incubator PMC members to review and vote on
> this
> > incubator release.
> >
> > PPMC and IPMC feedback received during rc1 and rc2 votes (respectively)
> > have been addressed with rc3.
> >
> > Thread [VOTE] :
> >
> > https://lists.apache.org/thread.html/4ad0b6889fb61738209ba464e30dcc
> 67d74ddacf60e820992dee83ab@%3Cdev.streams.apache.org%3E
> >
> > Thread [VOTE] [RESULT] :
> >
> > https://lists.apache.org/thread.html/4ad0b6889fb61738209ba464e30dcc
> 67d74ddacf60e820992dee83ab@%3Cdev.streams.apache.org%3E
> >
> >
> > The Release candidate to be voted upon is 0.4-incubating release
> candidate
> > (rc3), with the following artifacts up for a vote:
> >
> > incubator-streams-master source tag (r0.4-incubating):
> >
> > https://git-wip-us.apache.org/repos/asf?p=incubator-streams-
> master.git;h=b87b23b19649dbd17a26f43aac3e51358d7e2b32
> > incubator-streams
> >  streams-master.git;h=b87b23b19649dbd17a26f43aac3e51
> 358d7e2b32incubator-streams>
> > source tag (r0.4-incubating):
> >
> > https://git-wip-us.apache.org/repos/asf?p=incubator-streams.git;h=
> fc51194bcf44328759961dd1ee95df0b829fe98f
> > incubator-streams-examples
> >  fc51194bcf44328759961dd1ee95df0b829fe98fincubator-streams-examples>
> > source tag (r0.4-incubating):
> >
> > https://git-wip-us.apache.org/repos/asf?p=incubator-streams-
> examples.git;h=5cfcc2511a714922cdbc8b15f9cec5a3170f4162
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachestreams-1019
> >
> > Source releases:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/streams/0.
> 4-incubating/streams-master-0.4-incubating-source-release.zip
> >
> > https://dist.apache.org/repos/dist/dev/incubator/streams/0.
> 4-incubating/streams-project-0.4-incubating-source-release.zip
> >
> > https://dist.apache.org/repos/dist/dev/incubator/streams/0.
> 4-incubating/streams-examples-0.4-incubating-source-release.zip
> >
> >
> > Can you explain what each of these artifacts are?  what's in "master" vs
> > "project"?  Examples is clear enough.
> >
> >
> > Checksums of streams-master-0.4-incubating-source-release.zip:
> > MD5: 182ed359685f35d950df3ba631d7d5e1
> > SHA1: 3cf0110f6a1abd7160ae40088d35ce1d9b581ac0
> > Checksums of streams-project-0.4-incubating-source-release.zip:
> > MD5: 5321f8c3f470d464a6f354d8b624c726
> > SHA1: ea294756549569e1a9392db362f3e3b33adc9dc1
> > Checksums of streams-examples-0.3-incubating-source-release.zip:
> > MD5: e7af881128418f3a782bf90d669348cb
> > SHA1: f53abf0cd23e72f85b987

Re: [VOTE] Release Apache Streams 0.4-incubating

[Suneel Marthi]

Planting my vote from dev@

+1 binding

On Mon, Nov 7, 2016 at 11:51 AM, sblackmon  wrote:

> Hi Incubator PMC,
>
> The Apache Streams community has voted and approved the proposal to
> release Apache Streams 0.4 (incubating).
>
> We now kindly request the Incubator PMC members to review and vote on this
> incubator release.
>
> PPMC and IPMC feedback received during rc1 and rc2 votes (respectively)
> have been addressed with rc3.
>
> Thread [VOTE] :
> https://lists.apache.org/thread.html/4ad0b6889fb61738209ba464e30dcc
> 67d74ddacf60e820992dee83ab@%3Cdev.streams.apache.org%3E
>
> Thread [VOTE] [RESULT] :
> https://lists.apache.org/thread.html/4ad0b6889fb61738209ba464e30dcc
> 67d74ddacf60e820992dee83ab@%3Cdev.streams.apache.org%3E
>
> The Release candidate to be voted upon is 0.4-incubating release candidate
> (rc3), with the following artifacts up for a vote:
>
> incubator-streams-master source tag (r0.4-incubating):
> https://git-wip-us.apache.org/repos/asf?p=incubator-streams-master.git;h=
> b87b23b19649dbd17a26f43aac3e51358d7e2b32
> incubator-streams source tag (r0.4-incubating):
> https://git-wip-us.apache.org/repos/asf?p=incubator-streams.git;h=
> fc51194bcf44328759961dd1ee95df0b829fe98f
> incubator-streams-examples source tag (r0.4-incubating):
> https://git-wip-us.apache.org/repos/asf?p=incubator-streams-
> examples.git;h=5cfcc2511a714922cdbc8b15f9cec5a3170f4162
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachestreams-1019
>
> Source releases:
> https://dist.apache.org/repos/dist/dev/incubator/streams/0.
> 4-incubating/streams-master-0.4-incubating-source-release.zip
> https://dist.apache.org/repos/dist/dev/incubator/streams/0.
> 4-incubating/streams-project-0.4-incubating-source-release.zip
> https://dist.apache.org/repos/dist/dev/incubator/streams/0.
> 4-incubating/streams-examples-0.4-incubating-source-release.zip
>
> Checksums of streams-master-0.4-incubating-source-release.zip:
> MD5: 182ed359685f35d950df3ba631d7d5e1
> SHA1: 3cf0110f6a1abd7160ae40088d35ce1d9b581ac0
> Checksums of streams-project-0.4-incubating-source-release.zip:
> MD5: 5321f8c3f470d464a6f354d8b624c726
> SHA1: ea294756549569e1a9392db362f3e3b33adc9dc1
> Checksums of streams-examples-0.3-incubating-source-release.zip:
> MD5: e7af881128418f3a782bf90d669348cb
> SHA1: f53abf0cd23e72f85b9877db7624df8f2e706f6c
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/sblackmon.asc
>
> Note that Maven 3.3.9 and JDK 1.8+ are now required, and that MAVEN_OPTS
> should set the java heap to at least 2G for best results.
>
> These repositories must be built and installed locally in the right
> order: first streams-master, then streams-project, finally
> streams-examples.
>
> To see the full set of steps used to validate and perform the release
> candidate, and review the output of each step, visit this public wiki page.
>
> https://cwiki.apache.org/confluence/display/STREAMS/0.
> 4-incubating+rc3+release+logs
>
> Note that to execute the full suite of integration tests, one must first
> prepare a testing environment with docker databases and working credentials
> to all providers.
>
> Vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>

Re: [VOTE] Graduate Apache Geode (incubating)

[Suneel Marthi]

+1 binding 

Sent from my iPhone

> On Nov 6, 2016, at 3:58 PM, Roman Shaposhnik  wrote:
> 
> Hi!
> 
> after a very positive discussion in the Geode community
> and at the IPMC level:
>http://markmail.org/message/z4prj62hr7rn6cu6
> I'd like to bring the following resolution for a formal vote.
> 
> Please vote on the resolution pasted below to graduate
> Apache Geode from the incubator to top level project.
> 
> [ ] +1 Graduate Apache Geode from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Geode from the Incubator because...
> 
> This vote will be open for at least 72 hours.
> 
> Many thanks to our mentors and everyone else for the support,
> Roman (on behalf of the Apache Geode PPMC).
> 
> Resolution:
> 
> Establish the Apache Geode 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 data management platform that provides
> real-time, consistent access to data-intensive applications
> throughout widely distributed cloud architectures.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Geode Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that the Apache Geode Project be and hereby is
> responsible for the creation and maintenance of software
> related to a data management platform that provides real-time,
> consistent access to data-intensive applications throughout
> widely distributed cloud architectures.
> 
> RESOLVED, that the office of "Vice President, Apache Geode" 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 Geode Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Geode 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 Geode Project:
> 
> * Anilkumar Gingade 
> * Anthony Baker 
> * Ashvin Agrawal 
> * Avinash Dongre 
> * Barry Oglesby < bogle...@apache.org>
> * Bruce Schuchardt 
> * Dan Smith 
> * Darrel Schneider 
> * Dave Barnes 
> * Eric Shu 
> * Greg Chase 
> * Hitesh Khamesra 
> * Jason Huynh 
> * Jens Deppe 
> * Jianxia Chen 
> * Jinmei Liao 
> * John Blum 
> * Karen Miller 
> * Konstantin Boudnik 
> * Kirk Lund 
> * Mark Bretl 
> * Nabarun Nag 
> * Niall Pemberton 
> * Nitin Lamba 
> * Roman Shaposhnik 
> * Sai Boorlagadda 
> * Swapnil Bawaskar 
> * Udo Kohlmeyer 
> * William Markito 
> * Xiaojian Zhou 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Bretl
> be appointed to the office of Vice President, Apache Geode, 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 Geode PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache Geode Project; and be it further
> 
> RESOLVED, that the Apache Geode Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Geode podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Geode podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
> 
> -
> 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

[VOTE] Release Apache Streams 0.4.0 incubating

[Suneel Marthi]

Hi Incubator PMC,

The Apache Streams community has voted and approved the proposal to
release Apache Streams 0.4.0 (incubating).

We now kindly request the Incubator PMC members to review and vote on this
incubator release.

Thread [VOTE] :
https://lists.apache.org/thread.html/104310391acd0c4ad0097427ae8175
c85ce43f99a8bd824e35336b1e@%3Cdev.streams.apache.org%3E


Thread [VOTE] [RESULT] :
https://lists.apache.org/thread.html/92720097cc5e8ed19e2c8a6ff1adfa
51761ec86497b158f46e8973a4@%3Cdev.streams.apache.org%3E

The Release candidate to be voted upon is 0.4-incubating release candidate
(rc2),
with the following artifacts up for a vote:

incubator-streams-master source tag (r0.4-incubating):
https://git-wip-us.apache.org/repos/asf?p=incubator-streams-
master.git;a=commit;h=b5096fa46bdccfdafce95ee7bcd535a604a63041
incubator-streams source tag (r0.4-incubating):
https://git-wip-us.apache.org/repos/asf?p=incubator-streams.
git;a=commit;h=7417348cbadc068e3f9d45b07ed51bc286676d64
incubator-streams-examples source tag (r0.4-incubating):
https://git-wip-us.apache.org/repos/asf?p=incubator-streams-
examples.git;a=commit;h=5807a4522c9ea3f93547baf801f4eb64d1a8
3383(https://git-wip-us.apache.org/repos/asf?p=incubator-
streams-examples.git)

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachestreams-1016

Source releases:
https://repository.apache.org/service/local/repositories/org
apachestreams-1016/content/org/apache/streams/streams-master

/0.4-incubating/streams-master-0.4-incubating-source-release.zip
https://repository.apache.org/service/local/repositories/org

apachestreams-1016/content/org/apache/streams/streams-projec
t/0.4-incubating/streams-project-0.4-incubating-source-release.zip

https://repository.apache.org/service/local/repositories/org
apachestreams-1016/content/org/apache/streams/streams-exampl
es/0.4-incubating/streams-examples-0.4-incubating-source-release.zip

Checksums of streams-master-0.4-incubating-source-release.zip:
MD5: 8378e982583d218b10e70183e4f6363c
SHA1: 90e557b6f36314e47d7cdbb43bb62d45522270f8
Checksums of streams-project-0.4-incubating-source-release.zip:
MD5: 0a9d967da4c3314ec9e0b4f0b6d90f90
SHA1: 8d775596c0376ed5c5ac4d349379c2e01ff39ee2
Checksums of streams-examples-0.3-incubating-source-release.zip:
MD5: 9a46bfc7afd3fe2ee40eabf0a2ca876c
SHA1: b8fa09d1e016cf998b81240ac34058ea275c8e50

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/sblackmon.asc

Note that Maven 3.3.9 and JDK 1.8+ are now required, and that MAVEN_OPTS
should set the java heap to at least 2G for best results.

These repositories must be built and installed locally in the right
order: first streams-master, then streams-project, finally streams-examples.

To see the full set of steps used to validate and perform the release
candidate, and review the output of each step, visit this public wiki page.

https://cwiki.apache.org/confluence/display/STREAMS/0.4-incu
bating+rc2+release+logs

Note that to execute the full suite of integration tests, one must first
prepare a testing environment with docker databases and working credentials
to all providers.

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Re: [VOTE] Apache Pirk 0.2.0-incubating Release

[Suneel Marthi]

Moving my vote from dev@

+1 binding

On Fri, Oct 7, 2016 at 8:14 AM, Justin Mclean 
wrote:

> Hi,
>
> +1 binding
>
> I checked:
> - name including incubating
> - signature and hashed good
> - DISCLAIMER exists
> - LICENSE and NOTICE good
> - Files have Apache header except this file [1]. Please fix in the next
> release.
> - No unexpected binary files in source release
> - Can compile from source
>
> Thanks,
> Justin
>
> 1. ./apache-pirk-0.2.0-incubating/docs/script.js
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache PredictionIO 0.10.0 (incubating) RC5

[Suneel Marthi]

Moving my vote from dev@

+1 binding

On Fri, Oct 7, 2016 at 8:42 AM, Justin Mclean 
wrote:

> Hi,
>
> +1 binding
>
> I checked,
> - incubating in name
> - signatures and hashes correct
> - LICENSE and NOTICE is fine
> - No unexpected binaries
> - All source files have ASF headers (although there are a large number of
> file that could possible have headers that don’t).
> - Can compile from source
>
> Very minor. Noticed there still this odd file in the release [1] which
> probably contains incorrect information, also this file [2] has an author
> tag, author tags are generally not used in Apache projects.
>
> Thanks,
> Justin
>
> 1. docs/manual/source/humans.txt
> 2. examples/scala-parallel-recommendation/custom-query/
> data/src/main/scala/org/template/recommendation/ImportDataScript.scala
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Streams version 0.3-incubating

[Suneel Marthi]

+1 binding

Checked:

1. Signatures and hashes are correct
2. Compiles from source
3. Verified Apache headers
4. License and Notice files are good


On Fri, Sep 30, 2016 at 1:13 AM,  wrote:

> Hi,
>
> +1 binding
>
> Everything checked as pre previous email.
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Request to join Apache Streams (Incubating) as Mentor

[Suneel Marthi]

Re: [VOTE] Retire Apache Streams to the attic

[Suneel Marthi]

I am sorry to be reading this, but I was at Steve Blackmon's talk last week
in Berlin at Flink forward about using Streams +  Flink.

It was a very interesting talk and I chatted with Steve briefly about the
Streams project.

Is there absolutely no chance of reviving this project or giving the
project some more time before calling the attic ?




On Mon, Sep 19, 2016 at 4:58 PM, Ate Douma  wrote:

> On 2016-09-19 16:33, Ate Douma wrote:
>
>> On 2016-09-19 15:44, John D. Ament wrote:
>>
>>> Ate,
>>>
>>> Please also note the instructions from the incubator's retirement guide.
>>>
>>> http://incubator.apache.org/guides/retirement.html
>>>
>>
>> Right.
>> Thanks for pointing this out John.
>>
>> I've never before had to handle a podling retirement and overlooked this
>> requires different handling from a TLP retirement.
>> And with slightly different consequences, e.g. website will be taken down,
>> instead of flagged as being retired.
>>
>> So, to do this proper, I'll first cancel the vote thread on dev@streams
>> and open a new [FINAL][DISCUSS] thread for retirement again, this
>> time also pointing to the podling retirement page.
>> This way at least everyone on that list will have a proper notice what
>> the retirement entails.
>> (not that I expect a different outcome, but there is no rush either)
>>
>
> Reading the podling retirement guide a bit more thoroughly, I think I it is
> sufficient to restart the [VOTE] thread for retirement on dev@streams
> with the
> link to the podling retirement guide.
>
>
>
>> And after that I'll open the final [VOTE] for retirement here on general@
>>
>> Ate
>>
>>
>>> John
>>>
>>> On Mon, Sep 19, 2016 at 6:37 AM Ate Douma  wrote:
>>>
>>> FYI, I've started below vote to retire Apache Streams, after I first
 initiated a
 [discuss] thread more than a week ago, which resulted in zero feedback.

 Ate
 (Streams mentor)

  Forwarded Message 
 Subject: [VOTE] Retire Apache Streams to the attic
 Date: Sun, 18 Sep 2016 23:27:11 +0200
 From: Ate Douma 
 To: d...@streams.incubator.apache.org 

 As a final follow up on the earlier [discuss] thread, lets formally
 vote on
 retiring Apache Streams and move it to the attic.

 The process is described at http://attic.apache.org/process.html

 [ ] +1 Move Streams to the Attic
 [ ] ±0 Proceed according to the majority
 [ ] -1 Do not move Streams to the Attic, because... [please add
 justification]

 Ate



 -
 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] Apache Pirk 0.1.0-incubating Release

[Suneel Marthi]

+1 binding

1. License, Disclaimer, Notice look good
2. Compiled source and all tests pass
3. Verified MD5 , SHA1 sigs of artifacts
4. RAT checks pass

On Fri, Aug 26, 2016 at 8:02 PM, Justin Mclean 
wrote:

> Hi,
>
> +1 binding
>
> I checked:
> - name included incubating
> - signature and hashes good
> - DISCLAIMER exists
> - LICENSE and NOTICE good
> - No unexpected binary files in release
> - Can compile from source
>
> I noticed you’ve dropped “apache” from the release artefact names, IMO
> it’s good to keep it for branding reasons.
>
> In the export section of the README I’m little confused. The text mentions
> the JCA  (and there’s a couple of java.security classes imported in the
> code) and has a link to the oracle website [1] but fails to mention the
> bundled cryptographic code [2] or include a link to the relevant Apache
> page. Also out of interest where did [2] original come from?
>
> Thanks,
> Justin
>
> 1. http://www.oracle.com/us/products/export/eccn-matrix-345817.html
> 2. ./src/main/java/org/apache/pirk/encryption/Paillier.java
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Pirk 0.1.0-incubating Release

[Suneel Marthi]

Posting my vote from dev@ here

+1 binding

On Wed, Aug 24, 2016 at 1:16 PM, Ellison Anne Williams <
eawilliamsp...@gmail.com> wrote:

> Hi All,
>
> The PPMC vote for the Apache Pirk 0.1.0-incubating release has passed; it
> is
> a source-only release (no binary artifacts). We kindly request that the
> IPMC now vote on the release.
>
> The PPMC vote thread is located here:
> https://lists.apache.org/thread.html/f9321c1ce45c4f696639ecac2eac6a
> cdcfbff6a669281941c9c06742@%3Cdev.pirk.apache.org%3E
>
> The artifacts can be downloaded here: https://repository.apache.org/
> content/
> repositories/orgapachepirk-1002
>
> The artifacts have been signed with key 1FD8849B found in the KEYS file:
> https://dist.apache.org/repos/dist/dev/incubator/pirk/KEYS
>
> All JIRAs completed for this release are tagged with 'FixVersion = 0.1.0'.
> You can view the release notes here: https://issues.apache.
> org/jira/secure/ReleaseNote.jspa?projectId=12320320&version=12338109
>
> Please vote accordingly:
>
> [ ] +1, accept as the official Apache Pirk 0.1.0-incubating release
> [ ] -1, do not accept as the official Apache Pirk 0.1.0-incubating release
>  because...
>
> The vote will run for at least 72 hours.
>
> Thanks!
>
> Ellison Anne
>

Re: [VOTE] Release Apache Ranger 0.6.1 (incubating) - rc2

[Suneel Marthi]

+1 (binding)

1.Verified the MD5 and SHA1 sums
2. Ran a clean build, tests on src tar and all tests pass

On Tue, Aug 16, 2016 at 6:05 PM, Alan Gates  wrote:

> Forwarding my +1 from the dev list.
>
> Alan.
>
> > On Aug 16, 2016, at 15:05, Selvamohan Neethiraj 
> wrote:
> >
> > Incubator PMC:
> >
> > Apache Ranger community has voted on and approved a proposal to release
> Apache Ranger 0.6.1 (incubating).
> > [VOTE RESULT] thread from dev community:
> > - https://lists.apache.org/thread.html/53bc84b26d76bb76a1c4375172fb43
> c5335865d82d4eead3ad374993@%3Cdev.ranger.apache.org%3E
> > - https://lists.apache.org/thread.html/02daa7ebce5588e170eb6fdf747a6d
> f52dadc1dfe8aee4dcd6260d2b@%3Cdev.ranger.apache.org%3E
> >
> >
> > Apache ranger-0.6.1-rc2 release candidate is now available with the
> following artifacts up for IPMC vote.
> > I kindly request that the Incubator PMC members to review and vote on
> this incubator release.
> >
> > Release (Source) Information:
> > Git tag for the release:
> >  https://github.com/apache/incubator-ranger/commits/ranger-0.6.1-rc2
> (last commit id :  428f1207e694e9d2648ddaeddd2b0cea79d765ea)
> > Sources for the release:
> >   https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.
> 1-incubating-rc2/apache-ranger-incubating-0.6.1.tar.gz
> >
> > Source release verification:
> > PGP Signature:
> >https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.
> 1-incubating-rc2/apache-ranger-incubating-0.6.1.tar.gz.asc
> > MD5/SHA  Hash:
> >   https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.
> 1-incubating-rc2/apache-ranger-incubating-0.6.1.tar.gz.mds
> > Keys to verify the signature of the release artifact are available at:
> >   https://people.apache.org/keys/group/ranger.asc
> > Build verification steps can be found at:
> >http://ranger.incubator.apache.org/quick_start_guide.html
> >
> >
> > Release Notes:
> >https://cwiki.apache.org/confluence/display/RANGER/
> Apache+Ranger+0.6.1+-+Release+Notes
> >
> >
> > The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >
> > Here is my +1 (non binding).
> >
> > Thank you,
> > Selva-
> >
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept ARIA-TOSCA into the Apache Incubator

[Suneel Marthi]

ttract
> > more diversity to the core team.
> > For ARIA community to thrive and success It is important to plug into
> > dependent communities that consumes ARIA(such as Cloudify, Open-O and
> > others) encourage and facilitate discussions and joint contributions.
> >
> > ===  Core Developers ===
> > Lior Mizrahi, Tal Liron, Maxim Orlov, Ran Ziv.
> > New core developers (initial committers) for the ARIA project are welcome
> > to join the community by code contributions, broad involvement in the
> > community through code reviews, mailing lists and IRC.
> >
> > === Alignment ===
> > Project ARIA’s main goal is to become a healthy, neutral, open-governance
> > open-source project, we strongly believe that the Apache Software
> > Foundation provides the most substantial framework to achieve such
> > community.
> > === Known Risks ===
> >  Orphaned products 
> > Starting from ARIA’s first release is the core orchestration library in
> > Cloudify, commercially offered by GigaSpaces. There’s a strong commitment
> > by GigaSpaces to keep a leadership role in the ARIA community, to
> maintain
> > and advance the project.
> >  Inexperience with Open Source 
> > The team behind ARIA has vast experience in many open source communities,
> > and has been working on Cloudify, an open source project of it’s own
> since
> > 2013. All development is  in public on GitHub, backed up by mailing lists
> > on Google groups and IRC. The team of committers are committed to the
> > principles of open source, and count amongst their number existing Apache
> > committers.
> >
> >
> >  Homogenous Developers 
> > The initial list of committers includes developers from several different
> > geographically distributed locations, spanning across the U.S and
> > Europe,they are experienced with working in a distributed environment.
> >
> >  Reliance on Salaried Developers 
> > The initial committers are affiliated with GigaSpaces. The majority of
> the
> > commits to the project to date have been GigaSpaces employees in the line
> > of their work.
> > Our community is growing, and we hope to grow the community significantly
> > and bring more diversity into the list of committers.
> >
> >  Relationships with Other Apache Products 
> >
> > === A Excessive Fascination with the Apache Brand ===
> >
> >
> > While we expect the Apache brand may help attract more contributors, our
> > interests in starting this project under the Apache Software Foundation
> is
> > build a neutral community consisted of users, developers and vendors
> alike.
> > We feel that the Apache Software Foundation is the natural home for such
> a
> > community.
> > We will be sensitive to inadvertent abuse of the Apache brand and will
> work
> > with the Incubator PMC and the PRC to ensure the brand policies are
> > respected.
> >
> > === Documentation ===
> > www.ARIATOSCA.org
> > Complete project documentation is being planned for upcoming releases.
> >
> > === Initial Source ===
> > The initial source of ARIA 0.1  is based on Cloudify 3.4 mature code
> base.
> > Reaching to ARIA 1.0 release after refactoring to make ARIA easily
> > consumable library(and corresponding Cloudify 3.5 release which consumes
> > ARIA as the Orchestration Kernel) all core orchestration capabilities are
> > developed in ARIA.
> >
> > === Source and Intellectual Property Submission Plan ===
> >
> > The code is licensed under Apache License V2, and all contributions are
> > subject to an Apache-style ICLA. In addition to the code, there is a logo
> > currently used for the project which would be contributed to the ASF. The
> > PPMC will work with GigaSpaces and project's stakeholders in order to
> > identify additional properties and donate them to the Apache Foundation.
> > There are also a number of other assets related to the project, such as
> > its domain name, Twitter account, and IRC channel. During incubation the
> > PPMC will identify all these assets, and arrange the transfer,
> replacement,
> > or deprecation of these assets as appropriate.
> >
> >
> > === External Dependencies ===
> > The dependencies all have Apache compatible licenses. These include BSD,
> > CDDL, CPL, MPL and MIT licensed dependencies.
> >
> > === Cryptography ===
> >
> > === Required Resources ===
> >
> >  Mailing lists 
> > We seek "ARIA-Dev" and "ARIA-User" lists to replace the lists currently
> in
> > use. In alignment with Apache's standard practices, we would also have a
> > "ARIA-Private" list for the PMC members.
> >
> >  Source Control 
> > We would require a Git repository named "ARIA-TOSCA" to hold the ARIA
> > source code, and "ARIA-SITE" to hold the web site source code. We would
> > like these to be mirrored to GitHub repositories, where we intend to
> follow
> > the same model currently used by Apache projects.
> >
> >  Issue Tracking 
> > Jira, with a project name of "ARIA-TOSCA".
> >
> > === Initial Committers ===
> > Lior Mizrahi
> >
> > Ran Ziv
> >
> > Maxim Orlov
> >
> > Tal Liron
> >
> > Dan Kilman
> >
> > Idan Moyal
> >
> > Nir Biran
> >
> > Avia Efrat
> >
> > Adam Levin
> >
> > Lukasz Maksymczuk
> >
> > Arthur Berezin
> >
> >
> >
> > == Affiliations ==
> > The majority of the commits to the project so far have been made by
> > people who were employees of GigaSpaces at the time of the contribution,
> > and the vast majority of those commits were in the line of their
> > employment. All named initial committers are employees of GigaSpaces.
> > As stated in the Known Risks section, we appreciate that this cannot
> > continue long term, and a key goal of the podling will be to encourage
> > people not affiliated with GigaSpaces to join the project as committers
> and
> > PMC members.
> >
> > == Sponsors ==
> >
> > === Champion ===
> > Suneel Marthi
> >
> > === Nominated Mentors ===
> > Jakob Homan
> >
> > John D. Ament
> >
> > Suneel Marthi
> >
> > === Sponsoring Entity ===
> > We request sponsorship from the Incubator PMC.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: ARIA TOSCA Project Proposal

[Suneel Marthi]

All,

Any feedback on this proposal? If not, I would like to start a Voting
thread soon.

Suneel

On Thu, Aug 4, 2016 at 10:47 AM, Arthur Berezin 
wrote:

> Hi All
>
>
> I would like to propose ARIA TOSCA to be an Apache Incubator Project.
>
> ARIA TOSCA project offers an easily consumable Software Development
> Kit(SDK) and a Command Line Interface(CLI) to implement TOSCA(Topology and
> Orchestration Specification of Cloud Applications) based solutions which
> will help in driving adoption of TOSCA, and help in market consolidation
> around TOSCA based Orchestration.
>
> One of the key attributes of the TOSCA specification by OASIS is that it is
> a vendor neutral and technology agnostic specification, allowing to
> describe applications and then to orchestrate them using various
> technologies of choice, such as Amazon AWS, Google GCP, OpenStack, VMware,
> Puppet, Ansible Chef, etc’. The reality is such that TOSCA is a complex
> specification,making software vendors trying to implement the specification
> make implementation decisions, ending up with different and incompatible
> implementations, creating even more market segmentation instead of
> consolidating around a single standard for orchestration.
>
> ARIA a vendor neutral and technology agnostic(via plugins mechanism)
> reference implementation of the TOSCA specification. It is an open source
> python library that helps orchestrators and management tools in developing
> TOSCA enabled solutions. ARIA aims to become the main reference
> implementation of the OASIS TOSCA(Topology and Orchestration Specification
> for Cloud Applications) specification for orchestrating cloud applications.
>
> ARIA TOSCA targets NFV Orchestration and Hybrid/Multi Cloud orchestration
> as main use-cases it solves.
>
> ARIA can be executed via CLI to orchestrate application templates,
> additionally it allows embedding its python library for creating TOSCA
> compatible services, and includes rich set of plugins for Iaas
> orchestration, such as Amazon AWS, Google GCP, OpenStack and VMWare; It
> Includes plugins for Container orchestration, with Docker and Kubernetes
> plugins, configuration management tools(Puppet,Chef, Ansible) and a rich
> API that allows to create plugins for any new technology.
>
> ARIA also serves as a codebase that allows to test the TOSCA specification,
> and experiment with new approaches of modeling and orchestration of
> applications, providing feedback and real world use cases OASIS to further
> refine and advance the standard specification.
>
> Please find the full project proposal here:
> https://wiki.apache.org/incubator/AriaProposal
>
> *Champion:*
> Suneel Marthi
>
> *Nominated Mentors*
> Jakob Homan
> John D. Ament
> Suneel Marthi
>
>
>
>
> Thank You,
> Arthur Berezin
>

Re: Mentors and Champion for Aria Proposal

[Suneel Marthi]

Please sign me up as mentor.

On Fri, Jul 22, 2016 at 1:38 PM, John D. Ament 
wrote:

> All,
>
> The Aria Proposal needs your help.  The team behind it is in need of both
> champion and mentors to help out drive the community.
>
> https://wiki.apache.org/incubator/AriaProposal
>
> Its a great initiative to drive cloud computing forward and standardize a
> lot of tools in use.
>
> John
>

Re: [VOTE] Accept DistributedLog into the Apache Incubator

[Suneel Marthi]

+1 (binding)

On Tue, Jun 21, 2016 at 1:11 AM, Sijie Guo  wrote:

> Hello All,
>
> Following the discussion thread, I would like to call a VOTE on accepting
> DistributedLog into the Apache Incubator.
>
> [] +1 Accept DistributedLog into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept DistributedLog into the Apache Incubator because ...
>
> This vote will be open for at least 72 hours.
>
> The proposal follows, you can also access the wiki page:
> https://wiki.apache.org/incubator/DistributedLogProposal
>
> Here is my +1.
>
> Thanks,
> Sijie
>
> = Abstract =
> DistributedLog is a high-performance replicated log service. It offers
> durability, replication and strong consistency, which provides a
> fundamental building block for building reliable distributed systems, e.g
> replicated-state-machines, general pub/sub systems, distributed databases,
> distributed queues and etc.
>
> See “Building Distributedlog - Twitter’s high performance replicated log
> service” for details:
>
> https://blog.twitter.com/2015/building-distributedlog-twitter-s-high-performance-replicated-log-service
>
> = Proposal =
> We propose to contribute DistributedLog codebase and associated artifacts
> (e.g. documentation, web-site content etc.) to the Apache Software
> Foundation with the intent of forming a productive, meritocratic and open
> community around DistributedLog’s continued development, according to the
> ‘Apache Way’.
>
> = Background =
> Engineers at Twitter began developing DistributedLog in early 2013.
> DistributedLog is described in a Twitter engineering blog post and
> presented at the Messaging Meetup in Sep 2015. It has been released as an
> Apache-licensed open-source project on GitHub in May 2016.
>
> DistributedLog is a high-performance replicated log service, which provides
> simple stream-oriented abstractions over log-segments and offers
> durability, replication and strong consistency for building reliable
> distributed systems. The features offered by DistributedLog includes:
>
>  * Simple high-level, stream oriented interface
>  * Naming and metadata scheme for managing streams and other entities
>  * Log data management policies, include data segmentation and data
> retention
>  * Fast write pipeline leveraging batching and compression
>  * Fast read mechanism leveraging long-poll and read-ahead caching
>  * Service tiers supporting writer fan-in and reader fan-out
>  * Geo-replicated logs
>
> DistributedLog’s most important benefit is high-performance with a strong
> durability guarantee, making it extremely appropriate for running different
> workloads from distributed database journaling to real-time stream
> computing. Its modern, layered architecture makes it easy to run the
> service tiers in multi-tenant datacenter environments such as Apache Mesos
> or cloud environments such as EC2.
>
> = Rationale =
> DistributedLog is designed to provide core fundamental features like
> high-performance, durability and strong consistency to anyone who is
> building reliable distributed systems, in a simple and efficient way.
>
> We believe that the ASF is the right venue to foster an open-source
> community around DistributedLog’s development. We expect that
> DistributedLog will benefit from collaboration with related Apache
> projects, and under the auspices of the ASF will attract talented
> contributors who will push DistributedLog’s development forward at a faster
> pace.
>
> We believe that the timing is right for DistributedLog’s development to
> move to the ASF: DistributedLog has already run in production at Twitter
> for 3 years and served various workloads including a distributed database
> journal, reliable cross datacenter replication, search ingestion,
> andgeneral pub/sub messaging. The project is stable. We are excited to see
> where an ASF-based community can take DistributedLog.
>
> = Current Status =
> DistributedLog is a stable project that has been used in production at
> Twitter for 3 years. The source code is public at github.com/twitter,
> which
> will seed the Apache git repository.
>
> = Meritocracy =
> We understand the central importance of meritocracy to the Apache Way. We
> will work to establish a welcoming, fair and meritocratic community.
> Several companies have already expressed interest in this project, and we
> intend to invite additional developers to participate. We look forward to
> growing a rich user and developer community.
>
> = Community =
> There is a large need for a performant replicated log service for
> applications such as distributed databases, distributed transactional
> systems, replicated-state-machines and pub/sub messaging/queuing. We want
> to attract more developers to the project, and we believe that the ASF’s
> open and meritocratic philosophy will help us with this. We note the
> success of other similar projects already part of the ASF, like Kafka.
>
> = Core Developers =
> DistributedLog is actively developed within Twitter. Most of t

Re: [VOTE] Accept Pirk into the Apache Incubator

[Suneel Marthi]

Products
> >
> > Risk of orphaning is limited though it is important to grow the
> community.
> > The project user and developer base is growing and there is already
> > operational use of Pirk.
> >
> > Inexperience with Open Source
> >
> > The initial committers to Pirk have limited experience with true open
> > source software development. However, despite the project origins being
> > from closed source development we have modeled our behavior and community
> > development on The Apache Way to the greatest extent possible. We are
> > committed to the ideals of open source software and will eagerly seek out
> > mentors and sponsors who can help us quickly come up to speed.
> >
> > Homogenous Developers
> >
> > The initial committers of Pirk come from a limited set of entities though
> > we are committed to recruiting and developing additional committers from
> a
> > broad spectrum of industries and backgrounds.
> >
> > Reliance on Salaried Developers
> >
> > We expect Pirk development to continue on salaried time and through
> > volunteer time. The majority of initial committers are paid by their
> > employers to contribute to this project. We are committed to developing
> and
> > recruiting participation from developers both salaried and non-salaried.
> >
> > Relationship with other Apache Projects
> >
> > As described in the alignment section, Pirk is already heavily dependent
> on
> > other ASF projects and we anticipate further dependence and integration
> > with new and emerging projects in the Apache family.
> >
> > An Excessive Fascination with the Apache Brand
> >
> > We respect the Apache brand and desire to adopt its community building
> > principles. Our desire is to build and foster an open source community
> > around scalable, robust PIR which aligns with the Apache tenets. Further,
> > Apache is a natural home for Pirk given our existing dependencies and
> > alignment with ASF projects.
> >
> > Documentation
> >
> > At this time there is no Pirk documentation on the web. However, we have
> > documentation included within the application that details usage. Using
> > incubator infrastructure we will be rapidly expanding the available
> > documentation to cover things like installation, developer guide,
> > frequently asked questions, best practices, and more.
> >
> > Initial Source
> >
> > The core codebase is written in Java and includes detailed Javadocs and
> > feature documentation.
> >
> > Source and Intellectual Property Submission
> >
> > The Pirk code and documentation materials will be submitted by the
> National
> > Security Agency. Pirk has been developed by government employees.
> Material
> > developed by the government employees is in the public domain and no U.S.
> > copyright exists in works of the federal government. NSA has submitted
> > Corporate Contributor License Agreement to the Apache Software
> Foundation;
> > the Software Grant Agreement is forth coming.
> >
> > External Dependencies
> >
> > We believe all current dependencies are compatible with the ASF
> guidelines.
> > Our dependency licenses come from the Apache v 2.0 and Eclipse Public v1.
> >
> > Cryptography
> >
> > Consistent with http://www.apache.org/licenses/exports/ we believe Pirk
> is
> > classified as ECCN 5D002. In the event that it becomes necessary we will
> > engage with appropriate Apache members to ensure we file any necessary
> > paperwork or clarified any cryptographic export license concerns.
> >
> > Required Resources
> >
> > Mailing Lists
> >
> > d...@pirk.incubator.apache.org
> >
> > priv...@pirk.incubator.apache.org
> >
> > comm...@pirk.incubator.apache.org
> >
> > Source Control
> >
> > Pirk requests use of Git for source control (git://
> git.apache.org/pirk.git
> > ).
> > We request a writeable Git repo for Pirk with mirroring to be setup to
> > Github through INFRA.
> >
> > Issue Tracking
> >
> > JIRA Pirk (PIRK)
> >
> > Initial Committers
> >
> > Tracy Brown , CLA submitted
> >
> > Christopher Harris , CLA submitted
> >
> > Walter Ray-Dulaney , CLA submitted
> >
> > Jacob Wilder , CLA submitted
> >
> > Ellison Anne Williams , CLA
> confirmed
> >
> > Joe Witt , CLA confirmed
> >
> > Sponsors
> >
> > Champion
> >
> > Billie Rinaldi , IPMC Member
> >
> > Nominated Mentors
> >
> > Billie Rinaldi , IPMC Member
> >
> > Joe Witt , IPMC Member
> >
> > Josh Elser , IPMC Member
> >
> > Suneel Marthi , IPMC Member
> >
> > Tim Ellison , Apache Member
> >
> > Sponsoring Entity
> >
> > We request the Apache Incubator to sponsor this project.
> >
>

Re: Requesting write access to the incubator wiki for TimEllison

[Suneel Marthi]

smarthi

On Wed, Jun 8, 2016 at 11:10 AM, John D. Ament 
wrote:

> What is your username?
>
> On Wed, Jun 8, 2016 at 11:06 AM Suneel Marthi  wrote:
>
> > Please add my name to that list too, didn't realize I wasn't there.
> >
> > On Wed, Jun 8, 2016 at 11:02 AM, John D. Ament 
> > wrote:
> >
> > > Done! Happy editing.
> > >
> > > (ps - hope you saw my other mail)
> > >
> > > John
> > >
> > > On Wed, Jun 8, 2016 at 11:01 AM Tim Ellison 
> > wrote:
> > >
> > > > Please would an administrator add TimEllison to the incubator wiki
> > > > contributors group?
> > > >
> > > > Thanks,
> > > > Tim
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
>

Re: Requesting write access to the incubator wiki for TimEllison

[Suneel Marthi]

Please add my name to that list too, didn't realize I wasn't there.

On Wed, Jun 8, 2016 at 11:02 AM, John D. Ament 
wrote:

> Done! Happy editing.
>
> (ps - hope you saw my other mail)
>
> John
>
> On Wed, Jun 8, 2016 at 11:01 AM Tim Ellison  wrote:
>
> > Please would an administrator add TimEllison to the incubator wiki
> > contributors group?
> >
> > Thanks,
> > Tim
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] Pirk Incubation Proposal

[Suneel Marthi]

If looking for mentors, I would be glad to jump in and I have no real
organizational affiliation.

On Tue, Jun 7, 2016 at 12:54 PM, Josh Elser  wrote:

> Completely understand where you're coming from, Henry, and thanks for
> keeping us honest.
>
> I'll echo Joe's sentiment that I volunteered to mentor, not due to any
> affiliation or interest at my dayjob, but instead my social network
> connecting me with the project and a personal desire to help make this a
> success. My affiliation is purely something following me around.
>
> At the risk of putting words into Ellison Anne's mouth: I think we would
> be happy to receive mentors from other affiliations. I feel pretty safe
> saying that 3 mentors from Hortonworks was completely circumstantial, but
> it is by no means meant to be interpreted as no other mentors are desired.
> If anyone else is interested in volunteering, that would be great.
>
>
> Henry Saputra wrote:
>
>> HI Joe,
>>
>> Thanks for your reply.
>>
>> Technically, that is what ALL mentors suppose to do. Wear different hats
>> when representing as Apache member.
>>
>> But we all know that is not how it happens in reality. Most people
>> nowadays
>> get paid to do open source by day employer so like it or not some
>> influence
>> of the employer will take effect.
>>
>> I would encourage do bit more homework in terms finding mentors. Others
>> new
>> podlings such as Eagle, CarbonData, and Kudu had done extra effort to find
>> mentors from different orgs.
>>
>> Hope this helps.
>>
>> - Henry
>>
>> On Tue, Jun 7, 2016 at 9:37 AM, Joe Witt  wrote:
>>
>> Henry
>>>
>>> I totally understand the spirit of your statement but I want to be
>>> clear in speaking for my own involvement here.  I am participating in
>>> this proposal and proposed podling as an apache member.  That I happen
>>> to work for hortonworks has absolutely nothing to do with it and
>>> frankly I wish it was not called out in this document.  The template
>>> even calls this out as a controversial item.
>>>
>>> I believe I am the only one on the initial committers list that is
>>> affiliated with hortonworks for what it is worth.
>>>
>>> Thanks
>>> Joe
>>>
>>> On Tue, Jun 7, 2016 at 12:27 PM, Henry Saputra
>>> wrote:
>>>
 One immediate concern is all mentors coming from Hortonworks.

 I would strongly suggest to find more balance mentors.

 I know we had this discussion about "fake" diversity stuff, but I

>>> strongly
>>>
 advise to do more effort to get mentors from different background than

>>> one
>>>
 company.


 - Henry


 On Tuesday, June 7, 2016, Ellison Anne Williams<

>>> eawilliamsp...@gmail.com>
>>>
 wrote:

 Hi All,
>
>
> We would like to discuss the proposal of a new project to the incubator
>
 -
>>>
 Pirk.
>
>
> Pirk is a framework for scalable Private Information Retrieval (PIR).
>
>
> The proposal is contained below and can also be found on the wiki at
> https://wiki.apache.org/incubator/PirkProposal
>
>
> Looking forward to the discussion -
>
>
> Thanks!
>
>
> Ellison Anne
>
>
> 
>
>
> = Pirk Proposal =
>
> == Abstract ==
> Pirk is a framework for scalable Private Information Retrieval (PIR).
>
> == Proposal ==
>
> Pirk is a software framework for scalable Private Information Retrieval
>
 and
>>>
 is meant to provide a landing place for robust, scalable, and practical
> implementations of PIR algorithms. The initial scalable PIR algorithms
>
 of
>>>
 Pirk were developed at the National Security Agency.
>
> == Background ==
>
> Private Information Retrieval (PIR) is an area of computer science and
> mathematics that enables a user/entity to privately and securely obtain
> information from a dataset, to which they have been granted access,
>
 without
>>>
 revealing, to the dataset owner or to an observer, any information
> regarding the questions asked or the results obtained. Employing
> homomorphic encryption techniques, PIR enables datasets to remain
>
 resident
>>>
 in their native locations while giving the ability to query the datasets
> with sensitive terms.
>
> == Rationale ==
>
> Although PIR has been in existence for over twenty years, it has
> largely
> remained an academic discipline with very little robust or scalable
> implementation. Pirk not only provides implementations of novel
> scalable
> PIR algorithms, but it provides a framework into which robust,
> scalable,
> and practical PIR may be developed.
>
> Pirk fits well within the Apache Software Foundation (ASF) family as it
> depends on numerous ASF projects and integrates with several others
>
 such as
>>>
 Hadoop and Spark. We also anticipate developing extensions/adapt

Re: Joe Witt joins the Incubator PMC

[Suneel Marthi]

Welcome Joe!!

On Tue, Jun 7, 2016 at 12:22 PM, Seetharam Venkatesh <
venkat...@innerzeal.com> wrote:

> Welcome aboard, Joe.
>
> On Mon, Jun 6, 2016 at 11:44 PM Sergio Fernández 
> wrote:
>
> > Welcome, Joe!
> >
> > On Tue, Jun 7, 2016 at 4:03 AM, Joe Witt  wrote:
> >
> > > Thank you all.  Very happy to be able to help and give back to new
> > > communities forming in the incubator.  I know I benefited greatly from
> > > the mentors we had during incubation and definitely feel like I need
> > > to return the favor.
> > >
> > > I can definitely not be as awesome as Justin is with licensing/release
> > > review diligence but I can sure try to help take the edge off!
> > >
> > > On Mon, Jun 6, 2016 at 9:53 PM, Martin Gainty 
> > wrote:
> > > > Welcome Joseph!
> > > >
> > > > Martin
> > > >
> > > >
> > > >
> > > >> From: mar...@rectangular.com
> > > >> Date: Mon, 6 Jun 2016 12:48:35 -0700
> > > >> Subject: Joe Witt joins the Incubator PMC
> > > >> To: general@incubator.apache.org
> > > >>
> > > >> Greets,
> > > >>
> > > >> I'm pleased to announce that Apache Member Joe Witt has joined the
> > > >> Incubator PMC!
> > > >>
> > > >> Joe is a core contributor to Apache NiFi, and is currently the
> > > >> project's PMC Chair.  Joe knows the Incubator from NiFi's trip
> through
> > > >> it -- we look forward to him returning to contribute as a member of
> > > >> the IPMC!
> > > >>
> > > >> Marvin Humphrey, on behalf of the IPMC
> > > >>
> > > >>
> -
> > > >> 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
> > >
> > >
> >
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e: sergio.fernan...@redlink.co
> > w: http://redlink.co
> >
>

Re: [DICSUSS] Graduation of Apache Twill as Top Level Project

[Suneel Marthi]

+1 binding

On Wed, Jun 1, 2016 at 1:24 PM, Henry Saputra 
wrote:

> Hi All,
>
> The Apache Twill PPMCs and the community had discussed and voted to
> graduate to become Apache TLP.
>
> It is a small but welcoming community, and the mentors and rest of PPMCs
> believe that we have satisfied the learning phase during our incubation
> period.
>
> The community has made several good releases and added new PPMC during its
> time in incubator [1]
>
> It also has been used by external project such as Cask Data CDAP [2] and
> Apache Fluo [3]
>
> The PPMCs also have made some presentations in conferences and meetups to
> be open and inclusive [4] [5]
>
>
> Here is the link to the VOTE:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6ZB1DZVWZJNd+-ib0NXZwyWebSBE0evs0Yp8uthe+=o...@mail.gmail.com%3e
>
>
> Here is link to the VOTE result summary:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6aSYs=daVpeeYO0GPKdfu=dkhvyhw12jdj66-dpzsq...@mail.gmail.com%3e
>
> Thanks,
>
> - Henry
> On behalf of Apache Twill PPMC
>
>
> [1] http://incubator.apache.org/projects/twill.html
> [2] http://cdap.io
> [3] https://wiki.apache.org/incubator/FluoProposal
> [4]
>
> http://apacheconnorthamerica2014.sched.org/event/1fhOZ6T/harnessing-the-power-of-yarn-with-apache-twill
> [5]
>
> http://apachebigdata2016.sched.org/event/6Lzt/building-large-scale-applications-in-apache-hadoop-yarn-with-apache-twill-henry-saputra-terence-yim-apache-software-foundation?iframe=no&w=&sidebar=yes&bg=no
>
> ## Resolution to create a TLP from graduating Incubator podling
>
>
> X. Establish the Apache Twill 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 set of libraries to provide
> abstraction
>
>to develop distributed applications such as with Apache Hadoop YARN.
>
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>
>Committee (PMC), to be known as the "Apache Twill Project",
>
>be and hereby is established pursuant to Bylaws of the
>
>Foundation; and be it further
>
>
>RESOLVED, that the Apache Twill Project be and hereby is
>
>responsible for the creation and maintenance of software
>
>related to providing a set of libraries to provide abstraction
> to develop
>
>distributed applications such as with Apache Hadoop YARN
>
>and be it further
>
>
>RESOLVED, that the office of "Vice President, Apache Twill" 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 Twill Project, and to have primary responsibility
>
>for management of the projects within the scope of
>
>responsibility of the Apache Twill 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 Twill Project:
>
>
>  * Terence Yim 
>
>  * Andreas Neumann 
>
>  * Gary Helmling 
>
>  * Albert Shau 
>
>  * Poorna Chandra 
>
>  * Henry Saputra 
>
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Terence Yim
>
>be appointed to the office of Vice President, Apache Twill, 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 Twill PMC be and hereby is
>
>tasked with the creation of a set of bylaws intended to
>
>encourage open development and increased participation in the
>
>Apache Twill Project; and be it further
>
>
>RESOLVED, that the Apache Twill Project be and hereby
>
>is tasked with the migration and rationalization of the Apache
>
>Incubator Twill podling; and be it further
>
>
>RESOLVED, that all responsibilities pertaining to the Apache
>
>Incubator Twill podling encumbered upon the Apache Incubator
>
>Project are hereafter discharged.
>

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[Suneel Marthi]

; all transitive dependencies to verify this information and introduce
> > license checking into the build and release process by integrating with
> > Apache RAT.
> >
> > Cryptography
> >
> > PredictionIO does not include cryptographic code. We utilize standard
> > JCE and JSSE APIs provided by the Java Runtime Environment.
> >
> > Required Resources
> >
> > We request that following resources be created for the project to use
> >
> > Mailing lists
> >
> >   predictionio-priv...@incubator.apache.org (with moderated
> subscriptions)
> >   predictionio-dev
> >   predictionio-user
> >   predictionio-commits
> >
> >   We will migrate the existing PredictionIO mailing lists.
> >
> > Git repository
> >
> >   The PredictionIO team would like to use Git for source control, due to
> > our
> >   current use of GitHub.
> >
> >   git://git.apache.org/incubator-predictionio
> >
> > Documentation
> >
> >   https://predictionio.incubator.apache.org/docs/
> >
> > JIRA instance
> >
> >   PredictionIO currently uses the GitHub issue tracking system associated
> >   with its repository:
> https://github.com/PredictionIO/PredictionIO/issues
> > .
> >   We will migrate to Apache JIRA.
> >
> >   JIRA PREDICTIONIO
> >   https://issues.apache.org/jira/browse/PREDICTIONIO
> >
> > Other Resources
> >
> >   TravisCI for builds and test running.
> >
> >   PredictionIO's documentation, included in the code repo (docs/manual
> >   directory), is built with Middleman and publicly hosted at
> >   https://docs.prediction.io
> >
> >   A blog to drive adoption and excitement at https://blog.prediction.io
> >
> > Initial Committers
> >
> >   Pat Ferrell
> >   Tamas Jambor
> >   Justin Yip
> >   Xusen Yin
> >   Lee Moon Soo
> >   Donald Szeto
> >   Kenneth Chan
> >   Tom Chan
> >   Simon Chan
> >   Marco Vivero
> >   Matthew Tovbin
> >   Yevgeny Khodorkovsky
> >   Felipe Oliveira
> >   Vitaly Gordon
> >   Alex Merritt
> >
> > Affiliations
> >
> >   Pat Ferrell - ActionML
> >   Tamas Jambor - Channel4
> >   Justin Yip - independent
> >   Xusen Yin - USC
> >   Lee Moon Soo - NFLabs
> >   Donald Szeto - Salesforce
> >   Kenneth Chan - Salesforce
> >   Tom Chan - Salesforce
> >   Simon Chan - Salesforce
> >   Marco Vivero - Salesforce
> >   Matthew Tovbin - Salesforce
> >   Yevgeny Khodorkovsky - Salesforce
> >   Felipe Oliveira - Salesforce
> >   Vitaly Gordon - Salesforce
> >   Alex Merritt - ActionML
> >
> > Sponsors
> >
> > Champion
> >
> >   Andrew Purtell 
> >
> > Nominated Mentors
> >
> >   Andrew Purtell 
> >   James Taylor 
> >   Lars Hofhansl 
> >   Suneel Marthi 
> >   Xiangrui Meng 
> >   Luciano Resende 
> >
> > Sponsoring Entity
> >
> >   Apache Incubator PMC
> >
> >
> > --
> > Best regards,
> >
> >- Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

Re: [DISCUSS] PredictionIO incubation proposal

[Suneel Marthi]

The current list is good to go and includes all (both present and former)
PIO folks.
I am fine with going for Voting with the present list.

+1

On Fri, May 20, 2016 at 11:47 AM, Andrew Purtell 
wrote:

> The current list of initial committers was that provided me by the
> PredictionIO folks so I have every reason to believe they all have a stake
> at entering incubation.
>
> It's totally fine with me if we stick to that list. I am just trying to
> facilitate the fairest process possible.
>
>
> On Friday, May 20, 2016, Roman Shaposhnik  wrote:
>
> > On Thu, May 19, 2016 at 9:16 PM, Suneel Marthi  > > wrote:
> > > I definitely have concerns about too many folks becoming initial
> > committers
> > > and bringing their own corporate agendas to this project.
> > >
> > > I suggest that first we vote PIO into incubator then bring in those
> less
> > > experienced with the project. We have a good start with people who have
> > > worked on the project from several orgs. Let us get organized first and
> > > then bring in new people.
> >
> > I think this is a reasonable concern. Andrew, any chance you can look
> over
> > the names of initial committers and let us know who has had a stake in
> the
> > project before entering the incubation vs. those who are trying to join
> in
> > as
> > part of the ASF Incubation.
> >
> > I'm not saying we need to pass judgement one way or the other yet, but it
> > will be a very useful data point to know before voting.
> >
> > Thanks,
> > Roman.
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > 
> > For additional commands, e-mail: general-h...@incubator.apache.org
> > 
> >
> >
>
> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

Re: [DISCUSS] PredictionIO incubation proposal

[Suneel Marthi]

gt; > > PredictionIO has existed as a healthy open source project for almost
> two
> > > years and is the most starred Scala project on GitHub. All of the
> > proposed
> > > committers have contributed to ASF and Linux Foundation open source
> > > projects. Several current committers on Apache projects and Apache
> > Members
> > > are involved in this proposal and intend to provide mentorship.
> > >
> > >  Homogeneous Developers 
> > > The initial list of committers includes developers from several
> > > institutions, including Salesforce, ActionML, Channel4, USC as well as
> > > unaffiliated developers.
> > >
> > >  Reliance on Salaried Developers 
> > > Like most open source projects, PredictionIO receives substantial
> support
> > > from salaried developers. PredictionIO development is partially
> supported
> > > by Salesforce.com, but there are many contributors from various other
> > > companies, and an active mailing list composed of hundreds of users. We
> > > will continue our efforts to ensure stewardship of the project to be
> > > independent of salaried developers by meritocratically promoting those
> > > contributors to committers.
> > >
> > >  Relationships with Other Apache Product 
> > > PredictionIO relies heavily on top level apache projects such as Apache
> > > Spark, HBase and Hadoop. However it brings a distinguished
> functionality,
> > > rather than just an abstraction - Machine Learning in a plug-and-play
> > > fashion.
> > >
> > > Compared to Apache Mahout, which focuses on the development of a wide
> > > variety of algorithms, PredictionIO offers a platform to manage the
> whole
> > > machine learning workflow, including data collection, data preparation,
> > > modeling, deployment and management of predictive services in
> production
> > > environments.
> > >
> > >  An Excessive Fascination with the Apache Brand 
> > > PredictionIO is already a widely known open source project. This
> proposal
> > > is not for the purpose of generating publicity. Rather, the primary
> > > benefits to joining Apache are those outlined in the Rationale section.
> > >
> > > === Documentation ===
> > > PredictionIO boasts rich and live documentation, included in the code
> > repo
> > > (docs/manual directory), is built with Middleman, and publicly hosted
> at
> > > https://docs.prediction.io
> > >
> > > === Initial Source and Intellectual Property Submission Plan ===
> > > Currently, the PredictionIO codebase is distributed under the Apache
> 2.0
> > > License and hosted on GitHub:
> > https://github.com/PredictionIO/PredictionIO
> > >
> > > === External Dependencies ===
> > > PredictionIO has the following external dependencies:
> > >  * Apache Hadoop 2.4.0 (optional, required only if YARN and HDFS are
> > > needed)
> > >  * Apache Spark 1.3.0 for Hadoop 2.4
> > >  * Java SE Development Kit 8
> > >  * and one of the following sets:
> > > ​  ​
> > >* PostgreSQL 9.1
> > >
> > > ​  ​
> > > or
> > >
> > > ​  ​
> > > * MySQL 5.1
> > > ​  ​
> > >  or
> > >
> > > ​  ​
> > >  * Apache HBase 0.98.6
> > >
> > > ​  ​
> > > * Elasticsearch 1.4.0
> > >
> > > Upon acceptance to the incubator, we would begin a thorough analysis of
> > > all transitive dependencies to verify this information and introduce
> > > license checking into the build and release process by integrating with
> > > Apache RAT.
> > >
> > > === Cryptography ===
> > > PredictionIO does not include cryptographic code. We utilize standard
> > > JCE and JSSE APIs provided by the Java Runtime Environment.
> > >
> > > === Required Resources ===
> > > We request that following resources be created for the project to use
> > >
> > >  Mailing lists 
> > >
> > > predictionio-priv...@incubator.apache.org (with moderated
> subscriptions)
> > >
> > > predictionio-dev
> > >
> > > predictionio-user
> > >
> > > predictionio-commits
> > >
> > > We will migrate the existing PredictionIO mailing lists.
> > >
> > >  Git repository 
> > > The PredictionIO team would like to use Git for source control, due to
> > our
> > > current use of GitHub.
> > >
> > > git://git.apache.org/incubator-predictionio
> > >
> > >  Documentation 
> > > https://predictionio.incubator.apache.org/docs/
> > >
> > >  JIRA instance 
> > > PredictionIO currently uses the GitHub issue tracking system associated
> > > with its repository:
> https://github.com/PredictionIO/PredictionIO/issues
> > .
> > > We will migrate to Apache JIRA.
> > >
> > > JIRA PREDICTIONIO
> > > https://issues.apache.org/jira/browse/PREDICTIONIO
> > >
> > >  Other Resources 
> > > * TravisCI for builds and test running.
> > >
> > > * PredictionIO's documentation, included in the code repo (docs/manual
> > > directory), is built with Middleman and publicly hosted
> > > https://docs.prediction.io
> > >
> > > * A blog to drive adoption and excitement at
> https://blog.prediction.io
> > >
> > > === Initial Committers ===
> > >
> > > * Pat Ferrell
> > >
> > > * Tamas Jambor
> > >
> > > * Justin Yip
> > >
> > > * Xusen Yin
> > >
> > > * Lee Moon Soo
> > >
> > > * Donald Szeto
> > >
> > > * Kenneth Chan
> > >
> > > * Tom Chan
> > >
> > > * Simon Chan
> > >
> > > * Marco Vivero
> > >
> > > * Matthew Tovbin
> > >
> > > * Yevgeny Khodorkovsky
> > >
> > > * Felipe Oliveira
> > >
> > > * Vitaly Gordon
> > >
> > > === Affiliations ===
> > >
> > > * Pat Ferrell - ActionML
> > >
> > > * Tamas Jambor - Channel4
> > >
> > > * Justin Yip - independent
> > >
> > > * Xusen Yin - USC
> > >
> > > * Lee Moon Soo - NFLabs
> > >
> > > * Donald Szeto - Salesforce
> > >
> > > * Kenneth Chan - Salesforce
> > >
> > > * Tom Chan - Salesforce
> > >
> > > * Simon Chan - Salesforce
> > >
> > > * Marco Vivero - Salesforce
> > >
> > > * Matthew Tovbin - Salesforce
> > >
> > > * Yevgeny Khodorkovsky - Salesforce
> > >
> > > * Felipe Oliveira - Salesforce
> > >
> > > * Vitaly Gordon - Salesforce
> > >
> > > === Sponsors ===
> > >
> > >  Champion 
> > >
> > > Andrew Purtell 
> > >
> > >  Nominated Mentors 
> > >
> > > * Andrew Purtell 
> > >
> > > * James Taylor 
> > >
> > > * Lars Hofhansl 
> > >
> > > * Suneel Marthi 
> > >
> > > * Xiangrui Meng 
> > >
> > > * Luciano Resende 
> > >
> > >  Sponsoring Entity 
> > >
> > > Apache Incubator PMC
> > >
> >
>
>
>
> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

Re: Looking for a champion (and maybe a mentor)

[Suneel Marthi]

I can volunteer to champion this

Sent from my iPhone

> On May 19, 2016, at 11:13 AM, Daniel Gruno  wrote:
> 
> Hi folks!
> 
> We (a bunch of ASF people and then some) are looking for a champion for
> a new podling proposal called Pony Mail. Unfortunately, the original
> champion had to bow out due to time constraints, so we are looking for a
> new one. We are mostly ASF/IPMC members, so we could do it ourselves,
> but we'd love it if someone not too heavily involved with the codebase
> could champion it.
> 
> The initial proposal can be found at:
> https://wiki.apache.org/incubator/PonyMailProposal
> 
> And, well, the software can be found in action at
> https://lists.apache.org among other places :)
> 
> Looking forward to your replies!
> 
> With regards,
> Daniel.
> 
> -
> 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] PredictionIO incubation proposal

[Suneel Marthi]

Thanks Henry

On Tue, May 17, 2016 at 5:11 PM, Henry Saputra 
wrote:

> As mentor, you will have karma to commit to the source repository.
>
> As you probably know, the initial committers and mentors will form the
> initial PPMCs for the podling.
> Hopefully for day to day operations you should not need to have distinction
> of committer vs mentors anymore.
>
> You do not have to be listed as committer for the proposal.
>
> - Henry
>
> On Tue, May 17, 2016 at 1:57 PM, Suneel Marthi  wrote:
>
> > Thanks for having me as a mentor for PIO.  I would like to be added to
> the
> > initial list of committers and am looking to actively participate in the
> > development too. I am not sure if my being a mentor automatically grants
> me
> > the 'commit' karma.
> >
> > Its already been suggested earlier in this thread by Roman and
> > Jean-Baptiste that the project needs to be decoupled from Spark and
> > integrated with Beam.  It would be good to reduce the reliance on
> > Spark-Submit from what I have seen of the project so far. But let's not
> > talk architecture and design here when the project's not in incubator
> yet.
> > :)
> >
> >
> >
> >
> > On Tue, May 17, 2016 at 4:09 PM, Henry Saputra 
> > wrote:
> >
> > > Cool, this will make code grant process to be easier =)
> > >
> > > The initial committers and mentors look great.
> > > I am sure more will come as contributions start pouring in to the
> > project.
> > >
> > > Looking forward for the VOTE thread soon.
> > >
> > > - Henry
> > >
> > > On Mon, May 16, 2016 at 12:07 PM, Simon Chan 
> > wrote:
> > >
> > > > Yes, it includes everyone who previously contributed code from
> > > PredictionIO
> > > > before the acquisition and still want to be involved in the project.
> > > >
> > > > We may have missed "Alex Merritt", going to add him to the list soon.
> > > >
> > > > Simon
> > > >
> > > >
> > > > On Mon, May 16, 2016 at 11:58 AM, Suneel Marthi 
> > > > wrote:
> > > >
> > > > > I do have a question about the proposed list of committers.
> > > > >
> > > > > Does the list also include all of those folks who were with
> > > PredictionIO
> > > > > (and had contributed to the project) and then chose to leave when
> PIO
> > > was
> > > > > acquired by Salesforce?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Mon, May 16, 2016 at 1:13 PM, Jean-Baptiste Onofré <
> > j...@nanthrax.net
> > > >
> > > > > wrote:
> > > > >
> > > > > > By the way, we have some discussion about integrating Zeppelin
> with
> > > > Beam
> > > > > ;)
> > > > > >
> > > > > > Regards
> > > > > > JB
> > > > > >
> > > > > > On 05/15/2016 02:32 AM, Roman Shaposhnik wrote:
> > > > > >
> > > > > >> Super excited to see this proposal! This will finally allow us
> to
> > > have
> > > > > >> an ASF managed
> > > > > >> backend for next generation data-driven apps that I see emerging
> > > quite
> > > > > >> rapidly.
> > > > > >>
> > > > > >> The proposal looks great to me (although I'd recommend calling
> > Scala
> > > > > >> as an implementation
> > > > > >> language more prominently since it may attract additional
> > developers
> > > > > >> with affinity to it).
> > > > > >>
> > > > > >> I do have two questions about technology:
> > > > > >> 1. do you think it would be possible to leverage Apache Beam
> > > > > >> (incubating)
> > > > > >> for abstracting away dependency on execution frameworks?
> > My
> > > > > >> understanding
> > > > > >> is that PredictionIO currently only run on Spark.
> > > > > >> 2. is there a potential integration with Apache Zeppelin
> > > possible?
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Roman.
> > > > > >>
> > > > > >> On Fr

Re: [DISCUSS] PredictionIO incubation proposal

[Suneel Marthi]

Thanks for having me as a mentor for PIO.  I would like to be added to the
initial list of committers and am looking to actively participate in the
development too. I am not sure if my being a mentor automatically grants me
the 'commit' karma.

Its already been suggested earlier in this thread by Roman and
Jean-Baptiste that the project needs to be decoupled from Spark and
integrated with Beam.  It would be good to reduce the reliance on
Spark-Submit from what I have seen of the project so far. But let's not
talk architecture and design here when the project's not in incubator yet.
:)




On Tue, May 17, 2016 at 4:09 PM, Henry Saputra 
wrote:

> Cool, this will make code grant process to be easier =)
>
> The initial committers and mentors look great.
> I am sure more will come as contributions start pouring in to the project.
>
> Looking forward for the VOTE thread soon.
>
> - Henry
>
> On Mon, May 16, 2016 at 12:07 PM, Simon Chan  wrote:
>
> > Yes, it includes everyone who previously contributed code from
> PredictionIO
> > before the acquisition and still want to be involved in the project.
> >
> > We may have missed "Alex Merritt", going to add him to the list soon.
> >
> > Simon
> >
> >
> > On Mon, May 16, 2016 at 11:58 AM, Suneel Marthi 
> > wrote:
> >
> > > I do have a question about the proposed list of committers.
> > >
> > > Does the list also include all of those folks who were with
> PredictionIO
> > > (and had contributed to the project) and then chose to leave when PIO
> was
> > > acquired by Salesforce?
> > >
> > >
> > >
> > >
> > > On Mon, May 16, 2016 at 1:13 PM, Jean-Baptiste Onofré  >
> > > wrote:
> > >
> > > > By the way, we have some discussion about integrating Zeppelin with
> > Beam
> > > ;)
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On 05/15/2016 02:32 AM, Roman Shaposhnik wrote:
> > > >
> > > >> Super excited to see this proposal! This will finally allow us to
> have
> > > >> an ASF managed
> > > >> backend for next generation data-driven apps that I see emerging
> quite
> > > >> rapidly.
> > > >>
> > > >> The proposal looks great to me (although I'd recommend calling Scala
> > > >> as an implementation
> > > >> language more prominently since it may attract additional developers
> > > >> with affinity to it).
> > > >>
> > > >> I do have two questions about technology:
> > > >> 1. do you think it would be possible to leverage Apache Beam
> > > >> (incubating)
> > > >> for abstracting away dependency on execution frameworks? My
> > > >> understanding
> > > >> is that PredictionIO currently only run on Spark.
> > > >> 2. is there a potential integration with Apache Zeppelin
> possible?
> > > >>
> > > >> Thanks,
> > > >> Roman.
> > > >>
> > > >> On Fri, May 13, 2016 at 1:41 PM, Andrew Purtell <
> apurt...@apache.org>
> > > >> wrote:
> > > >>
> > > >>> Greetings,
> > > >>>
> > > >>> It is my pleasure to
> > > >>>
> > > >>> propose the PredictionIO project for incubation at the Apache
> > Software
> > > >>> Foundation.
> > > >>>
> > > >>> PredictionIO is a
> > > >>> popular
> > > >>> open
> > > >>>
> > > >>> source Machine Learning Server built on top of a state-of-the-art
> > open
> > > >>> source stack, including several Apache technologies, that
> > > >>>
> > > >>> enables developers to manage and deploy production-ready predictive
> > > >>> services for various kinds of machine learning tasks
> > > >>> , with more than 400 production deployments around the world and a
> > > >>> growing
> > > >>> contributor community.
> > > >>>
> > > >>>
> > > >>> The text of the proposal is included below and is also available at
> > > >>> https://wiki.apache.org/incubator/PredictionIO
> > > >>>
> > > >>> Best regards,
> > > >>> Andrew Purtell
> > > >>>
> 

Re: [DISCUSS] PredictionIO incubation proposal

[Suneel Marthi]

 of salaried developers by meritocratically promoting those
>>> contributors to committers.
>>>
>>>  Relationships with Other Apache Product 
>>> PredictionIO relies heavily on top level apache projects such as Apache
>>> Spark, HBase and Hadoop. However it brings a distinguished functionality,
>>> rather than just an abstraction - Machine Learning in a plug-and-play
>>> fashion.
>>>
>>> Compared to Apache Mahout, which focuses on the development of a wide
>>> variety of algorithms, PredictionIO offers a platform to manage the whole
>>> machine learning workflow, including data collection, data preparation,
>>> modeling, deployment and management of predictive services in production
>>> environments.
>>>
>>>  An Excessive Fascination with the Apache Brand 
>>> PredictionIO is already a widely known open source project. This proposal
>>> is not for the purpose of generating publicity. Rather, the primary
>>> benefits to joining Apache are those outlined in the Rationale section.
>>>
>>> === Documentation ===
>>> PredictionIO boasts rich and live documentation, included in the code
>>> repo
>>> (docs/manual directory), is built with Middleman, and publicly hosted at
>>> https://docs.prediction.io
>>>
>>> === Initial Source and Intellectual Property Submission Plan ===
>>> Currently, the PredictionIO codebase is distributed under the Apache 2.0
>>> License and hosted on GitHub:
>>> https://github.com/PredictionIO/PredictionIO
>>>
>>> === External Dependencies ===
>>> PredictionIO has the following external dependencies:
>>>   * Apache Hadoop 2.4.0 (optional, required only if YARN and HDFS are
>>> needed)
>>>   * Apache Spark 1.3.0 for Hadoop 2.4
>>>   * Java SE Development Kit 8
>>>   * and one of the following sets:
>>>
>>> * PostgreSQL 9.1
>>>
>>>
>>> or
>>>
>>>
>>> * MySQL 5.1
>>>
>>>   or
>>>
>>>
>>>   * Apache HBase 0.98.6
>>>
>>>
>>> * Elasticsearch 1.4.0
>>>
>>> Upon acceptance to the incubator, we would begin a thorough analysis of
>>> all transitive dependencies to verify this information and introduce
>>> license checking into the build and release process by integrating with
>>> Apache RAT.
>>>
>>> === Cryptography ===
>>> PredictionIO does not include cryptographic code. We utilize standard
>>> JCE and JSSE APIs provided by the Java Runtime Environment.
>>>
>>> === Required Resources ===
>>> We request that following resources be created for the project to use
>>>
>>>  Mailing lists 
>>>
>>> predictionio-priv...@incubator.apache.org (with moderated subscriptions)
>>>
>>> predictionio-dev
>>>
>>> predictionio-user
>>>
>>> predictionio-commits
>>>
>>> We will migrate the existing PredictionIO mailing lists.
>>>
>>>  Git repository 
>>> The PredictionIO team would like to use Git for source control, due to
>>> our
>>> current use of GitHub.
>>>
>>> git://git.apache.org/incubator-predictionio
>>>
>>>  Documentation 
>>> https://predictionio.incubator.apache.org/docs/
>>>
>>>  JIRA instance 
>>> PredictionIO currently uses the GitHub issue tracking system associated
>>> with its repository: https://github.com/PredictionIO/PredictionIO/issues
>>> .
>>> We will migrate to Apache JIRA.
>>>
>>> JIRA PREDICTIONIO
>>> https://issues.apache.org/jira/browse/PREDICTIONIO
>>>
>>>  Other Resources 
>>> * TravisCI for builds and test running.
>>>
>>> * PredictionIO's documentation, included in the code repo (docs/manual
>>> directory), is built with Middleman and publicly hosted
>>> https://docs.prediction.io
>>>
>>> * A blog to drive adoption and excitement at https://blog.prediction.io
>>>
>>> === Initial Committers ===
>>>
>>> * Pat Ferrell
>>>
>>> * Tamas Jambor
>>>
>>> * Justin Yip
>>>
>>> * Xusen Yin
>>>
>>> * Lee Moon Soo
>>>
>>> * Donald Szeto
>>>
>>> * Kenneth Chan
>>>
>>> * Tom Chan
>>>
>>> * Simon Chan
>>>
>>> * Marco Vivero
>>>
>>> * Matthew Tovbin
>>>
>>> * Yevgeny Khodorkovsky
>>>
>>> * Felipe Oliveira
>>>
>>> * Vitaly Gordon
>>>
>>> === Affiliations ===
>>>
>>> * Pat Ferrell - ActionML
>>>
>>> * Tamas Jambor - Channel4
>>>
>>> * Justin Yip - independent
>>>
>>> * Xusen Yin - USC
>>>
>>> * Lee Moon Soo - NFLabs
>>>
>>> * Donald Szeto - Salesforce
>>>
>>> * Kenneth Chan - Salesforce
>>>
>>> * Tom Chan - Salesforce
>>>
>>> * Simon Chan - Salesforce
>>>
>>> * Marco Vivero - Salesforce
>>>
>>> * Matthew Tovbin - Salesforce
>>>
>>> * Yevgeny Khodorkovsky - Salesforce
>>>
>>> * Felipe Oliveira - Salesforce
>>>
>>> * Vitaly Gordon - Salesforce
>>>
>>> === Sponsors ===
>>>
>>>  Champion 
>>>
>>> Andrew Purtell 
>>>
>>>  Nominated Mentors 
>>>
>>> * Andrew Purtell 
>>>
>>> * James Taylor 
>>>
>>> * Lars Hofhansl 
>>>
>>> * Suneel Marthi 
>>>
>>> * Xiangrui Meng 
>>>
>>> * Luciano Resende 
>>>
>>>  Sponsoring Entity 
>>>
>>> Apache Incubator PMC
>>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] PredictionIO incubation proposal

[Suneel Marthi]

gt;> contributors to committers.
>>>
>>>  Relationships with Other Apache Product 
>>> PredictionIO relies heavily on top level apache projects such as Apache
>>> Spark, HBase and Hadoop. However it brings a distinguished functionality,
>>> rather than just an abstraction - Machine Learning in a plug-and-play
>>> fashion.
>>>
>>> Compared to Apache Mahout, which focuses on the development of a wide
>>> variety of algorithms, PredictionIO offers a platform to manage the whole
>>> machine learning workflow, including data collection, data preparation,
>>> modeling, deployment and management of predictive services in production
>>> environments.
>>>
>>>  An Excessive Fascination with the Apache Brand 
>>> PredictionIO is already a widely known open source project. This proposal
>>> is not for the purpose of generating publicity. Rather, the primary
>>> benefits to joining Apache are those outlined in the Rationale section.
>>>
>>> === Documentation ===
>>> PredictionIO boasts rich and live documentation, included in the code
>>> repo
>>> (docs/manual directory), is built with Middleman, and publicly hosted at
>>> https://docs.prediction.io
>>>
>>> === Initial Source and Intellectual Property Submission Plan ===
>>> Currently, the PredictionIO codebase is distributed under the Apache 2.0
>>> License and hosted on GitHub:
>>> https://github.com/PredictionIO/PredictionIO
>>>
>>> === External Dependencies ===
>>> PredictionIO has the following external dependencies:
>>>   * Apache Hadoop 2.4.0 (optional, required only if YARN and HDFS are
>>> needed)
>>>   * Apache Spark 1.3.0 for Hadoop 2.4
>>>   * Java SE Development Kit 8
>>>   * and one of the following sets:
>>>
>>> * PostgreSQL 9.1
>>>
>>>
>>> or
>>>
>>>
>>> * MySQL 5.1
>>>
>>>   or
>>>
>>>
>>>   * Apache HBase 0.98.6
>>>
>>>
>>> * Elasticsearch 1.4.0
>>>
>>> Upon acceptance to the incubator, we would begin a thorough analysis of
>>> all transitive dependencies to verify this information and introduce
>>> license checking into the build and release process by integrating with
>>> Apache RAT.
>>>
>>> === Cryptography ===
>>> PredictionIO does not include cryptographic code. We utilize standard
>>> JCE and JSSE APIs provided by the Java Runtime Environment.
>>>
>>> === Required Resources ===
>>> We request that following resources be created for the project to use
>>>
>>> ==== Mailing lists 
>>>
>>> predictionio-priv...@incubator.apache.org (with moderated subscriptions)
>>>
>>>
>>> predictionio-dev
>>>
>>> predictionio-user
>>>
>>> predictionio-commits
>>>
>>> We will migrate the existing PredictionIO mailing lists.
>>>
>>>  Git repository 
>>> The PredictionIO team would like to use Git for source control, due to
>>> our
>>> current use of GitHub.
>>>
>>> git://git.apache.org/incubator-predictionio
>>>
>>>  Documentation 
>>> https://predictionio.incubator.apache.org/docs/
>>>
>>>  JIRA instance 
>>> PredictionIO currently uses the GitHub issue tracking system associated
>>> with its repository: https://github.com/PredictionIO/PredictionIO/issues
>>> .
>>> We will migrate to Apache JIRA.
>>>
>>> JIRA PREDICTIONIO
>>> https://issues.apache.org/jira/browse/PREDICTIONIO
>>>
>>>  Other Resources 
>>> * TravisCI for builds and test running.
>>>
>>> * PredictionIO's documentation, included in the code repo (docs/manual
>>> directory), is built with Middleman and publicly hosted
>>> https://docs.prediction.io
>>>
>>> * A blog to drive adoption and excitement at https://blog.prediction.io
>>>
>>> === Initial Committers ===
>>>
>>> * Pat Ferrell
>>>
>>> * Tamas Jambor
>>>
>>> * Justin Yip
>>>
>>> * Xusen Yin
>>>
>>> * Lee Moon Soo
>>>
>>> * Donald Szeto
>>>
>>> * Kenneth Chan
>>>
>>> * Tom Chan
>>>
>>> * Simon Chan
>>>
>>> * Marco Vivero
>>>
>>> * Matthew Tovbin
>>>
>>> * Yevgeny Khodorkovsky
>>>
>>> * Felipe Oliveira
>>>
>>> * Vitaly Gordon
>>>
>>> === Affiliations ===
>>>
>>> * Pat Ferrell - ActionML
>>>
>>> * Tamas Jambor - Channel4
>>>
>>> * Justin Yip - independent
>>>
>>> * Xusen Yin - USC
>>>
>>> * Lee Moon Soo - NFLabs
>>>
>>> * Donald Szeto - Salesforce
>>>
>>> * Kenneth Chan - Salesforce
>>>
>>> * Tom Chan - Salesforce
>>>
>>> * Simon Chan - Salesforce
>>>
>>> * Marco Vivero - Salesforce
>>>
>>> * Matthew Tovbin - Salesforce
>>>
>>> * Yevgeny Khodorkovsky - Salesforce
>>>
>>> * Felipe Oliveira - Salesforce
>>>
>>> * Vitaly Gordon - Salesforce
>>>
>>> === Sponsors ===
>>>
>>>  Champion 
>>>
>>> Andrew Purtell 
>>>
>>>  Nominated Mentors 
>>>
>>> * Andrew Purtell 
>>>
>>> * James Taylor 
>>>
>>> * Lars Hofhansl 
>>>
>>> * Suneel Marthi 
>>>
>>> * Xiangrui Meng 
>>>
>>> * Luciano Resende 
>>>
>>>  Sponsoring Entity 
>>>
>>> Apache Incubator PMC
>>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Fluo into the Apache Incubator

[Suneel Marthi]

+1
Sent from my iPhone

> On May 14, 2016, at 11:21 AM, Ted Dunning  wrote:
> 
> +1
> 
> 
> 
> On Sat, May 14, 2016 at 10:09 AM, James Taylor 
> wrote:
> 
>> +1 (binding)
>> 
>> On Sat, May 14, 2016 at 9:31 AM, Roman Shaposhnik 
>> wrote:
>> 
>>> On Fri, May 13, 2016 at 11:22 AM, Billie Rinaldi 
>>> wrote:
 Since discussion has died down, I would like to call a VOTE on
>> accepting
 Fluo into the Apache Incubator.
 
 Proposal: http://wiki.apache.org/incubator/FluoProposal
 
 [ ] +1 Accept Fluo into the Apache Incubator
 [ ] +0 Abstain.
 [ ] -1 Do not accept Fluo into the Apache Incubator because…
>>> 
>>> +1 (binding)
>>> 
>>> Thanks,
>>> Roman.
>>> 
>>> -
>>> 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: [Incubator Wiki] Update of "GossipProposal" by P. Taylor Goetz

[Suneel Marthi]

Please add me to the list of contributors


* Suneel Marthi - smar...@apache.org - Red hat Inc.



On Fri, Apr 22, 2016 at 4:07 PM, Apache Wiki  wrote:

> Dear Wiki user,
>
> You have subscribed to a wiki page or wiki category on "Incubator Wiki"
> for change notification.
>
> The "GossipProposal" page has been changed by P. Taylor Goetz:
> https://wiki.apache.org/incubator/GossipProposal?action=diff&rev1=3&rev2=4
>
>   == Issue Tracking ==
>   JIRA tracker: GOSSIP
>   = Initial Committers =
> -  * Edward Capriolo (Hive Committer, PMC)
> -  * P. Taylor Goetz (Storm PMC)
> -  * Gary Dusbabek (Cassandra Committer, PMC)
> -  * Dorian Ellerbe (requires CLA)
> +  * Edward Capriolo (ecapriolo at apache dot org)
> +  * P. Taylor Goetz (ptgoetz at apache dot org)
> +  * Gary Dusbabek (gdusbabek at apache dot org)
> +  * Dorian Ellerbe (Doellerbe06 at gmail dot com)(requires CLA)
>* Sathish Dhinakaran (requires CLA)
>   = Affiliations =
> - With diverse contributors the project will be able to make balanced
> decisions best for the future of the project.
> +  * Edward Capriolo - The Huffington Post
> +  * P. Taylor Goetz - Hortonworks
> +  * Gary Dusbabek - Silicon Valley Data Science
> +  * Dorian Ellerbe - Dstillery
> +  * Sathish Dhinakaran - Dstillery
> +  * Sean Busbey - Cloudera
> +  * Josh Elser - Hortonworks
> +
>   = Additional Interested Contributors =
>
>   Those interested in getting involved with the project as it starts are
> encourage to list themselves here.
>
> -
> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> For additional commands, e-mail: cvs-h...@incubator.apache.org
>
>

Request to join Incubator PMC

[Suneel Marthi]

Hi All,

I am interested in joining the incubator PMC.

Regards,
Suneel