Re: [VOTE] Graduate Apache Mnemonic project from Incubator

[Patrick Hunt]

+1 Graduate Apache Mnemonic from the Incubator

Regards,

Patrick

On Tue, Sep 19, 2017 at 10:16 AM, Gang(Gary) Wang  wrote:

> Hello IPMC and everyone,
>
> The Mnemonic community has voted on its Dev list to graduate, The vote
> passed with
> 14 +1s (including  +9s from the PPMC) and 0 -1s.
>
> Here is the vote result thread in the Dev list:
> https://lists.apache.org/thread.html/bbc187108b73d57fddec0d6a6c2945
> 27b626c7c439a7cdab991ea84e@%3Cdev.mnemonic.apache.org%3E
>
> and the vote thread:
> https://lists.apache.org/thread.html/a49e82d507bb00839413e90b05cb8b
> 9448ea242aeb021622f5deb323@%3Cdev.mnemonic.apache.org%3E
>
> With the discussion having settled down, I would now like to call for
> a recommendation VOTE to present the ASF board with the following
> resolution
> to graduate from incubation and establish Apache Mnemonic
> as a top-level project (TLP).
> https://lists.apache.org/thread.html/94664579041db58bfe2893af6e9d54
> 957652653b278d4007e914c672@%3Cgeneral.incubator.apache.org%3E
>
> Apache Mnemonic entered incubation in March 2016. Since then there have
> been nine releases and four committers and two PMC candidate members
> have been added to the project. For each release, source artifacts
> have been made available. Based on the completed maturity evaluation,
> we believe that the project is ready to graduate from the incubator.
> More checklist info about graduation, please refer to
> https://cwiki.apache.org/confluence/display/MNEMONIC/Maturity+Evaluation
>
> Please vote on whether to graduate Mnemonic from incubator and
> recommend the following graduation resolution to the ASF Board.
>
> [ ] +1 Graduate Apache Mnemonic from the Incubator
> [ ] +0 Don't care
> [ ] -1 Don't graduate Apache Mnemonic from the Incubator because...
>
> This VOTE will be open for at least 72 hours.
> Thanks to all Mentors and Apache Mnemonic Project members
> for their support and contributions again.
>
> 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.
> --
> Establish the Apache Mnemonic 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 transparent nonvolatile hybrid memory oriented library for
> Big data, High-performance computing, and Analytics.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Mnemonic Project", be and hereby is
> established pursuant to Bylaws of the Foundation, and be it further
>
> RESOLVED, that the Apache Mnemonic Project be and hereby is responsible
> for the creation and maintenance of software related to a transparent
> nonvolatile hybrid memory oriented library for Big data,
> High-performance computing and Analytics; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Mnemonic" 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 Mnemonic
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Mnemonic
> 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 Mnemonic
> Project:
>
>  * Andrew Kyle Purtell  
>  * Debojyoti Dutta  
>  * Gang Wang
>  * Hao Cheng
>  * James R. Taylor  
>  * Johnu George 
>  * Kai Zheng
>  * Patrick D. Hunt  
>  * Rakesh Radhakrishnan 
>  * Uma Maheswara Rao G  
>  * Yanping Wang 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gang Wang be appointed to
> the office of Vice President, Apache Mnemonic, 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 Mnemonic 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 Mnemonic Project;
> and be it further
>
> RESOLVED, that the Apache Mnemonic Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Mnemonic
> podling; and be it further
>
> 

Re: [DISCUSS] Migrating to the New Incubator Website

[Patrick Hunt]

On Sat, Jun 17, 2017 at 5:35 AM, John D. Ament 
wrote:

> All,
>
> I'd like to start the process to move forward on a new incubator website.
> Based on discussions in the past on list, I wanted to do the following:
>
> - Roll out a new technology stack + repository
> - Leave content in place, while we work later on content enhancements
>
> For right now, I'm planning to leave the existing /projects and
> /ip-clearance in place.  My hope is that we may not need them in the
> future.
>
> The website staging area can be seen here:
> https://incubator.apache.org/ngtest/
> 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
> (with
> github mirror at https://github.com/apache/incubator/tree/jbake-site )
>
> I'd like to get some final feedback on the layout and colors (not the
> content).  I want to start tracking content enhancements in JIRA to help
> come up with a backlog of areas of improvement for our incubator guides.
>
>
I'm very familiar with the old layout, so this may be coloring my feedback.
However I find the new layout to be less usable than previous. In
particular the drop downs lack structure. I think it would be better to
focus on "solutions" e.g. "bootstrapping a new podling" along with assoc
docs, or "graduating a podingling" etc... - basically focus around the
lifecycle of podling rather than a big long list of "guides". Additionally
it's hard to find things with the new layout, I used to use the browser
"search" feature to narrow down to a particular doc. Now I need to click on
each of the drop downs to find the content I'm looking for. Additionally
things like wiki/faq/etc... - can't find them at all.

Patrick


> John
>

Re: [VOTE] Release of Apache Mnemonic-0.6.0-incubating [rc1]

[Patrick Hunt]

+1 xsum/sig verified, RAT ran clean, checklist looks ok. Was able to
build/test/install the source. lgtm.

Patrick

On Mon, Apr 10, 2017 at 4:06 PM, Gang(Gary) Wang  wrote:

> Hello incubator PMCs,
>
> The Apache Mnemonic community PPMCs and developers have voted and
> approved the proposal to release Apache Mnemonic 0.6.0 (incubating).
>
> Apache Mnemonic is an advanced hybrid memory storage oriented library,
> it's proposed a non-volatile/durable Java object model and durable
> computing model that bring several advantages to significantly improve
> the performance of massive real-time data processing/analytic.
> developers are able to use this library to design their cache-less and
> SerDe-less high performance applications.
>
> [VOTE] thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-
> mnemonic-dev/201704.mbox/%3CCALuGr6Z1UX-pU4wRHea-J4roWW%
> 2BwYOK20tfF%2B4-EdRT6TS6K_A%40mail.gmail.com%3E
>
> http://mail-archives.apache.org/mod_mbox/incubator-
> mnemonic-dev/201704.mbox/%3CCAG7vPR%2B5Uv9ide1gnaPQT4a%
> 3DWrgsDLfzN9i3xJ3i8Dq-G3oyuA%40mail.gmail.com%3E
>
> http://mail-archives.apache.org/mod_mbox/incubator-
> mnemonic-dev/201704.mbox/%3CD50D574B.2FDB5%25uma.gangumalla%40intel.com%3E
>
> http://mail-archives.apache.org/mod_mbox/incubator-
> mnemonic-dev/201704.mbox/%3CCAOgX8sz9vy3ms_sEpP0%
> 3DmV6adJX8JFbwynppRAPfkXkNi17%3DrQ%40mail.gmail.com%3E
>
> [VOTE RESULT] thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-
> mnemonic-dev/201704.mbox/%3CCAOgX8sy7mSUR8HvrWCfc2YXtMNR
> 9R5UCj3EaL_RF145SARbKAA%40mail.gmail.com%3E
> We now kindly request the Incubator PMC members review and vote on
> this incubator release.
>
> The Apache Mnemonic-0.6.0-incubating release candidate is now
> available with the following artifacts for a project vote:
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0.
> 6.0-incubating-rc1/src/
>
> The tag to be voted upon is v0.6.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-
> mnemonic.git;a=shortlog;h=refs/tags/v0.6.0-incubating
>
> The release hash is d40a8f23bd18954b0d93ba7f8196f40d05c55dcc:
> https://git-wip-us.apache.org/repos/asf?p=incubator-
> mnemonic.git;a=commit;h=d40a8f23bd18954b0d93ba7f8196f40d05c55dcc
>
> Release artifacts are signed with the following key:
> https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/mnemonic/KEYS
>
> For information about the contents of this release, see:
> https://dist.apache.org/repos/dist/dev/incubator/mnemonic/0.
> 6.0-incubating-rc1/CHANGES.txt
>
> The vote will be open for ~72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.  The
> please vote:
>
> [ ] +1 Release this package as apache-mnemonic-0.6.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
>
> Thanks,
> Gary on behalf of the Apache Mnemonic (incubating) team
>

Re: [RESULT][VOTE] Release of Apache Mnemonic-0.1.2-incubating [rc2] (Revised)

[Patrick Hunt]

Hi Gary. You want to summarize all the votes, including the ones on the
project's dev list, here - I (and others) had voted on the dev list thread
already.

Patrick

On Tue, May 24, 2016 at 8:55 AM, Gary  wrote:

> Hi all,
>
>
> After being open for over 72 hours, the vote for releasing Apache Mnemonic
> 0.1.2-incubating passed with 3 binding +1s and no +0 and no -1.
>
>
>
> Binding +1s:
>
> Henry Saputra
>
> Justin Mclean
> Gangumalla, Uma
>
>
> A issue we need to work on -
>
> 1. Justin had issues building from source on OSX . We will look into the
> issue.
>
>
> Thanks to everyone who voted!
>
>
> Thanks,
>
> Gary on behalf of the Apache Mnemonic (incubating) team
>
>
>

Re: [VOTE] Release of Apache Mnemonic-0.1.2-incubating [rc2] (Revised)

[Patrick Hunt]

I had to use

mvn -pl
'!mnemonic-memory-services/mnemonic-nvml-vmem-service,!mnemonic-memory-services/mnemonic-pmalloc-service'
clean install

on my mac (guess I didn't have mvem and pmalloc installed?)

Patrick


On Thu, May 19, 2016 at 7:36 PM, Justin Mclean 
wrote:

> Hi,
>
> +1 binding
>
> I checked:
> - file name contains incubating
> - DISCLAIMER exits
> - LICENSE and NOTICE correct
> - All source files have headers
> - No binary files in release
> - Unable to build from source
>
> Other than the build issue also a very easy release to review.
>
> I was unable to build from source on OSX even with:
>  mvn -pl '!mnemonic-memory-services/mnemonic-nvml-vmem-service' clean
> package
>
> But assuming it’s my setup.
>
> Would be nice for the README could have slightly clearer instructions on
> how to build on different platforms.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Final draft of the Incubator Board Report - April 2016

[Patrick Hunt]

Hey there, just back from vacation and getting caught up. Thanks for
the reminder!

Patrick

On Tue, Apr 12, 2016 at 4:38 PM, Wang, Yanping  wrote:
> Hi, John
>
> I think our mentors are busy during the day.
> Patrick was on vacation last week. I'd suggest give them a few more hours to 
> signoff the report.
>
> Thanks,
> Yanping
>
> -Original Message-
> From: John D. Ament [mailto:johndam...@apache.org]
> Sent: Tuesday, April 12, 2016 4:32 PM
> To: general@incubator.apache.org
> Subject: Re: Final draft of the Incubator Board Report - April 2016
>
> I'm a bit curious about how we should handle Mnemonic.  I've received no
> response thus far from the podling.  I'd rather not kick them out of the
> monthly report.
>
> John
>
> On Mon, Apr 11, 2016 at 11:28 PM Marvin Humphrey 
> wrote:
>
>> On Mon, Apr 11, 2016 at 3:56 AM, John D. Ament 
>> wrote:
>>
>> > Below is the final draft of the board report.
>>
>> The report looks good to me!  Comments inline.
>>
>> >   - Airflow
>> >   - Gearpump
>> >   - Mnemonic
>> >   - Omid
>> >   - Tephra
>> >
>> > * Graduations
>> >
>> >   The board has motions for the following:
>> >
>> >   - Apex
>> >   - Johnzon
>> >   - TinkerPop
>> >   - AsterixDB
>>
>> What turnover!  I see that with the addition of Quickstep that's *six* new
>> podlings in one month, which has to be a record.
>>
>> Congrats to all the entrants and graduates!
>>
>> > * Credits
>> >
>> >   - Report Manager:
>>
>> I added the credit for this month's erstwhile Report Manager. :)
>>
>> > * Did not report, expected next month
>> >
>> >   - Concerted
>> >   - OpenAz
>> >   - Tephra
>>
>> The OpenAZ report was due in January and is thus 4 months late, which I
>> have
>> now noted on the wiki.  OpenAZ's status has been raised on
>> private@incubator
>> and we just have to keep raising it each month until a report gets filed.
>>
>> > 
>> > Fineract
>> >
>> > Fineract is an open source system for core banking as a platform.
>> >
>> > Fineract has been incubating since 2015-12-15.
>> >
>> > Three most important issues to address in the move towards graduation:
>> >
>> >   1. Finalising the initial release
>> >   2. Improve the communication around the differences between the
>> previous
>> >  MifosX project and the new Fineract project, especially in the
>> MifosX
>> >  community, website etc.
>> >   3. With the first initial release, encourage the community to use the
>> >  proper infastructure (mailing lists, issue tracker) for the ongoing
>> >  collaboration within the community.
>> >   4. Change management towards less 'key-man' dependency on previous
>> >  tech/community leaders from MifosX, more towards community driven
>> >  consensus.
>> >   5. Reduce clutter on mailinglist from JIRA updates etc.
>> >
>> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> > aware of?
>> >
>> >   On the mailinglist there have been discussions around the lack of
>> traffic
>> >   on it. This is part of the switchover from the current MifosX community
>> >   and mailinglists towards the new Fineract lists. At the same time the
>> >   recent meet-up of Mifosx and Fineract devs and people interested in it
>> >   (see community development), has also triggered a lot of offline
>> >   interaction.
>> >
>> > How has the community developed since the last report?
>> >
>> >   While activity on the mailinglist has been pretty low, we've had a
>> great
>> >   meet-up in Amsterdam where a nice mix of existing MifosX community
>> members
>> >   and a group of new interested people was present. This has boosted
>> >   interest in Fineract.
>> >
>> >   We have a high level of interest from new contributors throughout
>> Africa -
>> >   we are working to properly engage them and guide them to the correct
>> >   collaboration channels in our Fineract community.
>> >
>> > How has the project developed since the last report?
>> >
>> >   Individual members of the leading partner organizations building
>> solutions
>> >   using the Fineract platform have begun to effectively use the Fineract
>> >   issue tracker to communicate and track the requirements and
>> enhancements
>> >   they're building and contributing to Fineract. These individuals are
>> >   setting a good example that other individuals from our partner
>> community
>> >   should follow.
>> >
>> > Date of last release:
>> >
>> >   N/A
>> >
>> > When were the last committers or PMC members elected?
>> >
>> >   N/A
>> >
>> > Signed-off-by:
>> >
>> >   [ ](fineract) Ross Gardler
>> >   [ ](fineract) Greg Stein
>> >   [X](fineract) Roman Shaposhnik
>>
>> This report provides excellent insight into the challenges and
>> opportunities
>> before the Fineract community.  Thank you for a good read, and good luck!
>>
>> > 
>> > FreeMarker
>>
>> > How has the project developed since the last report?
>> >
>> >   FreeMarker had 

[RESULT] [VOTE] Accept Mnemonic as an Apache Incubator Podling

[Patrick Hunt]

This vote has PASSED with the following tallies:

+1 Binding total 9
Patrick Hunt
Jacques Nadeau
Henry Saputra
James Taylor
Andrew Purtell
Chris Nauroth
Arvind Prabhakar
P. Taylor Goetz
Ted Dunning

+1 No-binding, total 11
Phillip Rhodes
Ramkrishna S Vasudevan
Uma Gangumalla
Debo Dutta
Tsuyoshi Ozawa
Kai Zheng
Liang Chen
Dapeng Sun
Priyank Ashok Rastogi
Sravya Tirukkovalur
Hao Hao

No other votes were submitted.

Thanks to everyone who voted. The mentors will now assist in getting
the project bootstrapped.

Regards,

Patrick

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

[VOTE] Accept Mnemonic into the Apache Incubator

[Patrick Hunt]

the larger community as well.

=== Documentation ===
The documentation is currently available at Intel and will be posted
under: https://mnemonic.incubator.apache.org/docs

=== Initial Source ===
Initial source code is temporary hosted Github for general viewing:
https://github.com/NonVolatileComputing/Mnemonic.git
It will be moved to Apache http://git.apache.org/ after podling.

The initial Source is written in Java code (88%) and mixed with JNI C
code (11%) and shell script (1%) for underlying native allocation
libraries.

=== Source and Intellectual Property Submission Plan ===
As soon as Mnemonic is approved to join the Incubator, the source code
will be transitioned via the Software Grant Agreement onto ASF
infrastructure and in turn made available under the Apache License,
version 2.0.

=== External Dependencies ===
The required external dependencies are all Apache licenses or other
compatible Licenses
Note: The runtime dependent licenses of Mnemonic are all declared as
Apache 2.0, the GNU licensed components are used for Mnemonic build
and deployment. The Mnemonic JNI libraries are built using the GNU
tools.

maven and its plugins (http://maven.apache.org/ ) [Apache 2.0]
JDK8 or OpenJDK 8 (http://java.com/) [Oracle or Openjdk JDK License]
Nvml (http://pmem.io ) [optional] [Open Source]
PMalloc (https://github.com/bigdata-memory/pmalloc ) [optional] [Apache 2.0]

Build and test dependencies:
org.testng.testng v6.8.17  (http://testng.org) [Apache 2.0]
org.flowcomputing.commons.commons-resgc v0.8.7 [Apache 2.0]
org.flowcomputing.commons.commons-primitives v.0.6.0 [Apache 2.0]
com.squareup.javapoet v1.3.1-SNAPSHOT [Apache 2.0]
JDK8 or OpenJDK 8 (http://java.com/) [Oracle or Openjdk JDK License]

=== Cryptography ===
Project Mnemonic does not use cryptography itself, however, Hadoop
projects use standard APIs and tools for SSH and SSL communication
where necessary.

=== Required Resources ===
We request that following resources be created for the project to use

 Mailing lists 
priv...@mnemonic.incubator.apache.org (moderated subscriptions)
comm...@mnemonic.incubator.apache.org
d...@mnemonic.incubator.apache.org

 Git repository 
https://github.com/apache/incubator-mnemonic

 Documentation 
https://mnemonic.incubator.apache.org/docs/

 JIRA instance 
https://issues.apache.org/jira/browse/mnemonic

=== Initial Committers ===
* Gang (Gary) Wang (gang1 dot wang at intel dot com)

* Yanping Wang (yanping dot wang at intel dot com)

* Uma Maheswara Rao G (umamahesh at apache dot org)

* Kai Zheng (drankye at apache dot org)

* Rakesh Radhakrishnan Potty  (rakeshr at apache dot org)

* Sean Zhong  (seanzhong at apache dot org)

* Henry Saputra  (hsaputra at apache dot org)

* Hao Cheng (hao dot cheng at intel dot com)

=== Additional Interested Contributors ===
* Debo Dutta (dedutta at cisco dot com)

* Liang Chen (chenliang613 at Huawei dot com)

=== Affiliations ===
* Gang (Gary) Wang, Intel

* Yanping Wang, Intel

* Uma Maheswara Rao G, Intel

* Kai Zheng, Intel

* Rakesh Radhakrishnan Potty, Intel

* Sean Zhong, Intel

* Henry Saputra, Independent

* Hao Cheng, Intel

=== Sponsors ===
==== Champion 
Patrick Hunt

==== Nominated Mentors 
* Patrick Hunt  - Apache IPMC member

* Andrew Purtell  - Apache IPMC member

* James Taylor  - Apache IPMC member

* Henry Saputra  - Apache IPMC member

 Sponsoring Entity 
Apache Incubator PMC

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

Re: [VOTE] Graduate Sentry

[Patrick Hunt]

+1 Graduate Sentry from the Incubator

Patrick

On Wed, Feb 24, 2016 at 11:20 AM, Sravya Tirukkovalur <sra...@apache.org> wrote:
> Hi all,
>
> Following the positive discussion[1] and vote[2] in the Sentry
> community and a discussion[3] on the incubator list to graduate
> Sentry, I am calling a VOTE to graduate the project from the Incubator
> to a TLP. Please vote on the resolution pasted below.
>
> [ ] +1 Graduate Sentry from the Incubator
> [ ] +0 Don't care
> [ ] -1 Don't graduate Sentry from the Incubator (please specify reason)
>
> This vote will be open for at least 72 hours.
>
> References:
>
> [1] https://s.apache.org/dev_discuss
> [2] https://s.apache.org/dev_vote_result
> [3] https://s.apache.org/general_discuss
> Other:
> https://s.apache.org/general_notify
> https://cwiki.apache.org/confluence/display/SENTRY/Sentry+maturity+assessment
>
> Resolution to create a TLP from graduating Incubator podling:
>
> ==
>
>
> X. Establish the Apache Sentry 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 Fine grained authorization to data and
> metadata in Hadoop.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Sentry Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Sentry Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to Fine grained authorization to data and metadata in Hadoop;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Sentry" 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 Sentry Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Sentry 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 Sentry Project:
>
> * Ali Rizvi <a...@apache.org>
>
>* Anne Yu <ann...@apache.org>
>
>* Arun Suresh <asur...@apache.org>
>
>* Brock Noland <br...@apache.org>
>
>* Chaoyu Tang <ct...@apache.org>
>
>* Colin Ma <co...@apache.org>
>
>* Daisy Zhou <da...@apache.org>
>
>* Dapeng Sun <s...@apache.org>
>
>* David Nalley <ke4...@apache.org>
>
>* Erick Tryzelaar <eri...@apache.org>
>
>* Gregory Chanan <gcha...@apache.org>
>
>* Guoquan Shen <gqs...@apache.org>
>
>* Hadi Nahari <h...@apache.org>
>
>* Hao Hao <ha...@apache.org>
>
>* Jarek Jarcec Cecho <jar...@apache.org>
>
>* Johnny Zhang <dreamb...@apache.org>
>
>* Karthik Ramachandran <kramachand...@apache.org>
>
>* Mark Grover <m...@apache.org>
>
>* Milo Polte <m...@apache.org>
>
>* Lenni Kuff <lsk...@apache.org>
>
>* Patrick Daly <d...@apache.org>
>
>* Patrick Hunt <ph...@apache.org>
>
>* Prasad Mujumdar <pras...@apache.org>
>
>* Raghu Mani <raghu_m...@apache.org>
>
>* Sean Mackrory <mackror...@apache.org>
>
>* Shreepadma Venugopalan <shreepa...@apache.org>
>
>* Sravya Tirukkovalur <sra...@apache.org>
>
>* Tuong Truong <tuongtru...@apache.org>
>
>* Vamsee Yarlagadda <vam...@apache.org>
>
>* Xiaomeng Huang <xi...@apache.org>
>
>* Xuefu Zhang <xu...@apache.org>
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sravya Tirukkovalur
>   be appointed to the office of Vice President, Apache Sentry, 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

Re: [VOTE] Release Apache Twill-0.7.0-incubating

[Patrick Hunt]

I already voted on the dev list thread, but here's my +1 again.

Patrick

On Thu, Jan 21, 2016 at 8:52 PM, Henry Saputra  wrote:
> Hi IPMCs,
>
> Please help Twill community to VOTE on release.
>
> Thank you.
>
> - Henry
>
> On Sat, Jan 16, 2016 at 8:42 PM, Justin Mclean  wrote:
>
>> Hi,
>>
>> +1 binding
>>
>> I checked:
>> - incubating in name
>> - signatures and hashes correct
>> - disclaimer exists
>> - LICENSE and NOTICE correct
>> - no binary files
>> - all files have apache source headers
>> - can compile from source
>>
>> Very minor issue - year is incorrect in NOTICE.
>>
>> Thanks
>> Justin
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

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

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

On Wed, Nov 4, 2015 at 5:52 PM, Joe Brockmeier  wrote:

> On Wed, Nov 4, 2015, at 08:43 PM, John D. Ament wrote:
> > I don't think that's the question on the table.  Typically, podlings make
> > committers == PPMC members.  The reasoning being that the only thing a
> > PPMC member can do is vote on adding new members.  Other votes are all
> > non-binding (unless you're an IPMC member).  It also helps promote the
> > synergy needed to become a TLP, forming a strong PMC.
>
> I don't suppose we have stats on that, do we?
>
> My first project was CloudStack, and I was surprised to find other
> podlings *didn't* distinguish between committer and PPMC. While PPMC
> votes on members, being a committer does give privileges beyond just
> being an occasional contributor, so some folks may find it a useful step
> between "we have to review all of your patches" and "you're helping with
> governance/growth of the project."
>
>
My experience on other projects is the same as Joe. afaik it's up to the
podling, and most I've been involved with decided to go with committer !=
ppmc. Honestly I thought that was the default.

Patrick


>
> jzb
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

On Wed, Nov 4, 2015 at 12:47 AM, Bertrand Delacretaz <bdelacre...@apache.org
> wrote:

> On Tue, Nov 3, 2015 at 10:42 PM, Patrick Hunt <ph...@apache.org> wrote:
> > ...what would the action item the community should take away from
> > this? As their mentor I'm not sure what advice i can give them. "add more
> > ppmc members"? Sounds like that's in the pipeline. Seems artificial to
> me
>
> If it's in the pipeline that's fine, what's important IMO is that the
> podling demonstrates that it can grow/renew its (p)PMC, during
> incubation.
>
>
This highlights my concern though. It's why this thread was started in the
first place IMO - the fact that the incubator graduation requirements are a
moving target. It's one of the more frustrating aspects of being a mentor.

A few years ago being in the incubator was strict, but much more
straightforward. Bootstrap, build your community, address the IP issues,
show you understand the Apache way and you are on your way - "best wishes".
Now we seem to think everyone is out to do the wrong thing, rather than
everyone having positive motives and are trying their best.

If you read the graduation requirements it says nothing about adding PPMC
as a strict requirement to graduation:
http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator

Bertrand - you had stated a strong "-1" previously. Are you now saying that
you would be +1?

Based on my reading Sentry has more than met the minimum requirements and I
recommend we allow graduation.

Patrick



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

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

On Wed, Nov 4, 2015 at 8:03 AM, Bertrand Delacretaz <bdelacre...@apache.org>
wrote:

> Hi,
>
> On Wed, Nov 4, 2015 at 4:52 PM, Patrick Hunt <ph...@apache.org> wrote:
> > ...If you read the graduation requirements it says nothing about adding
> PPMC
> > as a strict requirement to graduation:
> >
> http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator
> ...
>
> I agree but in the meantime we have
> https://community.apache.org/apache-way/apache-project-maturity-model.html
> which many agree is a more fine grained evaluation of a project's
> health.
>
>
Is that a rubric for incubation? I don't see it mentioned anywhere in the
incubator documents.

Maturity is fine, but it's relative. We're talking about an incubator here,
not a full grown chick.


> >
> > ...Bertrand - you had stated a strong "-1" previously. Are you now
> saying that
> > you would be +1? ...
>
> I'd have to be convinced that there is a very good reason why no PPMC
> members have been added during incubation, as that's not a good sign.
>
>
So you are -1 then. That's fine. But it gets back to my original concern.
It's artificial. I can go back to the Sentry community and say "hey, you
need some PPMC members, vote some in" and they might do it. It was already
mentioned earlier in this thread that one of the mentors feels that a
couple of committers are ready. If they come back in a week and say "hey,
we just voted in 3 new ppmc members, now we're ready right?" you'll be fine
with that? This is why I highlighted it as artificial.

Patrick


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

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

On Wed, Nov 4, 2015 at 8:32 AM, Joe Brockmeier  wrote:

> On Wed, Nov 4, 2015, at 10:27 AM, Joe Schaefer wrote:
> > Joe, has any of this conversation put your mind at ease about the
> > podling?
>
> I'm less concerned than I was, yes. I'm still not in +1 territory. I'm
> not entirely sure I'm out of -1 territory.
>
> Sentry has made progress in its time in the incubator, but I feel it's
> required a lot of prodding at each step of the way - to reporting on
> time, adding contributors*, making sure its incubation status page is
> filled out, etc. It's also had some problems with release process, but I
> don't hold that against any podling because our release process can be
> hard to get right.
>
> But I view the podling as one that's concerned with releasing software,
> not growing community. I keep seeing references to "actively preventing"
> contributions - but I don't think that's a very high bar to clear. I
> want to see a podling actively working to make it possible to join and
> contribute.
>
> I'll note that I may see Sentry differently because I am a
> non-developer. The Jira-focused process may be adequate for folks who
> are primarily only focused on the release of software. It is not a
> particularly inviting or transparent process to anybody who might like
> to participate in Sentry in non-development roles. And I hope we care
> about contributors who will add value to Apache projects in
> non-development roles (documentation, marketing, translation, etc.).
>
> At any rate - I've said my piece, and I'll just reiterate that I don't
> think additional time is the answer. The signal I get from Sentry is
> that the podling feels it's ready to graduate, and they've indicated
> that they don't feel my suggestions are a "valid ask" - so I don't see
> much value in holding back a DISCUSSION and VOTE.
>
>
Personally I don't see this. To be fair, to my eye in each case when you've
brought up issues the podling has done their best to address them. They
even reached out to all the mentors recently and asked for feedback on
whether they are ready or not. The frustration podlings have is that
graduation is a moving target, even the mentors/ipmc can't agree. They are
trying to do their best, but growing a community is hard. They have been in
the incubator for two years, have built a useful tool, multiple releases,
have 30+ committers and 20+ ppmc members. Of course they want to graduate.
What I see in the sentry discussions is that they want to stay true to the
apache way, but don't want to do it artificially so. Just "ticking the
boxes" as has been brought up elsewhere in this thread.


> Note, as I understand it the board "is unlikely" to approve a podling
> where a mentor is voting -1. While I have concerns, I also don't want to
> filibuster the process and just keep Sentry in Limbo. I'd appreciate
> input from other IPMC folks on best decorum (e.g. abstaining from the
> vote, stepping down as mentor) in this situation. If other folks share
> my concerns, the vote wouldn't pass. If I'm wrong, I don't feel I should
> hold it up single-handedly.
>
>
If we can't reach consensus then we shouldn't go ahead. Your input is
valuable, that's why I'm spending my personal time on it. ;-)  However we
need to have some clear action items for the podling so that they have
something solid to build off. As it stands now I don't see a path to
graduation given the current IPMC climate.

Patrick


> * I would invite folks with access to go to Sentry's private list and
> look over discussions about adding new contributors, and discussions
> about the project in general.
>
> Best,
>
> jzb
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

On Wed, Nov 4, 2015 at 8:50 AM, Greg Stein <gst...@gmail.com> wrote:

> On Nov 4, 2015 10:03 AM, "Bertrand Delacretaz" <bdelacre...@apache.org>
> wrote:
> >
> > Hi,
> >
> > On Wed, Nov 4, 2015 at 4:52 PM, Patrick Hunt <ph...@apache.org> wrote:
> > > ...If you read the graduation requirements it says nothing about adding
> PPMC
> > > as a strict requirement to graduation:
> > >
>
> http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator
> > ...
> >
> > I agree but in the meantime we have
> >
> https://community.apache.org/apache-way/apache-project-maturity-model.html
>
> "we" don't have anything. ComDev has produced an interesting to way to look
> at projects. Possibly a metric. ... But not an agreed-upon system for the
> proper evaluation of a podling's health and community.


The incubator has lost track of what "incubation" means... but I digress,
and I've tried really hard to stay away from getting onto my soapbox...

Patrick

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

On Wed, Nov 4, 2015 at 8:35 AM, Joe Brockmeier <j...@zonker.net> wrote:

> On Wed, Nov 4, 2015, at 11:26 AM, Patrick Hunt wrote:
> > So you are -1 then. That's fine. But it gets back to my original concern.
> > It's artificial. I can go back to the Sentry community and say "hey, you
> > need some PPMC members, vote some in" and they might do it. It was
> > already
> > mentioned earlier in this thread that one of the mentors feels that a
> > couple of committers are ready. If they come back in a week and say "hey,
> > we just voted in 3 new ppmc members, now we're ready right?" you'll be
> > fine
> > with that? This is why I highlighted it as artificial.
>
> FWIW I agree with you that it's "artificial" and for a podling that's
> motivated to graduate (which Sentry appears to be) it's not hard to
> paper that over and just say "OK, if we want to graduate, let's tick
> this checkbox."
>
> Not having new PPMC folks is a symptom of what concerns me about Sentry.
> I didn't see a focus on adding committers until prodded. I don't see a
> focus on growing committers to become PMC members minus mentor prodding.
> If a project cares about sustainability and growth, shouldn't it be
> having these discussions? Their absence concerns me greatly.
>
>
In my experience "growing the community" is hard. It's very easy to say,
hard to do. Keep in mind all the things we're asking a bunch of folks to do
- look at this thread.

Patrick


> Best,
>
> jzb
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

On Wed, Nov 4, 2015 at 10:05 AM, P. Taylor Goetz  wrote:

>
> On Nov 4, 2015, at 11:32 AM, Joe Brockmeier  wrote:
>
> * I would invite folks with access to go to Sentry's private list and
> look over discussions about adding new contributors, and discussions
> about the project in general.
>
>
> I took a look.
>
> From a community growth perspective, I see them adding new committers,
> which is a good thing. What I don’t see is any discussion at all about
> adding PPMC members, nor any discussion about why they chose to go the
> Committer != PPMC route.
>
> In a thread related to the first new committer being added [1], it is
> pointed out that the podling website stated that Sentry was Committer ==
> PMC, but that the new member vote was only for Committer. At that point it
> looks like the website was updated to reflect Committer != PMC. From that
> point on, all new member votes were for Committer only, and there were no
> discussions regarding adding new PMC members or promoting committers to the
> PMC role.
>
> What I find slightly disconcerting is that there doesn’t seem to be any
> consideration or discussion around growing the PPMC and why that’s
> important. Sure they have 20-odd PPMC members from the initial committers
> list, so it would take a pretty large exodus to render the project unable
> to function, but I don’t see anything to indicate that they understand the
> function and importance of growing the PPMC.
>
>
Anyone from the community that can pitch in with more details? I realize
the firehose that is the IPMC can be overwhelming, and often intimidating,
but you should feel free to ensure the record is accurately reflected. :-)

Patrick


> If I’ve misinterpreted anything, please feel free to correct me.
>
> -Taylor
>
> [1]
> https://mail-search.apache.org/members/private-arch/sentry-private/201402.mbox/%3cCAHUddLNXceMb0xnk=1GEb6tVmCshYQMFe=zcpplgfcwgg+f...@mail.gmail.com%3e
>

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

On Tue, Nov 3, 2015 at 12:48 AM, Bertrand Delacretaz  wrote:

> On Mon, Nov 2, 2015 at 11:11 PM, Joe Brockmeier  wrote:
> > ...Sentry started with 24 committers/PPMC. It hasn't added any PPMC
> members
> > since its inception...
>
> If that's correct I'm -1 on graduating Sentry.
>
> and earlier he wrote:
> > ..The model that Sentry is pursing may work very well *for the existing
> > members of the podling.* In my opinion, its process is entirely too
> > opaque to allow for interested parties outside of the existing podling
> > and companies interested in Sentry development to become involved...
>
> Not having added any PPMC members seems to confirm that.
>
>
Bertrand, imo this is a reasonable concern. I remember some discussion a
while back on the sentry lists about it. Note that the community has
highlighted it in their status reports, so it should be nothing
new/surprising. iirc (and I'm summarizing here, please correct me if I get
it wrong) the new committers have had varying levels of activity. Some more
active than others, but none that had reached ppmc status. Perhaps the team
should be more aggressive promoting folks, but I don't believe it's out of
exclusion or lack of understanding the Apache way.

That said what would the action item the community should take away from
this? As their mentor I'm not sure what advice i can give them. "add more
ppmc members"? Sounds like that's in the pipeline. Seems artificial to me.

Patrick


> Based on the information provided in this thread It looks to me like
> Sentry isn't operating according to items CO20, CO40, CS20 and CS50 of
> our maturity model [1].
>
>
> [1]
> https://community.apache.org/apache-way/apache-project-maturity-model.html
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

On Tue, Nov 3, 2015 at 2:23 PM, Joe Brockmeier <j...@zonker.net> wrote:

>
>
> On Tue, Nov 3, 2015, at 04:42 PM, Patrick Hunt wrote:
> > On Tue, Nov 3, 2015 at 12:48 AM, Bertrand Delacretaz
> > <bdelacre...@apache.org
> > > wrote:
> >
> > > On Mon, Nov 2, 2015 at 11:11 PM, Joe Brockmeier <j...@zonker.net>
> wrote:
> > > > ...Sentry started with 24 committers/PPMC. It hasn't added any PPMC
> > > members
> > > > since its inception...
> > >
> > > If that's correct I'm -1 on graduating Sentry.
> > >
> > > and earlier he wrote:
> > > > ..The model that Sentry is pursing may work very well *for the
> existing
> > > > members of the podling.* In my opinion, its process is entirely too
> > > > opaque to allow for interested parties outside of the existing
> podling
> > > > and companies interested in Sentry development to become involved...
> > >
> > > Not having added any PPMC members seems to confirm that.
> > >
> > >
> > Bertrand, imo this is a reasonable concern. I remember some discussion a
> > while back on the sentry lists about it. Note that the community has
> > highlighted it in their status reports, so it should be nothing
> > new/surprising. iirc (and I'm summarizing here, please correct me if I
> > get it wrong) the new committers have had varying levels of activity.
> Some
> > more active than others, but none that had reached ppmc status. Perhaps
> the
> > team should be more aggressive promoting folks, but I don't believe it's
> out
> > of exclusion or lack of understanding the Apache way.
>
> We generally shy away from discussing individuals on open lists w/r/t
> "this person should/shouldn't be a PPMC member" type things, so I'm not
> sure it'd be right to specifically point to any Sentry contributors as
> an example.
>
>
Understood.


> I will say I can think of at least two Sentry contributors added since
> Sentry entered incubation who seem just as active as other folks who
> came in with the podling.  When you say "reached PPMC status" I'm not
> sure there's a clear signal to me that they're less worthy than the
> folks ushered in with the podling.
>
>
If that's the case as a ppmc member/mentor why not propose them for ppmc
membership, start a discussion thread for each I mean. Perhaps others
haven't seen the same thing you have, or more likely are not as sensitive
to it. It's a great learning opportunity for the mentees.


> You said it "sounds like" making more folks PPMC members is "in the
> pipeline" - do you mean if Sentry graduates, or is there some other
> discussion I've missed where that's being pondered?
>
>
I don't know what the community might do re promoting folks as part of
graduation. I've seen graduating projects do this in the past and it's
fine. But I think that's not addressing the real concern being raised here.
That's what I was trying to get at when I said "Seems artificial to me".
This would be another such example.

"Sounds like that's in the pipeline." I mean that mentors have given
feedback in the past about increasing (new) PPMC diversity, there are a
number of new committers that at active, it's just a matter of time. I'm
not aware of any explicit discussions at this time either.

Regards,

Patrick



> Best,
>
> jzb
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

I haven't seen the "quick closing" aside from things like some test
cleanups, even then the average was 5 days. I ran the jira report for
resolution time and it certainly doesn't seem like jiras are being closed
"instantly". Most of these are closed after many (typ. double digit, some
tripple) days.

https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12314720=daily=30=12314720=com.atlassian.jira.plugin.system.reports%3Aresolutiontime-report=Next

All of the jira events are forwarded to the Sentry mailing list, so from
the perspective of following along and getting an opportunity to respond I
haven't seen an issue. As Vinod mentioned many projects (e.g. hadoop)
operate in this manner. Jira is used to focus discussion and ensure there
is a record and an action item. ML discussion isn't discouraged, but it can
be hard to follow multiple threads of discussion/resolution.

Patrick


On Mon, Nov 2, 2015 at 10:09 AM, Joe Schaefer  wrote:

> Joe, can we see some jira tickets that you find questionable?  Hard to tell
> what the problem is just by scanning the email traffic.
>
> On Mon, Nov 2, 2015 at 1:06 PM, Vinod Vavilapalli  >
> wrote:
>
> > Missed that part, that sounds really bad.
> >
> > +Vinod
> >
> > On Nov 2, 2015, at 9:52 AM, Joe Brockmeier  j...@zonker.net>> wrote:
> >
> > Discussions are happening out of sight, and - in
> > Arvind's own words - "as if following a roadmap the community does not
> > have control over... that too is not an issue in my opinion at all."
> >
> >
>

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

I see this (the release discussion threads you linked) as a semi-mature
community that's well aligned. A number of folks responded to the request
for discussion and said they were in favor. It was done on the ML in the
open. What more do we want? I don't see anyone excluded and I'm sure if
there was a new person looking to get involved they would have been
welcomed into the discussion, no one is being turned away from what I can
see.

Patrick

On Mon, Nov 2, 2015 at 12:28 PM, Joe Brockmeier  wrote:

> On 11/02/2015 01:09 PM, Joe Schaefer wrote:
> > Joe, can we see some jira tickets that you find questionable?  Hard to
> tell
> > what the problem is just by scanning the email traffic.
>
> I'll (again) point to the previous conversation that came out of David's
> discussion with Sentry folks at ApacheCon [1] and then the reply from
> Arvind which basically says he doesn't consider it an issue if the
> project is "following a roadmap the community does not have control
> over... that too is not an issue in my opinion at all." [2]
>
> It's not specific tickets - it's (again) that there appears to be a lot
> of discussion and planning taking place off-list, out of sight. Take the
> 1.6.0 release discussion - no roadmap discussed for 1.6.0 at all, it
> just appeared [3] and then within 15 minutes there's an "I agree, and
> I'll be release manager!" [4] message and then several +1 / "I agree"
> messages, and then .. done. This looks a lot to me like planning and
> decisions happening off-list and then a cursory "discussion" for
> appearance's sake.
>
> How is a person who's not tapped into the Sentry development process
> already supposed to get involved? How is this building community? I see
> the Sentry podling creating code... just not much evidence of a
> community outside what Sentry came in with.
>
> [1] http://s.apache.org/611
> [2] http://s.apache.org/bhQ
> [3] http://s.apache.org/ZRV
> [4] http://s.apache.org/g9v
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

On Mon, Nov 2, 2015 at 1:55 PM, Joe Brockmeier  wrote:

> On 11/02/2015 04:41 PM, Sravya Tirukkovalur wrote:
> > I think it is a good sign that community is volunteering to do the
> release
> > work.
>
> I think the point I'm making is largely being ignored. I'm not seeing
> much room for volunteers, and a lot of indication that
> conversations/decisions are happening off list and being carried back
> rather than being done entirely openly.
>
>
Sorry, I don't think it's being ignored, just that the rest of us are not
able to see the same issues.

For example I see over 30 committers on the Sentry status page.
http://incubator.apache.org/projects/sentry.html
That doesn't indicate a project that's hard to join. Sentry has been in
incubation for over 2 years, it's pretty mature and as Sravya highlighted
there's a bunch of good information for folks trying to join. Above and
beyond jira and ML discussions.

Patrick


> > Here is the formal release work starting email[1] and discussing details
> on
> > when to branch and when to release giving sufficient time for everyone
> who
> > want to get their favorite jiras in. Dapeng (RM for 1.6.0) also started a
> > jira[2] to track the release work in detail:
>
> We might disagree on what constitutes "sufficient time" here - it looks
> like one week notice for the 1.6.0 branch, and then one week (planned)
> to release from there.
>
> > ". I will say that the only Jira I've seen from outside recently
> > didn't exactly get a warm reception. [1] Not rejected, just radio
> silence."
> >
> > That is not true, this is just one off instance. It has only been a week
> > since that jira has been created and I am sure one of us will review it
> > soon . But there are numerous instances where community was very
> welcoming
> > for new contributors and users[3][4][5]. In fact I feel proud to say that
> > community enabled many folks who filed bugs to also contribute bug fix
> > patches.
>
> OK, fair. I'll assume that's a one-off then, and apologize for missing
> the other examples.
>
> Best,
>
> jzb
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Patrick Hunt]

fwiw it's +9 by my count (24->33). Sentry is security, so by my definition
that's pretty good. ;-)

Patrick

On Mon, Nov 2, 2015 at 5:34 PM, Joe Schaefer  wrote:

> All of our projects are primarily in the recruitment business, so it does
> concern
> me that a project that's been here for over a year and hasn't managed to
> attract
> any new talent yet has some issues that need addressing.
>
> But that said I think you might be being a little hard on these guys Joe
> for failing in
> that regard.  If your advice is being ignored that's a problem, but if it's
> not and still
> no good outcomes yet, them's the breaks.  I wouldn't consider that a
> blocker for
> graduation if so.
>
>
> On Mon, Nov 2, 2015 at 6:15 PM, Upayavira  wrote:
>
> >
> >
> > On Mon, Nov 2, 2015, at 08:28 PM, Joe Brockmeier wrote:
> > > On 11/02/2015 01:09 PM, Joe Schaefer wrote:
> > > > Joe, can we see some jira tickets that you find questionable?  Hard
> to
> > tell
> > > > what the problem is just by scanning the email traffic.
> > >
> > > I'll (again) point to the previous conversation that came out of
> David's
> > > discussion with Sentry folks at ApacheCon [1] and then the reply from
> > > Arvind which basically says he doesn't consider it an issue if the
> > > project is "following a roadmap the community does not have control
> > > over... that too is not an issue in my opinion at all." [2]
> >
> > Joe, I'd encourage you to re-read what he says there under [2]. When he
> > says "following a roadmap the community doesn't control over" he seems
> > to be paraphrasing what has previously been stated, and when he says
> > "this is not an issue" it seems to me he is saying "this is not
> > happening" rather than "this doesn't bother me". It seems to me you are
> > misrepresenting him based upon this one email.
> >
> > > It's not specific tickets - it's (again) that there appears to be a lot
> > > of discussion and planning taking place off-list, out of sight. Take
> the
> > > 1.6.0 release discussion - no roadmap discussed for 1.6.0 at all, it
> > > just appeared [3] and then within 15 minutes there's an "I agree, and
> > > I'll be release manager!" [4] message and then several +1 / "I agree"
> > > messages, and then .. done. This looks a lot to me like planning and
> > > decisions happening off-list and then a cursory "discussion" for
> > > appearance's sake.
> > >
> > > How is a person who's not tapped into the Sentry development process
> > > already supposed to get involved? How is this building community? I see
> > > the Sentry podling creating code... just not much evidence of a
> > > community outside what Sentry came in with.
> >
> > I have no comment/perspective on the rest of this.
> >
> > Upayavira
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] Mentor neutrality policy

[Patrick Hunt]

10x to what Chris said, put much better than I could.

We all wear multiple hats, can't tell you the number of times I've worn my
Apache hat in the office, in some cases to my own detriment there. If I
weren't associated with the project at Apache that representation would be
missing. So really it cuts both ways.

Patrick


On Sat, Oct 10, 2015 at 7:49 AM, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> So here’s my elaboration.
>
> The proposal below would have prevented me from ever helping
> projects to the ASF and convincing them that it may be a good
> home for them. I’ve always had financial ties to a project’s
> Incubation status. In many cases, projects being at the ASF,
> and my involvement in them has assisted my mission of doing
> scientific research and helping win proposals and so forth for
> NASA and other agencies.
>
> Further, I’ve many times been at the same institution in which
> the project has originated from before the ASF.
>
> I think I’ve done a good job on the projects I’ve helped to
> bring here and they have been successful too and have overall
> benefitted the ASF.
>
> This rings to me very similar to Roy’s email circa 2012 I believe
> in which in the Incubator we tried to force the diversity requirement
> as a graduation requirement, and Roy succinctly explained that we
> can’t punish e.g., a podling for having people all from the same
> institution. That would punish that institution for hiring folks
> for open source who work on code at the ASF. Diversity is always
> a strong property of a podling as I feel it makes it more resilient
> but it’s not a hard requirement. I feel the same thing in this thread.
>
> Cheers,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
>
>
> -Original Message-
> From: jpluser 
> Reply-To: "general@incubator.apache.org" 
> Date: Friday, October 9, 2015 at 5:14 PM
> To: "general@incubator.apache.org" 
> Subject: Re: [DISCUSS] Mentor neutrality policy
>
> >I do not agree with this proposal I will elaborate more later
> >
> >Sent from my iPhone
> >
> >> On Oct 9, 2015, at 8:07 AM, Daniel Gruno  wrote:
> >>
> >> Hi Incubator folks,
> >>
> >> I would like to propose we adopt a mentor neutrality policy for
> >> incubating podlings:
> >>
> >> - A mentor must not be financially tied to the project or its incubation
> >> status.
> >> - A mentor must not have a vested interest in incubating, graduating or
> >> dismantling a podling that goes beyond the general Apache mission
> >> - A mentor must not be affiliated with the entity granting the code
> >> (company or original project community)
> >>
> >> Furthermore, I would like to see this extended to votes on graduating or
> >> retiring podlings, so that only people with no organizational (aparty
> >> from the ASF) or financial ties to the project (or the companies behind
> >> it) can cast a binding vote on graduation or retirement.
> >>
> >> This would essentially mean:
> >>
> >> - If you work for a company (or are hired as consultant/advisor) that is
> >> entering a project into incubation, you cannot mentor it nor vote
> >> for/against its incubation, graduation or retirement.
> >> - If you are a in the original community behind the project, you cannot
> >> mentor it nor vote for/against it.
> >>
> >> I believe this would create a neutral mentorship whose sole mission is
> >> to guide podlings with the interests of the ASF in mind.
> >>
> >>
> >> Please do discuss this. If there is (mostly) positive feedback, I would
> >> like to, at some point, have a vote on including this in the Incubator
> >> policy. I realize this would cut down on the number of potential
> >> mentors, and I would ask that more people step up to the challenge of
> >> mentoring if adopted.
> >>
> >> 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: June report prep

[Patrick Hunt]

I believe the podling community was interested to update the report,
however they were concerned about making changes after the cutoff
date. (didn't want to get into more process issues...)

I agree with Ted's reply about adding the additional detail he called
out in his response and moving forward.

Patrick

On Tue, Jun 9, 2015 at 6:53 PM, John D. Ament johndam...@apache.org wrote:
 So, I hate to bring this up, but I think we're at a stalemate for the
 sentry podling for this month.  We tend to not include a podlings report if
 there are no mentor sign offs.  It seems like the mentors aren't inclined
 to sign off based on some of the issues that have popped up.

 On Mon, Jun 8, 2015 at 12:35 PM Patrick Hunt ph...@apache.org wrote:

 Hi David, you and Joe have been doing great, I'm afraid I've been
 distracted with more issues at home/work than usual. I've been
 concerned, and this is more serious than usual given the fact that
 both the community and the oversight missed a serious issue, but given
 the current feedback and the response (ongoing) from the community we
 should be able to get things back on track.

 Thanks,

 Patrick

 On Sat, Jun 6, 2015 at 3:14 PM, David Nalley da...@gnsa.us wrote:
  On Fri, Jun 5, 2015 at 3:23 PM, Patrick Hunt ph...@apache.org wrote:
  Ted can you give some concrete examples, because I see some good
 feedback
  along with folks attempting to address the feedback. Processes updated
 or
  re-iterated, etc... I haven't seen any comments like stop the presses
  till... is addressed and that being ignored. More along the lines of an
  issue being raised and the community immediately working to address it.
 For
  example most recently giving more time to construct the board report.
 
  Failing to cc general@ on the vote is a serious issue. That's part of
 the
  release process though, it's documented and been followed in previous
  releases. Human error this time around afaict (along with the mentors,
  myself included, who didn't notice it till later)
  https://cwiki.apache.org/confluence/display/SENTRY/How+to+Release
 
  They seem oblivious to process issues
 
  Are there specific process issues that are missing and should hold up a
  vote? I see alot of process related details on their wiki
  https://cwiki.apache.org/confluence/display/SENTRY/Home
 
  Patrick
 
 
 
  Patrick,
 
  I agree with most of what you wrote. In many ways I'm worried that
  this is a failure on the part of mentors. Very early, this morning in
  Tokyo, it dawned on me that perhaps the mentors (esp. me) are part of
  the problem. This isn't the first time that issues have been called
  out with Sentry - and there does seem to be willingness to address
  issues on the part of the project. 'We keep saying $n is problematic'
  - and I worry (and am certainly guilty in my case) of assuming
  everyone largely 'gets it'. I've also not shown them specific concrete
  examples of some types of non-problematic behavior. By the time most
  folks become a member, or join the IPMC, the Apache way of doing
  things is second nature, and we don't always realize that it may be
  completely foreign to folks who haven't been doing it for as long.
 
  I've just sent a long email to dev@ to hopefully make this clearer,
  call out some examples, and hopefully generate a discussion on how we
  move forward.
 
  --David
 
  -
  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: June report prep

[Patrick Hunt]

Hi David, you and Joe have been doing great, I'm afraid I've been
distracted with more issues at home/work than usual. I've been
concerned, and this is more serious than usual given the fact that
both the community and the oversight missed a serious issue, but given
the current feedback and the response (ongoing) from the community we
should be able to get things back on track.

Thanks,

Patrick

On Sat, Jun 6, 2015 at 3:14 PM, David Nalley da...@gnsa.us wrote:
 On Fri, Jun 5, 2015 at 3:23 PM, Patrick Hunt ph...@apache.org wrote:
 Ted can you give some concrete examples, because I see some good feedback
 along with folks attempting to address the feedback. Processes updated or
 re-iterated, etc... I haven't seen any comments like stop the presses
 till... is addressed and that being ignored. More along the lines of an
 issue being raised and the community immediately working to address it. For
 example most recently giving more time to construct the board report.

 Failing to cc general@ on the vote is a serious issue. That's part of the
 release process though, it's documented and been followed in previous
 releases. Human error this time around afaict (along with the mentors,
 myself included, who didn't notice it till later)
 https://cwiki.apache.org/confluence/display/SENTRY/How+to+Release

 They seem oblivious to process issues

 Are there specific process issues that are missing and should hold up a
 vote? I see alot of process related details on their wiki
 https://cwiki.apache.org/confluence/display/SENTRY/Home

 Patrick



 Patrick,

 I agree with most of what you wrote. In many ways I'm worried that
 this is a failure on the part of mentors. Very early, this morning in
 Tokyo, it dawned on me that perhaps the mentors (esp. me) are part of
 the problem. This isn't the first time that issues have been called
 out with Sentry - and there does seem to be willingness to address
 issues on the part of the project. 'We keep saying $n is problematic'
 - and I worry (and am certainly guilty in my case) of assuming
 everyone largely 'gets it'. I've also not shown them specific concrete
 examples of some types of non-problematic behavior. By the time most
 folks become a member, or join the IPMC, the Apache way of doing
 things is second nature, and we don't always realize that it may be
 completely foreign to folks who haven't been doing it for as long.

 I've just sent a long email to dev@ to hopefully make this clearer,
 call out some examples, and hopefully generate a discussion on how we
 move forward.

 --David

 -
 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: June report prep

[Patrick Hunt]

Ted can you give some concrete examples, because I see some good feedback
along with folks attempting to address the feedback. Processes updated or
re-iterated, etc... I haven't seen any comments like stop the presses
till... is addressed and that being ignored. More along the lines of an
issue being raised and the community immediately working to address it. For
example most recently giving more time to construct the board report.

Failing to cc general@ on the vote is a serious issue. That's part of the
release process though, it's documented and been followed in previous
releases. Human error this time around afaict (along with the mentors,
myself included, who didn't notice it till later)
https://cwiki.apache.org/confluence/display/SENTRY/How+to+Release

 They seem oblivious to process issues

Are there specific process issues that are missing and should hold up a
vote? I see alot of process related details on their wiki
https://cwiki.apache.org/confluence/display/SENTRY/Home

Patrick

On Fri, Jun 5, 2015 at 8:03 AM, Ted Dunning ted.dunn...@gmail.com wrote:

 I don't think that the Sentry PPMC actually disagrees with the mentor's
 recommendation (and, in fact, at least one person agreed to reverting to
 monthly reports).

 But in reading the last 4 months of traffic on the dev list, I really don't
 think that the PPMC has internalized the critique at all either.  They seem
 oblivious to process issues and have even voted to try to proceed with
 graduation without really noticing that there are problems.

 This indicates (to me) that the Incubator shepherds and project mentors are
 largely not being understood by the PPMC.  Neither are the release
 procedures being internalized.  The result is that the conversation tends
 to go a bit like

 MENTOR: I see a serious problem X
 PPMC: We will have to address that in the future
 ...
 PPMC: Let's release
 ...
 MENTOR: I see a serious problem Y with your release
 PPMC: We will have to address that in the future
 ...
 ...
 PPMC: Let's graduate


 There is never an argument or contradiction to the assertion of a problem,
 but there doesn't seem to be much attention paid either.  My impression is
 that the community is not actually reading the dev list very carefully.




 On Fri, Jun 5, 2015 at 3:23 PM, John D. Ament john.d.am...@gmail.com
 wrote:

  Does the Sentry podling (PPMC) disagree with their mentors
 recommendation?
  I agree with the mentors proposal for both and actually raised this last
  month as an issue.
 
  John
 
  On Fri, Jun 5, 2015 at 8:56 AM Ted Dunning ted.dunn...@gmail.com
 wrote:
 
   Marvin,
  
   Thanks as ever for the coaching.
  
   One question that has come in from David Nalley is how to deal with the
   issue of Sentry.  They have had some problems with process and seem not
  to
   recognize that in the report.  David suggests reverting to monthly
  reports
   as we try to clear up the questions.  I suggest adding a note to the
   report. The situation is a bit problematic because there are several
  people
   in the project who should understand process better and raise this
 issue
   themselves.
  
  
   On Fri, Jun 5, 2015 at 8:37 AM, Marvin Humphrey 
 mar...@rectangular.com
   wrote:
  
On Tue, May 26, 2015 at 8:38 PM, Ted Dunning ted.dunn...@gmail.com
wrote:
 On Tue, May 26, 2015 at 4:35 PM, Marvin Humphrey 
   mar...@rectangular.com

 wrote:

 The responsibilities of the Report Manager are documented using a
script,
 report_runbook.py, which generates all the necessary commands.
 Ted,
please
 try running this from a checkout of the Incubator Subversion repo:

 python3 report_runbook.py --month=6 --apache-id=tdunning

 The first action of the June report cycle is to send the
 timeline
email
 to general@incubator.  This should be done by the last Wednesday
 of
   the
 month, so that people see it a full week before podling reports
 are
   due.
 Here's a sample:

 Yay!

 With the correct version of python, this now works for me.  We
 won't
   know
 what problems I had before, but I don't plan to care too much.
   
Hi Ted,
   
Now that the deadline has passed for filing podling reports, we can
perform a
few more actions.
   
*   Normalize podling report formatting.
*   Generate list of releases.
*   Categorize the podlings by stage of incubation and create the
  podling
summary.
*   Edit podlings.xml to assign podlings who did not report a
 monthly
   tag
so that they don't fall through the cracks.  See
http://s.apache.org/At0.
   
See the output of report_runbook.py for more detailed instructions
 and
   let
us
know if you have questions.
   
I'll work on the narrative section either tomorrow or Saturday.
   
The goal is to have everything done by Sunday night so that we can
 send
out a
mature draft on Monday.
   
Marvin Humphrey
   

Re: [VOTE] Release Sentry incubating version 1.5.0 (rc0)

[Patrick Hunt]

+1 - xsum/sig are valid. Rat ran clean. Ran through the release checklist
and everything seems fine there.

Patrick

On Sun, May 31, 2015 at 7:11 PM, gqshen gqs...@apache.org wrote:

 Hello IPMC
 We have passed the PPMC vote for Sentry incubator release 1.5.0-rc0 with 3
 +1  votes from Prasad Mujumdar, Lenni Kuff and Sean Mackrory.  We ask for
 your help to vote on this incubator release.

 This is the incubator release of Apache Sentry, version 1.5.0-incubating.
 The list of fixed issues, added features and improvements can be found
 here:

 https://git-wip-us.apache.org/repos/asf?p=incubator-sentry.git;a=blob;f=CHANGELOG.txt;h=5d96434653aa292dfd025c7baa876013e95a5a15;hb=refs/heads/branch-1.5.0

 Source files : http://people.apache.org/~gqshen/sentry-1.5.0-rc0/

 Tag to be voted on (release 1.5.0-rc0/SHA:
 589ea2c36f7bbec2affbddf10c3320178fdec9bf):

 https://git-wip-us.apache.org/repos/asf?p=incubator-sentry.git;a=commit;h=589ea2c36f7bbec2affbddf10c3320178fdec9bf
 Sentry's KEYS containing the PGP key we used to sign the release:
 http://www.apache.org/dist/incubator/sentry/KEYS

 Note that this is a source only release and we are voting on the source:
 tag=release-1.5.0-rc0, SHA=589ea2c36f7bbec2affbddf10c3320178fdec9bf

 Vote will be opened for 72 hours.

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

 Thank you for your prompt votes.

 Respectfully,

 Sentry 1.5.0 Release Manager (Guoquan Shen)

Re: [VOTE] Release Apache Twill-0.5.0-incubating

[Patrick Hunt]

+1. the sig/xsum validate. Rat ran clean and the files all look right to me.

Patrick

On Wed, Feb 25, 2015 at 5:36 PM, Henry Saputra henry.sapu...@gmail.com wrote:
 Signature file look good
 Checksum files looks good
 NOTICE file looks good
 LICENSE file look good
 DISCLAIMER file exist
 No third party executables
 Source code compiled

 +1 (binding)

 Congrats!



 On Tue, Feb 24, 2015 at 12:52 PM, Terence Yim cht...@apache.org wrote:
 Hi all,

 This is to call for a vote on releasing Apache Twill 0.5.0-incubating.
 This is the sixth release for Twill.

 Apache Twill is an abstraction over Apache Hadoop YARN that reduces
 the complexity of developing distributed applications.

 Vote on twill-dev:
 http://s.apache.org/lfz

 Result on vote on twill-dev:
 http://s.apache.org/YQY

 The source tarball, including signatures, digests, etc can be found at:
 https://dist.apache.org/repos/dist/dev/incubator/twill/0.5.0-incubating-rc1/src/

 The tag to be voted upon is v0.5.0-incubating:
 https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=shortlog;h=refs/tags/v0.5.0-incubating

 The release hash is 01cbe903b37eb981b8fab0bde9d9ff0f7dc4fd5c
 https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=commit;h=01cbe903b37eb981b8fab0bde9d9ff0f7dc4fd5c

 The Nexus Staging URL:
 https://repository.apache.org/content/repositories/orgapachetwill-1016

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

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

 For information about the contents of this release see:
 https://dist.apache.org/repos/dist/dev/incubator/twill/0.5.0-incubating-rc1/CHANGES.txt

 Please vote on releasing this package as Apache Twill 0.5.0-incubating

 The vote will be open for 72 hours.

 [ ] +1 Release this package as Apache Twill 0.5.0-incubating
 [ ] +0 no opinion
 [ ] -1 Do not release this package because ...

 Thanks,
 Terence

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


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


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

Re: [VOTE] Release Apache Twill-0.4.1.-incubating

[Patrick Hunt]

+1 - xsums/sig verify, RAT ran clean and the appropriate files are there.

Note: for some reason the sha512 file is gzip'd (at least it was when
I d/l it via chrome), not a text file. However if you un-gzip it the
sha512 matches.

Patrick

On Mon, Feb 2, 2015 at 11:21 PM, Henry Saputra henry.sapu...@gmail.com wrote:
 NOTICE file needs to have year updated but not blocker and JIRA is
 filed: TWILL-114
 LICENCE file looks good
 DISCLAIMER file looks good
 Hash files look good
 Signature file look good
 No 3rd party executable in source artifact

 +1 (binding)

 - Henry

 On Mon, Feb 2, 2015 at 10:18 AM, Terence Yim cht...@apache.org wrote:
 Hi all,

 This is to call for a vote for releasing twill-0.4.1-incubating. This
 is the fifth release for Twill.

 Vote on twill-dev:
 http://s.apache.org/HKb

 Result on vote on twill-dev:
 http://s.apache.org/921

 The source tarball, including signatures, digests, etc can be found at:
 https://dist.apache.org/repos/dist/dev/incubator/twill/0.4.1-incubating-rc3/src

 The tag to be voted upon is v0.4.1-incubating:
 https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=shortlog;h=refs/tags/v0.4.1-incubating

 The release hash is d2bebf3f016e77e6fb12bf8297053c7b081e92a5
 https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=commit;h=d2bebf3f016e77e6fb12bf8297053c7b081e92a5

 The Nexus Staging URL:
 https://repository.apache.org/content/repositories/orgapachetwill-1011

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

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

 For information about the contents of this release see:
 https://dist.apache.org/repos/dist/dev/incubator/twill/0.4.1-incubating-rc3/CHANGES.txt

 Please vote on releasing this package as Apache Twill 0.4.1-incubating

 The vote will be open for 72 hours.

 [ ] +1 Release this package as Apache Twill 0.4.1-incubating
 [ ] +0 no opinion
 [ ] -1 Do not release this package because ...

 Thanks,
 The Apache Twill Team

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


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


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

Re: [VOTE] Release Apache Parquet Format (incubating) 2.2.0 RC2

[Patrick Hunt]

+1 sig/xsum are valid. RAT ran clean and the checklist looks fine to
me (license/notice/disclaimer/etc... are all good, etc...)

Patrick

On Mon, Nov 10, 2014 at 2:35 PM, Ryan Blue b...@apache.org wrote:
 Hi everyone,

 I'd like to propose a vote to release parquet-format-2.2.0-rc2 as the
 official Parquet Format 2.2.0 release.

 This release candidate has passed a podling vote, which can be found here:

 https://mail-archives.apache.org/mod_mbox/incubator-parquet-dev/201411.mbox/%3C54613B48.6060602%40apache.org%3E

 The release candidate, signature, and checksums are available at:
   https://dist.apache.org/repos/dist/dev/incubator/parquet/2.2.0-rc2/

 The branch used to create the release candidate is:

 https://git-wip-us.apache.org/repos/asf?p=incubator-parquet-format.git;hb=release-2.2.0-rc2

 KEYS to validate the signature are available at:
   https://dist.apache.org/repos/dist/dev/incubator/parquet/KEYS

 Please download, verify, and test.

 [ ] +1: Release this tag as parquet-format-2.2.0
 [ ] +0:
 [ ] -1: This release is not ready because . . .


 == More details ==

 This will be the first release from the Parquet project. We are releasing
 parquet-format first because the other projects (parquet-mr and parquet-cpp)
 depend on it.

 This release uses the pre-Apache maven coordinate com.twitter:parquet-format
 and parquet.* package names. To make the transition to org.apache naming as
 smooth as possible for downstream projects, we are planning to release a
 com.twitter artifact immediately followed by an org.apache artifact. These
 artifacts will be identical except for naming changes:

 * com.twitter:parquet-format = org.apache.parquet:parquet-format
 * package parquet.* = package org.apache.parquet.*

 There are three major changes included in this release:
 * PARQUET-119: Add encoding stats to ColumnMetaData
 * PARQUET-79: Streaming thrift API
 * PARQUET-12: New logical types


 rb


 --
 Ryan Blue

 -
 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: Request for mentor assessment

[Patrick Hunt]

The S4 retirement vote is in progress:
http://markmail.org/message/mkxdu6fnzmsybeq2

Patrick

On Wed, Jun 11, 2014 at 4:33 PM, Roman Shaposhnik r...@apache.org wrote:
 Hi!

 I would like to kindly request some assistance
 from the mentors of the following projects: devicemap,
 kalumet, s4, wave and npanday (all CCed).

 I would like to figure out whether the concerns I have
 for these projects are justified and if they are, what
 would be the proposed steps for the IPMC.

 To be more specific:
* DeviceMap has been in the incubator since
   2012-01-03. It seems like it is still struggling
   with the basics: producing releases and growing
   its PMC. What's the recommendation here?

* Kalumet has been in the incubator since 2011-09-20.
  On one hand, it may be ready to graduate, but there
  are also a few troubling signs. We need to get
  recommendation on how to proceed.

* S4 seems to be on a trajectory for retirement. Can we,
   please, have mentors initiate that discussion in the
   community and follow up on general@ ?

* Wave is similar to Kalumet in that its been incubating
   for a very long time (since 2010-12-01) but still show
   troubling signs of lack of activity, lack of releases and
   active PMC involvement.

* NPanday has been incubating since 2010-08-13. Has
   a pretty consistent track record of missing reports and
   low amount of activity.

 And speaking of NPanday it seems to also have an additional
 complication of mentors missing in action. I am also looking
 for ideas of how to fix that. The best thought I have so far
 is to ask for volunteers to step in and help.

 Anyway, to make long story short, if mentors could check
 back with their projects and reply to this thread with
 concrete assessments and recommendations that would
 be awesome.

 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: [VOTE] Release Sentry 1.3.0 incubating rc0

[Patrick Hunt]

-1. The release artifact seems to be totally wrong to me, I think it
was built incorrectly/accidentally, it certainly wasn't built the same
way as the 1.2.0 release artifact.

Some of the problems:
1) the artifact is 500MB - the previous artifact (1.2.0) was 86k,
unless you added tons of test data I think this should be a red
flag...
2) it contains a lib directory with tons of third party binary artifacts
3) many of the required files are missing (such as DISCLAIMER)

Are you following the how to release process? Perhaps it's not
updated per the last release?
https://cwiki.apache.org/confluence/display/SENTRY/How+to+Release

I think you need to step back and look into what happened. Compare the
release artifact that you generate to the previous release. Read and
understand the details here before you attempt to cut a release:
http://incubator.apache.org/guides/releasemanagement.html

Patrick

On Wed, Mar 26, 2014 at 6:32 PM, Ramachandran, Karthik
kramachand...@iqt.org wrote:
 This is a release of Apache Sentry, version 1.3.0-incubating


 It fixes the following issues: http://s.apache.org/Ckp

 Source files : http://people.apache.org/~kramachandran/sentry-1.3.0-rc0/

 Tag to be voted on (rc0): 
 https://git-wip-us.apache.org/repos/asf/incubator-sentry/repo?p=incubator-sentry.git;a=log;h=refs/tags/release-1.3.0-rc0

 Sentry's KEYS containing the PGP key we used to sign the release:
 https://people.apache.org/keys/group/sentry.asc

 Note that this is a source only release and we are voting on the source (tag).


 Vote will be open for 72 hours.

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


 Thanks,

 Karthik Ramachandran

 ---
 Lab41 Team Manager
 In-Q-Tel /  Lab41
 Cell: 571-455-5576
 E-mail: kramachand...@iqt.orgmailto:kramachand...@iqt.org , 
 kramachand...@apache.org



 This e-mail, and any attachments hereto, may contain information that is 
 privileged, proprietary, confidential and/or exempt from disclosure under law 
 and are intended only for the designated addressee(s). If you are not the 
 intended recipient of this message, or a person authorized to receive it on 
 behalf of the intended recipient, you are hereby notified that you must not 
 use, disseminate, copy in any form, or take any action based upon the email 
 or information contained therein. If you have received this email in error, 
 please permanently and immediately delete it and any copies of it, including 
 any attachments, and promptly notify the sender at In-Q-Tel by reply e-mail, 
 fax: 703-248-3001, or phone: 703-248-3000. Thank you for your cooperation.

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

Re: [VOTE] Release of Apache Twill 0.1.0-incubating [rc1]

[Patrick Hunt]

+1, looks good to me. (I'd suggest you verify that your mentors are
all signed up, it's pretty easy using the list command on your
private ML)

Patrick

On Sat, Feb 1, 2014 at 2:02 PM, Terence Yim cht...@gmail.com wrote:
 Hi Patrick,

 I've updated the status page yesterday with dates (both Incubation
 status reports and Project setup section). Is it not update enough?

 Thanks,
 Terence

 On Sat, Feb 1, 2014 at 1:13 PM, Patrick Hunt ph...@apache.org wrote:
 -1, the release looks good however the status page needs to be updated
 before you publish this (generally, but specifically see the Project
 Setup section):
 http://incubator.apache.org/projects/twill.html

 If you're not familiar with the mechanics of this see:
 http://incubator.apache.org/guides/website.html#Edit+your+project+status+page

 Patrick

 On Fri, Jan 31, 2014 at 4:42 PM, Terence Yim cht...@gmail.com wrote:
 Hi all,

 This is to call for a vote for release of Apache Twill
 v0.1.0-incubating. This will be the first incubator release for Apache
 Twill.

 Vote on twill-dev:
 http://s.apache.org/Rsy

 Result on vote on twill-dev:
 http://s.apache.org/KMR

 The tag to be voted upon is v0.1.0-incubating:
 https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=tag;h=refs/tags/v0.1.0-incubating

 The source tarball, including signatures, digests, etc can be found at:
 https://dist.apache.org/repos/dist/dev/incubator/twill/0.1.0-incubating-rc1/src

 The binary artifacts can be found at:
 https://dist.apache.org/repos/dist/dev/incubator/twill/0.1.0-incubating-rc1/bin

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

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

 For information about the contents of this release see:
 https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=log;h=refs/tags/v0.1.0-incubating

 Please vote on releasing this package as Apache Twill 0.1.0-incubating

 The vote will be open for 72 hours.

 [ ] +1 Release this package as Apache Twill 0.1.0-incubating
 [ ] -1 Do not release this package because ...

 Thanks,
 Apache Twill Team

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


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


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

Re: [VOTE] Release of Apache Twill 0.1.0-incubating [rc1]

[Patrick Hunt]

-1, the release looks good however the status page needs to be updated
before you publish this (generally, but specifically see the Project
Setup section):
http://incubator.apache.org/projects/twill.html

If you're not familiar with the mechanics of this see:
http://incubator.apache.org/guides/website.html#Edit+your+project+status+page

Patrick

On Fri, Jan 31, 2014 at 4:42 PM, Terence Yim cht...@gmail.com wrote:
 Hi all,

 This is to call for a vote for release of Apache Twill
 v0.1.0-incubating. This will be the first incubator release for Apache
 Twill.

 Vote on twill-dev:
 http://s.apache.org/Rsy

 Result on vote on twill-dev:
 http://s.apache.org/KMR

 The tag to be voted upon is v0.1.0-incubating:
 https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=tag;h=refs/tags/v0.1.0-incubating

 The source tarball, including signatures, digests, etc can be found at:
 https://dist.apache.org/repos/dist/dev/incubator/twill/0.1.0-incubating-rc1/src

 The binary artifacts can be found at:
 https://dist.apache.org/repos/dist/dev/incubator/twill/0.1.0-incubating-rc1/bin

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

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

 For information about the contents of this release see:
 https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=log;h=refs/tags/v0.1.0-incubating

 Please vote on releasing this package as Apache Twill 0.1.0-incubating

 The vote will be open for 72 hours.

 [ ] +1 Release this package as Apache Twill 0.1.0-incubating
 [ ] -1 Do not release this package because ...

 Thanks,
 Apache Twill Team

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

Re: [VOTE] Graduation of Apache Spark from the Incubator

[Patrick Hunt]

+1

Patrick

On Fri, Jan 31, 2014 at 6:04 PM, Matei Zaharia matei.zaha...@gmail.com wrote:
 Hi folks,

 The Apache Spark community has VOTEd to graduate from the Apache incubator 
 (vote thread: http://s.apache.org/kq, discussion thread: 
 http://s.apache.org/aEQ).

 I'm now calling an official IPMC VOTE to make this happen as well. Here's the 
 community tally:

 +1
 Matei Zaharia
 Reynold Xin
 Tathagata Das
 Sean McNamara
 Patrick Wendell
 Mark Hamstra
 Chris Mattmann *
 Tom Graves
 Henry Saputra *
 Andy Konwinski
 Josh Rosen
 Mosharaf Chowdhury
 Mridul Muralidharan
 Nick Pentreath
 Andrew Xia
 Haoyuan Li
 Sandy Ryza
 Sebastian Schelter *
 Kostas Sakellis
 Christopher Nguyen
 Aaron Davidson
 Shivaram Venkataraman
 Kay Ousterhout
 Evan Sparks
 Xuefeng Wu
 Konstantin Boudnik
 Rahul Chugh
 Prashant Sharma
 Stephen Haberman
 Prabeesh K.
 Saisai Shao
 Junfeng Feng
 Jason Dai
 Stevo Slavic
 Heiko Braun
 Xia Zhu
 Manoj Awasthi

 +0
 (none)

 -1
 (none)

 * indicates IPMC member

 We've made three releases in the incubator, added new committers and IPMC 
 members, checked off the various requirements to migrate the development 
 process to the ASF, and more generally worked to build this community in the 
 Apache way.

 Please VOTE to graduate Apache Spark from the incubator. I'll leave the VOTE 
 open for 96 hours, until February 4th, 2014. The graduation resolution is 
 pasted below.

 Thanks!

 Matei and the Apache Spark community

  snip

 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 fast and flexible large-scale data analysis
 on clusters.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the Apache Spark Project, be
 and hereby is established pursuant to Bylaws of the Foundation;
 and be it further

 RESOLVED, that the Apache Spark Project be and hereby is
 responsible for the creation and maintenance of software
 related to efficient cluster management, resource isolation
 and sharing across distributed applications; and be it further
 RESOLVED, that the office of Vice President, Apache Spark 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 Spark Project, and to have primary responsibility for
 management of the projects within the scope of responsibility
 of the Apache Spark 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 Spark Project:

 * Mosharaf Chowdhury mosha...@apache.org
 * Jason Dai jason...@apache.org
 * Tathagata Das t...@eecs.berkeley.edu
 * Ankur Dave ankurd...@gmail.com
 * Aaron Davidson aarondavid...@berkeley.edu
 * Thomas Dudziak to...@apache.org
 * Robert Evans bo...@apache.org
 * Thomas Graves tgra...@apache.org
 * Andy Konwinski and...@apache.org
 * Stephen Haberman steph...@apache.org
 * Mark Hamstra markhams...@apache.org
 * Shane Huang shane_hu...@apache.org
 * Ryan LeCompte ryanlecom...@apache.org
 * Haoyuan Li haoy...@apache.org
 * Sean McNamara mcnam...@apache.org
 * Mridul Muralidharam mrid...@yahoo-inc.com
 * Kay Ousterhout k...@eecs.berkeley.edu
 * Nick Pentreath mln...@apache.org
 * Imran Rashid im...@quantifind.com
 * Charles Reiss wog...@apache.org
 * Josh Rosen joshro...@apache.org
 * Prashant Sharma prash...@apache.org
 * Ram Sriharsha harsh...@yahoo-inc.com
 * Shivaram Venkataraman shiva...@apache.org
 * Patrick Wendell pwend...@apache.org
 * Andrew Xia xiajunl...@gmail.com
 * Reynold Xin r...@apache.org
 * Matei Zaharia ma...@apache.org

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matei Zaharia be
 appointed to the office of Vice President, Apache Spark, to
 serve in accordance with and subject to the direction of the
 Board of Directors and the Bylaws of the Foundation until
 death, resignation, retirement, removal or disqualification, or
 until a successor is appointed; and be it further

 RESOLVED, that the Apache Spark Project be and hereby is
 tasked with the migration and rationalization of the Apache
 Incubator Spark podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Spark 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] Release Apache Spark 0.9.0-incubating (rc5)

[Patrick Hunt]

Hi Patrick, prior to any incubator release you should ensure that your
status page is up to date. The Project Setup section in particular:

http://incubator.apache.org/projects/spark.html

Patrick

On Mon, Jan 27, 2014 at 12:02 AM, Patrick Wendell pwend...@gmail.com wrote:
 Please vote on releasing the following candidate as Apache Spark
 (incubating) version 0.9.0.

 A vote on this release has passed within the Spark PPMC.

 The tag to be voted on is v0.9.0-incubating (commit 95d28ff3):
 https://git-wip-us.apache.org/repos/asf?p=incubator-spark.git;a=commit;h=95d28ff3d0d20d9c583e184f9e2c5ae842d8a4d9

 The release files, including signatures, digests, etc can be found at:
 http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5

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

 The list of keys associated with Spark is available at:
 https://people.apache.org/keys/group/spark.asc

 The staging repository for this release can be found at:
 https://repository.apache.org/content/repositories/orgapachespark-1006/

 The documentation corresponding to this release can be found at:
 http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5-docs/

 Please vote on releasing this package as Apache Spark 0.9.0-incubating!

 The vote is open until Thursday, January 30, at 08:05 UTC
 and passes if a majority of at least 3 +1 IPMC votes are cast.

 [ ] +1 Release this package as Apache Spark 0.9.0-incubating
 [ ] -1 Do not release this package because ...

 To learn more about Apache Spark, please see
 http://spark.incubator.apache.org/

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


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

Re: [VOTE] Release Apache Spark 0.9.0-incubating (rc5)

[Patrick Hunt]

-1 due to the status page not being up to date. But otw the sig/xsums
looked good, RAT checked out clean and I ran through the release
checklist which looks ok. If you fix the status I'll change my vote to
+1.

A couple nits that I noticed (but not to hold a rel for):

* your notice files should be updated for 2014

* the release artifact (spark-0.9.0-incubating.tgz) is missing the
DISCLAIMER file, I see that the text is included in the readme, this
is somewhat non-standard but seems fine.

Patrick

On Thu, Jan 30, 2014 at 2:50 PM, Patrick Hunt ph...@apache.org wrote:
 Hi Patrick, prior to any incubator release you should ensure that your
 status page is up to date. The Project Setup section in particular:

 http://incubator.apache.org/projects/spark.html

 Patrick

 On Mon, Jan 27, 2014 at 12:02 AM, Patrick Wendell pwend...@gmail.com wrote:
 Please vote on releasing the following candidate as Apache Spark
 (incubating) version 0.9.0.

 A vote on this release has passed within the Spark PPMC.

 The tag to be voted on is v0.9.0-incubating (commit 95d28ff3):
 https://git-wip-us.apache.org/repos/asf?p=incubator-spark.git;a=commit;h=95d28ff3d0d20d9c583e184f9e2c5ae842d8a4d9

 The release files, including signatures, digests, etc can be found at:
 http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5

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

 The list of keys associated with Spark is available at:
 https://people.apache.org/keys/group/spark.asc

 The staging repository for this release can be found at:
 https://repository.apache.org/content/repositories/orgapachespark-1006/

 The documentation corresponding to this release can be found at:
 http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5-docs/

 Please vote on releasing this package as Apache Spark 0.9.0-incubating!

 The vote is open until Thursday, January 30, at 08:05 UTC
 and passes if a majority of at least 3 +1 IPMC votes are cast.

 [ ] +1 Release this package as Apache Spark 0.9.0-incubating
 [ ] -1 Do not release this package because ...

 To learn more about Apache Spark, please see
 http://spark.incubator.apache.org/

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


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

Re: [VOTE] Release Apache Spark 0.9.0-incubating (rc5)

[Patrick Hunt]

The status page is updated and it looks good to me.

+1 Release this package as Apache Spark 0.9.0-incubating

Patrick

On Thu, Jan 30, 2014 at 3:34 PM, Patrick Hunt ph...@apache.org wrote:
 -1 due to the status page not being up to date. But otw the sig/xsums
 looked good, RAT checked out clean and I ran through the release
 checklist which looks ok. If you fix the status I'll change my vote to
 +1.

 A couple nits that I noticed (but not to hold a rel for):

 * your notice files should be updated for 2014

 * the release artifact (spark-0.9.0-incubating.tgz) is missing the
 DISCLAIMER file, I see that the text is included in the readme, this
 is somewhat non-standard but seems fine.

 Patrick

 On Thu, Jan 30, 2014 at 2:50 PM, Patrick Hunt ph...@apache.org wrote:
 Hi Patrick, prior to any incubator release you should ensure that your
 status page is up to date. The Project Setup section in particular:

 http://incubator.apache.org/projects/spark.html

 Patrick

 On Mon, Jan 27, 2014 at 12:02 AM, Patrick Wendell pwend...@gmail.com wrote:
 Please vote on releasing the following candidate as Apache Spark
 (incubating) version 0.9.0.

 A vote on this release has passed within the Spark PPMC.

 The tag to be voted on is v0.9.0-incubating (commit 95d28ff3):
 https://git-wip-us.apache.org/repos/asf?p=incubator-spark.git;a=commit;h=95d28ff3d0d20d9c583e184f9e2c5ae842d8a4d9

 The release files, including signatures, digests, etc can be found at:
 http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5

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

 The list of keys associated with Spark is available at:
 https://people.apache.org/keys/group/spark.asc

 The staging repository for this release can be found at:
 https://repository.apache.org/content/repositories/orgapachespark-1006/

 The documentation corresponding to this release can be found at:
 http://people.apache.org/~pwendell/spark-0.9.0-incubating-rc5-docs/

 Please vote on releasing this package as Apache Spark 0.9.0-incubating!

 The vote is open until Thursday, January 30, at 08:05 UTC
 and passes if a majority of at least 3 +1 IPMC votes are cast.

 [ ] +1 Release this package as Apache Spark 0.9.0-incubating
 [ ] -1 Do not release this package because ...

 To learn more about Apache Spark, please see
 http://spark.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: S4 Podling - May need some help

[Patrick Hunt]

On Fri, Dec 6, 2013 at 1:37 PM, Henry Saputra henry.sapu...@gmail.com wrote:
 Any updates from the mentors?


I reviewed/signedoff on the report. I've commented both in public and
in private to the s4 folks that they should consider retirement as an
option. I was/am waiting to see what the community decides.

Patrick

 I remember there were some sparks shown to re-energize the community
 about few months ago like to have weekly chats

 - Henry

 On Fri, Dec 6, 2013 at 4:10 AM, John D. Ament john.d.am...@gmail.com wrote:
 Hi,

 I completed my shepherd review of S4 now that their board report is in
 place.  Here's a copy:

 The board report reflects my sentiments as well.  S4 seems to be in a
 bit of rut.  I tried kicking off some conversations on the dev mailing
 list, no luck.  It seems like there are at best five active
 participants, between the users list and dev list.  Considering that
 there hasn't been a commit since last board report, it doesn't come
 off as a good sign for me.  I think retirement may be an option to
 start exploring.

 It seems like through a combination of low dev activity and low user
 feedback S4 is having difficulty progressing.

 -
 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: [RESULT] [VOTE] Accept Twill for Incubation

[Patrick Hunt]

FYI my vote is binding. :-)

Patrick

On Tue, Nov 12, 2013 at 2:42 PM, Andreas Neumann a...@apache.org wrote:
 The vote has passed with 13 binding and 10 non-binding +1 votes and no +0
 or -1 votes. We are looking forward to the next steps.
 -Andreas.

 Binding (+1)

1. Roman Shaposhnik
2. Doug Cutting
3. Oliver Lamy
4. Ted Dunning
5. Arun C. Murthy
6. Andrei Savu
7. Arvind Prabhakar
8. Henry Saputra
9. Marvin Humphrey
10. Suresh Marru
11. Jean-Baptiste Onofre
12. Alan D. Cabrera
13. Vinod Kumar Vavilapalli

 Non-Binding (+1)

1. Alejandro Abdelnur
2. Edward J. Yoon
3. Joe Stein
4. Patrick Hunt
5. Ashish
6. Tom White
7. Andrew Purtell
8. Bernd Fondermann
9. Larry Mccay
10. Seetharam Venkatesh

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

Re: [VOTE] Accept Twill for Incubation

[Patrick Hunt]

, HDFS, log4j, and others
 mentioned in the External Dependencies section are Apache projects, and
 Twill will benefit by close proximity to them.

 = Known Risks =

 == Orphaned Products ==

 There is very little risk of Twill being orphaned, as it is a key part of
 Continuuity’s products. The core Twill developers plan to continue to work
 on Twill, and Continuuity has funding in place to support their efforts
 going forward.
 Many other Big Data companies can benefit from Twill, and we have already
 received interest from various entities that would like to use and
 contribute to Twill.

 == Inexperience with Open Source ==

 Several of the core developers have experience with open source
 development. Terence Yim, Andreas Neumann and Gary Helmling are currently
 Apache committers for Helix, Oozie and HBase respectively
 Homogeneous Developers

 The current core developers are all Continuuity employees. However, we
 intend to establish a developer community that includes independent and
 corporate contributors. We are encouraging new contributors via our mailing
 lists, public presentations, and personal contacts, and we will continue to
 do so. Various entities have already expressed interest in becoming
 involved with Twill.

 == Reliance on Salaried Developers ==

 Currently, these developers are paid to work on Twill. Once the project has
 built a community, we expect to attract committers, developers and
 community
 other than the current core developers. However, because Continuuity
 products use Twill internally, the reliance on salaried developers is
 unlikely to change, at least in the near term.

 == Relationships with Other Apache Products ==

 Twill is deeply integrated with Apache projects. Twill uses Apache YARN as
 its underlying resource management and task scheduling system and Apache
 Zookeeper for coordination. In addition, Twill uses Apache HDFS and Apache
 Kafka. A number of other Apache projects are Twill dependencies and are
 listed in the External Dependencies section.

 == An Excessive Fascination with the Apache Brand ==

 While we respect the reputation of the Apache brand and have no doubt that
 it will attract contributors and users, our interest is primarily to give
 Twill a solid home as an open source project following an established
 development model. We have also given additional reasons in the Rationale
 and Alignment sections.

 = Documentation =

 The current documentation for Weave is at
 https://github.com/continuuity/weave.
 This will be adapted to the new name Twill.

 = Initial Source =

 The Weave codebase is currently hosted at
 https://github.com/continuuity/weave. Weave will be renamed to Twill to
 seed the Apache git repository.

 = External Dependencies =

 The dependencies all have Apache-compatible licenses:
  * avro (Apache 2.0)
  * hadoop (Apache 2.0)
  * gson (Apache 2.0)
  * guava-libraries (Apache 2.0)
  * hbase (Apache 2.0)
  * hdfs (Apache 2.0)
  * kafka (Apache 2.0)
  * netty (Apache 2.0)
  * snappy-java (Apache 2.0)
  * yarn (Apache 2.0)
  * zookeeper (Apache 2.0)
  * asm (BSD)
  * junit (EPL v1.0)
  * logback (EPL v1.0 )
  * slf4j (MIT)

 = Cryptography =

 Twill will depend on secure Hadoop, which can optionally use Kerberos.

 = Required Resources =

 == Mailing Lists ==

  * twill-private for private PMC discussions (with moderated subscriptions)
  * twill-dev for technical discussions among contributors
  * twill-commits for notification about commits

 == Subversion Directory ==

 Git is the preferred source control system: git://git.apache.org/twill

 == Issue Tracking ==

 JIRA Twill (TWILL)

 == Other Resources ==

 The existing code already has unit tests, so we would like a Hudson
 instance to run them whenever a new patch is submitted. This can be added
 after project creation.

 = Initial Committers =

  * Terence Yim
  * Andreas Neumann
  * Gary Helmling
  * Poorna Chandra
  * Albert Shau

 = Affiliations =

  * Terence Yim (Continuuity)
  * Andreas Neumann (Continuuity)
  * Gary Helmling (Continuuity)
  * Poorna Chandra (Continuuity)
  * Albert Shau (Continuuity)

 = Sponsors =

 == Champion ==

 Vinod K vinodkv at apache dot org (Apache Member)

 == Nominated Mentors ==

  * Arun C Murthy acmurthy at apache dot org
  * Tom White tomwhite at apache dot org
  * Patrick Hunt phunt at apache dot org
  * Andrei Savu asavu at apache dot org

 == Sponsoring Entity ==

 We are requesting that the Incubator sponsor this project.

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

Re: [VOTE] Graduate Apache Curator as an Apache Top Level Project

[Patrick Hunt]

+1 Graduate the Apache Curator podling from Apache Incubator as a TLP

Patrick

On Wed, Aug 28, 2013 at 10:44 AM, Jordan Zimmerman
jor...@jordanzimmerman.com wrote:
 This message is opening a VOTE to graduate the Apache Curator podling from 
 the Apache Incubator as an Apache Top Level Project.

 Apache Curator entered the Incubator in April of 2013. We have made 
 significant progress with the project since moving to Apache. We currently 
 have 4 committers listed on our status page [1] including 2 who were accepted 
 after the podling was formed.  A VOTE was held on the curator-dev group with 
 8 binding +1 and 2 non-binding +1 votes for graduation [2]. A VOTE was also 
 held to adopt the graduation resolution (below) with 7 +1 votes for 
 acceptance [3]. According to Ohloh, Curator has a large, active development 
 team [4].

 During incubation, Curator:
 * Produced 4 releases
 * Added 2 new Committer/PPMC members and showed constant community activities
 * Cleared IP on code
 * Developed roadmap(s) for major and minor releases in a community process [5]
 * Established that Apache Curator is a suitable name [6]
 * Showed that its community is active, healthy, and growing and has 
 demonstrated the ability to self-govern using accepted Apache practices

 Please cast your vote:
 [ ] +1 Graduate the Apache Curator podling from Apache Incubator as a TLP
 [ ] +0 Indifferent to the graduation status of Apache Curator podling
 [ ] -1 Reject graduation of Apache Curator podling from Apache Incubator 
 because ...

 We'll run the vote for at least 72 hours.

 [1] http://curator.incubator.apache.org/team-list.html#Contributors
 [2] 
 http://mail-archives.apache.org/mod_mbox/incubator-curator-dev/201308.mbox/%3C44CD80F8-10B1-4FBA-A9D9-6DDEA7280FA5%40jordanzimmerman.com%3E
 [3] 
 http://mail-archives.apache.org/mod_mbox/incubator-curator-dev/201308.mbox/%3C3859DF43-460C-406E-B816-DD9F4049B4DC%40jordanzimmerman.com%3E
 [4] http://www.ohloh.net/p/apache-curator/factoids#FactoidTeamSizeLarge
 [5] 
 https://issues.apache.org/jira/browse/CURATOR#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
 [6] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-28

 Sincerely,

 The Apache Curator Team

 Resolution:

 X. Establish the Apache Curator 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 library and tools for working with
Apache ZooKeeper.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Curator Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Curator Project be and hereby is
responsible for the creation and maintenance of software
related to a library and tools for working with Apache ZooKeeper;
and be it further

RESOLVED, that the office of Vice President, Apache Curator 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 Curator Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Curator 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 Curator Project:

  * Jordan Zimmerman (randgalt)
  * Jay Zarfoss (zarfide)
  * Eric Tschetter (cheddar)
  * Ioannis Canellos (iocanel)
  * Patrick Hunt (phunt)
  * Mahadev Konar (mahadev)
  * Luciano Resende (lresende)
  * Enis Söztutar (enis)

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jordan Zimmerman
be appointed to the office of Vice President, Apache Curator, 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 Curator 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 Curator Project; and be it further

RESOLVED, that the Apache Curator Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Curator podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Curator

Re: If I were king of the forest

[Patrick Hunt]

On Wed, May 8, 2013 at 1:15 PM, Alan Cabrera l...@toolazydogs.com wrote:

 On May 8, 2013, at 1:09 PM, Suresh Marru sma...@apache.org wrote:

 Sebb is awesome.


+1

Patrick

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

Re: [VOTE] S4 0.6.0 Incubating Release Candidate 5

[Patrick Hunt]

+1 (binding) sig/xsum verify. rat runs clean. I've run through the
release checklist and everything seems fine to me.

Patrick

On Mon, May 6, 2013 at 5:37 AM, Matthieu Morel mmo...@apache.org wrote:
 Hello,

 this is the *fifth* release candidate for Apache S4, version 0.6.0

 We fixed 2 blocking issues wrt RC1, related to s4 tools, 1 blocking issue in 
 RC2, related to metrics logging configuration, issues related to the package 
 contents and license headers in RC3, and removed included javadoc files in 
 RC4.



 This release fixes the following issues:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312322version=12321702


 *** Please download, test and vote by Thursday, May 9th 2013, 13:00:00 GMT ***


 Note that we are voting upon the source (tag).


 Source package in zip format:

 http://people.apache.org/~mmorel/s4-0.6.0-incubating-release-candidate-5/



 The (git) tag to be voted upon: 0.6.0-RC5:

 https://git-wip-us.apache.org/repos/asf?p=incubator-s4.git;a=tree;h=8b43b317104cfc9ebc42f6e8ec9c9557867155aa;hb=2f474503e2da111601bb92ca7186c136ba28e5b0



 S4 KEYS file containing PGP keys we use to sign the release:

 http://svn.apache.org/repos/asf/incubator/s4/dist/KEYS


 The README.md file contains instructions for installing the gradle wrapper 
 (which is not shipped with the source release).


 We include a RAT check task. (Can be used by fetching rat from /lib dir in 
 the git repo and using the .rat-excludes file at the root of the git repo)

 It can be run with :
 gradlew rat  output


 Please cast your vote, thanks!


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



 NOTES:

 - All releases by podlings must be approved by the Incubator PMC. The 
 conventional process is for the podling to follow the usual Apache process 
 and then call for a Incubator PMC VOTE on the general incubator list.
 For RC5 however, following recommendations from our mentors, we are 
 proceeding to a parallel vote on both general@incubator and s4-dev


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

Re: [CANCEL] [VOTE] Release Apache Curator 2.0.0-incubating

[Patrick Hunt]

Hi Jordan, re the voting process see:
http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote

Also the other links to how to release type pages for other
incubator projects. It will give you insight into the process and
things like templates for emails and such. I think I forwarded you
that previously, if you're having troubles with it let me or one of
the other mentors know.

Patrick

On Wed, May 1, 2013 at 10:44 AM, Jordan Zimmerman
jor...@jordanzimmerman.com wrote:
 Canceling this vote due to noob errors. I'll start a new thread.

 -JZ

 -
 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] S4 0.6.0 Incubating Release Candidate 3

[Patrick Hunt]

On Wed, Apr 3, 2013 at 11:10 AM, Matthieu Morel mmo...@apache.org wrote:

Hey there, just back from vacation, hopefully Sebb can weigh in but
here's my thinking:

 We have 2 key questions, which I reproduce below:

 1/ about the content of LICENSE and NOTICE, is the following correct?

 - in the LICENSE file of the binary distribution, in addition to references 
 to non-ASL included dependencies (already there), we need to reference all 
 included dependencies that use ASL2, with the following statement:  The 
 Apache License, Version 2.0 applies to the following libraries: A, B, C
 - in the NOTICE file of the binary distribution, we add notices that 
 dependency libraries explicitly ask for. That is already done and no change 
 is required.


Have you reviewed this section of the release guide?
http://incubator.apache.org/guides/releasemanagement.html#best-practice-license

Also the license howto was recently updated, a good test of the work done there:
http://www.apache.org/dev/licensing-howto.html (see also:
https://issues.apache.org/jira/browse/LEGAL-155)


 2/  about the inclusion of the gradle wrapper jar + script in the source 
 distribution:

 We currently use gradle for building the project. Gradle provides a basic 
 wrapper script so that the project can be built without installing gradle 
 beforehand. That is why we include the script + wrapper lib.  
 http://www.apache.org/legal/resolved.html#build-tools says that specific 
 [build] tools have been OK'ed for inclusion in Apache distribution when used 
 for that specific purpose [of building].

 Should we exclude the gradle wrapper from our distribution?


I don't see any prior LEGAL issue mentioning gradle:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20LEGAL%20AND%20text%20~%20gradle

however a number of other projects seem to depend on it, you should
check what they are doing:
https://issues.apache.org/jira/issues/?jql=text%20~%20%22gradle%22


Once you go through that process cut another RC and we'll see.

Regards,

Patrick



 On Mar 28, 2013, at 18:15 , Matthieu Morel wrote:

 Thanks for your comments,

 Inline, I provide some explanations and ask for guidance on some topics.

 On Mar 27, 2013, at 22:59 , sebb wrote:

 On 27 March 2013 20:57, Matthieu Morel mmo...@apache.org wrote:
 Thanks for the feedback,

 I replied inline.

 On Mar 27, 2013, at 21:00 , sebb wrote:

 On 27 March 2013 19:07, Matthieu Morel mmo...@apache.org wrote:
 Hi everyone,


 this is a call for a vote to release Apache S4 0.6.0 incubating.


 A vote was held on developer mailing list and it passed for RC3 with 
 6+1's with 5 of them binding:

 +1 IPMC (phunt)
 +1PPMC (mmorel, kishoreg, leoneu, fpj)
 +1 committer non PPMC (dferro)


 Here is the vote thread on s4-dev: 
 http://markmail.org/thread/n5totrx7jkh2nvzu


 This release fixes the following issues:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312322version=12321702


 Note that we are voting upon the source (tag), binaries are provided for 
 convenience.

 Source and binary packages in zip format:

 http://people.apache.org/~mmorel/s4-0.6.0-incubating-release-candidate-3/



 The (git) tag to be voted upon: 0.6.0-RC3:

 https://git-wip-us.apache.org/repos/asf?p=incubator-s4.git;a=tag;h=9b178170d76333579a9c56564dd060ccd173f115

 NOTICE says:

 Apache S4
 Copyright 2012 The Apache Software Foundation

 Have there been no substantive changes this year?

 I think you are reading from the master branch in the git repository. In 
 our development process (https://issues.apache.org/jira/browse/S4-35) the 
 master branch holds the released code, while the dev branch holds the code 
 accepted for inclusion and that will be part of the next release. So we 
 cut the release candidate from dev branch. The year in the NOTICE file is 
 2013.

 I followed the git link above that you provided, then clicked on tree.
 I don't know otherwise how to review the source tag.

 The tag 0.6.0-RC3 points to commit 96938d5afe060f8213f66b3269e6c846cfc045e3

 If you use the web interface of the apache git site, in order to reach that 
 commit from the provided link, you may either click on the commit id, on the 
 tag, or on the commit link.




 gradlew and gradlew.bat don't have AL headers; nor does s4.

 The s4 file does have headers in the release artifacts.

 These also need to be added to the GIT copies; and the GIT tag must
 agree with the source files in the archive(s).

 By checking out from the git tag for the release and building the 
 distribution (gradlew srcDist), we get the same content than the release 
 candidate. In this case and for that file, isn't what we distribute properly 
 licensed and matching the git tag?
 But we can certainly add the licensing to the s4 file itself.


 gradle/gradlew scripts to not have the ASL header because this is 
 generated code.

 According to the RAT tool, generated code does not need to bear the 
 license header.

 The RAT tool is just a tool, it does 

Re: [VOTE] S4 0.6.0 Incubating Release Candidate 3

[Patrick Hunt]

On Wed, Mar 27, 2013 at 2:59 PM, sebb seb...@gmail.com wrote:
 On 27 March 2013 20:57, Matthieu Morel mmo...@apache.org wrote:
 On Mar 27, 2013, at 21:00 , sebb wrote:
 On 27 March 2013 19:07, Matthieu Morel mmo...@apache.org wrote:
 gradle/gradlew scripts to not have the ASL header because this is generated 
 code.

 According to the RAT tool, generated code does not need to bear the license 
 header.

 The RAT tool is just a tool, it does not make the rules.

 This issue was identified and discussed during the voting process on s4-dev 
 mailing lis. For this release, it was considered valid to leave those 
 generated files not annotated by one of our mentors.


 That may not have been the correct decision.


Hi Sebb, I had originally -1'd the release due to the missing header
on these generated files. I was going by my understanding of Apache
guidelines, in particular
http://incubator.apache.org/guides/releasemanagement.html#notes-license-headers
and I generally follow that first paragraph - where ever possible add
the header.

I changed my vote based on the RAT output and then consulting the
second paragraph in that on license headers section linked above, in
particular Copyright may not subsist in a document which is generated
by an transformation from an original.

What's the correct decision here?

Patrick

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

Re: [VOTE] Accept Curator into the Incubator

[Patrick Hunt]

 Zarfoss
 Jordan has contributed towards Apache ZooKeeper and both Jordan and Jay are 
 familiar with Apache principles and philosophy for community driven software 
 development.

 Alignment

 Curator is a natural complement for Apache ZooKeeper. Java users of ZooKeeper 
 will naturally want to use Curator. When Curator graduates from Incubator it 
 may be useful to distribute Curator artifacts as part of ZooKeeper releases 
 as the preferred/recommended client side library. Further, at graduation a 
 determination can be made as to whether Curator should become a Top Level 
 Project or be merged into ZooKeeper itself. That being said, some IPMC 
 members feel that Curator should grow into its own TLP rather than be a part 
 of ZooKeeper.

 Known Risks

 Orphaned Products

 Curator is already deployed in production at multiple companies and they are 
 actively participating in creating new features. Curator is getting traction 
 with developers and thus the risks of it being orphaned are minimal.

 Inexperience with Open Source

 All code developed for Curator has been open sourced by Netflix under Apache 
 2.0 license. All committers to Curator are intimately familiar with the 
 Apache model for open-source development and are experienced with working 
 with new contributors.

 Homogeneous Developers

 The initial committers are from a single organization. However, we expect 
 that once approved for incubation, the project will attract new contributors 
 from diverse organizations and will thus grow organically. The submission of 
 patches from developers from several different organizations is a strong 
 indication that Curator will be widely adopted.

 Reliance on Salaried Developers

 It is expected that Curator will be developed on salaried and volunteer time, 
 although all of the initial developers will work on it mainly on salaried 
 time.

 Relationships with Other Apache Products

 Curator depends upon other Apache Projects: Apache ZooKeeper, Apache Log4J, 
 and multiple Apache Commons components. Its build depends upon Apache Maven. 
 Notably, there is interest from other Apache Projects such as HBase in 
 adopting Curator as the client library for ZooKeeper. Apache James Mailbox 
 has already incorporated Curator.

 An Excessive Fascination with the Apache Brand

 We would like Curator to become an Apache project to further foster a healthy 
 community of contributors and consumers around the project. Since Curator 
 directly interacts with Apache ZooKeeper and solves an important problem of 
 many ZooKeeper users, residing in the Apache Software Foundation will 
 increase interaction with the larger community.

 Documentation

 • Curator wiki at GitHub: https://github.com/Netflix/curator/wiki
 • Curator issues at GitHub: https://github.com/Netflix/curator/issues
 • Curator javadoc at GitHub: http://netflix.github.com/curator/doc/
 Initial Source

 • git://github.com/Netflix/curator.git
 Source and Intellectual Property Submission Plan

 • The initial source is already licensed under the Apache License, 
 Version 2.0. https://github.com/Netflix/curator/blob/master/LICENSE.txt
 External Dependencies

 The required external dependencies are all Apache License or compatible 
 licenses. Following components with non-Apache licenses are enumerated:

 • org.slf4j: MIT-like License
 • org.mockito: MIT-like License
 Cryptography

 Curator contains no known cryptography.

 Required Resources

 Mailing lists

 • curator-private (with moderated subscriptions)
 • curator-dev
 • curator-commits
 • curator-user
 GitHub Repositories

 http://github.com/apache/curator git://git.apache.org/curator.git

 Issue Tracking

 JIRA Curator (CURATOR)

 Other Resources

 The existing code already has unit and integration tests so we would like a 
 Jenkins instance to run them whenever a new patch is submitted. This can be 
 added after project creation.

 Initial Committers

 • Jordan Zimmerman (jzimmerman at netflix dot com)
 • Jay Zarfoss (jzarfoss at netflix dot com)
 Affiliations

 • Jordan Zimmerman, Netflix
 • Jay Zarfoss, Netflix
 Sponsors

 Champion

 • Patrick Hunt
 Nominated Mentors

 • Patrick Hunt
 • Enis Söztutar
 • Mahadev Konar
 • 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

Re: [PROPOSAL] Curator for the Apache Incubator

[Patrick Hunt]

On Tue, Feb 26, 2013 at 8:32 AM, Benson Margulies bimargul...@gmail.com wrote:
 If you think that the right destination for curator is as part of ZK,
 then it would be good to see substantive participation of the ZK PMC
 in the incubation. The goal should be to 'graduate' by having the
 curator community be granted karma at ZK and the code folded in. This
 would require, I think, the ZK community to supply at least one
 mentor, and to have a plan in advance for the eventual votes based on
 success in the incubator.

Hi Benson. What you're suggesting matches my current thinking.

The three Curator mentors are as follows: Mahadev and I (champion) are
both PMC members on ZK, Enis Söztutar is active on HBase and
interested in using Curator for that project (which already uses ZK
heavily).

Patrick

 On Tue, Feb 26, 2013 at 10:53 AM, Henry Saputra henry.sapu...@gmail.com 
 wrote:
 Ah no, I was not suggesting about Curator to become subproject of ZK. I
 just afraid that if Curator is going as incubator it will end up as sub of
 ZK as merging process.

 Like Greg has mentioned in another reply, I would prefer Curator to be
 merged as a higher level ZK client. Surely project like HBase and others
 that relying on ZK would appreciate simpler client to ZK.

 Thanks,

 Henry


 On Mon, Feb 25, 2013 at 11:23 PM, Patrick Hunt ph...@apache.org wrote:

 On Mon, Feb 25, 2013 at 11:01 PM, Henry Saputra henry.sapu...@gmail.com
 wrote:
  So isnt this similar to HCatalog which relying on Hive metadata service
  that ends up as sub project of Apache Hive?
 

 I was against having Curator as a sub when it came up on the original
 discussion thread, I still am.

 Patrick

 
 
  On Mon, Feb 25, 2013 at 7:10 PM, Greg Stein gst...@gmail.com wrote:
 
  My concern is that we're looking at two new committers, rather than
  a Curator community. Following normal Incubator work, Curator would
  build a community for itself. But then we'd have a community
  *distinct* from that of Zookeeper. And it really looks like this
  should be part of Zookeeper itself -- a more capable and easier-to-use
  client.
 
  So I question the incubation of this. Why do we want to build a
  new/separate project? Why isn't this just part of Zookeeper right from
  the start?
 
  I would suggest that this work is placed on a branch within Zookeeper.
  That Jordan and Jay become committers on that branch (not necessarily
  Zookeeper trunk). Over time, the branch can be folded into trunk,
  along with all the various tests, doc, and other artifacts that I see
  in the GitHub repository. And hopefully that Jordan and Jay become
  regular committers (and PMC members!) of the Zookeeper project itself.
 
  The current Zookeeper client can remain for backwards compat, and the
  Curator work can become the next-gen client.
 
  Honestly, in my opnion, incubating this project seems like it would
  create a distinct community, and really doesn't seem like it would
  serve the Zookeeper community.
 
  All that said, I am not familiar with the Zookeeper or Curator
  communities. But from this read, I don't think Incubation is the right
  approach. I would rather push for a more direct incorporation of
  Curator directly into Zookeeper. (use the short-form IP clearance) ...
  so, unless somebody can help me understand the communities and
  situation better, I'm -1 (binding) on this incubation. I'd rather see
  combined, rather than distinct, communities from the start.
 
  Thanks,
  -g
 
  On Mon, Feb 25, 2013 at 8:14 PM, Jordan Zimmerman
  jor...@jordanzimmerman.com wrote:
   Hello,
  
   I would like to propose that Curator to be an Apache Incubator
 project.
  
   The proposal can be found here:
  http://wiki.apache.org/incubator/CuratorProposal
  
   I have included the contents of the proposal below.
  
   Sincerely,
  
   Jordan Zimmerman
  
   ===
  
   = Curator - ZooKeeper client wrapper and rich ZooKeeper framework =
  
   == Abstract ==
  
   Curator is a set of Java libraries that make using Apache ZooKeeper
 much
  easier. While ZooKeeper comes bundled with a Java client, using the
 client
  is non-trivial and error prone.
  
   == Proposal ==
  
   Curator is a set of Java libraries that make using Apache ZooKeeper
 much
  easier. While ZooKeeper comes bundled with a Java client, using the
 client
  is non-trivial and error prone. It consists of three components that
 build
  on each other. Curator Client is a replacement for the bundled ZooKeeper
  class that takes care of some low-level housekeeping and provides some
  useful utilities. Curator Framework is a high-level API that greatly
  simplifies using ZooKeeper. It adds many features that build on
 ZooKeeper
  and handles the complexity of managing connections to the ZooKeeper
 cluster
  and retrying operations. Curator Recipes consists of implementations of
  some of the common ZooKeeper “recipes”. Additionally, Curator Test is
  included which includes utilities to help with unit

Re: [PROPOSAL] Curator for the Apache Incubator

[Patrick Hunt]

On Tue, Feb 26, 2013 at 10:30 AM, Mattmann, Chris A (388J)
chris.a.mattm...@jpl.nasa.gov wrote:
 Hi Guys,

 Sorry I have to ask the question here. If the mentors consist of PMC
 members on ZK
 (at least Pat and Mahadev), what's the problem with creating a branch in
 ZK and just
 having the code be there and getting the Curator proposed committers as
 committers in
 ZK ville, and hopefully PMC members soon thereafter.

 I have to agree with Greg here. Seems like Incubation is something that
 might not be
 needed. If the end result of this after N months is that Curator
 graduates into another
 set of flipping bylaw updates, and more legislation that makes these
 people unofficial
 PMC members on ZK, then I'm double triple -1 with 50 piles of coal on top.
 Yes, I'm
 still remembering the HCatalog/Hive thing here - I still don't get that.

 Either: (a) define Curator to be its own separate project/community, with
 a goal of TLP;
 or (b) nix Incubation and just make these guys part of ZK, on a branch
 now.

Hi Chris. Unfortunately it's not clear cut to me where Curator should
go, perhaps because I'm close to it. For example the Curator as TLP
argument might sound like this:

1) curator has been around for a while, people seem to like it
2) it shares no code with ZK today, in the sense that it's a consumer
of the ZK APIs, what we call recipes. No code duplication. Granted
it does try to make writing clients easier.
3) (afaik) none of the current ZK committers have contributed to
Curator, when this proposal came up previously for discussion on the
ZK dev list there wasn't strong interest to pull it into ZK itself
4) the initial committers on curator don't have experience at Apache

On the contrary I personally think it might make sense to have a
combined community with Curator and ZooKeeper together, but I'm not
sure.

My hope was that Curator could come into the incubator, work through
the IP issues and other incubation activities, learn about Apache
process, and then decide based on the new found insight/experience.

The proposal guide talks about this and makes it clear (at least to
me) that leaving graduation open is not only an option, but a
requirement Note that the final destination within the Apache
organizational structure will be decided upon graduation. Given this
I don't see why we'd artificially constrain things up front as you've
suggested.

Patrick



 On 2/26/13 9:40 AM, Benson Margulies bimargul...@gmail.com wrote:

On Tue, Feb 26, 2013 at 12:22 PM, Patrick Hunt ph...@apache.org wrote:
 On Tue, Feb 26, 2013 at 8:32 AM, Benson Margulies
bimargul...@gmail.com wrote:
 If you think that the right destination for curator is as part of ZK,
 then it would be good to see substantive participation of the ZK PMC
 in the incubation. The goal should be to 'graduate' by having the
 curator community be granted karma at ZK and the code folded in. This
 would require, I think, the ZK community to supply at least one
 mentor, and to have a plan in advance for the eventual votes based on
 success in the incubator.

 Hi Benson. What you're suggesting matches my current thinking.

 The three Curator mentors are as follows: Mahadev and I (champion) are
 both PMC members on ZK, Enis Söztutar is active on HBase and
 interested in using Curator for that project (which already uses ZK
 heavily).

OK, that's lovely.



 Patrick

 On Tue, Feb 26, 2013 at 10:53 AM, Henry Saputra
henry.sapu...@gmail.com wrote:
 Ah no, I was not suggesting about Curator to become subproject of ZK.
I
 just afraid that if Curator is going as incubator it will end up as
sub of
 ZK as merging process.

 Like Greg has mentioned in another reply, I would prefer Curator to be
 merged as a higher level ZK client. Surely project like HBase and
others
 that relying on ZK would appreciate simpler client to ZK.

 Thanks,

 Henry


 On Mon, Feb 25, 2013 at 11:23 PM, Patrick Hunt ph...@apache.org
wrote:

 On Mon, Feb 25, 2013 at 11:01 PM, Henry Saputra
henry.sapu...@gmail.com
 wrote:
  So isnt this similar to HCatalog which relying on Hive metadata
service
  that ends up as sub project of Apache Hive?
 

 I was against having Curator as a sub when it came up on the original
 discussion thread, I still am.

 Patrick

 
 
  On Mon, Feb 25, 2013 at 7:10 PM, Greg Stein gst...@gmail.com
wrote:
 
  My concern is that we're looking at two new committers, rather
than
  a Curator community. Following normal Incubator work, Curator
would
  build a community for itself. But then we'd have a community
  *distinct* from that of Zookeeper. And it really looks like this
  should be part of Zookeeper itself -- a more capable and
easier-to-use
  client.
 
  So I question the incubation of this. Why do we want to build a
  new/separate project? Why isn't this just part of Zookeeper right
from
  the start?
 
  I would suggest that this work is placed on a branch within
Zookeeper.
  That Jordan and Jay become committers on that branch (not
necessarily
  Zookeeper trunk

Re: [PROPOSAL] Curator for the Apache Incubator

[Patrick Hunt]

On Tue, Feb 26, 2013 at 1:10 PM, Mattmann, Chris A (388J)
chris.a.mattm...@jpl.nasa.gov wrote:
 Hey Pat,


 On 2/26/13 11:39 AM, Patrick Hunt ph...@apache.org wrote:

[…snip…]

 Either: (a) define Curator to be its own separate project/community,
with
 a goal of TLP;
 or (b) nix Incubation and just make these guys part of ZK, on a branch
 now.

Hi Chris. Unfortunately it's not clear cut to me where Curator should
go, perhaps because I'm close to it.

 Yep, I think that's part of it, but you're doing good discussing it here,
 and please don't take my comments as criticism. If the answer were to be
 that this project followed the Incubator process, and arrived at TLP, I
 would have *zero* concern. My concern is the implication that this could
 end up as part of Zookeeper (ZK). It's more of a general concern about
 allowing
 that within the Incubator. I'll comment more below.


Hey Chris, no worries on my end what so ever. I appreciate your
insight. If you remember you're the reason I'm in this mess in the
first place. ;-) (you pulled me into my first incubation project as a
mentor, now I'm hooked)

My hope was that Curator could come into the incubator, work through
the IP issues and other incubation activities, learn about Apache
process, and then decide based on the new found insight/experience.

 I totally get it.

 I'm not questioning you, more of the Incubator here.


That's cool. However changing incubator policy is outside the scope of
this discussion - Curator's specific proposal. That's for a different
day.

 Let me cut to the chase. I *don't* think the Incubator should be home to
 projects
 whose potential destination is as a product of an existing TLP (or
 sub-module).
 I think that leads to a LOT of potential problems down the road, some of
 which
 include:

 1. The dev that happens in the Incubator on new podling X, whose
 destination is TLP
 Y is rarely monitored or seen by those in TLP Y. If it is closely
 monitored, then
 why isn't the new podling part of TLP Y? And if it's not monitored, then
 TLP Y is
 more likely to end up at some forced agreement or bylaw mumbo jumbo to
 assimilate the
 people and products of podling X into the TLP Y.

 2. Creating the new community in the Incubator means that new people will
 be added
 as members of podling X that TLP Y didn't add. We've seen problems with
 TLP Y then not
 wanting to assimilate those podling X PPMC members into the TLP Y.

 3. Sub-modules tend to hide things like sub-projects. I can count on two
 hands how many
 TLPs have went through that process, and all of them typically have had
 hardship and
 crap along the way that I'm trying to save you guys the hassle of
 (lessons learned)

 Instead, if the home for a potential new podling X is TLP Y, my desire
 would be to
 work as an existing member of TLP Y to shepherd the contributions in that
 way.


The proposal guide talks about this and makes it clear (at least to
me) that leaving graduation open is not only an option, but a
requirement Note that the final destination within the Apache
organizational structure will be decided upon graduation. Given this
I don't see why we'd artificially constrain things up front as you've
suggested.

 Well the proposal guide is great, and all but it's not doctrine :)


One of my favorites. Either it's not written down, or it is. In either
case its what we want it to be.

 I realize you're in a tough spot here and somewhat in a COI, not exactly
 knowing what the right answer is,
 and I'm not sure I know it either, but my gut instinct based on experience
 for a while
 here indicates that Incubation makes sense here and this is a new
 community and so I won't
 stand in the way of that. I will however, throw up my comments and a fuss
 again if this is another
 situation similar to HCatalog where at the end of this you guys try and
 shove it into ZK
 in any other way of intersect([set of Curator PPMC], [set of ZK PMC]).


My own view is that if it goes into incubation and then to ZK or TLP
we'lll straighten it out. A worse situation would be to lose the
opportunity to try.

 That's my ultimate worry, and the Incubator is not a clearinghouse for
 punting on those
 types of situations at least not the Incubator I would like to participate
 in.

Think about it this way. If we fail miserably you'll have a great
example to use the next time it comes up. ;-)

Patrick





Patrick



 On 2/26/13 9:40 AM, Benson Margulies bimargul...@gmail.com wrote:

On Tue, Feb 26, 2013 at 12:22 PM, Patrick Hunt ph...@apache.org wrote:
 On Tue, Feb 26, 2013 at 8:32 AM, Benson Margulies
bimargul...@gmail.com wrote:
 If you think that the right destination for curator is as part of ZK,
 then it would be good to see substantive participation of the ZK PMC
 in the incubation. The goal should be to 'graduate' by having the
 curator community be granted karma at ZK and the code folded in. This
 would require, I think, the ZK community to supply at least one
 mentor, and to have a plan

Re: [PROPOSAL] Curator for the Apache Incubator

[Patrick Hunt]

 into ZooKeeper itself.

 = Known Risks =

 == Orphaned Products ==

 Curator is already deployed in production at multiple companies and they are 
 actively participating in creating new features. Curator is getting traction 
 with developers and thus the risks of it being orphaned are minimal.

 == Inexperience with Open Source ==

 All code developed for Curator has been open sourced by Netflix under Apache 
 2.0 license.  All committers to Curator are intimately familiar with the 
 Apache model for open-source development and are experienced with working 
 with new contributors.

 == Homogeneous Developers ==

 The initial committers are from a single organization. However, we expect 
 that once approved for incubation, the project will attract new contributors 
 from diverse organizations and will thus grow organically. The submission of 
 patches from developers from several different organizations is a strong 
 indication that Curator will be widely adopted.

 == Reliance on Salaried Developers ==

 It is expected that Curator will be developed on salaried and volunteer 
 time, although all of the initial developers will work on it mainly on 
 salaried time.

 == Relationships with Other Apache Products ==

 Curator depends upon other Apache Projects: Apache ZooKeeper, Apache Log4J, 
 and multiple Apache Commons components. Its build depends upon Apache Maven. 
 Notably, there is interest from other Apache Projects such as HBase in 
 adopting Curator as the client library for ZooKeeper. Apache James Mailbox 
 has already incorporated Curator.

 == An Excessive Fascination with the Apache Brand ==

 We would like Curator to become an Apache project to further foster a 
 healthy community of contributors and consumers around the project.  Since 
 Curator directly interacts with Apache ZooKeeper and solves an important 
 problem of many ZooKeeper users, residing in the Apache Software Foundation 
 will increase interaction with the larger community.

 = Documentation =

  * Curator wiki at GitHub: https://github.com/Netflix/curator/wiki
  * Curator issues at GitHub: https://github.com/Netflix/curator/issues
  * Curator javadoc at GitHub: http://netflix.github.com/curator/doc/

 = Initial Source =

  * git://github.com/Netflix/curator.git

 == Source and Intellectual Property Submission Plan ==

  * The initial source is already licensed under the Apache License, Version 
 2.0. https://github.com/Netflix/curator/blob/master/LICENSE.txt

 == External Dependencies ==

 The required external dependencies are all Apache License or compatible 
 licenses. Following components with non-Apache licenses are enumerated:

  * org.slf4j: MIT-like License
  * org.mockito: MIT-like License

 == Cryptography ==

 Curator contains no known cryptography.

 = Required Resources =

 == Mailing lists ==

  * curator-private (with moderated subscriptions)
  * curator-dev
  * curator-commits
  * curator-user

 == Github Repositories ==

 http://github.com/apache/curator git://git.apache.org/curator.git

 == Issue Tracking ==

 JIRA Curator (CURATOR)

 == Other Resources ==

 The existing code already has unit and integration tests so we would like a 
 Jenkins instance to run them whenever a new patch is submitted. This can be 
 added after project creation.

 = Initial Committers =

  * Jordan Zimmerman (jzimmerman at netflix dot com)
  * Jay Zarfoss (jzarfoss at netflix dot com)

 = Affiliations =

  * Jordan Zimmerman, Netflix
  * Jay Zarfoss, Netflix

 = Sponsors =

 == Champion ==

  * Patrick Hunt

 == Nominated Mentors ==

  * Patrick Hunt
  * Enis Söztutar
  * Mahadev Konar

 == Sponsoring Entity ==

  * Apache Incubator PMC

 -
 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: [PROPOSAL] Curator for the Apache Incubator

[Patrick Hunt]

 License or compatible
 licenses. Following components with non-Apache licenses are enumerated:
 
   * org.slf4j: MIT-like License
   * org.mockito: MIT-like License
 
  == Cryptography ==
 
  Curator contains no known cryptography.
 
  = Required Resources =
 
  == Mailing lists ==
 
   * curator-private (with moderated subscriptions)
   * curator-dev
   * curator-commits
   * curator-user
 
  == Github Repositories ==
 
  http://github.com/apache/curator git://git.apache.org/curator.git
 
  == Issue Tracking ==
 
  JIRA Curator (CURATOR)
 
  == Other Resources ==
 
  The existing code already has unit and integration tests so we would
 like a Jenkins instance to run them whenever a new patch is submitted. This
 can be added after project creation.
 
  = Initial Committers =
 
   * Jordan Zimmerman (jzimmerman at netflix dot com)
   * Jay Zarfoss (jzarfoss at netflix dot com)
 
  = Affiliations =
 
   * Jordan Zimmerman, Netflix
   * Jay Zarfoss, Netflix
 
  = Sponsors =
 
  == Champion ==
 
   * Patrick Hunt
 
  == Nominated Mentors ==
 
   * Patrick Hunt
   * Enis Söztutar
   * Mahadev Konar
 
  == Sponsoring Entity ==
 
   * Apache Incubator PMC

 -
 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: Crunch status (Was: [Incubator Wiki] Update of November2012 by MatthiasFriedrich)

[Patrick Hunt]

I second this. Short of the name search these folks are ready to graduate.

Patrick

On Fri, Nov 16, 2012 at 3:38 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 Hi,

 Thanks for the report, Crunch!

 On Fri, Nov 2, 2012 at 6:20 PM, Apache Wiki wikidi...@apache.org wrote:
 +   The Crunch community has been very active and continues to
 +   grow. Two new committers have been voted in and one existing
 +   committer has joined the PPMC. As a result, Crunch now has 10
 +   committers from 7 different organizations.
 +   We have created our first release in September and have published
 +   a website using the Apache CMS a few days later. Our second
 +   release will follow in November.

 Sounds like you're doing great! In fact in my brief review of your
 status I found no big blockers to graduation.

 + The most important steps towards graduation:
 +
 +   - Create another release or two
 +   - Perform the name search

 You've already demonstrated your ability to cut releases, so you
 should be fine to start going through the name search and other steps
 of the graduation process as soon as the community feels ready for it.

 BR,

 Jukka Zitting

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


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

Re: [VOTE] Release Apache Crunch 0.4.0 (incubating) RC1

[Patrick Hunt]

+1, sig/xsum validate, code is compiling/installing, I ran through the
release checklist and everything checks out.

Patrick

On Fri, Nov 16, 2012 at 10:07 AM, Doug Cutting cutt...@apache.org wrote:
 +1 RAT tests pass (as do others), checksums  sigs match.

 On Tue, Nov 13, 2012 at 9:54 AM, Matthias Friedrich m...@mafr.de wrote:
 Hi,

 this is a call for a vote on releasing the following candidate as
 Apache Crunch 0.4.0 (incubating). This is the second release candidate
 of our second release at Apache, and it fixes the following issues:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313526version=12323244

 Our vote thread on crunch-dev:
 http://mail-archives.apache.org/mod_mbox/incubator-crunch-dev/201211.mbox/%3C20121113173454.GA3000%40mafr.de%3E

 We already collected one IPMC vote from Roman Shaposhnik (thanks!),
 so we still need two more votes.

 Please download, test, and vote by November 16th at 18:00 UTC.

 Release artifacts:
 http://people.apache.org/~mafr/apache-crunch-0.4.0-incubating-rc1/

 Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachecrunch-034/

 The tag to be voted upon:
 https://git-wip-us.apache.org/repos/asf?p=incubator-crunch.git;a=commit;h=91e6c96899f85245255476f0a5e7d5feb48ddac0

 PGP keys for the Crunch team:
 https://people.apache.org/keys/group/crunch.asc

 Some basic release validation checks:
 https://cwiki.apache.org/confluence/display/CRUNCH/Validating+a+Release

 The vote will be open for 72 hours.

 Regards,
   Matthias

 -
 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] Accept Helix into Apache Incubator

[Patrick Hunt]

 one of the core developers has experience with open source
 development. Kishore has been actively involved with the ASF as a
 committer and lead developer of S4.

 === Homogeneous Developers ===
 The current core developers are all from LinkedIn. However, we hope to
 establish a developer community that includes contributors from
 several corporations and we are actively encouraging new contributors
 via the mailing lists and public presentations of Helix.

 === Reliance on Salaried Developers ===
 Currently, the developers are paid to do work on Helix. However, once
 the project has a community built around it, we expect to get
 committers, developers and community from outside the current core
 developers. However, because LinkedIn relies on Helix internally, the
 reliance on salaried developers is unlikely to change.

 === Relationships with Other Apache Products ===
 Helix uses Apache ZooKeeper to coordinate its state amongst the
 managed cluster components and for leader election to provide fault
 tolerance, and uses Apache Maven for build management.

 === An Excessive Fascination with the Apache Brand ===
 While we respect the reputation of the Apache brand and have no doubts
 that it will attract contributors and users, our interest is primarily
 to give Helix a solid home as an open source project following an
 established development model. We have also given reasons in the
 Rationale and Alignment sections.

 == Documentation ==
 Information about Helix can be found at
 [https://github.com/linkedin/helix/wiki]. The following links provide
 more information about the project:

  * Home Page: http://linkedin.github.com/helix/
  * Github source: https://github.com/linkedin/helix
  * Documentation: https://github.com/linkedin/helix/wiki
  * Javadocs: http://linkedin.github.com/helix/apidocs/

 == Initial Source ==
 Helix has been under development at LinkedIn since April 2011. It is
 currently hosted on github under the Apache license 2 at
 [https://github.com/linkedin/helix]
 Helix is written in Java. Its source tree is entirely self-contained
 and relies on Maven as its build system and dependency resolution
 mechanism.

 == External Dependencies ==
 The dependencies all have Apache compatible licenses.
  * log4j
  * zookeeper
  * xstream
  * jackson-core-asl
  * jackson-mapper-asl
  * commons-io
  * commons-cli
  * commons-math
  * zkclient
  * camel-josql
  * camel-core
  * gentlyweb-utils
  * josql
  * commons-management
  * commons-logging-api
  * org.restlet
  * com.noelios.restlet
  * net.sf.jsqlparser

 Non-Apache build tools that are used by Helix are as follows:
  * Cobertura: GNU GPLv2
 Note that Cobertura is optional and is only used for calculating unit
 test coverage.


 == Cryptography ==
 Not applicable.

 == Required Resources ==
 === Mailing Lists ===
  * helix-private for private PMC discussions (with moderated subscriptions)
  * helix-dev
  * helix-commits
  * helix-user

 === Git Directory ===
 Since Git is now available to be used as primary repo type, Helix
 would be available in the git repository instead of svn.
 [https://git.apache.org/helix.git]

 === Issue Tracking ===
 JIRA Helix (HELIX)

 === Other Resources ===
 The existing code already has unit and integration tests, so we would
 like a Jenkins instance to run them whenever a new patch is submitted.
 This can be added after project creation.

 == Initial Committers ==
  * Kishore Gopalakrishna
  * Shi Lu
  * Zhen Zheng
  * Adam Silberstein
  * Kapil Surlaker
  * Bob Schulman
  * Swaroop Jagadish
  * Rahul Aggarwal
  * Terence Yim
  * Santiago Perez


 == Affiliations ==
  * Kishore Gopalakrishna (LinkedIn)
  * Shi Lu (LinkedIn)
  * Jason Zheng (LinkedIn)
  * Adam Silberstein (Trifacta)
  * Kapil Surlaker (LinkedIn)
  * Bob Schulman (LinkedIn)
  * Swaroop Jagadish (LinkedIn)
  * Rahul Aggarwal (LinkedIn)
  * Terence Yim (LinkedIn)
  * Santiago Perez (LinkedIn)

 == Sponsors ==
 === Champion ===
  * Patrick Hunt (Apache Member)

 === Nominated Mentors ===
  * Patrick Hunt  (Apache Member)
  * Mahadev Konar (Apache Member)
  * Owen O'Malley (Apache Member)

 === Sponsoring Entity ===
 We are requesting the Incubator to sponsor this project.

 -
 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: [PROPOSAL] Helix for the Apache Incubator

[Patrick Hunt]

 Developers ===
 The current core developers are all from LinkedIn. However, we hope to
 establish a developer community that includes contributors from
 several corporations and we are actively encouraging new contributors
 via the mailing lists and public presentations of Helix.

 === Reliance on Salaried Developers ===
 Currently, the developers are paid to do work on Helix. However, once
 the project has a community built around it, we expect to get
 committers, developers and community from outside the current core
 developers. However, because LinkedIn relies on Helix internally, the
 reliance on salaried developers is unlikely to change.

 === Relationships with Other Apache Products ===
 Helix uses Apache ZooKeeper to coordinate its state amongst the
 managed cluster components and for leader election to provide fault
 tolerance, and uses Apache Maven for build management.

 === An Excessive Fascination with the Apache Brand ===
 While we respect the reputation of the Apache brand and have no doubts
 that it will attract contributors and users, our interest is primarily
 to give Helix a solid home as an open source project following an
 established development model. We have also given reasons in the
 Rationale and Alignment sections.

 == Documentation ==
 Information about Helix can be found at
 [https://github.com/linkedin/helix/wiki]. The following links provide
 more information about the project:

  * The GitHub site: [https://github.com/linkedin/helix ] Will be made
 public in second week of October.
  * Helix paper at SOCC 2012: [Available_after_October_15th]

 == Initial Source ==
 Helix has been under development at LinkedIn since April 2011. It is
 currently hosted on github under the Apache license 2 at
 [https://github.com/linkedin/helix]
 Helix is written in Java. Its source tree is entirely self-contained
 and relies on Maven as its build system and dependency resolution
 mechanism.

 == External Dependencies ==
 The dependencies all have Apache compatible licenses.
  * log4j
  * zookeeper
  * xstream
  * jackson-core-asl
  * jackson-mapper-asl
  * commons-io
  * commons-cli
  * commons-math
  * zkclient
  * camel-josql
  * camel-core
  * gentlyweb-utils
  * josql
  * commons-management
  * commons-logging-api
  * org.restlet
  * com.noelios.restlet
  * net.sf.jsqlparser

 Non-Apache build tools that are used by Crunch are as follows:
 * Cobertura: GNU GPLv2
 Note that Cobertura is optional and is only used for calculating unit
 test coverage.


 == Cryptography ==
 Not applicable.

 == Required Resources ==
 === Mailing Lists ===
  * helix-private for private PMC discussions (with moderated subscriptions)
  * helix-dev
  * helix-commits
  * helix-user

 === Git Directory ===
 Since Git is now available to be used as primary repo type, Helix
 would be available in the git repository instead of svn.
 [https://git.apache.org/helix.git]

 === Issue Tracking ===
 JIRA Helix (HELIX)

 === Other Resources ===
 The existing code already has unit and integration tests, so we would
 like a Jenkins instance to run them whenever a new patch is submitted.
 This can be added after project creation.

 == Initial Committers ==
  * Kishore Gopalakrishna
  * Shi Lu
  * Zhen Zheng
  * Adam Silberstein
  * Kapil Surlaker
  * Bob Schulman
  * Swaroop Jagadish
  * Rahul Aggarwal
  * Terence Yim
  * Santiago Perez


 == Affiliations ==
  * Kishore Gopalakrishna (LinkedIn)
  * Shi Lu (LinkedIn)
  * Jason Zheng (LinkedIn)
  * Adam Silberstein (Trifacta)
  * Kapil Surlaker (LinkedIn)
  * Bob Schulman (LinkedIn)
  * Swaroop Jagadish (LinkedIn)
  * Rahul Aggarwal (LinkedIn)
  * Terence Yim (LinkedIn)
  * Santiago Perez (LinkedIn)

 == Sponsors ==
 === Champion ===
  * Patrick Hunt (Apache Member)

 === Nominated Mentors ===
  * Patrick Hunt  (Apache Member)
  * Mahadev Konar (Apache Member)
  * Owen O'Malley (Apache Member)

 === Sponsoring Entity ===
 We are requesting the Incubator to sponsor this project.

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


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

Re: [VOTE] Graduate Bigtop podling from Apache Incubator

[Patrick Hunt]

+1

Patrick

On Wed, Sep 12, 2012 at 9:08 AM, Roman Shaposhnik r...@apache.org wrote:
 This is a call for vote to graduate Bigtop podling from Apache Incubator

 The Apache Bigtop project entered incubator in June of 2011. Since then we
 have grown the community in users and contributors, and we've made
 significant improvements to the project. Following the Apache guidelines we
 have made four releases, we are preparing a 5th major and 6th maintenance
 releases, and we've added two new committers. The current set of committers
 and PPMC members are from different organizations and have demonstrated
 interest in growing the community further. We have learned the basis to manage
 the different aspects of an Apache project. The community of Bigtop is active,
 healthy and growing and has demonstrated the ability to self-govern using
 accepted Apache practices. Bigtop community has voted to proceed with
 graduation [1] and the result can be found at [2].

 Please cast your votes:

 [  ] +1 Graduate Bigtop podling from Apache Incubator
 [  ] +0 Indifferent to the graduation status of Bigtop podling
 [  ] -1 Reject graduation of Bigtop podling from Apache Incubator

 This vote will remain open for at least 72 hours from now (till 15 Sep
 2012, NOON PST). Please find the proposed board resolution below.

 [1] http://s.apache.org/SGm
 [2] http://s.apache.org/LOA

 Thanks,
 Roman Shaposhnik

 X. Establish the Apache Bigtop 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 related to a system for integration,
packaging, deployment and validation of a big data management
software distribution based on Apache Hadoop
for distribution at no charge to the public.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Bigtop Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Bigtop Project be and hereby is
responsible for the creation and maintenance of software
related to a system for
open-source software related to a system for integration,
packaging, deployment and validation of a big data management
software distribution based on Apache Hadoop; and be it further

RESOLVED, that the office of Vice President, Apache Bigtop 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 Bigtop Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Bigtop 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 Bigtop Project:

 * Alan Gatesga...@apache.org
 * Patrick Hunt  ph...@apache.org
 * Steve Loughranste...@apache.org
 * Tom White tomwh...@apache.org

 * Alejandro Abdelnurt...@apache.org
 * Andrew Bayer  aba...@apache.org
 * Konstantin Boudnikc...@apache.org
 * Stephen Chu   s...@apache.org
 * Bruno Mahébm...@apache.org
 * Peter Linnell plinn...@apache.org
 * James Pagejamesp...@apache.org
 * Patrick Taylor Ramsey p...@apache.org
 * Roman Shaposhnik  r...@apache.org
 * Michael Stack st...@apache.org
 * Andrei Savu   as...@apache.org
 * Edward J. Yoonedwardy...@apache.org

 * Andre Arcilla arci...@apache.org
 * Eli Collins   e...@apache.org
 * Travis Crawford   traviscrawf...@apache.org
 * John Sichij...@apache.org
 * Owen O'Malley omal...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Roman Shaposhnik
be appointed to the office of Vice President, Apache Bigtop,
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 Bigtop 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 Bigtop Project; and be it further

RESOLVED, that the Apache Bigtop Project

Re: [VOTE] S4 0.5.0 Release Candidate 1

[Patrick Hunt]

+1. The signature and checksum files all verify for me. I ran through
the release checklist and that seems fine. RAT check looked good.
license/notice files look valid for both src and bin artifacts.

Patrick

On Wed, Aug 1, 2012 at 4:11 PM, Flavio Junqueira f...@yahoo-inc.com wrote:
 +1, I checked that the src artifact compiles and tests pass. I have also gone 
 through license and notice files for the bin artifact, and I couldn't spot 
 any issue.

 On Aug 1, 2012, at 7:16 PM, Leo Neumeyer wrote:

 +1 Thank you for your leadership, Matthieu.

 On Wed, Aug 1, 2012 at 7:54 AM, kishore g g.kish...@gmail.com wrote:

 +1

 On Wed, Aug 1, 2012 at 2:55 AM, Daniel Gómez Ferro
 danie...@yahoo-inc.comwrote:

 +1

 * Signatures and checksums match
 * I created and ran a simple app using both src and bin packages with a
 clean maven/gradle repository
 * src package matches git tag
 * All tests pass



 On 31/7/12 17:02 , Matthieu Morel wrote:

 Hello,

 this is the first release candidate for Apache S4, version 0.5.0

 It fixes the following issues:
 https://issues.apache.org/**jira/secure/ReleaseNote.jspa?**
 projectId=12312322version=**12318653
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312322version=12318653


 *** Please download, test and vote by Friday August 3rd 2012, 16.00 GMT

 Note that we are voting upon the source (tag), binaries are provided for
 convenience.

 Source and binary packages in zip format:
 http://people.apache.org/~**mmorel/s4-0.5.0-incubating-**
 release-candidate-1/
 http://people.apache.org/~mmorel/s4-0.5.0-incubating-release-candidate-1/

 The (git) tag to be voted upon: 0.5.0:

 https://git-wip-us.apache.org/**repos/asf?p=incubator-s4.git;**a=tag;h=**
 70806aa1ee0b9154d36fd834dc4907**cd8d3eb791
 https://git-wip-us.apache.org/repos/asf?p=incubator-s4.git;a=tag;h=70806aa1ee0b9154d36fd834dc4907cd8d3eb791


 S4 KEYS file containing PGP keys we use to sign the release:
 http://svn.apache.org/repos/**asf/incubator/s4/dist/KEYS
 http://svn.apache.org/repos/asf/incubator/s4/dist/KEYS

 Please cast your vote.

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


 NOTES:

 - The vote is open until Friday August 3rd 2012, 16.00 GMT and passes if
 a majority of at least 3 +1 IPMC votes are cast.

 - All votes are welcome, only Podling Project Management Committe (PPMC)
 votes are binding, current PPMC = mentors + initial committers

 - After approval from the development community, we shall require
 approval from Incubator PMCs through another vote on the general
 incubator mailing list.






 --

 Leo Neumeyer (@leoneu)


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

Re: [VOTE] S4 0.5.0 Release Candidate 1

[Patrick Hunt]

You need passes if a majority of at least 3 +1 IPMC votes are cast..
afaict so far you have 1 (me).

Patrick

On Fri, Aug 3, 2012 at 1:30 AM, Flavio Junqueira f...@s4.io wrote:
 We are missing an IPMC vote for this release and the vote closes today. Can 
 we get an IPMC member to vote, please?

 Thanks,
 -Flavio

 On Aug 2, 2012, at 1:11 AM, Flavio Junqueira wrote:

 +1, I checked that the src artifact compiles and tests pass. I have also 
 gone through license and notice files for the bin artifact, and I couldn't 
 spot any issue.

 On Aug 1, 2012, at 7:16 PM, Leo Neumeyer wrote:

 +1 Thank you for your leadership, Matthieu.

 On Wed, Aug 1, 2012 at 7:54 AM, kishore g g.kish...@gmail.com wrote:

 +1

 On Wed, Aug 1, 2012 at 2:55 AM, Daniel Gómez Ferro
 danie...@yahoo-inc.comwrote:

 +1

 * Signatures and checksums match
 * I created and ran a simple app using both src and bin packages with a
 clean maven/gradle repository
 * src package matches git tag
 * All tests pass



 On 31/7/12 17:02 , Matthieu Morel wrote:

 Hello,

 this is the first release candidate for Apache S4, version 0.5.0

 It fixes the following issues:
 https://issues.apache.org/**jira/secure/ReleaseNote.jspa?**
 projectId=12312322version=**12318653
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312322version=12318653


 *** Please download, test and vote by Friday August 3rd 2012, 16.00 GMT

 Note that we are voting upon the source (tag), binaries are provided for
 convenience.

 Source and binary packages in zip format:
 http://people.apache.org/~**mmorel/s4-0.5.0-incubating-**
 release-candidate-1/
 http://people.apache.org/~mmorel/s4-0.5.0-incubating-release-candidate-1/

 The (git) tag to be voted upon: 0.5.0:

 https://git-wip-us.apache.org/**repos/asf?p=incubator-s4.git;**a=tag;h=**
 70806aa1ee0b9154d36fd834dc4907**cd8d3eb791
 https://git-wip-us.apache.org/repos/asf?p=incubator-s4.git;a=tag;h=70806aa1ee0b9154d36fd834dc4907cd8d3eb791


 S4 KEYS file containing PGP keys we use to sign the release:
 http://svn.apache.org/repos/**asf/incubator/s4/dist/KEYS
 http://svn.apache.org/repos/asf/incubator/s4/dist/KEYS

 Please cast your vote.

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


 NOTES:

 - The vote is open until Friday August 3rd 2012, 16.00 GMT and passes if
 a majority of at least 3 +1 IPMC votes are cast.

 - All votes are welcome, only Podling Project Management Committe (PPMC)
 votes are binding, current PPMC = mentors + initial committers

 - After approval from the development community, we shall require
 approval from Incubator PMCs through another vote on the general
 incubator mailing list.






 --

 Leo Neumeyer (@leoneu)


 -
 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] S4 0.5.0 Release Candidate 1

[Patrick Hunt]

FYI, you should CC the incubator general list on release votes.

I mentioned it on the dev list - the incubator status page for s4
needs to be updated, it's significantly out of date.

Patrick

On Tue, Jul 31, 2012 at 8:02 AM, Matthieu Morel mmo...@apache.org wrote:
 Hello,

 this is the first release candidate for Apache S4, version 0.5.0

 It fixes the following issues:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312322version=12318653

 *** Please download, test and vote by Friday August 3rd 2012, 16.00 GMT

 Note that we are voting upon the source (tag), binaries are provided for
 convenience.

 Source and binary packages in zip format:
 http://people.apache.org/~mmorel/s4-0.5.0-incubating-release-candidate-1/

 The (git) tag to be voted upon: 0.5.0:
 https://git-wip-us.apache.org/repos/asf?p=incubator-s4.git;a=tag;h=70806aa1ee0b9154d36fd834dc4907cd8d3eb791

 S4 KEYS file containing PGP keys we use to sign the release:
 http://svn.apache.org/repos/asf/incubator/s4/dist/KEYS

 Please cast your vote.

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


 NOTES:

 - The vote is open until Friday August 3rd 2012, 16.00 GMT and passes if a
 majority of at least 3 +1 IPMC votes are cast.

 - All votes are welcome, only Podling Project Management Committe (PPMC)
 votes are binding, current PPMC = mentors + initial committers

 - After approval from the development community, we shall require approval
 from Incubator PMCs through another vote on the general incubator mailing
 list.


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

[RESULT][VOTE] Accept Blur into the Apache Incubator

[Patrick Hunt]

Blur has been accepted into the incubator with the following vote tally:

+1 : 15  (10 binding)
-1 : 0

Patrick

vote details:
Dave Fisher (binding)
Bill Graham
Tim Williams (binding)
Jukka Zitting (binding)
Mohammad Nour El-Din (binding)
Patrick Hunt (binding)
Ashish Paliwal
Olivier Lamy (binding)
Brock Noland
Doug Cutting (binding)
Sajeevan Achuthan
Julien Vermillard (binding)
Tommaso Teofili (binding)
Tom White (binding)
Eric Charles

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

Re: [VOTE] Accept Blur into the Apache Incubator

[Patrick Hunt]

 of being orphaned. The customers that
 currently use Blur are committed to improving the codebase of the
 project due to its fulfilling needs not addressed by any other
 software. In addition, one customer is providing financial support to
 further develop Blur given its importance on mission-critical
 projects.

 === Inexperience with Open Source ===
 The codebase has been treated internally as an open source project
 since its beginning, and Near Infinity has extensive experience
 developing and releasing open source projects
 (http://www.nearinfinity.com/products/open_source). We do not
 anticipate difficulty in operating under the Apache Way.

 === Homogeneous Developers ===
 Current developers are all employed by Near Infinity but we are
 actively seeking contributors from different companies and would
 welcome their participation.

 === Reliance on Salaried Developers ===
 Blur was originally created by Aaron !McCurry as a personal project
 and he remains the primary contributor.  Currently, Aaron’s employer
 (Near Infinity) fully supports his continued participation with paid,
 dedicated time to work on Blur. All other current developers are paid
 by Near Infinity to work on Blur as well.

 === Relationships with Other Apache Products ===
 Blur dependencies:

  * Apache Hadoop
  * Apache Lucene
  * Apache !ZooKeeper
  * Apache Thrift
  * Apache log4j

 === Apache Brand ===
 Our interest in releasing this code as an Apache project is due to its
 strong relationship with other Apache projects, i.e. Blur has
 dependencies on Hadoop, Lucene, !ZooKeeper, and Thrift and its
 uniqueness within the Hadoop ecosystem.

 == Documentation ==
 Current documentation can be found at http://blur.io and
 https://github.com/nearinfinity/blur.

 == Initial Source ==
 Blur has been in development since summer 2010. The core codebase
 consists of about ~29,000 (~10,000 if the generated RPC code is not
 included) lines of code mainly Java.

 == Source and Intellectual Property Submission Plan ==
 Blur core code, examples, documentation, and training materials will
 be submitted by Near Infinity Corporation.

 == External Dependencies ==
  * concurrentlinkedhashmap - Apache 2.0 License -
 http://code.google.com/p/concurrentlinkedhashmap/

 == Cryptography ==
 none

 == Required Resources ==
  * Mailing Lists
* blur-private
* blur-dev
* blur-commits
* blur-user
  * Subversion Directory
* https://git-wip-us.apache.org/repos/asf/blur.git
  * Issue Tracking
* JIRA
  * Continuous Integration
* Jenkins
  * Web
* http://incubator.apache.org/blur/wiki at http://wiki.apache.org
 or http://cwiki.apache.org

 == Initial Committers ==
  * Aaron !McCurry (aaron.mccurry at nearinfinity dot com)
  * Scott Leberknight (scott.leberknight at nearinfinity dot com)
  * Ryan Gimmy (ryan.gimmy at nearinfinity dot com)
  * Tim Williams (twilliams at apache dot org)
  * Patrick Hunt (phunt at apache dot org)
  * Doug Cutting (cutting at apache dot org)

 == Affiliations ==
  * Aaron !McCurry, Near Infinity
  * Scott Leberknight, Near Infinity
  * Ryan Gimmy, Near Infinity
  * Patrick Hunt, Cloudera
  * Doug Cutting, Cloudera

 == Sponsors ==
  * Champion: Patrick Hunt

 == Nominated Mentors ==
  * Tim Williams  (twilliams at apache dot org)
  * Doug Cutting (cutting at apache dot org)
  * Patrick Hunt (phunt at apache dot org)

 == Sponsoring Entity ==
  * Apache Incubator

 -
 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: S4 status (Was: [Incubator Wiki] Update of June2012 by PatrickHunt)

[Patrick Hunt]

On Tue, Jun 12, 2012 at 10:39 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 On Wed, Jun 6, 2012 at 1:46 PM, Apache Wiki wikidi...@apache.org wrote:
 +  1. Still working towards an initial release on Apache with the current
 +     code (version 0.4 = version 0.3 + checkpointing + bugfixes)

 Is there some specific issue blocking the release? You've been
 incubating for 1.5 years already, which is a long time without a
 release. Quite a few podlings have trouble coming up with their first
 release, so I'm wondering if there's something specific we could do to
 make that task easier.

Hi Jukka, I agree they should create a release soon, however it's just
been 9 months (sept 2011) not 1.5 yrs since incubation started.

Regards,

Patrick

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

Re: ANNOUNCE Apache Oozie 3.2.0 release

[Patrick Hunt]

Seems that was dropped from the template? it's here on the how to
release page: http://incubator.apache.org/oozie/HowToRelease.html

On Sun, Jun 10, 2012 at 6:45 AM, sebb seb...@gmail.com wrote:
 On 9 June 2012 15:36, Alejandro Abdelnur t...@apache.org wrote:
 The Apache Oozie team is pleased to announce the release of Oozie
 3.2.0 from the Apache Incubator.

 Please include a brief synopsis (1 or 2 sentences) of what Oozie is in
 all announcements sent outside the Oozie mailing lists.

 The Oozie developers and users will (presumably) know what Oozie is,
 but others are unlikely to know.

 Yes, they can click on the link, but why should the have to do so?

 Providing the details can help promote the podling.

 Note: the announcement should also be sent to the general incubator
 list (copied with this reply)

 The details of the release and download location can be found at
 http://incubator.apache.org/oozie

 The highlights of this release are:

 * Hive action
 * Sqoop action
 * Shell action
 * Tool to create/upgrade database schema
 * Kerberos SPNEGO authentication
 * Proxy User capabilities for Oozie users
 * Job ACLs support
 * Improved Job information over HTTP REST API
 * Improved Workflow validation
 * Sharelib directories per action
 * New EL functions for Workflow and Coordinator applications

 In addition it includes several improvements for performance and
 stability and several bug fixes.

 Your help and feedback is more than welcome. For more information on
 how to report problems and to get involved, visit the project website
 at http://incubator.apache.org/oozie/.

 The Apache Oozie Team

 -
 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: Flume Graduation (was Re: June reports in two weeks)

[Patrick Hunt]

Isn't this why we vote. To come to a decision when consensus can't be
reached and allow people to move on.

Patrick

On Tue, Jun 5, 2012 at 8:22 AM, Ralph Goers ralph.go...@dslextreme.com wrote:



 The graduation requirements say

 The project is considered to have a diverse community when it is not highly 
 dependent on any single contributor (there are at least 3 legally independent 
 committers and there is no single company or entity that is vital to the 
 success of the project). Basically this means that when a project mostly 
 consists of contributors from one company, this is a sign of not being 
 diverse enough..

 This doesn't specify a hard number. In fact, Roy responded to this thread 
 saying he doesn't believe there even is a diversity requirement  -

 There is no diversity requirement for graduating from the incubator. In many 
 ways, incubation hinders community growth. The requirement is that the 
 project makes decisions as an Apache project, not in private, which is harder 
 to get used to doing if a lot of people share the same office.

 So I am left a bit confused. If I go by the what the graduation page says 
 literally, then all the statistics that have been generated would seem to 
 show that Cloudera is vital to the success of the project. Although Arvind is 
 a bit of the driving force, I'm sure if something terrible were to happen to 
 him Cloudera would insure his energy was replaced. However, if something 
 terrible happened to Cloudera I suspect we would have several Apache projects 
 in trouble, not just Flume.

 While I clearly don't like some of the ways the project has chosen to 
 organize itself, all those decisions were done properly and in public. Again, 
 while I don't like that little discussion happens on the dev list, it does 
 happen in Jira issues and in the review board, all of which is routed to the 
 dev list, so again, most, if not all, of the development is done in public.

 So my answer to the question is really that I am finding it hard to reconcile 
 whether we actually have or should have a diversity requirement. From what 
 I've been told privately Flume would certainly not be the first project to 
 graduate from the incubator in a similar situation.

 The other thing I find interesting is that I am also the only non-Cloudera 
 mentor on the project. I find it a bit odd that while the incubator has the 
 requirement for graduation it doesn't have any such requirement for a 
 codling's mentors.  That said, IMO every one of the mentors on the project 
 has been doing a good job.

 One other disclaimer. My employer is a customer of Cloudera specifically for 
 paid support for Flume, so I also have a vested interest in seeing both the 
 project and Cloudera succeed.  However, with regards to Flume's graduation, I 
 haven't even discussed this issue with anyone in by $dayjob.

 So again - if the basis we are to use is whether a single company or entity 
 is vital to a project then I don't believe Flume is quite there. OTOH I am 
 not completely necessary that that is vital for graduation, in which case the 
 section in the graduation requirements needs to be changed. So at this point 
 the best I can do is say I'm not really sure how to vote.

 Ralph





 On Jun 5, 2012, at 6:49 AM, Alan Gates wrote:


 On Jun 5, 2012, at 2:19 PM, Marvin Humphrey wrote:

 On Sat, May 26, 2012 at 11:44 PM, Ralph Goers
 ralph.go...@dslextreme.com wrote:
 Another way of  looking at these same statistics:
 Cloudera - 217
 Other - 16

 That means Cloudera is responsible for over 93% of the Jira issues.  It is
 great that Cloudera is doing so much work but those stats hardly prove
 diversity.

 I was surprised to see the IPMC Flume graduation VOTE today -- I don't 
 recall
 seeing another situation like it in the last couple years, where the 
 community
 graduation VOTE was contended.

 I checked the Flume dev list archives and I don't see a message from Ralph
 indicating that he thinks the latest measures address the concerns that have
 been raised.


 Agreed.  It's hard to vote for graduation for a podling when one of the 
 mentors feels strongly that the podling is not ready.

 Alan.


 -
 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: June reports in two weeks

[Patrick Hunt]

On Tue, Jun 5, 2012 at 1:01 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 There is currently no shepherd assigned, someone want to volunteer
 or doesn't it make sense at this point?

 I'll give a closer look at your upcoming report unless someone beats
 me to it. I guess you're still busy setting things up, so there are no
 broader graduation concerns yet.

Yes, pretty mechanical at this point. (committer accounts just
created, I was requesting the mailing lists yesterday :-) )

Patrick

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

Re: June reports in two weeks

[Patrick Hunt]

Btw, S4 is short a mentor. It would be great if one or two IPMC
members could volunteer and help Arun and I with mentorship duties.

Regards,

Patrick

On Wed, May 23, 2012 at 5:36 PM, Patrick Hunt ph...@apache.org wrote:
 Hi Jukka, I'm also concerned for S4 not having a release and low
 activity. I pinged them about cutting a release a couple months ago
 and they said they weren't ready. As for activity there is some
 mailing list traffic but almost no jira/commits listed in april/may.

 For Bigtop i've been tracking diversity. A couple weeks ago I reviewed
 their recent commits and didn't see anyone that might be a good fit
 for new committer. I know they are trying hard though hosting events,
 helping new contributors, etc... but so far diversity continues to be
 low. Perhaps someone will have some insight on how to gather new
 contributors that hasn't been tried yet?

 Patrick

 On Wed, May 23, 2012 at 4:28 PM, Jukka Zitting jukka.zitt...@gmail.com 
 wrote:
 Hi all,

 There's plenty of time still before the June reports [1] start flowing
 in. As an early remainder to podlings starting to draft their reports,
 here's how the IPMC saw your status as of the previous quarterly
 report in March [2]:

  IP clearance: Openmeetings
  No release: Bloodhound, Cordova, OpenOffice
  Low activity: Kalumet, Kato
  Low diversity: Bigtop, Etch, Isis, HCatalog, S4, Wave
  Ready to graduate: Flume

 Has the situation in your podling changed over the last three months?
 If not, what's your plan for improving the situation? Is there
 anything for which you'd appreciate more help?

 I'm especially worried about Kato as it seems like the project has
 more or less died even though the JSR 326 / Oracle trouble got finally
 sorted out. Is it time to retire the project or can we hope for a
 revival?

 I also wanted to start preparing for this reporting round in good time
 by assigning shepherds [3] already now. Using a fuzzy algorithm based
 on the available volunteers, their stated preferences, and the
 podlings they're already mentoring, I came up with the following
 initial assignments that I've also recorded on the wiki page:

  Benson Margulies - CloudStack, HCatalog, Kato
  Dave Fisher      - Bloodhound, Flume
  Matt Franklin    - Bigtop, Flex, Openmeetings
  Matt Hogstrom    - Cordova, OpenOffice.org
  Jukka Zitting    - Etch, Isis, S4
  Mohammad Nour    - Kalumet
  Ross Gardler     - Wave

 Feel free to shuffle these around or ask for someone else to fill in
 if you're expecting to be too busy for the extra reviews in early
 June. Other IPMC members and interested observers, please jump in and
 volunteer as extra shepherds if you'd like to help this effort.

 As discussed earlier, shepherds are not there to replace existing
 mentors. If everything is going well with a project, the shepherd can
 simply acknowledge a report and move on. If there are any relevant
 questions that the report doesn't answer, the shepherd may ask the
 podling and its mentors for more details. And finally if something
 seems wrong, the shepherd should raise a flag for the mentors and the
 rest of the IPMC to focus on. Most importantly, we need to be talking
 *with* the podlings, not just *about* them, so especially any
 constructive and encouraging feedback to them will be highly useful.

 [1] http://wiki.apache.org/incubator/June2012
 [2] http://wiki.apache.org/incubator/March2012
 [3] http://wiki.apache.org/incubator/IncubatorShepherds

 BR,

 Jukka Zitting

 -
 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: Flume Graduation (was Re: June reports in two weeks)

[Patrick Hunt]

On Tue, Jun 5, 2012 at 11:01 AM, Marvin Humphrey mar...@rectangular.com wrote:
 On Tue, Jun 5, 2012 at 9:53 AM, Patrick Hunt ph...@apache.org wrote:
 Isn't this why we vote. To come to a decision when consensus can't be
 reached and allow people to move on.

 When diversity concerns were raised in the ManifoldCF podling by Jukka,
 graduation was delayed to address them.

 When diversity concerns were raised in the Lucy podling by Torsten Curdt,
 graduation was delayed to address them.

 When diversity concerns were raised with regards to Flume, a VOTE was called.


I think that's an oversimplification that ignores the work and good
faith the Flume community has done to address the concerns raised.
Extensive discussion ensued and afaict Ralph's concerns were
addressed. He raised issues and the community worked to resolve them.
(ie promoting committers to pmc as part of graduation).

 Contentious VOTEs force people to take sides and create winners and losers
 where none existed before.  It is often worth going the extra mile to avoid
 imposing a tyranny of the majority and fostering alienation.

 In my opinion, there would be a benefit to the Flume community for staying in
 the Incubator a while longer and wrestling with how to increase diversity.
 Have you folks ever had a non-Cloudera Release Manager?  Was there ever a
 possibility of a non-Cloudera Flume VP?  How about waiting until someone other
 than a Cloudera person emerges who is willing to lead a graduation push?  I
 think the community would develop healthy habits by prioritizing such concerns
 for a little while.

 On the other hand, there are benefits to graduation in terms of enlarging the
 pool of potential contributors by those who are willing to get involved with
 graduated projects but not podlings.  Ralph has shown an open mind and has
 been weighing the plusses and minuses.  We all want what is best for Flume.


All great ideas. But this highlights my concern and the problem I have
with many of these discussions.

I've been on the other side of the fence on this stuff. You're trying
to make forward progress. How do you separate the must do's from the
good ideas. From what I could see the Flume community worked with
the IPMC to review the status and address any concerns. At which point
the vote was moved forward. If you don't agree then -1. That's why we
have voting. That's why it's majority vs veto'able. If the vote
doesn't pass is will list explicit grounds for a -1, the community can
go back, address those, and start a new vote when the issues are
addressed. There should be no shame in getting a -1, voting (after
healthy discussion) allows the community to speak clearly and
definitively and it also respects the community requesting the vote.

Patrick

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

Re: [VOTE] Release Oozie 3.2.0-incubating (candidate 1)

[Patrick Hunt]

+1. sig/xsum verified. The RAT report looks good.  I ran through the
incubator release checklist and all of the items seem to be covered. I
was able to run all of the unit tests successfully.

Patrick

On Fri, Jun 1, 2012 at 4:35 PM, Alejandro Abdelnur t...@cloudera.com wrote:
 Dear Incubator PMCs,

 Oozie Incubator community has voted on the Oozie 3.2.0-incubating release.

 The tally of the votes is:

 Results: 8 +1 votes, 0 -1 votes

  developers/users: 3 +1 (mona, jeremy, roman)
  committers: 4 +1 (harsh, virag, angelo, tucu)
  mentors: 1 +1 (alan)

 Below you'll find the email sent to the Oozie developer alias with the VOTE
 request. There you'll find the details of the release and where to download
 the release artifact.

 Vote closes on Monday JUN/04 17:00 PST.

 Thanks

 Alejandro

 -- Forwarded message --
 From: Alejandro Abdelnur t...@cloudera.com
 Date: Tue, May 29, 2012 at 3:23 PM
 Subject: [VOTE] Release Oozie 3.2.0-incubating (candidate 1)
 To: oozie-...@incubator.apache.org


 Dear Oozie community,

 The release candidate 1 for for Oozie 3.2.0-incubating is available.

 Changes from candidate 0:

 * removes native files and adds instructions on how to test Pipe
 * consolidate rat report
 * minor fix in the demo example


 Some of the new features are:

 * Hive action
 * Sqoop action
 * Shell action
 * Tool to create/upgrade database schema
 * Kerberos SPNEGO authentication
 * Proxy User capabilities for Oozie users
 * Job ACLs support
 * Improved Job information over HTTP REST API
 * Improved Workflow validation
 * Sharelib directories per action
 * EL functions for Workflow and Coordinator applications

 In addition it includes several improvements for performance and
 stability and several bug fixes.

 Keys used to sign the release are available at
 http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup.

 Please download, test, and try it out:

   http://people.apache.org/~tucu/oozie-3.2.0-incubating-candidate-1

 The release, md5 signature, gpg signature, and rat report can all be
 found at the above URL.

 Vote closes on Friday JUN/01 15:30 PST.

 Thanks

 --
 Alejandro

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

Re: June reports in two weeks

[Patrick Hunt]

I've added Crunch to the monthly report for June. There is currently
no shepherd assigned, someone want to volunteer or doesn't it make
sense at this point?

Patrick

On Wed, May 23, 2012 at 4:28 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 Hi all,

 There's plenty of time still before the June reports [1] start flowing
 in. As an early remainder to podlings starting to draft their reports,
 here's how the IPMC saw your status as of the previous quarterly
 report in March [2]:

  IP clearance: Openmeetings
  No release: Bloodhound, Cordova, OpenOffice
  Low activity: Kalumet, Kato
  Low diversity: Bigtop, Etch, Isis, HCatalog, S4, Wave
  Ready to graduate: Flume

 Has the situation in your podling changed over the last three months?
 If not, what's your plan for improving the situation? Is there
 anything for which you'd appreciate more help?

 I'm especially worried about Kato as it seems like the project has
 more or less died even though the JSR 326 / Oracle trouble got finally
 sorted out. Is it time to retire the project or can we hope for a
 revival?

 I also wanted to start preparing for this reporting round in good time
 by assigning shepherds [3] already now. Using a fuzzy algorithm based
 on the available volunteers, their stated preferences, and the
 podlings they're already mentoring, I came up with the following
 initial assignments that I've also recorded on the wiki page:

  Benson Margulies - CloudStack, HCatalog, Kato
  Dave Fisher      - Bloodhound, Flume
  Matt Franklin    - Bigtop, Flex, Openmeetings
  Matt Hogstrom    - Cordova, OpenOffice.org
  Jukka Zitting    - Etch, Isis, S4
  Mohammad Nour    - Kalumet
  Ross Gardler     - Wave

 Feel free to shuffle these around or ask for someone else to fill in
 if you're expecting to be too busy for the extra reviews in early
 June. Other IPMC members and interested observers, please jump in and
 volunteer as extra shepherds if you'd like to help this effort.

 As discussed earlier, shepherds are not there to replace existing
 mentors. If everything is going well with a project, the shepherd can
 simply acknowledge a report and move on. If there are any relevant
 questions that the report doesn't answer, the shepherd may ask the
 podling and its mentors for more details. And finally if something
 seems wrong, the shepherd should raise a flag for the mentors and the
 rest of the IPMC to focus on. Most importantly, we need to be talking
 *with* the podlings, not just *about* them, so especially any
 constructive and encouraging feedback to them will be highly useful.

 [1] http://wiki.apache.org/incubator/June2012
 [2] http://wiki.apache.org/incubator/March2012
 [3] http://wiki.apache.org/incubator/IncubatorShepherds

 BR,

 Jukka Zitting

 -
 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: Flume Graduation (was Re: June reports in two weeks)

[Patrick Hunt]

On Wed, May 23, 2012 at 11:18 PM, Ralph Goers
ralph.go...@dslextreme.com wrote:

 On May 23, 2012, at 10:48 PM, Patrick Hunt wrote:

 On Wed, May 23, 2012 at 10:36 PM, Ralph Goers
 ralph.go...@dslextreme.com wrote:

 On May 23, 2012, at 10:15 PM, Benson Margulies wrote:

 On Wed, May 23, 2012 at 10:09 PM, Ralph Goers
 ralph.go...@dslextreme.com wrote:
 Right after I read Jukka's email that started this thread and I posted my 
 reply and discovered to my shock that they had started a graduation vote. 
  I am shocked because I have pointed out repeatedly the project's 
 complete lack of diversity.  Virtually all the active PMC members and 
 committers work for the same employer.  I have told them several times 
 that I would actually like to participate in the project but the way the 
 project works is very different then every other project I am involved 
 with at the ASF and the barriers to figure out what is actually going on 
 is very high. Almost nothing is discussed directly on the dev list - it 
 is all done through Jira issues or the Review tool.  While all the Jira 
 issue updates and reviews are sent to the dev list most of that is just 
 noise.  Feel free to review the dev list archives to see what I am 
 talking about.

 I don't follow flume, but I'd propose to soften your objection only
 slightly. I've met other groups of people who like a JIRA centric view
 of the world. I suspect that if they did a bunch of other good things
 called out below, you or others would find the JIRA business
 digestible. Also, on the other hand, I fear that the co-employed
 contributors are collaborating in the hallway, and the lack of the
 context in JIRA or on the list is contributing to the problem.

 I have reason to doubt the collaboration in the hallway aspect and I 
 certainly do not doubt everyone's good intent.  I'm not objecting to the 
 collaboration style as an issue preventing graduation. I'm just saying I 
 find it difficult to participate with that style and that simply makes me 
 wonder if that is making it harder to attract new committers.  I fully 
 realize that that issue might just be with me, but the fact remains that 
 there is practically no diversity in the project and I cannot in good 
 conscience recommend graduation for a project in that situation.


 Hi Ralph, Benson, et. al., some background:

 Flume is similar to Hadoop and other related projects in that it is
 very jira heavy for development activity. No slouch in terms of
 mailing list traffic either though (1200 last month):
 http://flume.markmail.org/

 Sorry I didn't include this in my prior post but here you are making my point 
 exactly.  I participate in several other Apache projects. Wading through 
 1200+ emails per month that are largely Jira/Review noise makes it very 
 difficult for me to find posts that have any value. As a consequence I am 
 largely forced to simply delete everything generated by he Review tool and 
 Jira.  And I'm a mentor. I just don't see how newcomers are going to find 
 this style welcoming.

There are separate lists it's just that markmail clubs them all
together. It's also pretty easy to filter...

Patrick

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

Re: [VOTE] Accept Crunch into the Apache Incubator

[Patrick Hunt]

+1

Patrick

On Wed, May 23, 2012 at 2:49 PM, Alan D. Cabrera l...@toolazydogs.com wrote:
 +1


 Regards,
 Alan


 On May 23, 2012, at 11:45 AM, Josh Wills wrote:

 I would like to call a vote for accepting Apache Crunch for
 incubation in the Apache Incubator. The full proposal is available
 below.  We ask the Incubator PMC to sponsor it, with phunt as
 Champion, and phunt, tomwhite, and acmurthy volunteering to be
 Mentors.

 Please cast your vote:

 [ ] +1, bring Crunch into Incubator
 [ ] +0, I don't care either way,
 [ ] -1, do not bring Crunch into Incubator, because...

 This vote will be open for 72 hours and only votes from the Incubator
 PMC are binding.

 http://wiki.apache.org/incubator/CrunchProposal


 -
 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: June reports in two weeks

[Patrick Hunt]

Hi Jukka, I'm also concerned for S4 not having a release and low
activity. I pinged them about cutting a release a couple months ago
and they said they weren't ready. As for activity there is some
mailing list traffic but almost no jira/commits listed in april/may.

For Bigtop i've been tracking diversity. A couple weeks ago I reviewed
their recent commits and didn't see anyone that might be a good fit
for new committer. I know they are trying hard though hosting events,
helping new contributors, etc... but so far diversity continues to be
low. Perhaps someone will have some insight on how to gather new
contributors that hasn't been tried yet?

Patrick

On Wed, May 23, 2012 at 4:28 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 Hi all,

 There's plenty of time still before the June reports [1] start flowing
 in. As an early remainder to podlings starting to draft their reports,
 here's how the IPMC saw your status as of the previous quarterly
 report in March [2]:

  IP clearance: Openmeetings
  No release: Bloodhound, Cordova, OpenOffice
  Low activity: Kalumet, Kato
  Low diversity: Bigtop, Etch, Isis, HCatalog, S4, Wave
  Ready to graduate: Flume

 Has the situation in your podling changed over the last three months?
 If not, what's your plan for improving the situation? Is there
 anything for which you'd appreciate more help?

 I'm especially worried about Kato as it seems like the project has
 more or less died even though the JSR 326 / Oracle trouble got finally
 sorted out. Is it time to retire the project or can we hope for a
 revival?

 I also wanted to start preparing for this reporting round in good time
 by assigning shepherds [3] already now. Using a fuzzy algorithm based
 on the available volunteers, their stated preferences, and the
 podlings they're already mentoring, I came up with the following
 initial assignments that I've also recorded on the wiki page:

  Benson Margulies - CloudStack, HCatalog, Kato
  Dave Fisher      - Bloodhound, Flume
  Matt Franklin    - Bigtop, Flex, Openmeetings
  Matt Hogstrom    - Cordova, OpenOffice.org
  Jukka Zitting    - Etch, Isis, S4
  Mohammad Nour    - Kalumet
  Ross Gardler     - Wave

 Feel free to shuffle these around or ask for someone else to fill in
 if you're expecting to be too busy for the extra reviews in early
 June. Other IPMC members and interested observers, please jump in and
 volunteer as extra shepherds if you'd like to help this effort.

 As discussed earlier, shepherds are not there to replace existing
 mentors. If everything is going well with a project, the shepherd can
 simply acknowledge a report and move on. If there are any relevant
 questions that the report doesn't answer, the shepherd may ask the
 podling and its mentors for more details. And finally if something
 seems wrong, the shepherd should raise a flag for the mentors and the
 rest of the IPMC to focus on. Most importantly, we need to be talking
 *with* the podlings, not just *about* them, so especially any
 constructive and encouraging feedback to them will be highly useful.

 [1] http://wiki.apache.org/incubator/June2012
 [2] http://wiki.apache.org/incubator/March2012
 [3] http://wiki.apache.org/incubator/IncubatorShepherds

 BR,

 Jukka Zitting

 -
 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: Flume Graduation (was Re: June reports in two weeks)

[Patrick Hunt]

On Wed, May 23, 2012 at 10:36 PM, Ralph Goers
ralph.go...@dslextreme.com wrote:

 On May 23, 2012, at 10:15 PM, Benson Margulies wrote:

 On Wed, May 23, 2012 at 10:09 PM, Ralph Goers
 ralph.go...@dslextreme.com wrote:
 Right after I read Jukka's email that started this thread and I posted my 
 reply and discovered to my shock that they had started a graduation vote.  
 I am shocked because I have pointed out repeatedly the project's complete 
 lack of diversity.  Virtually all the active PMC members and committers 
 work for the same employer.  I have told them several times that I would 
 actually like to participate in the project but the way the project works 
 is very different then every other project I am involved with at the ASF 
 and the barriers to figure out what is actually going on is very high. 
 Almost nothing is discussed directly on the dev list - it is all done 
 through Jira issues or the Review tool.  While all the Jira issue updates 
 and reviews are sent to the dev list most of that is just noise.  Feel free 
 to review the dev list archives to see what I am talking about.

 I don't follow flume, but I'd propose to soften your objection only
 slightly. I've met other groups of people who like a JIRA centric view
 of the world. I suspect that if they did a bunch of other good things
 called out below, you or others would find the JIRA business
 digestible. Also, on the other hand, I fear that the co-employed
 contributors are collaborating in the hallway, and the lack of the
 context in JIRA or on the list is contributing to the problem.

 I have reason to doubt the collaboration in the hallway aspect and I 
 certainly do not doubt everyone's good intent.  I'm not objecting to the 
 collaboration style as an issue preventing graduation. I'm just saying I find 
 it difficult to participate with that style and that simply makes me wonder 
 if that is making it harder to attract new committers.  I fully realize that 
 that issue might just be with me, but the fact remains that there is 
 practically no diversity in the project and I cannot in good conscience 
 recommend graduation for a project in that situation.


Hi Ralph, Benson, et. al., some background:

Flume is similar to Hadoop and other related projects in that it is
very jira heavy for development activity. No slouch in terms of
mailing list traffic either though (1200 last month):
http://flume.markmail.org/

Also note the extensive new developer type detail that's available
on the web/wiki:
https://cwiki.apache.org/confluence/display/FLUME/Index

The team list can provide insight into the diversity issue
http://incubator.apache.org/flume/team-list.html My understanding is
that there are at least 4 separate organizations represented by active
commiters.

Regards,

Patrick



 Needless to say, when the graduation proposal reaches this list, and I'm 
 sure it will, I will strongly endorse the IPMC to reject the proposal.

 FWIW, I found the post below to be 100% on target.

 Ralph



 On May 23, 2012, at 7:31 PM, Marvin Humphrey wrote:

 On Wed, May 23, 2012 at 5:36 PM, Patrick Hunt ph...@apache.org wrote:
 Perhaps someone will have some insight on how to gather new
 contributors that hasn't been tried yet?

 Jukka's written on this subject multiple times in the past.  Here are two
 gems, one from a while back, the other recent:

    http://markmail.org/message/o3gbgam4ny2upqte

    Most of the cases I've been involved so far of podlings in the hoping
    some more people come along have had symptoms of the project team not
    paying enough attention on making it easy for new contributors to show 
 up
    and stick around. Things like complex and undocumented build steps,
    missing Getting started or Getting involved guides, lack of quick 
 and
    positive feedback to newcomers, etc., are all too common. Fixing even 
 just
    some of such things will dramatically increase the odds of new people
    showing up.

    Those are things that are very easy to overlook when you're working on
    your first open source projects (it took me years to learn those 
 lessons),
    but we here have a massive amount of collective experience on such 
 things.
    That's what we could and IMHO should be sharing with the podlings. 
 That's
    what mentoring to me is about and that's where our most precious 
 added
    value is. Otherwise incubation just boils down to an indoctrination
    period on how to apply and conform to the various Apache rules and
    policies.

    http://incubator.markmail.org/thread/qpzg6wdoq7cwko55

    I've been involved with quite a few podlings with similar problems in
    attracting longer-term contributors. In my experience the best way to
    solve that problem is to change your mindset of expecting most such 
 people
    to be just one-off contributors. If you instead treat them as your next
    new committers and engage with them as peers, many (though of course not
    all) will respond in kind

Re: Policy for new committers to podlings

[Patrick Hunt]

On Fri, May 18, 2012 at 11:03 AM, Benson Margulies
bimargul...@gmail.com wrote:
 I'm embarrassed to report that I'm feeling a bit foggy on the new
 committer policy, and a quick tour with google failed to find it on a
 web page. We're long on pages about initial podling setup, and not so
 long on others.

 So, if a podling has held a vote for a new contributor, what exactly
 happens next? And what web page should I have read this on, and if it
 is actually missing, I'll go put it someplace.

is this what you're looking for?
http://incubator.apache.org/guides/ppmc.html (See Voting in a new
committer)


 -
 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] BOM and supported platforms for Bigtop 0.4.0

[Patrick Hunt]

On Sat, May 5, 2012 at 1:32 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 On Fri, May 4, 2012 at 11:00 PM, Roman Shaposhnik r...@apache.org wrote:
 Perhaps this preso can help a bit:
    http://people.apache.org/~rvs/apache-bigtop2.pdf

 Perfect, thanks!

Roman could you post this on the wiki? (looked but didn't notice it there)

Patrick

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

Re: [DISCUSS] BOM and supported platforms for Bigtop 0.4.0

[Patrick Hunt]

It's not the job of the incubator to create new rules, but rather to
help podlings to graduation while following existing Apache
guidelines. It's very clear from
http://www.apache.org/legal/resolved.html that what has been proposed
is acceptable under existing Apache rules. Bigtop is building
on/around ASL licensed software (packaging, iteroperability tests,
utilities, etc...), much like many other Apache projects, much like
other distributions do with Apache's own projects/software. I don't
see any reason to create new rules which limit the podling's ability
to include compatibly licensed software in their releases. (as long as
they follow the licenses of said software)

Patrick

On Thu, May 3, 2012 at 4:30 PM, Bruno Mahé br...@cloudera.com wrote:
 Hi,

 Please see my reply inline.

 On 05/03/2012 04:00 PM, Owen O'Malley wrote:
 On Thu, May 3, 2012 at 12:01 PM, Bruno Mahé bm...@apache.org wrote:

 As a mentor of the Bigtop project, I don't see it as acceptable for an
 Apache project to distribute binaries of non-Apache software. If the
 owners of the Hue project decide to donate it to Apache and it had
 been released by Apache, then it would be acceptable. I'm strictly -1
 on releasing any version of Bigtop with Hue or any other non-Apache
 software as part of the release.

 -- Owen


 As part of mentoring Apache Bigtop (incubating) project, it would also
 be greatly appreciated if you would explain why this -1.

 Apache Bigtop (incubating) does not and will not include anything that
 does not belong to the Apache Foundation.
 So I am really confused as to why this strong reaction.

 The strong reaction is because Roman was proposing a Bigtop release
 with rpms and debs for non-Apache projects. That is a non-starter.
 Apache will not distribute non-Apache projects. Saying that Bigtop
 does not release the projects that it incorporates is not justified
 given the fact that Bigtop is putting rpms of each of the incorporated
 projects into /dist/incubator/bigtop. The 2.9GB size of the latest
 Bigtop release has already caused infrastructure significant
 headaches.


 Seems like you are still (this is not the first time this is explained
 to you) conflating Apache releases on which members vote on, with
 convenience artefacts.
 Apache Bigtop (incubating) releases are not the packages. Apache Bigtop
 (incubating) releases are Apache Bigtop (incubating) source code.
 RPMs and DEBs are convenience artefact.
 If they are not that convenient to the Apache Foundation, I don't see
 the issue with not distributing the ones that are not convenient.

 As far as I know, Apache Infra was only asking for heads up. Which we
 will provide and we will pay attention to work more closely with them.
 I also fail to see the relationship between the size of the convenience
 artefacts and the bill of materials for the coming release of Apache
 Bigtop (incubating), which I repeat only contains Apache Bigtop
 (incubating) source code.

 So now we have establish that you issue is about the convenience
 artefacts, I don't see any remaining issue with Apache Bigtop
 (incubating) releases.


 The convenience artefact may pull Hue in, but this is in no way
 different from Apache Hadoop pulling in Google protocol buffer or Google
 guava. So again, how is this different? Is Apache Hadoop going to
 avandon Google Protocolbuffer?

 There is a big difference between referencing external projects that
 are required for your project's functionality and incorporating
 non-Apache projects into your project and publishing releases of them
 using independent artifacts. When the user installs a Hadoop rpm, the
 protobuf.jar is there under the hood, but is considered an
 implementation detail that is required for Hadoop to run.

 I'd complain similarly if Hadoop was downloading protobuf tarballs,
 making changes to protobuf, making protobuf rpms with those changes,
 and publishing those rpms on Apache's servers.


 In any case, there is still distribution of a non-Apache project's
 artefacts by both projects.
 You either distribute artefacts of it, or you don't. Here the end goal
 is not to provide packages, but a deployable big data stack. Packages
 are just a mean to an end.
 We don't distribute upstream projects, they are dependencies.


 However, it goes deeper than than that. If the user installs Bigtop's
 rpms and hits a bug do they contact Hue or Bigtop? Furthermore, I'm
 sure the links that are displayed when you run Bigtop's Hue point off
 to Cloudera's bug and support system. That kind of branding is not ok
 for an Apache project.


 Hue is not even integrated into Apache Bigtop (incubating). So let's
 cross that bridge when we get there. And in any case, this is an issue
 that can be fixed trivially, so I wouldn't make it a blocker.

 But beyond that, we don't patch anything. So any product issue would
 come from the product. Any integration issue would be an Apache Bigtop
 (incubating) issue. The same way with Apache Hadoop.
 No matter 

Re: [DISCUSS] BOM and supported platforms for Bigtop 0.4.0

[Patrick Hunt]

On Fri, May 4, 2012 at 9:47 AM, Owen O'Malley omal...@apache.org wrote:
 On Fri, May 4, 2012 at 8:58 AM, Patrick Hunt ph...@apache.org wrote:
 It's not the job of the incubator to create new rules, but rather to
 help podlings to graduation while following existing Apache
 guidelines.

 We aren't making new rules. We are trying to help the Bigtop project
 understand the rules about not releasing non-Apache software. There is
 a huge difference between depending on an artifact from another
 project and building and distributing non-Apache rpms in the project's
 /dist directory.

They are not releasing non-Apache software. They are not forking an
existing project. Bigtop's release artifact will contain packaging
code which allows users to compile packages (deb, rpm, etc...) for
this ASL licensed component, not the source/binaries of the component
itself.


 It's very clear from
 http://www.apache.org/legal/resolved.html that what has been proposed
 is acceptable under existing Apache rules.

 Can you find a single instance other than the disagreement between
 Apache Lucene and Apache Commons where one project is distributing
 another project's rpms? Are there any other non-Apache rpms in /dist?
 Clearly the answer is a resounding NO. It would be a huge violation of
 the trust the incubator is putting in me as a mentor if I didn't block
 Bigtop's plan to do so.

If the component made an objection to being included in Bigtop then I
could see an argument to be made, that's not the case here. The
opposite is true from what I've seen -- people want their software to
be included so that users can more easily consume it. That's why they
released their software under a less restrictive license in the first
place.

EOD existing Apache rules/license make no such distinction. Works
under the following licenses may be included within Apache products
(includes ASL).

Patrick

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

Re: [DISCUSS] BOM and supported platforms for Bigtop 0.4.0

[Patrick Hunt]

On Fri, May 4, 2012 at 11:54 AM, Greg Stein gst...@gmail.com wrote:
 On May 4, 2012 2:03 PM, Patrick Hunt ph...@apache.org wrote:
...
 EOD existing Apache rules/license make no such distinction. Works
 under the following licenses may be included within Apache products
 (includes ASL).

 Can people please stop using ASL or APL? No such thing. It is the
 Apache License. AL for short, or even ALv2.

Sorry for the incorrect tla usage. Will do.

Patrick

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

Re: [VOTE] Release MRUnit version 0.9.0-incubating-rc2

[Patrick Hunt]

+1, signatures and xsums all look good, rat passed, tests pass. lgtm.

On Wed, Apr 18, 2012 at 1:22 PM, Brock Noland br...@cloudera.com wrote:
 This is an incubator release for Apache MRUnit, version 0.9.0-incubating.

 It fixes the following issues:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292version=12316360

 *** Please download, test and vote by [3 working days after sending].

 Note that we are voting upon the source (tag), binaries are provided
 for convenience.

 Source and binary files:
 http://people.apache.org/~brock/mrunit-0.9.0-incubating-candidate-2/

 Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachemrunit-070/

 The tag to be voted upon:
 http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/

 MRUnit's KEYS file containing PGP keys we use to sign the release:
 http://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS

 Note that the Incubator PMC needs to vote upon the release after a
 successful PPMC vote before any release can be made official.

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

Re: [VOTE] Release MRUnit version 0.9.0-incubating-rc1

[Patrick Hunt]

-1. junit jar (CPL, cat b) is included in the binary artifact however
there is nothing in the notice for this.

Patrick

On Tue, Apr 17, 2012 at 7:14 AM, Brock Noland br...@cloudera.com wrote:
 Shoot, yes I meant to include them from the start. Current vote is

 +1  3  Brock Noland, Jim Donofrio, Jarek Jarcec Cecho
 -1   0

 On Tue, Apr 17, 2012 at 12:58 PM, Jim Donofrio donofrio...@gmail.com wrote:
 Brock,

 I guess you can email this up to general@incubator.apache.org now, right?


 On 04/17/2012 08:23 AM, Jarek Jarcec Cecho wrote:

 +1

 * Verified signature
 * Checked license files
 * build + test on both binary and src artifacts

 Jarcec

 On Apr 17, 2012, at 2:38 AM, Jim Donofrio wrote:

 +1 verified signature, successfully built for both hadoop 1.0.2 and
 0.23.1 using mvn clean package and mvn clean package -Dhadoop.version=2

 On 04/16/2012 01:57 PM, Brock Noland wrote:

 This is an incubator release for Apache MRUnit, version
 0.9.0-incubating.

 It fixes the following issues:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292version=12316360

 *** Please download, test and vote by [3 working days after sending].

 Note that we are voting upon the source (tag), binaries are provided
 for convenience.

 Source and binary files:
 http://people.apache.org/~brock/mrunit-0.9.0-incubating-candidate-1/

 Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachemrunit-057/

 The tag to be voted upon:

 http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/

 MRUnit's KEYS file containing PGP keys we use to sign the release:
 http://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS

 Note that the Incubator PMC needs to vote upon the release after a
 successful PPMC vote before any release can be made official.





 --
 Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

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

Re: [VOTE] Release MRUnit version 0.9.0-incubating-rc1

[Patrick Hunt]

Hi Brock, see these:

http://www.apache.org/legal/resolved.html
http://www.apache.org/legal/3party.html (older)

Junit is CPL, checkout the text How should so-called Weak Copyleft
Licenses be handled?, including Software under the following
licenses may be included in binary form within an Apache product if
the inclusion is appropriately labeled.

Regards,

Patrick

On Wed, Apr 18, 2012 at 12:39 PM, Brock Noland br...@cloudera.com wrote:
 Patrick,

 I think we should resolve this, but I am wondering s this a strict
 requirement for this release? In looking for the correct entry for
 JUnit I noticed hadoop-1.0.2 distributes the JUnit jar and nothing is
 mentioned in the NOTICE.txt.

 Brock

 On Wed, Apr 18, 2012 at 6:52 PM, Brock Noland br...@cloudera.com wrote:
 I created https://issues.apache.org/jira/browse/MRUNIT-103 once we get
 that fixed I will spin up another RC.

 Brock

 On Wed, Apr 18, 2012 at 6:40 PM, Patrick Hunt ph...@apache.org wrote:
 -1. junit jar (CPL, cat b) is included in the binary artifact however
 there is nothing in the notice for this.

 Patrick

 On Tue, Apr 17, 2012 at 7:14 AM, Brock Noland br...@cloudera.com wrote:
 Shoot, yes I meant to include them from the start. Current vote is

 +1  3  Brock Noland, Jim Donofrio, Jarek Jarcec Cecho
 -1   0

 On Tue, Apr 17, 2012 at 12:58 PM, Jim Donofrio donofrio...@gmail.com 
 wrote:
 Brock,

 I guess you can email this up to general@incubator.apache.org now, right?


 On 04/17/2012 08:23 AM, Jarek Jarcec Cecho wrote:

 +1

 * Verified signature
 * Checked license files
 * build + test on both binary and src artifacts

 Jarcec

 On Apr 17, 2012, at 2:38 AM, Jim Donofrio wrote:

 +1 verified signature, successfully built for both hadoop 1.0.2 and
 0.23.1 using mvn clean package and mvn clean package -Dhadoop.version=2

 On 04/16/2012 01:57 PM, Brock Noland wrote:

 This is an incubator release for Apache MRUnit, version
 0.9.0-incubating.

 It fixes the following issues:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292version=12316360

 *** Please download, test and vote by [3 working days after sending].

 Note that we are voting upon the source (tag), binaries are provided
 for convenience.

 Source and binary files:
 http://people.apache.org/~brock/mrunit-0.9.0-incubating-candidate-1/

 Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachemrunit-057/

 The tag to be voted upon:

 http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/

 MRUnit's KEYS file containing PGP keys we use to sign the release:
 http://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS

 Note that the Incubator PMC needs to vote upon the release after a
 successful PPMC vote before any release can be made official.





 --
 Apache MRUnit - Unit testing MapReduce - 
 http://incubator.apache.org/mrunit/



 --
 Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/



 --
 Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

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

Re: [VOTE] Release Apache Flume version 1.1.0-incubating (rc1)

[Patrick Hunt]

+1, lgtm. sig/xsums are all correct, was able to build/test
successfully, rat report was clean. I also ran through the incubator
release checklist and everything looks fine.

On Tue, Mar 20, 2012 at 2:01 PM, Brock Noland br...@cloudera.com wrote:
 +1

 Verified gpg/md5, unpacking, and startup.

 Brock

 On Tue, Mar 20, 2012 at 1:12 PM, Hari Shreedharan
 hshreedha...@cloudera.com wrote:
 +1

 Verified:
 * Unpacked source builds correctly.
 * Flume agent works using the sample config file on the built artifact.
 * LICENSE, CHANGELOG, NOTICE look good.

 --
 Hari Shreedharan


 On Monday, March 19, 2012 at 5:46 PM, Arvind Prabhakar wrote:

 This is the second incubator release for Apache Flume, version
 1.1.0-incubating. We are now voting on release candidate rc1.

 *** Please cast your vote within the next 72 hours ***

 The list of fixed issues:
 https://svn.apache.org/repos/asf/incubator/flume/tags/flume-1.1.0-incubating-rc1/CHANGELOG

 The tarball (*.tar.gz), signature (*.asc), checksum (*.md5sum,
 *.sha1sum) for the source and binary can be found at:
 http://people.apache.org/~arvind/flume/110rc1/

 The tag to be voted upon:
 https://svn.apache.org/repos/asf/incubator/flume/tags/flume-1.1.0-incubating-rc1/

 The KEYS file:
 http://www.apache.org/dist/incubator/flume/KEYS

 Changes since last build:
 * FLUME-1032. Fix Flume NG build for binary distribution
 * Updated change log and release notes.







 --
 Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/

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

Re: [VOTE] Release for Bigtop version 0.3.0-incubating

[Patrick Hunt]

+1 lgtm. The sig/xsum check out. I was able to build the zk debs
successfully on my ubuntu system. I ran through the incubator
checklist and everything seems in order.

I managed to generate the rat report via mvn apache-rat:check and it
checked out.

Patrick

On Wed, Mar 21, 2012 at 9:58 AM, Alan Gates ga...@hortonworks.com wrote:
 +1

 LICENSE, NOTICE, and CHANGES look good.  Checksum and key signature check 
 out.  It's nice when the changes file includes attribution on who did the 
 change, but that's not a requirement.

 You didn't include a rat report when you posed the release candidate.  I saw 
 a maven target that looked like it was supposed to produce a rat report, but 
 it didn't seem to when I ran it.  I did a quick look through the files and 
 didn't find anything that looked like it should have a header file but 
 doesn't.  But running rat on stuff is really helpful for voters when 
 producing a release.

 Alan.

 On Mar 20, 2012, at 11:35 AM, Roman Shaposhnik wrote:

 This is the third incubator release for Apache Bigtop, version 
 0.3.0-incubating.

 It fixes the following issues:
  https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12317841projectId=12311420

 The delta between RC0 and RC1 includes fixes for the following issues:
   BIGTOP-446. Typo in hadoop module for puppet
   BIGTOP-459. remove references to cloudera from the packaging files
   BIGTOP-443. deb/oozie/oozie-client.postinst installs an alternative
 for a path that isn't there
   BIGTOP-382. hadoop-conf-pseudo packages contains subversion metada
   BIGTOP-457. Bigtop 0.3.0: Hadoop namenode doesnt start after
 installing the deb package

 *** Please download, test, and vote by Mon, March 26

 Note that we are voting on the source (tag): release-0.3.0-incubating-RC1

 Source tarball, checksums, signature:
    http://people.apache.org/~rvs/bigtop-0.3.0-incubating-RC1/

 The tag to be voted on:
   
 https://svn.apache.org/repos/asf/incubator/bigtop/tags/release-0.3.0-incubating-RC1/

 Bigtop's KEYS file, containing the PGP keys used to sign the release:
   http://svn.apache.org/repos/asf/incubator/bigtop/dist/KEYS

 Please also make sure to try installing our convenience binary distribution
 artifacts. We are publishing the Bigtop 0.3.0 incubating distributions for 
 the
 following Linux platforms: Ubuntu 10.04, CentOS 5, CentOS 6, Fedora 15,
 Fedora 16, SLES 11. The easies way to install Bigtop distribution on
 your favorite Linux OS is to pick one of the attached files, and place
 it (as root) in the following folder:
  * Ubuntu -- /etc/apt/sources.list.d/
  * CentOS5, CentOS6, Fedora 15, Fedora 16 -- /etc/yum.repos.d/
  * SLES 11 -- /etc/zypp/repos.d/

 After that you can follow the installation instructions from over here (DO 
 NOT
 FORGET TO SKIP STEPS #1 and #2):
  https://cwiki.apache.org/confluence/display/BIGTOP/How+to+install+Hadoop+distribution+from+Bigtop

 Thanks!

 Bigtop 0.3.0 release manager,
 Roman Shaposhnik
 bigtop.tar.gz


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

Re: S4 status (was: Re: Thoughts on Incubator board reports)

[Patrick Hunt]

+s4-dev@

On Tue, Mar 13, 2012 at 6:48 AM, Daniel Shahaf d...@daniel.shahaf.name wrote:
 Ping, waiting for a response from s4-dev@ folks.

 Daniel Shahaf wrote on Sat, Mar 10, 2012 at 16:19:27 +0200:
 Jukka Zitting wrote on Sat, Mar 10, 2012 at 14:41:00 +0100:
  Just pick one from the list (ideally one that you aren't directly
  mentoring), read the submitted report (if one exists!) and compare it
  to the previous report (for most podlings that's the one from December
  [2]) and a quick browsing of things like the podling status page [3],
  web site, list archives and svn commit history. Then, if needed,
  follow up with a $podling status mail to general@ for any feedback
  or questions that you may have. You  may also place the podling in the
  appropriate category in the report summary if the review gave you a
  good enough picture of the podling status.
 

 Thanks for the actionable item Jukka, here's my take on the S4 report:

 It sounds like the project has successfully migrated its infrastructure
 to Apache and is progressing well on the technical front.  However, I'm
 concerned by the emphasis on technical details (eg, the feature list of
 the trunk-become-0.5 version) and the lack of details on Grow the
 community; it is the latter, not the former, which is the purpose of
 the incubator and a blocker to graduation.

 The community appears to consist of 2-3 active contributors:
 http://mail-archives.apache.org/mod_mbox/incubator-s4-dev/201202.mbox/author
 I'd like to hear from the PPMC how they plan to expand their dev
 community.

 Daniel

 P.S. The metrics aren't really clear.  What is 55 on dev --- 55 unique
 posters?  55 posts?  Did they change by more than X% since last quarter?

  [1] http://wiki.apache.org/incubator/March2012
  [2] http://wiki.apache.org/incubator/December2011
  [3] http://incubator.apache.org/projects/
 
  BR,
 
  Jukka Zitting
 
  -
  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: [DISCUSS] - Packages renaming and backward compatibility (was: Re: [VOTE] Graduate Sqoop podling from Apache Incubator)

[Patrick Hunt]

On Wed, Feb 29, 2012 at 5:23 AM, Alex Karasulu akaras...@apache.org wrote:

 The discussion pertains to the presence of com.cloudera packages in the
 source code of a podling for the sake of backwards compatibility with
 Cloudera products.

Alex this is an incorrect summary of the facts, similar to the FUD you
tried to spread on the original thread which Arvind provided detail
on. Sqoop was ASL licensed and had an open following long before it
was accepted for incubation to Apache. The community is trying to
rectify the short term migration requirements against doing the right
thing by both Apache and that community.

Arvind:

 ... it would have
 been easier for us[ sqoop community at apache] to drop any backward 
 compatibility requirements and
 get releases out quickly. The reason we chose to invest a lot in
 preserving backward compatibility is for our community. Sqoop has an
 active community that we care deeply about and we have done our best
 to make sure continues to use Sqoop effectively. It is this thriving
 community that was the primary reason for Sqoop to have come into the
 incubator in the first place.

Keep in mind also that this is a short term solution that has a longer
term resolution (one already discussed on the other thread as well):

Here is Arvind's response to Jukka proposing that Sqoop address the
packaging issue post graduation:

 Thanks Jukka. In fact, Sqoop already has a plan in place to completely
 remove com.cloudera.* namespace from its contents via the next major
 revision of the product. The work for that has already started and
 currently exists under the branch sqoop2 [3], tracked by SQOOP-365
 [4]. We hope that in a few months time, we will have feature parity in
 this branch with the trunk, which is when we will promote it to the
 trunk.

 [3] https://svn.apache.org/repos/asf/incubator/sqoop/branches/sqoop2/
 [4] https://issues.apache.org/jira/browse/SQOOP-365

Patrick

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

Re: [VOTE] Release MRUnit version 0.8.1-incubating

[Patrick Hunt]

me/tom/chris is not sufficient? Or did I miss something?

Patrick

On Tue, Feb 28, 2012 at 9:54 PM, Brock Noland br...@cloudera.com wrote:
 Great!  Now we only need one more +1 from an IPMC member. Added
 general to the email chain.

 Brock

 On Wed, Feb 29, 2012 at 11:12 AM, Mattmann, Chris A (388J)
 chris.a.mattm...@jpl.nasa.gov wrote:
 Hi Brock,

 +1 to release:

 Maven staged repo looks good.

 Checksums check out:

 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% curl -O 
 http://people.apache.org/~brock/mrunit-0.8.1-incubating-candidate-1/mrunit-0.8.1-incubating-dist.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  
 Current
                                 Dload  Upload   Total   Spent    Left  Speed
 100  106k  100  106k    0     0  81353      0  0:00:01  0:00:01 --:--:--  
 140k
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% curl -O 
 http://people.apache.org/~brock/mrunit-0.8.1-incubating-candidate-1/mrunit-0.8.1-incubating-dist.tar.gz.asc
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  
 Current
                                 Dload  Upload   Total   Spent    Left  Speed
 104   836  104   836    0     0   6162      0 --:--:-- --:--:-- --:--:-- 
 13062
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% curl -O 
 http://people.apache.org/~brock/mrunit-0.8.1-incubating-candidate-1/mrunit-0.8.1-incubating-dist.tar.gz.md5
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  
 Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0    32    0    32    0     0    118      0 --:--:-- --:--:-- --:--:--   280
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% curl -O 
 http://people.apache.org/~brock/mrunit-0.8.1-incubating-candidate-1/mrunit-0.8.1-incubating-dist.tar.gz.sha1
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  
 Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0    40    0    40    0     0    135      0 --:--:-- --:--:-- --:--:--   459
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% ls
 mrunit-0.8.1-incubating-dist.tar.gz       
 mrunit-0.8.1-incubating-dist.tar.gz.md5
 mrunit-0.8.1-incubating-dist.tar.gz.asc   
 mrunit-0.8.1-incubating-dist.tar.gz.sha1
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% 
 $HOME/bin/verify_md5_checksums
 md5sum: stat '*.bz2': No such file or directory
 md5sum: stat '*.zip': No such file or directory
 mrunit-0.8.1-incubating-dist.tar.gz: OK
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann%

 GPG sig checks out:

 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% 
 $HOME/bin/verify_gpg_sigs
 Verifying Signature for file mrunit-0.8.1-incubating-dist.tar.gz.asc
 gpg: Signature made Fri Feb 17 12:10:27 2012 PST using RSA key ID 8E991CC5
 gpg: Good signature from Brock Noland (CODE SIGNING KEY) br...@apache.org
 gpg: WARNING: This key is not certified with a trusted signature!
 gpg:          There is no indication that the signature belongs to the owner.
 Primary key fingerprint: 2847 DD2B 26E1 A3D8 1949  C883 9DC2 7AFB 8E99 1CC5
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann%

 Didn't test Unit tests, etc., b/c it requires Maven 3 :) Someday I'll 
 upgrade.

 Cheers,
 Chris

 On Feb 28, 2012, at 8:00 PM, Brock Noland wrote:

 Ping on the release VOTE.

 Cheers!
 Brock

 On Wed, Feb 22, 2012 at 7:56 PM, Mattmann, Chris A (388J)
 chris.a.mattm...@jpl.nasa.gov wrote:
 Guys,

 I'll try and VOTE/check out the release today or tomorrow.

 Cheers,
 Chris

 On Feb 22, 2012, at 6:42 AM, Brock Noland wrote:

 Hi,

 Good idea, I added MRUNIT-62 for that.

 Brock

 On Tue, Feb 21, 2012 at 11:50 PM, Karthik K oss@gmail.com wrote:
 Agree.

 We might add instructions to the developers to explicitly build as per
 their hadoop platform.

 I would also , suggest that the BUILD.txt  contains some instructions 
 about
 the build profiles for appropriate hadoop platforms as well.

 BUILDING:

 From the command line:

 $ mvn package

 $ mvn package -DskipTests

 $ mvn clean
 

 Having a word about the 3 different build profiles would be useful for
 developers to pick up the right version.

 --
  Karthik.


 On Wed, Feb 22, 2012 at 6:24 AM, Brock Noland br...@cloudera.com wrote:

 Great, thanks!

 I created MRUNIT-61 to remove the jar from the tar.gz. Since in
 previous releases we pushed a jar I figured including the jar this
 time would be OK.

 Brock

 On Tue, Feb 21, 2012 at 6:51 PM, Patrick Hunt ph...@apache.org wrote:
 +1 sig/xsum are correct, rat is clean, tests all pass. Looks good to 
 me.

 Note: the archive includes a mrunit jar file (the only jar file)
 'mrunit-0.8.1-incubating-hadoop100.jar'. Might be confusing for
 people.

 Regards,

 Patrick



 On Tue, Feb 21, 2012 at 3:48 PM, Brock Noland br...@cloudera.com
 wrote:
 Hi,

 Just a ping to remind people to vote.

 Brock

 On Fri

Re: [VOTE] Release MRUnit version 0.8.1-incubating

[Patrick Hunt]

Check your spam folder? ;-)

http://markmail.org/message/yvmtokdbprn5h2vl

Patrick

On Wed, Feb 29, 2012 at 9:29 AM, Brock Noland br...@cloudera.com wrote:
 I didn't see Tom's vote?  Sometimes emails don't show up in my box so
 I checked here as well and cannot find it?

 http://mail-archives.apache.org/mod_mbox/incubator-mrunit-dev/201202.mbox/%3CCAFukC%3D4Gie5Yvbyp84QmY%2BtVj9pJ9BMuEv4xeqCSHnamrZX6DQ%40mail.gmail.com%3E

 Brock

 On Wed, Feb 29, 2012 at 10:49 PM, Patrick Hunt ph...@apache.org wrote:
 me/tom/chris is not sufficient? Or did I miss something?

 Patrick

 On Tue, Feb 28, 2012 at 9:54 PM, Brock Noland br...@cloudera.com wrote:
 Great!  Now we only need one more +1 from an IPMC member. Added
 general to the email chain.

 Brock

 On Wed, Feb 29, 2012 at 11:12 AM, Mattmann, Chris A (388J)
 chris.a.mattm...@jpl.nasa.gov wrote:
 Hi Brock,

 +1 to release:

 Maven staged repo looks good.

 Checksums check out:

 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% curl -O 
 http://people.apache.org/~brock/mrunit-0.8.1-incubating-candidate-1/mrunit-0.8.1-incubating-dist.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  
 Current
                                 Dload  Upload   Total   Spent    Left  
 Speed
 100  106k  100  106k    0     0  81353      0  0:00:01  0:00:01 --:--:--  
 140k
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% curl -O 
 http://people.apache.org/~brock/mrunit-0.8.1-incubating-candidate-1/mrunit-0.8.1-incubating-dist.tar.gz.asc
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  
 Current
                                 Dload  Upload   Total   Spent    Left  
 Speed
 104   836  104   836    0     0   6162      0 --:--:-- --:--:-- --:--:-- 
 13062
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% curl -O 
 http://people.apache.org/~brock/mrunit-0.8.1-incubating-candidate-1/mrunit-0.8.1-incubating-dist.tar.gz.md5
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  
 Current
                                 Dload  Upload   Total   Spent    Left  
 Speed
  0    32    0    32    0     0    118      0 --:--:-- --:--:-- --:--:--   
 280
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% curl -O 
 http://people.apache.org/~brock/mrunit-0.8.1-incubating-candidate-1/mrunit-0.8.1-incubating-dist.tar.gz.sha1
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  
 Current
                                 Dload  Upload   Total   Spent    Left  
 Speed
  0    40    0    40    0     0    135      0 --:--:-- --:--:-- --:--:--   
 459
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% ls
 mrunit-0.8.1-incubating-dist.tar.gz       
 mrunit-0.8.1-incubating-dist.tar.gz.md5
 mrunit-0.8.1-incubating-dist.tar.gz.asc   
 mrunit-0.8.1-incubating-dist.tar.gz.sha1
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% 
 $HOME/bin/verify_md5_checksums
 md5sum: stat '*.bz2': No such file or directory
 md5sum: stat '*.zip': No such file or directory
 mrunit-0.8.1-incubating-dist.tar.gz: OK
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann%

 GPG sig checks out:

 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann% 
 $HOME/bin/verify_gpg_sigs
 Verifying Signature for file mrunit-0.8.1-incubating-dist.tar.gz.asc
 gpg: Signature made Fri Feb 17 12:10:27 2012 PST using RSA key ID 8E991CC5
 gpg: Good signature from Brock Noland (CODE SIGNING KEY) 
 br...@apache.org
 gpg: WARNING: This key is not certified with a trusted signature!
 gpg:          There is no indication that the signature belongs to the 
 owner.
 Primary key fingerprint: 2847 DD2B 26E1 A3D8 1949  C883 9DC2 7AFB 8E99 1CC5
 [guest-wireless-207-151-253-178:~/tmp/mrunit-0.8.1] mattmann%

 Didn't test Unit tests, etc., b/c it requires Maven 3 :) Someday I'll 
 upgrade.

 Cheers,
 Chris

 On Feb 28, 2012, at 8:00 PM, Brock Noland wrote:

 Ping on the release VOTE.

 Cheers!
 Brock

 On Wed, Feb 22, 2012 at 7:56 PM, Mattmann, Chris A (388J)
 chris.a.mattm...@jpl.nasa.gov wrote:
 Guys,

 I'll try and VOTE/check out the release today or tomorrow.

 Cheers,
 Chris

 On Feb 22, 2012, at 6:42 AM, Brock Noland wrote:

 Hi,

 Good idea, I added MRUNIT-62 for that.

 Brock

 On Tue, Feb 21, 2012 at 11:50 PM, Karthik K oss@gmail.com wrote:
 Agree.

 We might add instructions to the developers to explicitly build as per
 their hadoop platform.

 I would also , suggest that the BUILD.txt  contains some instructions 
 about
 the build profiles for appropriate hadoop platforms as well.

 BUILDING:

 From the command line:

 $ mvn package

 $ mvn package -DskipTests

 $ mvn clean
 

 Having a word about the 3 different build profiles would be useful for
 developers to pick up the right version.

 --
  Karthik.


 On Wed, Feb 22, 2012 at 6:24 AM, Brock Noland br...@cloudera.com 
 wrote:

 Great, thanks!

 I created MRUNIT-61 to remove the jar from the tar.gz. Since in
 previous releases

Re: [DISCUSS] - Packages renaming and backward compatibility (was: Re: [VOTE] Graduate Sqoop podling from Apache Incubator)

[Patrick Hunt]

On Wed, Feb 29, 2012 at 10:25 AM, Alex Karasulu akaras...@apache.org wrote:
 On Wed, Feb 29, 2012 at 7:16 PM, Patrick Hunt ph...@apache.org wrote:

 On Wed, Feb 29, 2012 at 5:23 AM, Alex Karasulu akaras...@apache.org

 Sqoop was ASL licensed and had an open following long before it
 was accepted for incubation to Apache. The community is trying to
 rectify the short term migration requirements against doing the right
 thing by both Apache and that community.


 OK that does not in any way invalidate my summary. You're just taking
 swipes for no reason. Do you honestly think I'm trying to spread FUD here?


You're a smart guy, it was discussed multiple times by multiple people
(myself, Arvind, Greg, Jukka, etc...) on the other thread. The basis
and rational clearly laid out. What else am I to think.

 You guys might have had to deal with a lot of nasty jealous types not
 liking that Cloudera is such a success. I'd like to think there are no
 people like this here but I may be naive. I'm not one of those people. I
 like to see Cloudera like commercialization occur but would like some care
 taken to protect the foundation. The foundation gains through your
 successes as well. So please don't classify me incorrectly: I'm not one of
 those types.


I don't believe that's the issue at all, at least not for me
personally. Arvind and I are careful to wear our Apache hats in these
discussions. The Sqoop community is trying it's best to follow
established Apache rules and policy. If there's an issue with Sqoop
where it's not doing this of course they'll make changes. However at
this point there is no such thing. Don't get me wrong here either, I
was/am fine with your highlighting this issue (your original point),
if you have a concern you need to raise it.

Patrick


 I read more into Scoop and I think I'm going to be a happy user soon too.

 And Arvind's comments below are noted but they don't change the existing
 conditions today. It just means you have a plan for the future: this is
 good.


 Arvind:

  ... it would have
  been easier for us[ sqoop community at apache] to drop any backward
 compatibility requirements and
  get releases out quickly. The reason we chose to invest a lot in
  preserving backward compatibility is for our community. Sqoop has an
  active community that we care deeply about and we have done our best
  to make sure continues to use Sqoop effectively. It is this thriving
  community that was the primary reason for Sqoop to have come into the
  incubator in the first place.

 Keep in mind also that this is a short term solution that has a longer
 term resolution (one already discussed on the other thread as well):

 Here is Arvind's response to Jukka proposing that Sqoop address the
 packaging issue post graduation:

  Thanks Jukka. In fact, Sqoop already has a plan in place to completely
  remove com.cloudera.* namespace from its contents via the next major
  revision of the product. The work for that has already started and
  currently exists under the branch sqoop2 [3], tracked by SQOOP-365
  [4]. We hope that in a few months time, we will have feature parity in
  this branch with the trunk, which is when we will promote it to the
  trunk.
 
  [3] https://svn.apache.org/repos/asf/incubator/sqoop/branches/sqoop2/
  [4] https://issues.apache.org/jira/browse/SQOOP-365

 Patrick

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




 --
 Best Regards,
 -- Alex

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

Re: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project

[Patrick Hunt]

+1 (binding)

On Tue, Feb 28, 2012 at 12:12 PM, Alan D. Cabrera l...@toolazydogs.com wrote:
 +1 - binding

 Regards,
 Alan


 On Feb 26, 2012, at 8:03 AM, Robert Burrell Donkin wrote:

 The graduation guide[1] recommends that the Rat community demonstrates it's 
 willingness to govern itself through a free VOTE before asking the IPMC to 
 approve graduation. So, here it is :-)

 See [2] for a draft of the charter, excluding the list of initial 
 committers. Unless anyone jumps into this thread, I'll assume that the 
 current list of committers would be fine. Please read, review and jump in - 
 but this is a vote on the principle of graduating now.

 This VOTE is open to all, and I'll tally this no early than Wednesday, 29 
 Feb 2012 17:00 UTC.

 Robert

 --8---
 [ ] +1 the RAT community feels ready to graduate as Apache Creadur
 [ ] +0
 [ ] -0
 [ ] -1 Do not graduate RAT at this time
 ---


 [1] http://incubator.apache.org/guides/graduation.html#toplevel
 [2] Suggested Draft Charter:

       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 related to the comprehension and
       auditing of software distributions for distribution at
       no charge to the public.

       NOW, THEREFORE, BE IT RESOLVED, that a Project Management
       Committee (PMC), to be known as the Apache Creadur Project,
       be and hereby is established pursuant to Bylaws of the
       Foundation; and be it further

       RESOLVED, that the Apache Creadur Project be and hereby is
       responsible for the creation and maintenance of open-source
       software related to the comprehension and auditing of software
       distributions for distribution at no charge to the public

       RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility
       for management of the projects within the scope of
       responsibility of the Apache Creadur 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 Creadur Project:

       ...

       NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell
       Donkin be appointed to the office of Vice President, Apache
       Creadur, 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 Creadur 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 Creadur Project; and be it further

       RESOLVED, that the Apache Creadur Project be and hereby
       is tasked with the migration and rationalization of the Apache
       Incubator RAT podling; and be it further

       RESOLVED, that all responsibilities pertaining to the Apache
       Incubator RAT 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


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

Re: [VOTE] Graduate Sqoop podling from Apache Incubator

[Patrick Hunt]

On Tue, Feb 28, 2012 at 1:06 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 On Tue, Feb 28, 2012 at 9:59 AM, Alex Karasulu akaras...@apache.org wrote:
 Cloudera's compatibility issues are not our problem. These packages need to
 go.

 Citation needed. Without a written policy to that effect these things
 are up for each project to decide. Jarek's rationale sounds perfectly
 fine to me.

 We have plenty of projects that provide such backwards compatibility
 wrappers or otherwise put stuff in non-apache namespaces for various
 reasons. See for example [1] or [2].

 [1] 
 http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/javahl/
 [2] http://svn.apache.org/repos/asf/geronimo/specs/trunk/


I agree with Jukka on this. There is no such policy. There are
examples of well established TLPs doing similar. The files are
explicitly deprecated and will be eventually removed, they are for the
convenience of users and others building on top of Sqoop who are
migrating from the original code base to Apache based packages. It
makes total sense to provide a bridge that enables that group to move
to the Apache version of the code.

Patrick

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

Re: [VOTE] Graduate Sqoop podling from Apache Incubator

[Patrick Hunt]

On Tue, Feb 28, 2012 at 9:57 AM, Alan D. Cabrera l...@toolazydogs.com wrote:
 On Feb 28, 2012, at 9:16 AM, Patrick Hunt wrote:
 On Tue, Feb 28, 2012 at 1:06 AM, Jukka Zitting jukka.zitt...@gmail.com 
 wrote:
 On Tue, Feb 28, 2012 at 9:59 AM, Alex Karasulu akaras...@apache.org wrote:
 I'm not sure that JSR specs are the same as old Cloudera code.  JMHO.

How about phrasing it as old Sqoop code instead. :-)

Really it's about respect for existing users and others migrating to
Apache. It's also about respect for the people doing the work. That's
my understanding from discussions with the team at least.

  I don't see the technical requirement that this code needs to stay at Apache 
 and not Cloudera.

I agree that this potentially could be an issue, but whether it's a
technical requirement is up to the team who's doing the work. If
Apache feels that there is a requirement that no project releases
code/document/etc... under any package other than org.apache.* then
that should be clearly defined and communicated. At this point my
understanding is there is no such requirement.

Patrick

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

Re: [VOTE] Graduate Sqoop podling from Apache Incubator

[Patrick Hunt]

On Tue, Feb 28, 2012 at 10:20 AM, Alex Karasulu akaras...@apache.org wrote:
 On Tue, Feb 28, 2012 at 8:13 PM, Patrick Hunt ph...@apache.org wrote:
 I agree that this potentially could be an issue, but whether it's a
 technical requirement is up to the team who's doing the work. If
 Apache feels that there is a requirement that no project releases
 code/document/etc... under any package other than org.apache.* then
 that should be clearly defined and communicated. At this point my
 understanding is there is no such requirement.


 I think this is a policy we should adhere too from this point forward.

Apache wide policy or incubator policy? If it's not Apache wide then
any project could just wait till graduation and do as they see fit.
The idea of incubation is to ensure that a podling adheres to Apache
policy before being let loose to run itself. If we make this an
incubator only restriction we're saying that that's not the case.

 The technical problem is small in comparison to other issues this brings into 
 play.

What issues? That people will be confused about whether Apache
released/branded code, downloaded from Apache, where the majority of
the code is org.apache packaged, but some subset of clearly marked
deprecated code, defined as an aid for migration is Apache or not?
Doesn't seem like an issue to me.

Patrick

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

Re: [VOTE] Graduate Sqoop podling from Apache Incubator

[Patrick Hunt]

On Tue, Feb 28, 2012 at 10:39 AM, Alan D. Cabrera l...@toolazydogs.com wrote:

 On Feb 28, 2012, at 10:13 AM, Patrick Hunt wrote:
 On Tue, Feb 28, 2012 at 9:57 AM, Alan D. Cabrera l...@toolazydogs.com 
 wrote:
 On Feb 28, 2012, at 9:16 AM, Patrick Hunt wrote:
 On Tue, Feb 28, 2012 at 1:06 AM, Jukka Zitting jukka.zitt...@gmail.com 
 wrote:
 On Tue, Feb 28, 2012 at 9:59 AM, Alex Karasulu akaras...@apache.org 
 wrote:
 public class MySQLManager
    extends org.apache.sqoop.manager.MySQLManager {

  public MySQLManager(final SqoopOptions opts) {
    super(opts);
  }

 }

 If all the code is like this it is absolutely ridiculous to have this at 
 Apache and not Cloudera.

This is a code issue, which is up the the team
(committers/pmc/community) doing the work. If they want to include
such code it's up to them. They are doing the work.

What's really at issue here is whether all (java) code at Apache MUST
be under org.apache.* package structure or not. afaik there is
currently no such requirement. If Apache decides to make it a
requirement then great, I'm sure the Sqoop team will make the
necessary changes.


We should also give Arvind and the rest of the Sqoop community some
indication how to proceed, given the voting period is completed.

Patrick

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

Re: [VOTE] Graduate Sqoop podling from Apache Incubator

[Patrick Hunt]

 Note that API is not just method signatures but includes all aspects
 of implementation such as class hierarchies, type compatibility,
 static and non-static state etc.

 I think that it's good to have binary compatibility with Cloudera's old 
 bindings.   I still don't see why it's a requirement for Apache to house code 
 whose sole use is to provide backward compatible bindings for Cloudera's old 
 bindings.

The Sqoop community moved from github where it was ASL licensed to
Apache. There is now a Sqoop community at Apache that continues
using/developing this code and they felt that having backward
compatibility was useful. There is no stated restriction from Apache
against doing such. I don't know the cost of just dropping the
com.cloudera migration aids, but I suspect it would have been easier
to just drop it than spend the time worrying about it and trying to
provide a solution. I'm primarily acting as a mentor, Arvind would be
in better position to provide insight into that background and why the
community felt it was important to carry this forward.

Patrick

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

Re: [VOTE] Graduate Sqoop podling from Apache Incubator

[Patrick Hunt]

On Tue, Feb 28, 2012 at 12:24 PM, Alan D. Cabrera a...@toolazydogs.com wrote:

 On Feb 28, 2012, at 11:39 AM, Alan D. Cabrera wrote:

 We should also give Arvind and the rest of the Sqoop community some
 indication how to proceed, given the voting period is completed.

 A concern has been raised by IPMC members and an effort is being made to 
 garner consensus.  The voting period is on hold.

 Opps, I didn't see that Arvind concluded the vote.  I still stand by my 
 opinion that there are some things that are not solely up to the people that 
 are doing the work.  Complete migration to the the org.apache.* package space 
 is one of them.

No worries. I respect your opinion and if Apache feels that this is
important enough to make explicit then certainly Sqoop should make the
changes. Short of that I don't see why we should hold Sqoop to a
higher standard than is expected of other Apache projects. (that's
_my_ opinion ;-) )

Regards!

Patrick

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

Re: [VOTE] Graduate Sqoop podling from Apache Incubator

[Patrick Hunt]

On Tue, Feb 28, 2012 at 4:02 PM, Mohammad Nour El-Din
nour.moham...@gmail.com wrote:
 On the other hand, I totally respect that Cloudera's interest to support
 their customers and provide backword compatibility, but this is *not* the
 point at all, the point is this *should* not, and even allow me to say this
 is *must* not be the problem of Apache, and yes I agree with the opinion
 that this is a matter to be decided by Sqoop team but not to make Apache's
 problem. So also let not get more into this!!!

Or course this is Apache's problem. You can't have your cake and eat
it too. If you accept code for a project you accept the community as
well. Say Apache accepts a project like Open Office, should we ignore
the existing community and not concern ourselves with backward
compatibility for that project as well, because the original code
wasn't birthed at Apache?

Patrick

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

Re: [VOTE] Graduate Sqoop podling from Apache Incubator

[Patrick Hunt]

+1 (binding)

On Sun, Feb 26, 2012 at 3:24 AM, Tommaso Teofili
tommaso.teof...@gmail.com wrote:
 +1 (binding)
 Tommaso

 2012/2/24 Arvind Prabhakar arv...@apache.org

 This is a call for vote to graduate Sqoop podling from Apache Incubator.

 Sqoop entered Incubator in June of 2011. Since then it has added three
 new committers from diverse organizations, added two new PPMC members,
 and made two releases following the ASF policies and guidelines. The
 community of Sqoop is active, healthy and growing and has demonstrated
 the ability to self-govern using accepted Apache practices. Sqoop
 community has voted to proceed with graduation [1] and the result can
 be found at [2].

 Please cast your votes:

 [  ] +1 Graduate Sqoop podling from Apache Incubator
 [  ] +0 Indifferent to the graduation status of Sqoop podling
 [  ] -1 Reject graduation of Sqoop podling from Apache Incubator

 This vote will be open for 72 hours. Please find the proposed board
 resolution below.

 [1] http://markmail.org/thread/xwhjtkik7pgrmypi
 [2] http://s.apache.org/sqoop

 Thanks,
 Arvind Prabhakar

 X. Establish the Apache Sqoop 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 related to efficiently transferring
       bulk data between Apache Hadoop and structured datastores
       for distribution at no charge to the public.

       NOW, THEREFORE, BE IT RESOLVED, that a Project Management
       Committee (PMC), to be known as the Apache Sqoop Project,
       be and hereby is established pursuant to Bylaws of the
       Foundation; and be it further

       RESOLVED, that the Apache Sqoop Project be and hereby is
       responsible for the creation and maintenance of software
       related to efficiently transferring bulk data between Apache
       Hadoop and structured datastores; and be it further

       RESOLVED, that the office of Vice President, Apache Sqoop 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 Sqoop Project, and to have primary responsibility
       for management of the projects within the scope of
       responsibility of the Apache Sqoop 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 Sqoop Project:

         * Aaron Kimball             kimba...@apache.org
         * Andrew Bayer              aba...@apache.org
         * Ahmed Radwan              ah...@apache.org
         * Arvind Prabhakar          arv...@apache.org
         * Bilung Lee                b...@apache.org
         * Greg Cottman              gcott...@apache.org
         * Guy le Mar                guyle...@apache.org
         * Jaroslav Cecho            jar...@apache.org
         * Jonathan Hsieh            jmhs...@apache.org
         * Olivier Lamy              ol...@apache.org
         * Paul Zimdars              pzimd...@apache.org
         * Roman Shaposhnik          r...@apache.org

       NOW, THEREFORE, BE IT FURTHER RESOLVED, that Arvind Prabhakar
       be appointed to the office of Vice President, Apache Sqoop, 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 Sqoop 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 Sqoop Project; and be it further

       RESOLVED, that the Apache Sqoop Project be and hereby
       is tasked with the migration and rationalization of the Apache
       Incubator Sqoop podling; and be it further

       RESOLVED, that all responsibilities pertaining to the Apache
       Incubator Sqoop 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