Re: [VOTE] Accept Zeppelin into the Apache Incubator

[Henry Saputra]

tps://github.com/NFLabs/zeppelin/blob/master/Roadmap.md
>  * Zeppelin issue tracking:
> https://zeppelin-project.atlassian.net/browse/ZEPPELIN
>  * Zeppelin codebase: https://github.com/NFLabs/zeppelin
>  * User group: https://groups.google.com/group/zeppelin-developers
>
> == Initial Source ==
> Zeppelin codebase is currently hosted on Github:
> https://github.com/NFLabs/zeppelin
>
> === Source and Intellectual Property Submission Plan ===
> Currently, the Zeppleing codebase is distributed under an Apache 2.0 License.
>
> == External Dependencies ==
> To the best of our knowledge, all other dependencies of Zeppelin are
> distributed under Apache compatible licenses (e.g. junit is EPL,
> Eclipse Public License v1.0, atmosphere-jersey is CDDL1.0  and
> dom4j:dom4 is BSD licensed, org.slf4j and
> org.java-websocket:Java-WebSocket are MIT).
> Only org.reflections:reflections
> https://github.com/ronmamo/reflections is WTFPL 2.0, which should not
> be a problem as of https://issues.apache.org/jira/browse/LEGAL-135
> Upon acceptance to the incubator, we would begin a thorough analysis
> of all transitive dependencies to verify this information and
> introduce license checking into the build and release process by
> integrating with Apache Rat.
>
> == Required Resources ==
> === Mailing list ===
> We will migrate the existing Zeppelin mailing lists as follows:
>  * zeppelin-develop...@googlegroups.com --> d...@zeppelin.incubator.apache.org
>  * us...@zeppelin.incubator.apache.org
>  * priv...@zeppelin.incubator.apache.org for PPMC members
>  * comm...@zeppelin.incubator.apache.org
> The latter is to be consistent with the new PIAO naming scheme for podlings.
>
> === Source control ===
> Zeppelin team would like to use Git for source control, as it already
> uses Git. We request a writeable Git repo for Zeppelin, and mirroring
> to be set up to Github through INFRA.
> https://git-wip-us.apache.org/repos/asf/incubator-zeppelin.git
>
> === Issue Tracking ===
> Zeppelin currently uses the Jira tracking system
> https://zeppelin-project.atlassian.net/browse/ZEPPELIN. We will
> migrate to the Apache JIRA:
> http://issues.apache.org/jira/browse/ZEPPELIN
>
>
> === Other Resources ===
>  * Jenkins/Hudson for builds and test running.
>  * Wiki for documentation purposes
>  * Blog to improve project dissemination
>
> == Initial Committers ==
>  * Lee Moon Soo 
>  * Anthony Corbacho , CLA submitted
>  * Damien Corneau , CLA submitted
>  * Alexander Bezzubov , CLA confirmed
>  * Kevin Sangwoo Kim , CLA confirmed
>
> == Affiliations ==
>  * Lee Moon Soo: NFLabs
>  * Anthony Corbacho: NFLabs
>  * Damien Corneau: NFLabs
>  * Alexander Bezzubov: NFLabs
>  * Kevin Sangwoo Kim: VCNC (a.k.a Between)
>
> == Sponsors ==
> === Champion ===
>  * Roman Shaposhnik
>
> === Nominated Mentors ===
>  * Konstantin Boudnik
>  * Ted Dunning
>  * Henry Saputra
>  * Roman Shaposhnik
>  * Hyunsik Choi
>
> === Sponsoring Entity ===
>  The 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: [Proposal] TinkerPop: A Graph Computing Framework

[Henry Saputra]

No way, Marko! This is AWESOME!!

As many people had mentioned before, you need Champion who is Apache member
and mentors who are member of Incubator PMCs.

And please do follow the format of the proposal as Hadrian mentioned in his
reply.

So excited!

- Henry

On Wed, Dec 17, 2014 at 11:09 AM, Marko Rodriguez 
wrote:
>
> Hello,
>
> My name is Marko A. Rodriguez and am a co-founder of TinkerPop (
> http://tinkerpop.com). There has been positive pressure on us (both
> internally and externally) to move TinkerPop to The Apache Foundation. This
> email contains our proposal and I, on behalf of TinkerPop, thank you for
> spending your time reading it.
>
> Take care,
> Marko.
>
> http://markorodriguez.com
>
> 
>
>
>
> *A. Abstract*
>
> TinkerPop is a graph computing framework written in Java --
> http://tinkerpop.com. TinkerPop started in 2009 and is currently in the
> milestone series of 3.0.0.  Graph system vendors such as in-memory graph
> libraries, OLTP graph databases, and OLAP graph processors can provide a
> TinkerPop implementation (
> http://markorodriguez.com/2013/01/09/on-graph-computing/). Once the core
> TinkerPop interfaces are implemented, the underlying graph system can be
> queried using the graph traversal language Gremlin. TinkerPop was designed
> to be used at any scale and as such, can be leveraged by both single-server
> and multi-machine compute clusters. For many, TinkerPop is seen as the JDBC
> of the graph computing community (
> http://en.wikipedia.org/wiki/Java_Database_Connectivity).
>
> *B. Proposal*
>
> Since its inception in 2009, TinkerPop has been open source, free to use.
> Initially the license was BSD, but as of TinkerPop3, the license is
> Apache2. The TinkerPop team is composed of developers as well as
> representatives from numerous graph system vendors (
> http://www.tinkerpop.com/docs/3.0.0-SNAPSHOT/#tinkerpop-contributors).
> TinkerPop has done its best to remain vendor agnostic and works closely
> with vendors to ensure that the constructs within TinkerPop are able to
> accommodate the requirements of the underlying graph system. To date, over
> 12 graph system vendors provide TinkerPop implementations. We believe that
> by joining The Apache Foundation, our vendors, users, and contributors will
> feel more comfortable in terms of legal protected, in terms of
> wider-adoption, and in terms of project stability.
>
> *C. Background*
>
> TinkerPop was founded in 2009 and has had steady, active development
> since. Over the years, the Gremlin query language within TinkerPop has been
> adopted by various JVM languages and as such, there exists Gremlin-Groovy,
> Gremlin-Scala, Gremlin-Clojure, Gremlin-JavaScript, and the like. In many
> ways, Gremlin is seen as a traversal language style that can be readily
> adopted by developers --- on and off the JVM. TinkerPop is not bound to the
> JVM in that developers wishing to interact with a TinkerPop-enabled graph
> system can leverage Gremlin Server which provides "over the wire"
> communication as well as the entry point for non-JVM language bindings.
> TinkerPop is being used is production graph-based applications around the
> world and is only getting better with age.
>
> *D. Rationale*
>
> The graph computing space has grown over the years to encompass numerous
> graph database and graph processing systems. TinkerPop was created as a
> unifying framework for interoperability, language standardization, and data
> model standardization.  This framework makes it simple to "plug and play"
> the back-end graph implementation without affecting the developer's code.
> This is analogous to the way in which JDBC allows users to swap relational
> databases while keeping the same programming interface. TinkerPop also
> brings together OLTP systems (graph databases) and OLAP systems (graph
> processors) by providing a single query language, Gremlin, for executing
> graph algorithms transparently over either type of system.  Finally,
> TinkerPop unifies single-machine systems and distributed systems,
> presenting an identical user experience within the boundaries of the
> computational space and time constraints of the underlying graph system.
>
> *E. Initial Goals*
>
> The goal of this proposal is to migrate TinkerPop to The Apache Foundation
> to 1.) get more exposure to the project and 2.) legally protect the
> developers and contributors of TinkerPop.
>
> *F. Current Status*
>
> TinkerPop is planning to release TinkerPop 3.0.0.GA early 2015 -- January
> or February. We would like to release TinkerPop 3.0.0.GA under The Apache
> Foundation.
>
> *G. Meritocracy*
>
> Anyone is welcome to join TinkerPop as a contributor. If an individual
> provides successful code updates, documentation updates, etc. then they are
> asked to join TinkerPop contributors. Once inside TinkerPop, they are able
> to voice their opinions/thoughts on the direction of the project. Moreover,
> TinkerPop actively seeks vendors

Re: [2nd DRAFT] Board Report for December 2014 - Please review

[Henry Saputra]

That is ok, we do not have to be part of incubator report.

Sorry about the confusion.

- Henry

On Mon, Dec 15, 2014 at 2:17 PM, John D. Ament  wrote:
> Personally, the board report was sent on Wednesday.  You only concluded
> your vote on Friday.
>
> On Mon, Dec 15, 2014 at 4:54 PM, Kostas Tzoumas  wrote:
>>
>> Hi Roman,
>>
>> I sent the email to board@ last week after the incubator vote closed
>> following the instructions at
>> http://incubator.apache.org/guides/graduation.html#top-level-board-proposal
>>
>> However, I missed subscribing to board@ first, so my email might be stuck
>> waiting for moderation.
>>
>> Kostas
>>
>> On Mon, Dec 15, 2014 at 10:38 PM, Henry Saputra 
>> wrote:
>> >
>> > Ah ok,
>> >
>> > I believe the rule was to send email to board @ list to let intention
>> > that graduation should be put in the agenda.
>> >
>> > I hope someone with proper karma to add to the board agenda seeing
>> > this email thread.
>> >
>> >
>> > - Henry
>> >
>> > On Mon, Dec 15, 2014 at 12:59 PM, Roman Shaposhnik > >
>> > wrote:
>> > > Personally, I see nothing wrong with that, but
>> > > I'd like to understand whether board members
>> > > would frown on such 'breaking news' addition.
>> > >
>> > > Thanks,
>> > > Roman.
>> > >
>> > > On Mon, Dec 15, 2014 at 12:51 PM, Henry Saputra <
>> henry.sapu...@gmail.com>
>> > wrote:
>> > >> Roman, John,
>> > >>
>> > >> Could we add Flink graduation resolution as part of the board meeting
>> > >> agenda for this month from incubator?
>> > >>
>> > >> - Henry
>> > >>
>> > >> On Wed, Dec 10, 2014 at 8:48 AM, Roman Shaposhnik <
>> ro...@shaposhnik.org>
>> > wrote:
>> > >>> Indeed! I'll fix it.
>> > >>>
>> > >>> Thanks,
>> > >>> Roman.
>> > >>>
>> > >>> P.S. I could swear I saw in the report though, but you're right.
>> > >>>
>> > >>>
>> > >>> On Wed, Dec 10, 2014 at 8:44 AM, Adunuthula, Seshu <
>> > sadunuth...@ebay.com> wrote:
>> > >>>> Kylin is a new podling which was approved, but do not see a mention
>> > here
>> > >>>> in this report.
>> > >>>>
>> > >>>> Thanks
>> > >>>> Seshu Adunuthula
>> > >>>>
>> > >>>>
>> > >>>> On 12/9/14, 6:13 PM, "John D. Ament"  wrote:
>> > >>>>
>> > >>>>>Below is the "final" copy of the report, ready to be signed off
>> on.  I
>> > >>>>>removed non-reporting podlings.
>> > >>>>>
>> > >>>>>Can we get someone from MRQL and Brooklyn to sign off on those
>> > reports?
>> > >>>>>Brooklyn specifically has a *lot* of mentors to find no one to sign
>> > off on
>> > >>>>>it.
>> > >>>>>
>> > >>>>>BTW, in my last email I incorrectly listed log4cxx as non-reporting.
>> > They
>> > >>>>>did report.
>> > >>>>>
>> > >>>>>= Incubator PMC report for December 2014 =
>> > >>>>>=== Timeline ===
>> > >>>>>||Wed December 03 ||Podling reports due by end of day ||
>> > >>>>>||Sun December 07 ||Shepherd reviews due by end of day ||
>> > >>>>>||Sun December 07 ||Summary due by end of day ||
>> > >>>>>||Tue December 09 ||Mentor signoff due by end of day ||
>> > >>>>>||Wed December 10 ||Report submitted to Board ||
>> > >>>>>||Wed December 17 ||Board meeting ||
>> > >>>>>
>> > >>>>>
>> > >>>>>=== Shepherd Assignments ===
>> > >>>>>||Alan D. Cabrera ||Ignite ||
>> > >>>>>||Andrei Savu ||Drill ||
>> > >>>>>||Andrei Savu ||Johnzon ||
>> > >>>>>||Dave Fisher ||NPanday ||
>> > >>>>>||John Ament ||MRQL ||
>> > >>>>>||John Ament ||log4cxx2 ||
>> > >>>>>||Justin Mclean ||Tamaya ||
>> >

Re: [2nd DRAFT] Board Report for December 2014 - Please review

[Henry Saputra]

Ah ok,

I believe the rule was to send email to board @ list to let intention
that graduation should be put in the agenda.

I hope someone with proper karma to add to the board agenda seeing
this email thread.


- Henry

On Mon, Dec 15, 2014 at 12:59 PM, Roman Shaposhnik  wrote:
> Personally, I see nothing wrong with that, but
> I'd like to understand whether board members
> would frown on such 'breaking news' addition.
>
> Thanks,
> Roman.
>
> On Mon, Dec 15, 2014 at 12:51 PM, Henry Saputra  
> wrote:
>> Roman, John,
>>
>> Could we add Flink graduation resolution as part of the board meeting
>> agenda for this month from incubator?
>>
>> - Henry
>>
>> On Wed, Dec 10, 2014 at 8:48 AM, Roman Shaposhnik  
>> wrote:
>>> Indeed! I'll fix it.
>>>
>>> Thanks,
>>> Roman.
>>>
>>> P.S. I could swear I saw in the report though, but you're right.
>>>
>>>
>>> On Wed, Dec 10, 2014 at 8:44 AM, Adunuthula, Seshu  
>>> wrote:
>>>> Kylin is a new podling which was approved, but do not see a mention here
>>>> in this report.
>>>>
>>>> Thanks
>>>> Seshu Adunuthula
>>>>
>>>>
>>>> On 12/9/14, 6:13 PM, "John D. Ament"  wrote:
>>>>
>>>>>Below is the "final" copy of the report, ready to be signed off on.  I
>>>>>removed non-reporting podlings.
>>>>>
>>>>>Can we get someone from MRQL and Brooklyn to sign off on those reports?
>>>>>Brooklyn specifically has a *lot* of mentors to find no one to sign off on
>>>>>it.
>>>>>
>>>>>BTW, in my last email I incorrectly listed log4cxx as non-reporting.  They
>>>>>did report.
>>>>>
>>>>>= Incubator PMC report for December 2014 =
>>>>>=== Timeline ===
>>>>>||Wed December 03 ||Podling reports due by end of day ||
>>>>>||Sun December 07 ||Shepherd reviews due by end of day ||
>>>>>||Sun December 07 ||Summary due by end of day ||
>>>>>||Tue December 09 ||Mentor signoff due by end of day ||
>>>>>||Wed December 10 ||Report submitted to Board ||
>>>>>||Wed December 17 ||Board meeting ||
>>>>>
>>>>>
>>>>>=== Shepherd Assignments ===
>>>>>||Alan D. Cabrera ||Ignite ||
>>>>>||Andrei Savu ||Drill ||
>>>>>||Andrei Savu ||Johnzon ||
>>>>>||Dave Fisher ||NPanday ||
>>>>>||John Ament ||MRQL ||
>>>>>||John Ament ||log4cxx2 ||
>>>>>||Justin Mclean ||Tamaya ||
>>>>>||Konstantin Boudnik ||Argus ||
>>>>>||Matthew Franklin ||Brooklyn ||
>>>>>||Raphael Bircher ||Kalumet ||
>>>>>||Raphael Bircher ||Streams ||
>>>>>||Roman Shaposhnik ||Sentry ||
>>>>>||Ross Gardler ||Wave ||
>>>>>||Suresh Marru ||Falcon ||
>>>>>||Suresh Marru ||Lens ||
>>>>>||Timothy Chen ||Ripple ||
>>>>>||Timothy Chen ||Taverna ||
>>>>>
>>>>>
>>>>>=== Report content ===
>>>>>{{{
>>>>>Incubator PMC report for December 2014
>>>>>
>>>>>The Apache Incubator is the entry path into the ASF for projects and
>>>>>codebases
>>>>>wishing to become part of the Foundation's efforts.
>>>>>
>>>>>There are currently 36 podlings undergoing incubation.  Two podlings
>>>>>joined
>>>>>us this month, NiFi and Tamaya.  Three new IPMC members and two new
>>>>>Shepherds joined our ranks as well.
>>>>>
>>>>>* Community
>>>>>
>>>>>  New IPMC members:
>>>>>
>>>>>  Andrew L. Farris
>>>>>  Thejas Nair
>>>>>  Brock Noland
>>>>>
>>>>>  New Incubator Shepherds:
>>>>>
>>>>>  Timothy Chen
>>>>>  Andrew L. Farris
>>>>>
>>>>>  People who left the IPMC:
>>>>>
>>>>>  None
>>>>>
>>>>>* New Podlings
>>>>>
>>>>>  Nifi
>>>>>  Tamaya
>>>>>
>>>>>* Graduations
>>>>>
>>>>>  The board has motions for the following:
>>>>>
>>>>>  The IPMC is currently voting on graudations for:
>>>>

Re: [2nd DRAFT] Board Report for December 2014 - Please review

[Henry Saputra]

>>>* Podling name search pending (PODLINGNAMESEARCH-61)
>>>* Discrepancy in status report with respect to commiter ids.
>>>
>>>
>>>Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>>aware
>>> of?
>>>- No
>>>
>>>How has the community developed since the last report?
>>>* More users & contributors have joined the falcon project and the
>>>community continues to grow
>>>
>>>How has the project developed since the last report?
>>>* Development activity has been very hectic more than 240 JIRAs have been
>>>created and about 200 resolved since the last report
>>>* There are more than 100 users subscribed on the dev mailing list
>>>
>>>Date of last release:
>>>
>>>  2014-12-03 (0.6-incubating)
>>>  2014-09-20 (0.5-incubating)
>>>
>>>When were the last committers or PMC members elected?
>>>  Aug 28, 2014
>>>
>>>Signed-off-by:
>>>
>>>  [ ](falcon) Arun Murthy
>>>  [X](falcon) Chris Douglas
>>>  [ ](falcon) Owen O'Malley
>>>  [ ](falcon) Devaraj Das
>>>  [ ](falcon) Alan Gates
>>>
>>>
>>>Ignite
>>>
>>>A unified In-Memory Data Fabric providing high-performance, distributed
>>>in-
>>>memory data management software layer between various data sources and
>>>user
>>>applications.
>>>
>>>Ignite has been incubating since 2014-10-01.
>>>
>>>Three most important issues to address in the move towards graduation:
>>>
>>>  1. Finish migration to Apache process.
>>>  2. Grow active and healthy community around Apache Ignite product.
>>>  3. Get on a stable release schedule and have 3 successful product
>>>releases.
>>>
>>>Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>>aware of?
>>>
>>>  None at the moment.
>>>
>>>How has the community developed since the last report?
>>>
>>>  No new committers/PPMC members were added.
>>>  Several new contributors have joined.
>>>
>>>How has the project developed since the last report?
>>>
>>>  - Project planning for the 1st sprint started with over 30 tickets filed
>>>in Ignite Jira.
>>>  - Landing web page was set.
>>>  - Website design was chosen in Jira, IGNITE-7. Initial version will be
>>>pushed early in the week of 12/9.
>>>  - Ignite code was pushed into Apache GIT repository. The code is fully
>>>maven-enabled and buildable.
>>>
>>>Date of last release:
>>>
>>>  No releases yet: the code is still in the development phase
>>>
>>>When were the last committers or PMC members elected?
>>>
>>>  10/01/2014 Initial committers were added.
>>>
>>>Signed-off-by:
>>>
>>>  [X](ignite) Branko Čibej
>>>  [X](ignite) Konstantin Boudnik
>>>  [ ](ignite) Henry Saputra
>>>  [ ](ignite) Roman Shaposhnik
>>>  [ ](ignite) Michael Stack
>>>
>>>
>>>
>>>Johnzon
>>>
>>>Implementation of JSR-353 JavaTM API for JSON Processing (Renamed from
>>> Fleece)
>>>
>>>Johnzon has been incubating since 2014-06-09.
>>>
>>>Three most important issues to address in the move towards graduation:
>>>
>>>  1. Expanding the community, increase dev list activity and adding new
>>> committers/pmc members.
>>>  2. Complete the status page
>>>  3. Add and improve documentation
>>>
>>>Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>>aware of?
>>>
>>>  * Nothing
>>>
>>>How has the community developed since the last report?
>>>
>>>  There are new people on the dev list and the project got contributions
>>>  from non-committers.  On the dev list there are approx. 70 msgs (on
>>>  average) messages per month. Christian Grobmeier quits as mentor.
>>>
>>>How has the project developed since the last report?
>>>
>>>  The project did its first and second incubator release.
>>>  During the last three month nine jira issues were reported and fixed.
>>>
>>>Date of last release:
>>>
>>>  2014-11-22
>>>
>>>When were the last committers or PMC members elected?
>>>
>>>  Last committer was e

Re: Graduation question

[Henry Saputra]

I am sorry not Robert, it was Kostas =)

On Mon, Dec 15, 2014 at 11:48 AM, Henry Saputra  wrote:
> Hi Marvin,
>
> Robert from Flink PPMC had sent email to board @ list to make Flink
> graduation to be included in the next board meeting.
>
> Could someone with enough karma to modify the board agenda to help add
> Flink graduation resolution to the agenda?
>
> - Henry
>
> On Mon, Dec 15, 2014 at 11:20 AM, Marvin Humphrey
>  wrote:
>> On Mon, Dec 15, 2014 at 10:36 AM, Alan Gates  wrote:
>>> As a Flink mentor can I submit the graduation resolution to the board now
>>> that it has passed, or is that a job for Roman as IPMC chair?
>>
>> Short answer: go ahead.
>>
>> Long answer: There's no role requirement, so in theory literally
>> anyone could send an email to board@apache with the resolution text.
>> However, it helps if it's someone who's subscribed to board@apache
>> (and thus whose messages won't get stuck in moderation) and who has
>> sufficient privileges to commit changes to the board agenda in svn.
>> In practice, that means that resolutions tend to be submitted by
>> Mentors who are also ASF Members subscribed to board@apache.
>>
>> Marvin Humphrey
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>

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

Re: Graduation question

[Henry Saputra]

Hi Marvin,

Robert from Flink PPMC had sent email to board @ list to make Flink
graduation to be included in the next board meeting.

Could someone with enough karma to modify the board agenda to help add
Flink graduation resolution to the agenda?

- Henry

On Mon, Dec 15, 2014 at 11:20 AM, Marvin Humphrey
 wrote:
> On Mon, Dec 15, 2014 at 10:36 AM, Alan Gates  wrote:
>> As a Flink mentor can I submit the graduation resolution to the board now
>> that it has passed, or is that a job for Roman as IPMC chair?
>
> Short answer: go ahead.
>
> Long answer: There's no role requirement, so in theory literally
> anyone could send an email to board@apache with the resolution text.
> However, it helps if it's someone who's subscribed to board@apache
> (and thus whose messages won't get stuck in moderation) and who has
> sufficient privileges to commit changes to the board agenda in svn.
> In practice, that means that resolutions tend to be submitted by
> Mentors who are also ASF Members subscribed to board@apache.
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [DISCUSS] [PROPOSAL] Zeppelin for Apache Incubator

[Henry Saputra]

 and being active on the mailing list. We are
> >> committed to create diverse mix of developers from all over the world.
> >>
> >> === Reliance on Salaried Developers ===
> >> Most of the Zeppelin contributors use it as tool of choice either in
> >> their own companies internally or distribute it as part of the
> >> product.
> >> Backend agnostic design helps to keep it as tool of choice for diverse
> >> community of data analysts even if they move from one employee to
> >> another.
> >> There also is at least one university in US with students who
> >> potentially might use Zeppelin for R’n’D projects.
> >>
> >> === Relationship with Other Apache Products ===
> >> Right now Zeppelin relies on Apache Spark to run distributed task
> >> across a cluster of machines, but it’s abstract interpreter design
> >> allows it to work with other systems like Apache MRQL, Apache Crunch
> >> as well as SQL-based systems like Apache Tajo, Apache Hive
> >>
> >> === A Excessive Fascination with the Apache Brand ===
> >> We believe that joining Apache will help us attract more contributors
> >> to Zeppelin, by giving us a well-defined, transparent development and
> >> governance process under a known brand. The reason for this proposal
> >> is not to gain publicity, but to further strengthen the longevity of
> >> the project without affiliation with any particular company. There are
> >> no plans to use of Apache brand in press releases nor posting
> >> advertising of acceptance it into Apache Incubator.
> >>
> >> === Documentation ===
> >> Additional documentation on Zeppelin may be found on its github website:
> >>  * Zeppelin overview:
> >> https://github.com/NFLabs/zeppelin/blob/master/README.md
> >>  * Zeppelin docs: http://zeppelin-project.org/docs/index.html
> >>  * Zeppelin road map:
> >> https://github.com/NFLabs/zeppelin/blob/master/Roadmap.md TODO!
> >>  * Zeppelin issue tracking:
> >> https://zeppelin-project.atlassian.net/browse/ZEPPELIN
> >>  * Zeppelin codebase: https://github.com/NFLabs/zeppelin
> >>  * User group: https://groups.google.com/group/zeppelin-developers
> >>
> >> == Initial Source ==
> >> Zeppelin codebase is currently hosted on Github:
> >> https://github.com/NFLabs/zeppelin
> >>
> >> === Source and Intellectual Property Submission Plan ===
> >> Currently, the Zeppleing codebase is distributed under an Apache 2.0
> >> License.
> >>
> >> == External Dependencies ==
> >> To the best of our knowledge, all other dependencies of Zeppelin are
> >> distributed under Apache compatible licenses (e.g. junit is EPL,
> >> Eclipse Public License v1.0, atmosphere-jersey is CDDL1.0  and
> >> dom4j:dom4 is BSD licensed, org.slf4j and
> >> org.java-websocket:Java-WebSocket are MIT).
> >> Only org.reflections:reflections
> >> https://github.com/ronmamo/reflections is WTFPL 2.0, which should not
> >> be a problem as of https://issues.apache.org/jira/browse/LEGAL-135
> >> Upon acceptance to the incubator, we would begin a thorough analysis
> >> of all transitive dependencies to verify this information and
> >> introduce license checking into the build and release process by
> >> integrating with Apache Rat.
> >>
> >> == Required Resources ==
> >> === Mailing list ===
> >> We will migrate the existing Zeppelin mailing lists as follows:
> >>  * zeppelin-develop...@googlegroups.com  -->
> >> d...@zeppelin.incubator.apache.org 
> >>  * us...@zeppelin.incubator.apache.org 
> >>  * priv...@zeppelin.incubator.apache.org  for PPMC
> members
> >>  * comm...@zeppelin.incubator.apache.org 
> >> The latter is to be consistent with the new PIAO naming scheme for
> >> podlings.
> >>
> >> === Source control ===
> >> Zeppelin team would like to use Git for source control, as it already
> >> uses Git. We request a writeable Git repo for Zeppelin, and mirroring
> >> to be set up to Github through INFRA.
> >> https://git-wip-us.apache.org/repos/asf/incubator-zeppelin.git
> >>
> >> === Issue Tracking ===
> >> Zeppelin currently uses the Jira tracking system
> >> https://zeppelin-project.atlassian.net/browse/ZEPPELIN. We will
> >> migrate to the Apache JIRA:
> >> http://issues.apache.org/jira/browse/ZEPPELIN
> >>
> >>
> >> === Other Resources ===
> >>  * Jenkins/Hudson for builds and test running.
> >>  * Wiki for documentation purposes
> >>  * Blog to improve project dissemination
> >>
> >> == Initial Committers ==
> >>  * Lee Moon Soo 
> >>  * Anthony Corbacho , CLA submitted
> >>  * Damien Corneau , CLA submitted
> >>  * Alexander Bezzubov , CLA confirmed
> >>  * Kevin Sangwoo Kim , CLA confirmed
> >>
> >> == Affiliations ==
> >>  * Lee Moon Soo: NFLabs
> >>  * Anthony Corbacho: NFLabs
> >>  * Damien Corneau: NFLabs
> >>  * Alexander Bezzubov: NFLabs
> >>  * Kevin Sangwoo Kim: VCNC (a.k.a Between)
> >>
> >> == Sponsors ==
> >> === Champion ===
> >>  * Roman Shaposhnik
> >>
> >> === Nominated Mentors ===
> >>  * Konstantin Boudnik
> >>  * Ted Dunning
> >>  * Henry Saputra
> >>  * Roman Shaposhnik
> >>
> >> === Sponsoring Entity ===
> >>  The 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: [VOTE] accept SAMOA into incubator

[Henry Saputra]

+1 (binding)


- Henry

On Thu, Dec 11, 2014 at 10:02 AM, Daniel Dai  wrote:
> Following the discussion earlier, I'm calling a vote to accept SAMOA as a
> new Incubator project.
>
> [ ] +1 Accept SAMOA into the Incubator
> [ ] +0 Indifferent to the acceptance of SAMOA
> [ ] -1 Do not accept SAMOA because ...
>
> The vote will be open for at least 72h and closes at the earliest on Dec 14
> 19:00 GMT.
>
> https://wiki.apache.org/incubator/SAMOAProposal
>
> Thanks,
> Daniel
>
> = SAMOA =
> == Abstract ==
> SAMOA is an an open-source platform for mining big data streams.
>
> == Proposal ==
> SAMOA provides a collection of distributed streaming algorithms for the
> most common data mining and machine learning tasks such as classification,
> clustering, and regression, as well as programming abstractions to develop
> new algorithms that run on top of distributed stream processing engines
> (DSPEs). It features a pluggable architecture that allows it to run on
> several DSPEs such as Apache Storm, Apache S4, and Apache Samza.
>
> == Background ==
> Hadoop and its ecosystem have changed the way data are processed by
> allowing to push algorithms to unprecedented scale. As an example, Mahout
> allows to run data mining and machine learning algorithms on very large
> datasets. However, Hadoop and Mahout are not suited to handle streaming
> data. Simply put, the goal of SAMOA is to provide a streaming counterpart
> to Mahout.
>
> == Rationale ==
> SAMOA aims to fill the current gap in tools for mining large scale streams.
> Many organizations can benefit from a scalable stream mining platform
> system such as SAMOA.
>
> SAMOA is a natural fit for the Apache Software Foundation. It is licensed
> under the ASL v2.0. It already interoperates with several existing Apache
> projects such as Storm, S4, and Samza. Furthermore, it is complementary to
> existing Apache projects such as Mahout. The initial committers are
> familiar with the Apache process and subscribes to the Apache mission.
> Indeed, the team includes multiple Apache committers. Finally, joining
> Apache will help coordinate the development effort of the growing number of
> organizations which contribute to SAMOA.
>
> == Initial Goals ==
> * Move the existing codebase to Apache
> * Integrate with the Apache development process
> * Incremental development and releases per Apache guidelines
>
> == Current Status ==
> SAMOA started as a research project at Yahoo Labs in 2013 and was
> open-sourced in October the same year. It has been under development on
> Yahoo's public GitHub repository since being open-sourced. It has undergone
> two releases (0.1, 0.2).
>
> === Meritocracy ===
> The SAMOA project already operates on meritocratic principles. Today, SAMOA
> has several developers and has accepted multiple patches from outside of
> Yahoo Labs. However, our intent with this incubator proposal is to start
> building a more diverse developer community around SAMOA that follows the
> Apache meritocracy model. We will identify all committers and PPMC members
> for the project operating under the ASF meritocratic principles. We plan to
> continue support for new contributors and work with those who contribute
> significantly to the project to make them committers.
>
> === Community ===
> SAMOA is currently being used internally at Yahoo. Acceptance into the
> Apache foundation would bolster the existing user and developer community
> around SAMOA. That community includes contributors from several
> institutions, active mostly on GitHub's pages. SAMOA has been starred more
> than 300 times and forked more than 50 times on GitHub as of November 2014.
>
> === Core Developers ===
> The core developers are a diverse group, many of which already very
> experienced with open source. There are two existing Apache committers,
> along with people from various companies and universities.
>
> === Alignment ===
> The ASF is the natural choice to host SAMOA. First, its goal of encouraging
> community-driven open-source projects fits with our vision for SAMOA.
> Additionally, many other projects that SAMOA is based on, such as Apache
> Storm, S4, Samza, and HDFS, are hosted by the ASF. Close proximity of SAMOA
> to these projects within the ASF will provide mutual benefit.
>
> == Known Risks ==
> === Orphaned Products ===
> Given the current level of investment in SAMOA the risk of the project
> being abandoned is minimal. There are several constituents who are highly
> incentivized to continue development, and Yahoo Labs relies on SAMOA as a
> platform for a large number of long-term research projects. However, the
> small number of initial committers might be a concern. We plan to address
> this issue during incubation by growing the community and the number of
> committers.
>
> === Inexperience with Open Source ===
> SAMOA has existed as a healthy open source project for one year. During
> this time, we have curated an open-source community successfully,
> attracting developer

Re: [VOTE] Recommend retirement for NPanday poddling

[Henry Saputra]

+1 (binding)

On Wed, Dec 10, 2014 at 10:36 PM, Roman Shaposhnik  wrote:
> This is a vote on recommending a retirement option
> for the NPanday poddling.
>
> NPanday entered incubator on 13th of August 2010:
>http://incubator.apache.org/projects/npanday.html
> Up until 2012 the poddling was doing reasonably well,
> producing two releases and adding mentors and
> committers. Starting from 2012 the community started
> to dwindle and no further releases were produced.
> Starting from 2014 the poddling really struggled to
> regain vitality despite of numerous attempts to help
> by Brett Porter and Konstantin Boudnik. The most
> visible attempt was in July/August 2014 and resulted in
> a spur of JIRA and ML activity, but couldn't be sustained
> without direct involvement of Brett and Konstantin:
> https://wiki.apache.org/incubator/August2014
> Starting from September the poddling was back to
> the usual levels:
> http://mail-archives.apache.org/mod_mbox/incubator-npanday-dev/
> http://mail-archives.apache.org/mod_mbox/incubator-npanday-commits/
> http://mail-archives.apache.org/mod_mbox/incubator-npanday-users/
> while missing Incubator reports:
> https://wiki.apache.org/incubator/November2014
> https://wiki.apache.org/incubator/December2014
> and having absolutely 0 commits coming into the repository.
> It now appears that that all of the PPMC has been disengaged
> and the user community for the project is pretty much non existent.
>
> IPMC has been monitoring the situation all throughout 2014:
>http://markmail.org/message/3sbwfpedosyqzqhn
>http://markmail.org/message/c2fbokolyujki3gl
>http://markmail.org/thread/3ttavmqnq5s6pe74
>http://markmail.org/message/bxelz5ati2hofe4y
> and at this point it feels like the most production option would
> be to recommend retirement of the poddling. Should
> the VOTE pass, Konstantin and myself are volunteering
> to take care of the poddling retirement mechanics.
>
> Vote will run for at least 72 hours (to 12/14/14, noon PST).
>
> [ ] +1 Recommend retiring NPanday poddling from the Incubator.
> [ ] +/-0 Don't care, but...
> [ ] -1 Don't recommend retiring NPanday poddling from the Incubator because 
> ...
>
> 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: Concerns about NPanday

[Henry Saputra]

Agree

It has bee brought up so many times and even mentors of the project no
longer active.

- Henry


On Wed, Dec 10, 2014 at 9:42 PM, Roman Shaposhnik  wrote:
> On Sat, Dec 6, 2014 at 2:16 AM, Konstantin Boudnik  wrote:
>> On Fri, Nov 28, 2014 at 10:43PM, Roman Shaposhnik wrote:
>>> On Tue, Nov 18, 2014 at 8:39 PM, Konstantin Boudnik  wrote:
>>> > I tend to agree with John. It seems that the project is pretty much 
>>> > lacking
>>> > the activity - mostly Brett is pulling it forward when he has cycles, but 
>>> > it
>>> > doesn't seems like a sustainable situation moving forward.
>>> >
>>> > I am new to the IPMC, so I am not sure how this type of situations is 
>>> > handled,
>>> > so I am looking for a guidance on this.
>>>
>>> It seems that the reasonable thing to do here is to reach out to the
>>> community one last time and perhaps suggest an option of retirement.
>>> Basically this all boils down to everything in ASF requiring at least
>>> 3 active participants. It feels like this project doesn't have that. If 
>>> that's
>>> indeed the case we need to force it into either getting 3 active members
>>> or retiring.
>>>
>>> Cos, any chance you can help here?
>>>
>>
>> Sorry for the delay - with holidays and all I just got around to answer this.
>> I think this is a reasonable course of actions. I will reach out to them and
>> discuss the options.
>
> Seems like there's very little chance for the community to come with
> the the required 3 semi-active members.
>
> At this point I'd like to proceed with the IPMC vote on retirement
> recommendation.
>
> 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] Graduation of Apache Flink

[Henry Saputra]

=)

The good thing both are in somewhat different domains

On Wed, Dec 10, 2014 at 12:19 AM, Bertrand Delacretaz
 wrote:
> On Tue, Dec 9, 2014 at 12:49 PM, Kostas Tzoumas  wrote:
>> ...The Flink community voted on its Dev list to graduate, The vote passed 
>> with
>> 27 +1s (including 12 +1s from the PPMC) and 0 -1s
>
> Including mentor votes, thanks!
>
> +1 for graduation.
>
> As a tongue-in-cheek sidenote, you won't be allowed to complain if
> someone confuses Flink with Sling due to the similar sound. Sling was
> here first ;-)
>
> -Bertrand
>
> -
> 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

Fwd: [VOTE] Graduate Flink from the Incubator

[Henry Saputra]

Forwarding original Apache Flink incubating VOTE thread to graduate to
general @ list for FYI


-- Forwarded message --
From: Kostas Tzoumas 
Date: Fri, Dec 5, 2014 at 2:46 AM
Subject: [VOTE] Graduate Flink from the Incubator
To: "d...@flink.incubator.apache.org" 


Hi everyone,

It seems that everyone is excited about graduating, so I am calling for a
community vote to graduate Apache Flink (incubating) to a top-level project
(TLP). If this VOTE proceeds successfully, I will start a similar VOTE
thread in the Incubator mailing list, and if that goes well, we will submit
the resolution below to be included in the agenda of the next Apache board
meeting. I will keep this vote open until Tuesday.

[  ] +1 Graduate Apache Flink (incubating) according to the resolution below
[  ] +0 Don't care
[  ] -1 Don't graduate Apache Flink (incubating) according to the
resolution below because...

I will close this VOTE on Tuesday, December 9, 12:00pm CET.

Remember, this is a community vote, so everyone can vote!

Best,
Kostas

resolution:

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 reliable large-scale data
analysis with focus on programmability, optimizability,
efficiency, and combination of batch and streaming data
processing.

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

RESOLVED, that the Apache Flink Project be and hereby is
responsible for the creation and maintenance of software
related to fast and reliable large-scale data analysis
with focus on programmability, optimizability, efficiency,
and combination of batch and streaming data processing;
and be it further

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

* Marton Balassi
* Ufuk Celebi   
* Stephan Ewen  
* Gyula Fora
* Alan Gates  
* Fabian Hueske 
* Vasia Kalavri 
* Aljoscha Krettek  
* Robert Metzger        
* Till Rohrmann 
* Henry Saputra
* Sebastian Schelter
* Kostas Tzoumas
* Timo Walther  
* Daniel Warneke

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

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

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Flink 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

Re: [VOTE] Graduation of Apache Flink

[Henry Saputra]

No, I believed we missed forwarding it.

I will forward the VOTE thread for bookkeeping purposes.

- Henry

On Tue, Dec 9, 2014 at 4:15 PM, John D. Ament  wrote:
> You have my +1 (binding), however just wondering - did you forward the vote
> notice to general@?  I may have missed it.
>
> http://incubator.apache.org/guides/graduation.html#tlp-community-vote
>
> John
>
> On Tue Dec 09 2014 at 6:49:10 AM Kostas Tzoumas  wrote:
>
>> Hi everyone,
>>
>> The Flink community voted on its Dev list to graduate, The vote passed with
>> 27 +1s (including 12 +1s from the PPMC) and 0 -1s.
>>
>> Here is the vote thread in the Dev list:
>> http://apache-flink-incubator-mailing-list-archive.1008284.
>> n3.nabble.com/VOTE-Graduate-Flink-from-the-Incubator-td2737.html
>>
>> and a preceding discussion thread:
>> http://apache-flink-incubator-mailing-list-archive.1008284.
>> n3.nabble.com/DISCUSS-Graduation-of-Flink-from-the-Incubator-td2660.html
>>
>> This is a new VOTE to decide if Apache Flink should graduate from the
>> Incubator. Please VOTE on the resolution pasted below the ballot. I'll
>> leave this VOTE open for at least 72 hours (until Friday, December 12, 1pm
>> CE/4am PST)
>>
>> [ ] +1 Graduate Apache Flink from the Incubator
>> [ ] +0 Don't care
>> [ ] -1 Don't graduate Apache Flink from the Incubator because...
>>
>> 
>>
>> Establish the Apache Flink 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 fast and reliable large-scale data
>> analysis with focus on programmability, optimizability,
>> efficiency, and combination of batch and streaming data
>> processing.
>>
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> Committee (PMC), to be known as the "Apache Flink Project",
>> be and hereby is established pursuant to Bylaws of the
>> Foundation; and be it further
>>
>> RESOLVED, that the Apache Flink Project be and hereby is
>> responsible for the creation and maintenance of software
>> related to fast and reliable large-scale data analysis
>> with focus on programmability, optimizability, efficiency,
>> and combination of batch and streaming data processing;
>> and be it further
>>
>> RESOLVED, that the office of "Vice President, Apache Flink" 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 Flink Project, and to have primary responsibility
>> for management of the projects within the scope of
>> responsibility of the Apache Flink 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 Flink Project:
>>
>> * Marton Balassi
>> * Ufuk Celebi   
>> * Stephan Ewen  
>> * Gyula Fora
>> * Alan Gates  
>> * Fabian Hueske 
>> * Vasia Kalavri 
>> * Aljoscha Krettek  
>> * Robert Metzger
>> * Till Rohrmann 
>> * Henry Saputra
>> * Sebastian Schelter
>> * Kostas Tzoumas
>> * Timo Walther  
>> * Daniel Warneke
>>
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephan Ewen
>> be appointed to the office of Vice President, Apache Flink, 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 Flink 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 Flink Project; and be it further
>>
>> RESOLVED, that the Apache Flink Project be and hereby
>> is tasked with the migration and rationalization of the Apache
>> Incubator Flink podling; and be it further
>>
>> RESOLVED, that all responsibilities pertaining to the Apache
>> Incubator Flink 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

Re: [VOTE] Graduation of Apache Flink

[Henry Saputra]

+1 (binding)

Wearing hat as one of the mentors I believe the team is ready to
continue the journey as ASF top level project.

The PPMCs have learnt to invite new committers/PPMCs, generate good
releases, and solve many issues in the Apache way.
Also the community have demonstrated the openness in discussions and
merit that exemplifies community over code.

- Henry

On Tue, Dec 9, 2014 at 3:49 AM, Kostas Tzoumas  wrote:
> Hi everyone,
>
> The Flink community voted on its Dev list to graduate, The vote passed with
> 27 +1s (including 12 +1s from the PPMC) and 0 -1s.
>
> Here is the vote thread in the Dev list:
> http://apache-flink-incubator-mailing-list-archive.1008284.n3.nabble.com/VOTE-Graduate-Flink-from-the-Incubator-td2737.html
>
> and a preceding discussion thread:
> http://apache-flink-incubator-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Graduation-of-Flink-from-the-Incubator-td2660.html
>
> This is a new VOTE to decide if Apache Flink should graduate from the
> Incubator. Please VOTE on the resolution pasted below the ballot. I'll
> leave this VOTE open for at least 72 hours (until Friday, December 12, 1pm
> CE/4am PST)
>
> [ ] +1 Graduate Apache Flink from the Incubator
> [ ] +0 Don't care
> [ ] -1 Don't graduate Apache Flink from the Incubator because...
>
> 
>
> Establish the Apache Flink 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 fast and reliable large-scale data
> analysis with focus on programmability, optimizability,
> efficiency, and combination of batch and streaming data
> processing.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Flink Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache Flink Project be and hereby is
> responsible for the creation and maintenance of software
> related to fast and reliable large-scale data analysis
> with focus on programmability, optimizability, efficiency,
> and combination of batch and streaming data processing;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache Flink" 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 Flink Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Flink 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 Flink Project:
>
> * Marton Balassi
> * Ufuk Celebi   
> * Stephan Ewen  
> * Gyula Fora    
> * Alan Gates  
> * Fabian Hueske 
> * Vasia Kalavri 
> * Aljoscha Krettek  
> * Robert Metzger
> * Till Rohrmann 
> * Henry Saputra
> * Sebastian Schelter
> * Kostas Tzoumas
> * Timo Walther  
> * Daniel Warneke
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephan Ewen
> be appointed to the office of Vice President, Apache Flink, 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 Flink 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 Flink Project; and be it further
>
> RESOLVED, that the Apache Flink Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Flink podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Flink 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

Re: [DISCUSS] [PROPOSAL] SAMOA for Apache Incubator

[Henry Saputra]

Ah so I stand corrected.
But I am not sure if then your VOTE will bind once the project going
to incubator.
It would probably help for SAMOA to have you as member of IPMCs.


- Henry

On Thu, Dec 4, 2014 at 3:36 PM, Daniel Dai  wrote:
> Oh, I am under the impression that mentor has to be IPMC member, but
> champion can be either IPMC member or Apache member:
>
> "Where the Champion is not a Member of the Foundation (i.e. is an Officer
> only), the Champion shall be a member of the PMC of the Sponsor."(
> http://incubator.apache.org/incubation/Roles_and_Responsibilities.html)
>
> Isn't it?
>
> On Thu, Dec 4, 2014 at 1:59 PM, jan i  wrote:
>
>> On Thursday, December 4, 2014, Henry Saputra 
>> wrote:
>>
>> > I was not saying to stop it but Daniel needs to send request to
>> > private@ list make sure he is part of IPMCs.
>>
>> Agreed, sorry if my wording sounded differently.
>>
>> rgds
>> jan i
>>
>> >
>> > - Henry
>> >
>> > On Thu, Dec 4, 2014 at 12:48 PM, jan i >
>> > wrote:
>> > > On Thursday, December 4, 2014, Henry Saputra > > >
>> > > wrote:
>> > >
>> > >> Daniel,
>> > >>
>> > >> Small formality, as I remember champion has to be member of IPMC in
>> > >> which you are not.
>> > >> Since you are a member of ASF, you can just send email to
>> > >> private@incubator.a.o to be added as member of IPMC.
>> > >
>> > >
>> > > I agree we need formalities to be in order, but in this case its really
>> > > only paperwork, so lets not stop the process for the project.
>> > >
>> > > just my opinion.
>> > > rgds
>> > > jan i
>> > >
>> > >>
>> > >> - Henry
>> > >>
>> > >>
>> > >> On Tue, Dec 2, 2014 at 9:27 PM, Daniel Dai > > 
>> > >> > wrote:
>> > >> > Hi,
>> > >> >
>> > >> > I would like to propose SAMOA as an Apache Incubator project.
>> > >> > https://wiki.apache.org/incubator/SAMOAProposal
>> > >> >
>> > >> > I've posted posted the text of the proposal below:
>> > >> >
>> > >> > Thanks,
>> > >> > Daniel
>> > >> >
>> > >> > = SAMOA =
>> > >> > == Abstract ==
>> > >> > SAMOA is an an open-source platform for mining big data streams.
>> > >> >
>> > >> > == Proposal ==
>> > >> > SAMOA provides a collection of distributed streaming algorithms for
>> > the
>> > >> > most common data mining and machine learning tasks such as
>> > >> classification,
>> > >> > clustering, and regression, as well as programming abstractions to
>> > >> develop
>> > >> > new algorithms that run on top of distributed stream processing
>> > engines
>> > >> > (DSPEs). It features a pluggable architecture that allows it to run
>> on
>> > >> > several DSPEs such as Apache Storm, Apache S4, and Apache Samza.
>> > >> >
>> > >> > == Background ==
>> > >> > Hadoop and its ecosystem have changed the way data are processed by
>> > >> > allowing to push algorithms to unprecedented scale. As an example,
>> > Mahout
>> > >> > allows to run data mining and machine learning algorithms on very
>> > large
>> > >> > datasets. However, Hadoop and Mahout are not suited to handle
>> > streaming
>> > >> > data. Simply put, the goal of SAMOA is to provide a streaming
>> > counterpart
>> > >> > to Mahout.
>> > >> >
>> > >> > == Rationale ==
>> > >> > SAMOA aims to fill the current gap in tools for mining large scale
>> > >> streams.
>> > >> > Many organizations can benefit from a scalable stream mining
>> platform
>> > >> > system such as SAMOA.
>> > >> >
>> > >> > SAMOA is a natural fit for the Apache Software Foundation. It is
>> > licensed
>> > >> > under the ASL v2.0. It already interoperates with several existing
>> > Apache
>> > >> > projects such as Storm, S4, and Samza. Furthermore, it is
>> > complementary
>> > >> to
&g

Re: [DISCUSS] [PROPOSAL] SAMOA for Apache Incubator

[Henry Saputra]

I was not saying to stop it but Daniel needs to send request to
private@ list make sure he is part of IPMCs.

- Henry

On Thu, Dec 4, 2014 at 12:48 PM, jan i  wrote:
> On Thursday, December 4, 2014, Henry Saputra 
> wrote:
>
>> Daniel,
>>
>> Small formality, as I remember champion has to be member of IPMC in
>> which you are not.
>> Since you are a member of ASF, you can just send email to
>> private@incubator.a.o to be added as member of IPMC.
>
>
> I agree we need formalities to be in order, but in this case its really
> only paperwork, so lets not stop the process for the project.
>
> just my opinion.
> rgds
> jan i
>
>>
>> - Henry
>>
>>
>> On Tue, Dec 2, 2014 at 9:27 PM, Daniel Dai > > wrote:
>> > Hi,
>> >
>> > I would like to propose SAMOA as an Apache Incubator project.
>> > https://wiki.apache.org/incubator/SAMOAProposal
>> >
>> > I've posted posted the text of the proposal below:
>> >
>> > Thanks,
>> > Daniel
>> >
>> > = SAMOA =
>> > == Abstract ==
>> > SAMOA is an an open-source platform for mining big data streams.
>> >
>> > == Proposal ==
>> > SAMOA provides a collection of distributed streaming algorithms for the
>> > most common data mining and machine learning tasks such as
>> classification,
>> > clustering, and regression, as well as programming abstractions to
>> develop
>> > new algorithms that run on top of distributed stream processing engines
>> > (DSPEs). It features a pluggable architecture that allows it to run on
>> > several DSPEs such as Apache Storm, Apache S4, and Apache Samza.
>> >
>> > == Background ==
>> > Hadoop and its ecosystem have changed the way data are processed by
>> > allowing to push algorithms to unprecedented scale. As an example, Mahout
>> > allows to run data mining and machine learning algorithms on very large
>> > datasets. However, Hadoop and Mahout are not suited to handle streaming
>> > data. Simply put, the goal of SAMOA is to provide a streaming counterpart
>> > to Mahout.
>> >
>> > == Rationale ==
>> > SAMOA aims to fill the current gap in tools for mining large scale
>> streams.
>> > Many organizations can benefit from a scalable stream mining platform
>> > system such as SAMOA.
>> >
>> > SAMOA is a natural fit for the Apache Software Foundation. It is licensed
>> > under the ASL v2.0. It already interoperates with several existing Apache
>> > projects such as Storm, S4, and Samza. Furthermore, it is complementary
>> to
>> > existing Apache projects such as Mahout. The initial committers are
>> > familiar with the Apache process and subscribes to the Apache mission.
>> > Indeed, the team includes multiple Apache committers. Finally, joining
>> > Apache will help coordinate the development effort of the growing number
>> of
>> > organizations which contribute to SAMOA.
>> >
>> > == Initial Goals ==
>> > * Move the existing codebase to Apache
>> > * Integrate with the Apache development process
>> > * Incremental development and releases per Apache guidelines
>> >
>> > == Current Status ==
>> > SAMOA started as a research project at Yahoo Labs in 2013 and was
>> > open-sourced in October the same year. It has been under development on
>> > Yahoo's public GitHub repository since being open-sourced. It has
>> undergone
>> > two releases (0.1, 0.2).
>> >
>> > === Meritocracy ===
>> > The SAMOA project already operates on meritocratic principles. Today,
>> SAMOA
>> > has several developers and has accepted multiple patches from outside of
>> > Yahoo Labs. However, our intent with this incubator proposal is to start
>> > building a more diverse developer community around SAMOA that follows the
>> > Apache meritocracy model. We will identify all committers and PPMC
>> members
>> > for the project operating under the ASF meritocratic principles. We plan
>> to
>> > continue support for new contributors and work with those who contribute
>> > significantly to the project to make them committers.
>> >
>> > === Community ===
>> > SAMOA is currently being used internally at Yahoo. Acceptance into the
>> > Apache foundation would bolster the existing user and developer community
>> > around SAMOA. That community includes contributors from several
>> > institutions, active m

Re: [DISCUSS] [PROPOSAL] SAMOA for Apache Incubator

[Henry Saputra]

Daniel,

Small formality, as I remember champion has to be member of IPMC in
which you are not.
Since you are a member of ASF, you can just send email to
private@incubator.a.o to be added as member of IPMC.

- Henry


On Tue, Dec 2, 2014 at 9:27 PM, Daniel Dai  wrote:
> Hi,
>
> I would like to propose SAMOA as an Apache Incubator project.
> https://wiki.apache.org/incubator/SAMOAProposal
>
> I've posted posted the text of the proposal below:
>
> Thanks,
> Daniel
>
> = SAMOA =
> == Abstract ==
> SAMOA is an an open-source platform for mining big data streams.
>
> == Proposal ==
> SAMOA provides a collection of distributed streaming algorithms for the
> most common data mining and machine learning tasks such as classification,
> clustering, and regression, as well as programming abstractions to develop
> new algorithms that run on top of distributed stream processing engines
> (DSPEs). It features a pluggable architecture that allows it to run on
> several DSPEs such as Apache Storm, Apache S4, and Apache Samza.
>
> == Background ==
> Hadoop and its ecosystem have changed the way data are processed by
> allowing to push algorithms to unprecedented scale. As an example, Mahout
> allows to run data mining and machine learning algorithms on very large
> datasets. However, Hadoop and Mahout are not suited to handle streaming
> data. Simply put, the goal of SAMOA is to provide a streaming counterpart
> to Mahout.
>
> == Rationale ==
> SAMOA aims to fill the current gap in tools for mining large scale streams.
> Many organizations can benefit from a scalable stream mining platform
> system such as SAMOA.
>
> SAMOA is a natural fit for the Apache Software Foundation. It is licensed
> under the ASL v2.0. It already interoperates with several existing Apache
> projects such as Storm, S4, and Samza. Furthermore, it is complementary to
> existing Apache projects such as Mahout. The initial committers are
> familiar with the Apache process and subscribes to the Apache mission.
> Indeed, the team includes multiple Apache committers. Finally, joining
> Apache will help coordinate the development effort of the growing number of
> organizations which contribute to SAMOA.
>
> == Initial Goals ==
> * Move the existing codebase to Apache
> * Integrate with the Apache development process
> * Incremental development and releases per Apache guidelines
>
> == Current Status ==
> SAMOA started as a research project at Yahoo Labs in 2013 and was
> open-sourced in October the same year. It has been under development on
> Yahoo's public GitHub repository since being open-sourced. It has undergone
> two releases (0.1, 0.2).
>
> === Meritocracy ===
> The SAMOA project already operates on meritocratic principles. Today, SAMOA
> has several developers and has accepted multiple patches from outside of
> Yahoo Labs. However, our intent with this incubator proposal is to start
> building a more diverse developer community around SAMOA that follows the
> Apache meritocracy model. We will identify all committers and PPMC members
> for the project operating under the ASF meritocratic principles. We plan to
> continue support for new contributors and work with those who contribute
> significantly to the project to make them committers.
>
> === Community ===
> SAMOA is currently being used internally at Yahoo. Acceptance into the
> Apache foundation would bolster the existing user and developer community
> around SAMOA. That community includes contributors from several
> institutions, active mostly on GitHub's pages. SAMOA has been starred more
> than 300 times and forked more than 50 times on GitHub as of November 2014.
>
> === Core Developers ===
> The core developers are a diverse group, many of which already very
> experienced with open source. There are two existing Apache committers,
> along with people from various companies and universities.
>
> === Alignment ===
> The ASF is the natural choice to host SAMOA. First, its goal of encouraging
> community-driven open-source projects fits with our vision for SAMOA.
> Additionally, many other projects that SAMOA is based on, such as Apache
> Storm, S4, Samza, and HDFS, are hosted by the ASF. Close proximity of SAMOA
> to these projects within the ASF will provide mutual benefit.
>
> == Known Risks ==
> === Orphaned Products ===
> Given the current level of investment in SAMOA the risk of the project
> being abandoned is minimal. There are several constituents who are highly
> incentivized to continue development, and Yahoo Labs relies on SAMOA as a
> platform for a large number of long-term research projects. However, the
> small number of initial committers might be a concern. We plan to address
> this issue during incubation by growing the community and the number of
> committers.
>
> === Inexperience with Open Source ===
> SAMOA has existed as a healthy open source project for one year. During
> this time, we have curated an open-source community successfully,
> attracting developers from a 

Re: [VOTE] Accept Kylin into the Apache Incubator

[Henry Saputra]

b
> project. All have been involved with the source code that has been
> released under an open source license, and several of them also have
> experience developing code in an open source environment. Though the
> core set of Developers do not have Apache Open Source experience,
> there are plans to onboard individuals with Apache open source
> experience on to the project.
>
> ## Homogenous Developers
>
> The core developers include developers from eBay, Ctrip and
> Hortonworks. Apache Incubation process encourages an open and diverse
> meritocratic community. Apache Kylin has the required amount of
> diversity with committers from three different organizations, but is
> also aware that bulk of the commits come from a single entity. Kylin
> intends to make every possible effort to build a diverse, vibrant and
> involved community and has already received substantial interest from
> various organizations
>
> ## Reliance on Salaried Developers
>
> eBay invested in Kylin as the OLAP solution on top of Hadoop clusters
> and some of its key engineers are working full time on the project. In
> addition, since there is a growing Big Data need for scalable OLAP
> solutions on Hadoop, we look forward to other Apache developers and
> researchers to contribute to the project. Additional contributors,
> including Apache committers have plans to join this effort shortly.
> Also key to addressing the risk associated with relying on Salaried
> developers from a single entity is to increase the diversity of the
> contributors and actively lobby for Domain experts in the BI space to
> contribute. Apache Kylin intends to do this. One approach already
> taken is to approach the Apache Drill project to explore possible
> cooperation.
>
> ## Relationships with Other Apache Products
>
> Kylin has a strong relationship and dependency with Apache Hadoop
> HBase, Hive and Calcite. Being part of Apache’s Incubation community,
> could help with a closer collaboration among these four projects and
> as well as others.
>
> Kylin is likely to have substantial value to Apache Drill due to the
> common use of Calcite as a query optimization engine and similar
> approaches between Kylin's approach to cubing and Drill's approach to
> input sources.
>
> ## An Excessive Fascination with the Apache Brand
>
> Kylin is proposing to enter incubation at Apache in order to help
> efforts to diversify the committer-base, not so much to capitalize on
> the Apache brand. The Kylin project is in production use already
> inside EBay, but is not expected to be an EBay product for external
> customers. As such, the Kylin project is not seeking to use the Apache
> brand as a marketing tool.
>
> # Documentation
>
> Information about Kylin can be found at
> https://github.com/KylinOLAP/Kylin. The following links provide more
> information about Kylin in open source:
>
> - Kylin web site: http://kylin.io
> - Codebase at Github: https://github.com/KylinOLAP/Kylin
> - Issue Tracking: https://github.com/KylinOLAP/Kylin/issues
> - User community: https://groups.google.com/forum/#!forum/kylin-olap
>
> ## Initial Source
>
> Kylin has been under development since 2013 by a team of engineers at
> eBay Inc. It is currently hosted on Github.com under an Apache license
> at https://github.com/KylinOLAP/Kylin
>
> ## External Dependencies
>
> Kylin has the following external dependencies.
>
> * Basic
>
> - JDK 1.6+
> - Apache Maven
> - JUnit
> - DBUnit
> - Log4j
> - Slf4j
> - Apache Commons
> - Google Guava
> - Jackson
>
> * Hadoop
>
> - Apache Hadoop
> - Apache HBase
> - Apache Hive
> - Apache Zookeeper
> - Apache Curator
>
> * Utility
>
> - H2
> - JSCH
>
> * REST Service
>
> - Spring
>
> * Query
>
> - Antlr
> - Apache Calcite (formerly Optiq)
> - Linq4j
>
> * Job
>
> - Quartz
>
> * Web build tool
>
> - NPM
> - Grunt
> - bower
>
> * Web
>
> - Angular JS
> - jQuery
> - Bootstrap
> - D3 JS
> - ACE
>
> ##Cryptography
>
> Kylin will eventually support encryption on the wire. This is not one
> of the initial goals, and we do not expect Kylin to be a controlled
> export item due to the use of encryption. Kylin supports but does not
> require the Kerberos authentication mechanism to access secured Hadoop
> services.
>
> # Required Resources
>
> ## Mailing List
>
> - kylin-private for private PMC discussions (with moderated subscriptions)
> - kylin-dev
> - kylin-commits
>
> ##Subversion Directory
>
> Git is the preferred source control system: git://git.apache.org/Kylin
>
> ## Issue Tracking
>
> JIRA Kylin (KYLIN)
>
> #

Re: [VOTE] (new) Release Apache Metamodel incubating 4.3.0

[Henry Saputra]

+1 (binding)

On Wed, Nov 19, 2014 at 2:10 PM, Kasper Sørensen
 wrote:
> Hi All,
>
> The previous vote on this subject was cancelled because of a misstep in the 
> artifact signing procedure. Now we're back with a properly signed release 
> (based on the same source code).
>
> Please vote on releasing the following candidate as Apache MetaModel version 
> 4.3.0-incubating.
>
> The Git tag to be voted on is v4.3.0- incubating
> tag: 
> https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.3.0-incubating
> commit: 
> https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=commit;h=eef82fb039e819b8841c55e393898260733a545b
>
> The source artifact to be voted on is:
> https://repository.apache.org/content/repositories/orgapachemetamodel-1004/org/apache/metamodel/MetaModel/4.3.0-incubating/MetaModel-4.3.0-incubating-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> https://repository.apache.org/content/repositories/orgapachemetamodel-1004/org/apache/metamodel/MetaModel/4.3.0-incubating
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/kaspersor.asc
>
> Release engineer public key id: 1FE1C2F5
>
> Vote thread link from d...@metamodel.incubator.apache.org mailing list:
> http://markmail.org/thread/cksfunp5oiihbag2
>
> Result thread link from d...@metamodel.incubator.apache.org mailing list:
> http://markmail.org/message/fc4adybhue6t2jay
>
> Please vote on releasing this package as Apache MetaModel 4.3.0- incubating.
>
> The vote is open for 72 hours, or until we get the needed number of votes (3 
> times +1).
>
> [ ] +1 Release this package as Apache MetaModel 4.3.0 -incubating
> [ ] -1 Do not release this package because ...
>
> More information about the MetaModel project can be found at 
> http://metamodel.incubator.apache.org/
>
> Thank you in advance for participating.
>
> Regards,
> Kasper Sørensen

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

[RESULT] [VOTE] Graduation of Apache MetaModel from the Incubator

[Henry Saputra]

Hi All,

The vote has passed with ten binding +1 votes, no +0, and no -1 votes.

+1 votes:

* Henry Saputra
* Chris Mattmann
* Ted Dunning
* Sergio Fernandez
* Jean-Louis Monteiro
* Jake Farrell
* Noah Slater
* Alan Cabrera
* Lewis McGibbney
* Arvind Prabhakar

I will ask the board to add the resolution to the agenda of the next
board meeting.

Thank you all for participating in the VOTE.

Thanks!

Henry

On Thu, Nov 13, 2014 at 9:39 PM, Henry Saputra  wrote:
> Hi All,
>
> The Apache MetaModel community has wrapped up the VOTE to propose for
> graduation from Apache incubator. The VOTE passed with result:
> 9 binding +1s
> zero 0s
> zero -1s
> (http://bit.ly/1u8n8eo)
>
> Apache MetaModel came into ASF incubator on 2013 and since then have
> grown into small but active community.
>
> We have made several good releases with different release managers,
> and also add new PPMC/committers [1].
> The project also has good traffic on the dev mailing list [2].
>
> We would like to propose graduation of Apache MetaModel from ASF
> incubator to top level project.
>
>
> [ ] +1 Graduate Apache MetaModel from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache MetaModel from the Incubator because.. .
>
>
> The VOTE will open for 72 hours (11/17/2014)
>
>
> Here is the proposal for the board resolution for graduation:
>
>
> === Board Resolution ==
>
> Establish the Apache MetaModel Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests
> of the Foundation and consistent with the Foundation's purpose to
> establish a Project Management Committee charged with the creation and
> maintenance of open-source software, for distribution at no charge to
> the public, related to providing an implementation of a
> Platform-as-a-Service Framework.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache MetaModel Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache MetaModel Project be and hereby is
> responsible for the creation and maintenance of software related to
> providing an implementation of a Platform-as-a-Service Framework; and
> be it further
>
> RESOLVED, that the office of "Vice President, MetaModel" 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 MetaModel
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache MetaModel
> 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 MetaModel
> Project:
>
> * Alberto Rodriguez 
> * Ankit Kumar 
> * Arvind Prabhakar 
> * Henry Saputra 
> * Juan Jose van der Linden 
> * Kasper Sørensen 
> * Matt Franklin 
> * Noah Slater 
> * Sameer Arora 
> * Tomasz Guzialek 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kasper Sørensen be
> appointed to the office of Vice President, MetaModel, 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 MetaModel 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 MetaModel
> Project; and be it further
>
> RESOLVED, that the Apache MetaModel Project be and hereby is tasked
> with the migration and rationalization of the Apache Incubator
> MetaModel podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> MetaModel podling encumbered upon the Apache Incubator Project are
> hereafter discharged.
>
>
>
>
> Thanks,
>
> Henry
> On behalf of Apache MetaModel incubating PPMCs
>
> [1] http://incubator.apache.org/projects/metamodel.html
> [2] http://mail-archives.apache.org/mod_mbox/metamodel-dev

-
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.0-incubating

[Henry Saputra]

Hi Terence,

Sorry for the belated reply. I thought Twill will resend the VOTE for
0.4.0 release due to some issue.

Signature and hash files look good
LICENCE and NOTICE files look good
DISCLAIMER file looks good
No 3rd party exes in the source artifact
Compiled

+1

Good job guys!

- Henry

On Mon, Nov 17, 2014 at 10:51 AM, Terence Yim  wrote:
> Hi all,
>
> This vote has been up for over a week, but only got two +1 binding
> votes (one forwarded from twill-dev@, one from Justin)
> and no 0 or -1 vote. Can I get some attention from the committee to
> help on the release?
>
> Thanks,
> Apache Twill Team
>
> On Sat, Nov 8, 2014 at 4:51 PM, Justin Mclean  
> wrote:
>> Hi,
>>
>> +1 (binding)
>>
>> Checked:
>> - Signatures and hashes correct
>> - Artefact name contains incubating
>> - DISCLAIMER exists
>> - LICENCE and NOTICE correct
>> - All source files have Apache header
>> - No binary files in source release
>> - Can compile from source
>> - tests pass
>>
>> Thanks,
>> Justin
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [RESULT] [VOTE] Apache Johnzon 0.2-incubating release

[Henry Saputra]

A little bit formality but the idea is that the IPMC that voted in the
dev@ list act in the capacity of PPMCs.

Sending formal request to general@ list to make sure other IPMCs could
add additional pair of eyes to review the releases:
"... then the Podling SHALL send a summary of that vote to the
Incubator'sgeneral list and formally request the Incubator PMC approve
such a release. Three +1 Incubator PMC votes are required ..." [1]

The IPMCs in the dev@ list should recast its +1 vote in the general
list to be accounted for.

- Henry

[1]: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases

On Sun, Nov 16, 2014 at 9:41 PM, Justin Mclean  wrote:
> Hi,
>
>> That's not how it works at all.  Please review [1].
>
> Looks correct to me as there is already 3 +1 incubator PCM binding votes. 
> What would you expect in this situation?
>
> 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

[CANCEL] [VOTE] Release Apache Metamodel incubating 4.3.0

[Henry Saputra]

Send CANCEL thread for this vote

On Sunday, November 16, 2014, Kasper Sørensen <
kasper.soren...@humaninference.com> wrote:

> -1
>
> Unfortunately I had made a mistake and applied the wrong key when signing
> the release artifacts.
> I will prepare a new release and post a new vote.
>
> Best regards,
> Kasper
>
> -Original Message-
> From: Henry Saputra [mailto:henry.sapu...@gmail.com ]
> Sent: 14. november 2014 23:09
> To: general@incubator.apache.org 
> Subject: Re: [VOTE] Release Apache Metamodel incubating 4.3.0
>
> +1 (binding)
>
> On Fri, Nov 14, 2014 at 2:06 PM, Kasper Sørensen <
> kasper.soren...@humaninference.com > wrote:
> > Hi All,
> >
> > Please vote on releasing the following candidate as Apache MetaModel
> version 4.3.0- incubating.
> > This will be the fourth incubator release for Metamodel in Apache (and
> potentially the last, if the also-ongoing vote about graduation passes).
> >
> > The Git tag to be voted on is v4.3.0- incubating:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=ta
> > g;h=refs/tags/MetaModel-4.3.0-incubating
> >
> > The source artifact to be voted on is:
> > https://repository.apache.org/content/repositories/orgapachemetamodel-
> > 1002/org/apache/metamodel/MetaModel/4.3.0-incubating/MetaModel-4.3.0-i
> > ncubating-source-release.zip
> >
> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> > https://repository.apache.org/content/repositories/orgapachemetamodel-
> > 1002/org/apache/metamodel/MetaModel/4.3.0-incubating
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/kaspersor.asc
> >
> > Release engineer public key id: 1FE1C2F5
> >
> > Vote thread link from d...@metamodel.incubator.apache.org 
> mailing list:
> > http://markmail.org/message/27orgrjxpnpanwop
> >
> > Result thread link from d...@metamodel.incubator.apache.org
>  mailing list:
> > http://markmail.org/message/qjgol4br3tzckpp6
> >
> > Please vote on releasing this package as Apache MetaModel 4.3.0-
> incubating.
> >
> > The vote is open for 72 hours, or until we get the needed number of
> votes (3 times +1).
> >
> > [ ] +1 Release this package as Apache MetaModel 4.3.0 -incubating [ ]
> > -1 Do not release this package because ...
> >
> > More information about the MetaModel project can be found at
> > http://metamodel.incubator.apache.org/
> >
> > Thank you in advance for participating.
> >
> > Regards,
> > Kasper Sørensen
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> 
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
>
>

Re: [VOTE] Release Apache Metamodel incubating 4.3.0

[Henry Saputra]

+1 (binding)

On Fri, Nov 14, 2014 at 2:06 PM, Kasper Sørensen
 wrote:
> Hi All,
>
> Please vote on releasing the following candidate as Apache MetaModel version 
> 4.3.0- incubating.
> This will be the fourth incubator release for Metamodel in Apache (and 
> potentially the last, if the also-ongoing vote about graduation passes).
>
> The Git tag to be voted on is v4.3.0- incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.3.0-incubating
>
> The source artifact to be voted on is:
> https://repository.apache.org/content/repositories/orgapachemetamodel-1002/org/apache/metamodel/MetaModel/4.3.0-incubating/MetaModel-4.3.0-incubating-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> https://repository.apache.org/content/repositories/orgapachemetamodel-1002/org/apache/metamodel/MetaModel/4.3.0-incubating
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/kaspersor.asc
>
> Release engineer public key id: 1FE1C2F5
>
> Vote thread link from d...@metamodel.incubator.apache.org mailing list:
> http://markmail.org/message/27orgrjxpnpanwop
>
> Result thread link from d...@metamodel.incubator.apache.org mailing list:
> http://markmail.org/message/qjgol4br3tzckpp6
>
> Please vote on releasing this package as Apache MetaModel 4.3.0- incubating.
>
> The vote is open for 72 hours, or until we get the needed number of votes (3 
> times +1).
>
> [ ] +1 Release this package as Apache MetaModel 4.3.0 -incubating
> [ ] -1 Do not release this package because ...
>
> More information about the MetaModel project can be found at 
> http://metamodel.incubator.apache.org/
>
> Thank you in advance for participating.
>
> Regards,
> Kasper Sørensen

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

Re: [PROPOSAL] Kylin for Incubation

[Henry Saputra]

Directory
>
> Git is the preferred source control system: git://git.apache.org/Kylin
>
> ## Issue Tracking
>
> JIRA Kylin (KYLIN)
>
> ## Other Resources
>
> The existing code already has unit tests so we will make use of
> existing Apache continuous testing infrastructure. The resulting load
> should not be very large.
>
> # Initial Committers
>
> - Jiang Xu < jiangxu.china at gmail dot com>
> - Luke Han 
> - Yang Li 
> - George Song 
> - Hongbin Ma 
> - Xiaodong Duo < oranjedog at gmail dot com>
> - Julian Hyde < jhyde at apache dot org >
> - Ankur Bansal < abansal at ebay dot com>
>
> ## Affiliations
>
> The initial committers are employees of eBay Inc., Ctrip and
> Hortonworks. The nominated mentors are employees of Hortonworks, MapR
> Technologies and Pivotal.
>
> # Sponsors
>
> ## Champion
>
> - Owen O’Malley < omalley at apache dot org >
> - Ted Dunning 
>
> ## Nominated Mentors
>
> - Owen O’Malley < omalley at apache dot org > - Apache IPMC member,
> Co-founder and Senior Architect, Hortonworks
> - Ted Dunning < tdunning at apache dot org> - Apache IPMC member,
> Chief Architect, MapR Technologies
> - Henry Saputra  - Apache IPMC member, Pivotal
> - Jacques Nadeau  (pending admission to
> IPMC) - Apache Drill PMC Chair, MapR Technologies
>
> #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

[VOTE] Graduation of Apache MetaModel from the Incubator

[Henry Saputra]

Hi All,

The Apache MetaModel community has wrapped up the VOTE to propose for
graduation from Apache incubator. The VOTE passed with result:
9 binding +1s
zero 0s
zero -1s
(http://bit.ly/1u8n8eo)

Apache MetaModel came into ASF incubator on 2013 and since then have
grown into small but active community.

We have made several good releases with different release managers,
and also add new PPMC/committers [1].
The project also has good traffic on the dev mailing list [2].

We would like to propose graduation of Apache MetaModel from ASF
incubator to top level project.


[ ] +1 Graduate Apache MetaModel from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache MetaModel from the Incubator because.. .


The VOTE will open for 72 hours (11/17/2014)


Here is the proposal for the board resolution for graduation:


=== Board Resolution ==

Establish the Apache MetaModel Project

WHEREAS, the Board of Directors deems it to be in the best interests
of the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to providing an implementation of a
Platform-as-a-Service Framework.

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

RESOLVED, that the Apache MetaModel Project be and hereby is
responsible for the creation and maintenance of software related to
providing an implementation of a Platform-as-a-Service Framework; and
be it further

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

* Alberto Rodriguez 
* Ankit Kumar 
* Arvind Prabhakar 
* Henry Saputra 
* Juan Jose van der Linden 
* Kasper Sørensen 
* Matt Franklin 
* Noah Slater 
* Sameer Arora 
* Tomasz Guzialek 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kasper Sørensen be
appointed to the office of Vice President, MetaModel, 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 MetaModel 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 MetaModel
Project; and be it further

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

RESOLVED, that all responsibilities pertaining to the Apache Incubator
MetaModel podling encumbered upon the Apache Incubator Project are
hereafter discharged.




Thanks,

Henry
On behalf of Apache MetaModel incubating PPMCs

[1] http://incubator.apache.org/projects/metamodel.html
[2] http://mail-archives.apache.org/mod_mbox/metamodel-dev

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

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

[Henry Saputra]

My vote:

+1 (binding)

On Thu, Nov 13, 2014 at 9:39 PM, Henry Saputra  wrote:
> Hi All,
>
> The Apache MetaModel community has wrapped up the VOTE to propose for
> graduation from Apache incubator. The VOTE passed with result:
> 9 binding +1s
> zero 0s
> zero -1s
> (http://bit.ly/1u8n8eo)
>
> Apache MetaModel came into ASF incubator on 2013 and since then have
> grown into small but active community.
>
> We have made several good releases with different release managers,
> and also add new PPMC/committers [1].
> The project also has good traffic on the dev mailing list [2].
>
> We would like to propose graduation of Apache MetaModel from ASF
> incubator to top level project.
>
>
> [ ] +1 Graduate Apache MetaModel from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache MetaModel from the Incubator because.. .
>
>
> The VOTE will open for 72 hours (11/17/2014)
>
>
> Here is the proposal for the board resolution for graduation:
>
>
> === Board Resolution ==
>
> Establish the Apache MetaModel Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests
> of the Foundation and consistent with the Foundation's purpose to
> establish a Project Management Committee charged with the creation and
> maintenance of open-source software, for distribution at no charge to
> the public, related to providing an implementation of a
> Platform-as-a-Service Framework.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache MetaModel Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache MetaModel Project be and hereby is
> responsible for the creation and maintenance of software related to
> providing an implementation of a Platform-as-a-Service Framework; and
> be it further
>
> RESOLVED, that the office of "Vice President, MetaModel" 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 MetaModel
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache MetaModel
> 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 MetaModel
> Project:
>
> * Alberto Rodriguez 
> * Ankit Kumar 
> * Arvind Prabhakar 
> * Henry Saputra 
> * Juan Jose van der Linden 
> * Kasper Sørensen 
> * Matt Franklin 
> * Noah Slater 
> * Sameer Arora 
> * Tomasz Guzialek 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kasper Sørensen be
> appointed to the office of Vice President, MetaModel, 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 MetaModel 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 MetaModel
> Project; and be it further
>
> RESOLVED, that the Apache MetaModel Project be and hereby is tasked
> with the migration and rationalization of the Apache Incubator
> MetaModel podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> MetaModel podling encumbered upon the Apache Incubator Project are
> hereafter discharged.
>
>
>
>
> Thanks,
>
> Henry
> On behalf of Apache MetaModel incubating PPMCs
>
> [1] http://incubator.apache.org/projects/metamodel.html
> [2] http://mail-archives.apache.org/mod_mbox/metamodel-dev

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

Re: [PROPOSAL] OpenAZ as new Incubator project

[Henry Saputra]

Ah my bad, I usually use abstract section to get main idea of the proposal.

And as per John request, lets start with DISCUSS thread instead.

- Henry

On Thu, Nov 13, 2014 at 2:59 PM, Hal Lockhart  wrote:
> Did you see the background section? I meant that to provide that information. 
> I was unclear on how much to assume the audience already knows about the 
> subject.
>
> Hal
>
>> -Original Message-
>> From: Henry Saputra [mailto:henry.sapu...@gmail.com]
>> Sent: Thursday, November 13, 2014 4:31 PM
>> To: general@incubator.apache.org
>> Subject: Re: [PROPOSAL] OpenAZ as new Incubator project
>>
>> Could you add more description on what is PEP and PDP and other
>> acronyms used in the proposal? If it is not directly relevant maybe you
>> can rephrase it to more generic analogy.
>>
>> Thanks,
>>
>> Henry
>>
>> On Thu, Nov 13, 2014 at 1:14 PM, Hal Lockhart 
>> wrote:
>> > Abstract
>> >
>> > OpenAz is a project to create tools and libraries to enable the
>> development of Attribute-based Access Control (ABAC) Systems in a
>> variety of languages. In general the work is at least consistent with
>> or actually conformant to the OASIS XACML Standard.
>> >
>> > Proposal
>> >
>> > Generally the work falls into two categories: ready to use tools
>> which implement standardized or well understood components of an ABAC
>> system and design proposals and proof of concept code relating to less
>> well understood or experimental aspects of the problem.
>> >
>> > Much of the work to date has revolved around defining interfaces
>> enabling a PEP to request an access control decision from a PDP. The
>> XACML standard defines an abstract request format in xml and protocol
>> wire formats in xaml and json, but it does not specify programmatic
>> interfaces in any language. The standard says that the use of XML (or
>> JSON) is not required only the semantics equivalent.
>> >
>> > The first Interface, AzAPI is modeled closely on the XACML defined
>> interface, expressed in Java. One of the goals was to support calls to
>> both a PDP local to the same process and a PDP in a remote server.
>> AzAPI includes the interface, reference code to handle things like the
>> many supported datatypes in XACML and glue code to mate it to the open
>> source Sun XACML implementation.
>> >
>> > Because of the dependence on Sun XACML (which is XACML 2.0) the
>> interface was missing some XACML 3.0 features. More recently this was
>> corrected and WSo2 has mated it to their XACML 3.0 PDP. Some work was
>> done by the JPMC team to support calling a remote PDP. WSo2 is also
>> pursuing this capability.
>> >
>> > A second, higher level interface, PEPAPI was also defined. PEPAPI is
>> more intended for application developers with little knowledge of
>> XACML. It allows Java objects which contain attribute information to be
>> passed in. Conversion methods, called mappers extract information from
>> the objects and present it in the format expected by XACML. Some
>> implementers have chosen to implement PEPAPI directly against their
>> PDP, omitting the use of AzAPI. Naomaru Itoi defined a C++ interface
>> which closely matches the Java one.
>> >
>> > Examples of more speculative work include: proposals for registration
>> and dispatch of Obligation and Advice handlers, a scheme called AMF to
>> tell PIPs how to retrieve attributes and PIP code to implement it,
>> discussion of PoC code to demonstrate the use of XACML policies to
>> drive OAuth interations and a proposal to use XACML policies to express
>> OAuth scope.
>> >
>> > AT&T has recently contributed their extensive XACML framework to the
>> project.
>> >
>> > The AT&T framework represents the entire XACML 3.0 object set as a
>> collection of Java interfaces and standard implementations of those
>> interfaces.  The AT&T PDP engine is built on top of this framework and
>> represents a complete implementation of a XACML 3.0 PDP, including all
>> of the multi-decision profiles. In addition, the framework also
>> contains an implementation of the OASIS XACML 3.0 RESTful API v1.0 and
>> XACML JSON Profile v1.0 WD 14. The PEP API includes annotation
>> functionality, allowing application developers to simply annotate a
>> Java class to provide attributes for a request. The annotation support
>> removes the need for application developers to learn much of the API.
>> >
>> > The AT&T framework also incl

Re: [PROPOSAL] OpenAZ as new Incubator project

[Henry Saputra]

Could you add more description on what is PEP and PDP and other
acronyms used in the proposal? If it is not directly relevant maybe
you can rephrase it to more generic analogy.

Thanks,

Henry

On Thu, Nov 13, 2014 at 1:14 PM, Hal Lockhart  wrote:
> Abstract
>
> OpenAz is a project to create tools and libraries to enable the development 
> of Attribute-based Access Control (ABAC) Systems in a variety of languages. 
> In general the work is at least consistent with or actually conformant to the 
> OASIS XACML Standard.
>
> Proposal
>
> Generally the work falls into two categories: ready to use tools which 
> implement standardized or well understood components of an ABAC system and 
> design proposals and proof of concept code relating to less well understood 
> or experimental aspects of the problem.
>
> Much of the work to date has revolved around defining interfaces enabling a 
> PEP to request an access control decision from a PDP. The XACML standard 
> defines an abstract request format in xml and protocol wire formats in xaml 
> and json, but it does not specify programmatic interfaces in any language. 
> The standard says that the use of XML (or JSON) is not required only the 
> semantics equivalent.
>
> The first Interface, AzAPI is modeled closely on the XACML defined interface, 
> expressed in Java. One of the goals was to support calls to both a PDP local 
> to the same process and a PDP in a remote server. AzAPI includes the 
> interface, reference code to handle things like the many supported datatypes 
> in XACML and glue code to mate it to the open source Sun XACML implementation.
>
> Because of the dependence on Sun XACML (which is XACML 2.0) the interface was 
> missing some XACML 3.0 features. More recently this was corrected and WSo2 
> has mated it to their XACML 3.0 PDP. Some work was done by the JPMC team to 
> support calling a remote PDP. WSo2 is also pursuing this capability.
>
> A second, higher level interface, PEPAPI was also defined. PEPAPI is more 
> intended for application developers with little knowledge of XACML. It allows 
> Java objects which contain attribute information to be passed in. Conversion 
> methods, called mappers extract information from the objects and present it 
> in the format expected by XACML. Some implementers have chosen to implement 
> PEPAPI directly against their PDP, omitting the use of AzAPI. Naomaru Itoi 
> defined a C++ interface which closely matches the Java one.
>
> Examples of more speculative work include: proposals for registration and 
> dispatch of Obligation and Advice handlers, a scheme called AMF to tell PIPs 
> how to retrieve attributes and PIP code to implement it, discussion of PoC 
> code to demonstrate the use of XACML policies to drive OAuth interations and 
> a proposal to use XACML policies to express OAuth scope.
>
> AT&T has recently contributed their extensive XACML framework to the project.
>
> The AT&T framework represents the entire XACML 3.0 object set as a collection 
> of Java interfaces and standard implementations of those interfaces.  The 
> AT&T PDP engine is built on top of this framework and represents a complete 
> implementation of a XACML 3.0 PDP, including all of the multi-decision 
> profiles. In addition, the framework also contains an implementation of the 
> OASIS XACML 3.0 RESTful API v1.0 and XACML JSON Profile v1.0 WD 14. The PEP 
> API includes annotation functionality, allowing application developers to 
> simply annotate a Java class to provide attributes for a request. The 
> annotation support removes the need for application developers to learn much 
> of the API.
>
> The AT&T framework also includes interfaces and implementations to 
> standardize development of PIP engines that are used by the AT&T PDP 
> implementation, and can be used by other implementations built on top of the 
> AT&T framework. The framework also includes interfaces and implementations 
> for a PAP distributed cloud infrastructure of PDP nodes that includes support 
> for policy distribution and pip configurations. This PAP infrastructure 
> includes a web application administrative console that contains a XACML 3.0 
> policy editor, attribute dictionary support, and management of PDP RESTful 
> node instances. In addition, there are tools available for policy simulation.
>
> Background
>
> Access Control is in some ways the most basic IT Security service. It 
> consists of making a decision about whether a particular request should be 
> allowed and enforcing that decision. Aside from schemes like permission bits 
> and Access Control Lists (ACLs) the most common way access control is 
> implemented is as code in a server or application which typically intertwines 
> access control logic with business logic, User interface and other software. 
> This makes it difficult to understand, modify, analyze or even locate the 
> security policy. The primary challenge of Access Control is striking the 
> right balance between p

Re: complex json file

[Henry Saputra]

Hi Joao,

Looks like you were trying to send email to dev@metamodel incubator instead.

I have forwarded your original email to dev@ list for Apache MetaModel
incubating.

- Henry

On Tue, Nov 11, 2014 at 7:55 AM, Joao Boto  wrote:
> i'm trying to understand how to read a complex json file..
>
> i started with this json (but will work with a much more complex):
> {
> "name":{ "first":"Joe", "last":"Sixpack" },
> "gender":"MALE",
> "verified":false,
> "userImage":"Rm9vYmFyIQ=="
> }
>
> trying to do what Kasper told me on
> https://issues.apache.org/jira/browse/METAMODEL-38
>
> I wrote the code below, but i can't get "first" and "last" fields..
>
> SimpleTableDef custTable = new SimpleTableDef(
> "customer",
> new String[] {"name.first","name.last","gender","verified","userimage"}
> );
>
> SchemaBuilder schema = new SimpleTableDefSchemaBuilder("tester", custTable)
> ;
> JsonDataContext dc = new JsonDataContext(new FileResource(new
> File("src/test/resources/datafeed.json")),schema);
> Table table = dc.getDefaultSchema().getTableByName("customer");
> Column firstName = table.getColumnByName("name.first");
> Column lastName = table.getColumnByName("name.last");
> Column gender = table.getColumnByName("gender");
> DataSet dataSet =
> dc.query().from(table).select(firstName,lastName,gender).execute();
> while (dataSet.next()) {
> String sFirstName = (String) dataSet.getRow().getValue(firstName);
> String sLastName = (String) dataSet.getRow().getValue(lastName);
> String sGender = (String) dataSet.getRow().getValue(gender);
> }
>
> can someone tell me what I'm doing wrong or indicate which way to go?
>
> thanks
>
> Best regards

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

Re: [VOTE] Apache Tamaya for Incubation

[Henry Saputra]

What is the "Sponsors:"  section of this proposal?

I believe the proposal would like to have Apache Incubator to sponsor
the project?

- Henry

On Mon, Nov 10, 2014 at 4:19 PM, Anatole Tresch  wrote:
> Hi all,
>
> Thanks for the feedback thus far on the Tamaya proposal.  Based on prior
> discussion, I'd like to start the vote for Tamaya to be accepted as a new
> incubator project.
>
> The proposal can be found here
> https://wiki.apache.org/incubator/TamayaProposal as well as copied below.
>
> Vote is open until at least Saturday, 15th November 2014, 23:59:00 UTC
>
>  [ ] +1 accept Tamaya in the Incubator
>  [ ] ±0
>  [ ] -1 because...
>
> Thanks and Best Regards
> Anatole
>
>
>
> --
> *Anatole Tresch*
> Java Engineer & Architect, JSR Spec Lead
> Glärnischweg 10
> CH - 8620 Wetzikon
>
> *Switzerland, Europe Zurich, GMT+1*
> *Twitter:  @atsticks*
> *Blogs: **http://javaremarkables.blogspot.ch/
> *
>
> *Google: atsticksMobile  +41-76 344 62 79*
>
> =
>
> = Apache Tamaya - Proposal =
>
> == Abstract ==
> Tamaya is a highly flexible configuration solution based on an
> modular, extensible and
> injectable key/value based design, which should provide a minimal but
> extendible
> modern and functional API leveraging SE, ME and EE environments.
>
> ''Tamaya'' hereby translates into ''in the middle'', which is exactly,
> what configuration should be. It should be
> in the middle between your code and your runtime.
>
> '''NOTE:''' Alternative names could be ''Mahkah=earth, Dakota=friend''
> or ''Orenda=magic force''.
>
>
> == Proposal ==
> Tamaya is a highly flexible configuration API based on an modular,
> extensible and
> injectable key/value based design. The basic building blocks hereby are:
>
>  * ''property providers'' implementing a small and easily
> implementable subset of a `Map`.
>  * support for configuration injection
>  * a type-safe configuration template mechanism
>  * serializable and remote configuration support
>  * a JMX/Rest based management console
>  * Configuration will follow the GoF composite pattern and support
> several combination strategies.
>  * An extendible and adaptable environment model, so configuration can
> be provided dependent of the environment currently active.
>  * extension points and a powerful SPI to seamlessly add additional
> logic to the API, such as secured views, multi-valued validation
> schemes, en-/decryption etc.
>  * Configuration (and property providers) are designed and implemented
> as indirectly mutable types, providing thread-safe and performant to
> configuration.
>  * Configuration changes can be observed by listening on `ConfigChange` 
> events.
>
> The API's focus is on simplicity and ease of use. Developers should
> only have to know a minimal set of artifacts to work with the
> solution.
> The API is built on latest Java 8 features and therefore fit perfectly
> with the functional features of Java 8.
>
> Additionally Apache Tamaya will provide
>  * A Java SE based implementation with minimal features and dependencies.
>  * A Java EE extension module for integration with Java EE and Apache
> Deltaspike.
>  * Once Java ME supports Lambdas, default methods, method references
> and functional interfaces an implementation targeting Java ME should
> be provided as well.
>  * Extension modules for different features.
>  * Adapter/inter-operation modules for other configuration solutions
> including Apache commons-config
>
> == Background ==
> There is a global initiative running now for about a year lead by
> Anatole Tresch (Credit Suisse)
> with the target of standardizing configuration in Java EE and SE. Due
> to several reasons it
> seems currently most sensible to start an OSS project on the topic to
> join forces that actively
> want to contribute to the project. It is highly probably that
> standardization will be restarted
> at a later point once we have a widely used Apache standard.
> For further information you may look at http://javaeeconfig.blogspot.com .
>
> == Rationale ==
> Configuration is one of the most cross-cutting concerns, which still
> lacks of a standard.
> Java EE is currently (EE7) in most areas strictly only configurable during
> build time of the deployed artifacts. Especially dynamic provisioning
> of resources or runtime configuration
> is not supported and in many cases impossible to add without tweaking
> the underlying application server.
> On the other hand running two separate configuration solutions for
> Java EE and Java SE as well make no or
> little sense. So it would be important we have a unified configuration
> model at hand, that is flexible enough, so
>
>  * it can be used in Java SE, EE and ME
>  * it can support contextual behaviour (like in Java EE and
> multi-tenancy/SaaS scenarios)
>  * it provides a uniform API, regardless, if its used in SE or EE scenarios
>  * it supports existing APIs, e.g. `System.getProperties,
> java.util.preferences` in SE and `CDI, JNDI` in 

Re: [RESULT][VOTE] Graduation of Apache Drill from the Incubator

[Henry Saputra]

I wish the discussions that Sean started had occur for projects like
Knox or Tez.

I interacted and watch Drill project for a while before being pulled
out from my prev employer to stop working on it and I could see that
the community did try very hard to diversify and embrace new
contributors from external people.

I think we should open another separate thread to continue the
diversity discussions without hijacking RESULT thread for Drill.

- Henry

On Sat, Oct 25, 2014 at 9:11 AM, Sean Owen  wrote:
> I'm reading http://incubator.apache.org/guides/graduation.html#community
>
> "A major criterion for graduation is to have developed an open and
> diverse meritocratic community ... 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. You can mitigate this requirement by admitting more external
> contributors to your project that have no tie to the single entity."
>
> This seems to contradict the idea that diversity is not required. I
> think Roy's saying something else: you shouldn't have to turn down a
> job to stay on a project, or leave a project to take a job. Of course.
> Nobody wants to kick out contributors, or force addition of people
> from other employers, to graduate. Of course, nobody said graduation
> is a fait accompli.
>
> The issue seems to have come up before, but is de facto not much
> 'enforced'. Diversity is great all else equal, but seems unrealistic
> to demand on entering incubation.  I'm surprised if opinion is that it
> also doesn't matter on exit. I think projects, realistically, get
> driven by companies, and necessarily often start around one company. A
> bit more diversity here would be good but hey. I take the message that
> being an Apache project doesn't signify as much as is advertised (see
> link above) about the 'community support' or diversity. Maybe just how
> it is now and no big deal, but thought I would ask. Thanks for
> indulging.
>
> Ted you raise good points. I was looking at +/- lines really, not
> commits, which is not affected by squashes, but still problematic.
> Size != significance. Github credits the person who made the PR, not
> who merged it (https://github.com/apache/incubator-drill/commits/master
> see authored vs committed) but I think you are saying there are
> significant commits that didn't start with a PR or similar. Recent
> commits follow a similar profile as all commits. I'm not talking so
> much about committers as community contribution. Yeah I'm speaking
> about past not future contributions since graduation has happened now.
>
>
>
> On Sat, Oct 25, 2014 at 4:31 PM, Mattmann, Chris A (3980)
>  wrote:
>> It¹s not a requirement for graduation from the Incubator, as succinctly
>> summarized by Roy (and I am +1 on this):
>>
>> http://markmail.org/message/w56cmyri4osgcgud
>
> -
> 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] Graduation of Apache Drill from the Incubator

[Henry Saputra]

+1 (binding)

God job guys!

- Henry

On Tue, Oct 21, 2014 at 9:21 PM, Tomer Shiran  wrote:
> Hi Everyone,
>
> We wrapped up the vote on the Apache Drill dev list in which the community
> expressed its desire to graduate to a top-level project. That vote passed
> with 23 +1s (http://bit.ly/1tcrHVS) and 0 -1s (including the project's
> mentors, PMC members and committers, as well as IPMC members).
>
> This is a new VOTE to decide if Apache Drill should graduate from the
> Incubator. Please VOTE on the resolution pasted below the ballot. I'll
> leave this VOTE open for at least 72 hours (October 24, 9:30pm PT).
>
> Thanks!
>
> [ ] +1 Graduate Apache Drill from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Drill from the Incubator because.. .
>
> Cheers,
> Tomer
>
>  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 interactive analysis of large-scale datasets.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC),
> to be known as the "Apache Drill Project", be and hereby is established
> pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Drill Project be and hereby is responsible for
> the creation and maintenance of software related to interactive analysis of
> large-scale datasets; and be it further RESOLVED, that the office of "Vice
> President, Apache Drill" 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 Drill Project, and to have primary responsibility for management
> of the projects within the scope of responsibility of the Apache Drill
> 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 Drill Project:
>
> * Jacques Nadeau 
> * Tomer Shiran 
> * Ted Dunning 
> * Jason Frantz 
> * MC Srivas 
> * Keys Botzum 
> * Julian Hyde 
> * Tim Chen 
> * Mehant Baid 
> * Jinfeng Ni 
> * Venki Korukanti 
> * Jason Altekruse 
> * Aditya Kishore 
> * Parth Chandra 
> * Aman Sinha 
> * Steven Phillips 
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jacques Nadeau be appointed to
> the office of Vice President, Apache Drill, 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 Drill Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Drill podling; and be
> it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Drill 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

Re: [VOTE] Release Apache Flink 0.7.0-incubating

[Henry Saputra]

Forward my VOTE from dev@ list

+1 (binding)

- Henry

On Wed, Oct 22, 2014 at 12:29 AM, Robert Metzger  wrote:
> Hi all,
>
> This is our second try to release Flink 0.7.0-incubating. The last time we
> found a critical issue while the vote was running, so I had to cancel the
> vote here.
> The 0.7.0-incubating release will be the second major-version release of
> Flink in the incubator.
>
>
> The vote thread can be found here:
> *https://mail-archives.apache.org/mod_mbox/incubator-flink-dev/201410.mbox/%3CCAGr9p8DqXzM1_SM32zw-nMzZ%2B7%2B1f8XNhyhQzFOxwFFRxp%3DYpw%40mail.gmail.com%3E
> *
>
> The vote passed with +6 binding votes from the PPMC.
>
> -
> The commit to be voted on is in the branch "release-0.7.0-rc2" (commit
> cf4c6e7077fa4c3e3d96758b2f563ec17148a786):
> *http://git-wip-us.apache.org/repos/asf/incubator-flink/commit/cf4c6e70
> *
>
> The release artifacts to be voted on can be found at:
> *http://people.apache.org/~rmetzger/flink-0.7.0-incubating-rc2/
> *
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/rmetzger.asc
>
> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapacheflink-1016
> -
>
> Please vote to approve this release.
>
> The vote is open for 72 hours or until the necessary number of votes is
> reached (+3).
> [ ] +1 Release this package as Apache Flink 0.7.0-incubating
> [ ] -1 Do not release this package because ...
>
>
> Thanks!

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

Re: Project Idea - TagSheets

[Henry Saputra]

Unfortunately, I think you can not attach files to the mailing list so
the attachments need to be somewhere accessible via links.

- Henry

On Thu, Oct 2, 2014 at 10:43 AM, Scott McFarland  wrote:
> I watch Analysts put their data into spreadsheets – Inventory data,
> bug/issues data, other miscellaneous data.  And see them struggle to fit new
> types of data items into their existing set of spreadsheet columns.  And see
> them struggle to find ways to correlate like-type items (frequently done by
> creating new columns to capture relationships).  And see them traversing up
> and down the sheet, unable to easily surf from one item to a related one.
>
> I think that the world is ready for a more loosely-defined type of “sheet”,
> that is to a traditional spreadsheet what a NoSQL database is to a
> relational database.  Less regimented, more flexible.  And, Twitter’s
> popularity has made the “Hashtag” concept intuitive to a wide audience.
> Hence I propose development of a “TagSheet” mechanism to store data, that
> captures relationships between entities by means of associating hashtags to
> them.
>
> This might quickly fill a niche for users who resist complex tools – who
> reflexively reach for spreadsheets when they need to track information.  It
> is a nice fit for inventory management, to start with.
>
> Attached are two markup screens that show what a TagSheet could look like.
> I see it as a small web application, built with Java and JSP, that can run
> under any web server.  Does anyone think that this concept is one that
> Apache would want to develop and promulgate?
>
>
> -
> 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 Ignite into the Apache Incubator

[Henry Saputra]

sts ===
>  * priv...@ignite.incubator.apache.org (with moderated subscriptions)
>  * d...@ignite.incubator.apache.org
>  * commi...@ignite.incubator.apache.org
>
> === Git & JIRA ===
>  * Git: https://git-wip-us.apache.org/repos/asf/incubator-ignite.git
>  * JIRA: JIRA Ignite (IGNITE)
>
> == Initial Committers & Affiliation ==
>  * Dmitriy Setrakyan (GridGain Systems, dsetrakyan at gridgain dot com)
>  * Yakov Zhdanov (GridGain Systems, yzhdanov at gridgain dot com)
>  * Alexey Goncharuk (GridGain Systems, agoncharuk at gridgain dot com)
>  * Sergey Vladykin (GridGain Systems, svladykin at gridgain dot com)
>  * Valentin Kulichenko (GridGain Systems, vkulichenko at gridgain dot com)
>  * Semen Boikov (GridGain Systems, sboikov at gridgain dot com)
>  * Vladimir Ozerov (GridGain Systems, vozerov at gridgain dot com)
>  * Nikita Ivanov (GridGain Systems, nivanov30 at gmail dot com)
>  * Sergey Khisamov (FitechSource, skh at gmail dot com)
>  * Ilya Sterin (ChronoTrack, isterin at gmail dot com)
>  * Ryan Rawson (WANdisco, rawson at apache dot org)
>  * Konstantin Boudnik (WANdisco, cos at apache dot org)
>  * Roman Shaposhnik (Pivotal, rvs at apache dot org)
>  * Branko Cibej (WANdisco, brane at apache dot org)
>
> == Sponsors ==
> === Apache Champion ===
>  * Konstantin Boudnik (cos at apache dot org)
>
> === Nominated Mentors ===
>  * Michael Stack (stack at apache dot org)
>  * Roman Shaposhnik (rvs at apache dot org)
>  * Konstantin Boudnik (cos at apache dot org)
>  * Henry Saputra (hsaputra at apache dot org)
>  * Branko Cibej (brane at apache dot org)
>
> == 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] Silk as new Incubator project

[Henry Saputra]

Cos,

I believe you may also need commits@ list for all the commits
activities to the source repo.

- Henry

On Fri, Sep 26, 2014 at 8:36 PM, Konstantin Boudnik  wrote:
> We have updated the proposal with the section of
>  "Comparative analysis to relevant projects"
>
> which addresses the questions expressed below.
>
> Regards,
>   Cos
>
> On Thu, Sep 18, 2014 at 10:21PM, Henry Saputra wrote:
>> Hi Cos,
>>
>> Looks like a good start of the proposal.
>>
>> How would this project relate to compare to existing ones like Apache
>> Spark, Storm, or Samza?
>>
>> Would love to have comparisons to existing ASF projects section to the 
>> proposal.
>>
>> Also, would you guys mind adding or soliciting more mentors?
>> Seemed like most of initial committers have not been involved in ASF
>> yet so may need some help to adjust to Apache way.
>>
>> - Henry
>>
>> On Thu, Sep 18, 2014 at 9:40 PM, Konstantin Boudnik  wrote:
>> > I would like to propose Silk as an Apache Incubator project. The new
>> > proposal is added to https://wiki.apache.org/incubator/SilkProposal and
>> > is duplicated below.
>> >
>> > --
>> > Regards,
>> >   Cos
>> >
>> >
>> > = Silk Apache Incubator Proposal =
>> >
>> > == Abstract ==
>> >
>> > Apache Silk will be a unified In-Memory Data Fabric providing 
>> > high-performance,
>> > distributed in-memory data management software layer between various data
>> > sources and user applications.
>> >
>> > == Proposal ==
>> >
>> > Apache Silk is written mostly in Java and Scala with small amount of C++ 
>> > code
>> > and will initially combine the following technologies under one unified
>> > umbrella:
>> >  * In-Memory Data Grid
>> >  * In-Memory Compute Grid
>> >  * In-Memory Streaming Processing
>> > This unified in-memory fabric will provide high-performance, distributed
>> > in-memory software layer that sits in between various data sources and user
>> > applica tions. Data sources can include SQL RDBMS, NoSQL, or HDFS. 
>> > Applications
>> > APIs will be available for Java (and Java-based scripting languages), 
>> > Scala,
>> > C++ and .NET (C#).
>> >
>> > GridGain Systems, Inc. submits this proposal to donate its Apache 
>> > 2.0-licensed
>> > open source project generally known as “GridGain In-Memory Computing 
>> > Platform”,
>> > its source code, documentation, and websites to the Apache Software 
>> > Foundation
>> > (“ASF”) with the goal of extending the vibrant open source community around
>> > this technology ultimately governed by “Apache Way”.  Proposed Naming
>> >
>> > We have been advised by the ASF mentors that the name “Silk” may not be 
>> > ideal
>> > because the name may be too generic and may not pass ASF legal check. Here 
>> > are
>> > the alternatives that we have come up with and any of those will be 
>> > acceptable
>> > for the project pending the ASF legal green light:
>> >  * Apache Silk (preferable name)
>> >  * Apache Sylk
>> >  * Apache Memstor
>> >  * Apache Ignite
>> >
>> > == Background & Rationale ==
>> >
>> > In-Memory Data Fabric is a natural and evolutionary consolidation of 
>> > various
>> > “in-memory technologies” from the last decade. From simple local caching
>> > (JSR-107), to distributed caching, to data grids and databases, to 
>> > streaming
>> > and plug-n-play acceleration - the in-memory space has grown quite
>> > dramatically.
>> >
>> > With rapid advances in NVRAM and significant price reduction of traditional
>> > DRAM on one hand, and growing sophistication and demand for faster data
>> > processing on another - many users of these silo-ed technologies and 
>> > products
>> > started to look for a “strategic approach” to in-memory - an in-memory data
>> > fabric - that would provide suitable APIs for different types of payloads: 
>> > from
>> > data caching, to data grids, to in-memory SQL data stores, to HPC, to 
>> > streaming
>> > processing.
>> >
>> > With expensive and proprietary in-memory computing products from companies 
>> > like
>> > Oracle, SAP, Microsoft, and IBM -  the developers worldwide need an 
>> > unhindered
>> > access to advanced open source in-memory soft

Re: [VOTE] Graduate Apache Storm to a TLP

[Henry Saputra]

Congrats again for Apache Storm for being TLP, great work!  =)

- Henry

On Tue, Sep 23, 2014 at 5:52 AM, P. Taylor Goetz  wrote:
> Hi Henry,
>
> I'm working with press@ to put together an official press release (currently 
> waiting on some quotes from PMC members).
>
> That process can take up to two weeks. I only learned of it recently by 
> reading some past board meeting minutes, so we're a little behind time wise.
>
> It might be worthwhile to add something to the graduation guide [1] so other 
> podlings don't make the same mistake.
>
> -Taylor
>
> [1] http://incubator.apache.org/guides/graduation.html
>
>> On Sep 22, 2014, at 9:20 PM, Henry Saputra  wrote:
>>
>> Hi Guys,
>>
>> Question for Apache Storm PPMCs, with Apache Storm graduating, why is
>> the announcement happening at HortonWorks website:
>>
>>  http://hortonworks.com/blog/apache-storm-graduates-top-level-project/
>>
>> rather than in https://blogs.apache.org ?
>>
>> - Henry
>>
>>
>>
>>> On Mon, Aug 18, 2014 at 2:02 PM, P. Taylor Goetz  wrote:
>>> Apache Storm has been incubating since September 2014. Since then we have 
>>> added 3 additional committers (with another 2 approved and pending account 
>>> creation), and performed two releases. The Storm community recently voted 
>>> to graduate[1] with 11 +1 votes. Of the 11 votes, 2 were from IPMC members:
>>>
>>>- Arvind Prabhakar
>>>- Suresh Srinivas
>>>
>>> I would now like to ask the IPMC to vote for the graduation of Apache Storm 
>>> to a top-level project.
>>>
>>> Please vote to indicate if Apache Storm is ready to graduate. The proposed 
>>> board resolution is included below.
>>>
>>> [ ] +1 Graduate Apache Storm as a TLP
>>> [ ] +0 No opinion
>>> [ ] -1 Do not graduate Apache Storm as a TLP because…
>>>
>>> This vote will be open for at least 72 hours.
>>>
>>> - Taylor
>>>
>>> [1] 
>>> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201408.mbox/%3c6ea90e5b-792f-4ec2-b5fc-086caf642...@apache.org%3e
>>>
>>>
>>>
>>> === Board Resolution ===
>>>
>>>X. Establish the Apache Storm 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 distributed, fault-tolerant,
>>>   and high-performance realtime computation.
>>>
>>>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>>   Committee (PMC), to be known as the "Apache Storm Project",
>>>   be and hereby is established pursuant to Bylaws of the
>>>   Foundation; and be it further
>>>
>>>   RESOLVED, that the Apache Storm Project be and hereby is
>>>   responsible for the creation and maintenance of software
>>>   related to distributed, fault-tolerant, and high-
>>>   performance realtime computation; and be it further
>>>
>>>   RESOLVED, that the office of "Vice President, Apache Storm" 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 Storm Project, and to have primary responsibility
>>>   for management of the projects within the scope of
>>>   responsibility of the Apache Storm 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 Storm Project:
>>>
>>> * Derek Dagit  (da...@apache.org)
>>> * Devaraj Das  (d...@apache.org)
>>> * Ted Dunning  (tdunn...@apache.org)
>>> * Robert Evans (bo...@apache.org)
>>> * Andy Feng(af...@apache.org)
>>> * P. Taylor Goetz  (ptgo...@apache.org)
>>> * Jason Jackson(jjack...@apache.org)
>>> * Flip Kromer  (mrf...@apache.org)
>>> * David Lao(d...@apache.org)
>>> * Nathan Marz  (nathanm...@apache.org)
>>>  

Re: [VOTE] Graduate Apache Storm to a TLP

[Henry Saputra]

Thanks for the update Taylor. Just to make sure you guys working with
press@ for the official announcement.

Incubator projects are little bit scrutinized when making
announcements under ASF so I want to make sure HW understand about it.

Thanks,


Henry

On Tue, Sep 23, 2014 at 5:52 AM, P. Taylor Goetz  wrote:
> Hi Henry,
>
> I'm working with press@ to put together an official press release (currently 
> waiting on some quotes from PMC members).
>
> That process can take up to two weeks. I only learned of it recently by 
> reading some past board meeting minutes, so we're a little behind time wise.
>
> It might be worthwhile to add something to the graduation guide [1] so other 
> podlings don't make the same mistake.
>
> -Taylor
>
> [1] http://incubator.apache.org/guides/graduation.html
>
>> On Sep 22, 2014, at 9:20 PM, Henry Saputra  wrote:
>>
>> Hi Guys,
>>
>> Question for Apache Storm PPMCs, with Apache Storm graduating, why is
>> the announcement happening at HortonWorks website:
>>
>>  http://hortonworks.com/blog/apache-storm-graduates-top-level-project/
>>
>> rather than in https://blogs.apache.org ?
>>
>> - Henry
>>
>>
>>
>>> On Mon, Aug 18, 2014 at 2:02 PM, P. Taylor Goetz  wrote:
>>> Apache Storm has been incubating since September 2014. Since then we have 
>>> added 3 additional committers (with another 2 approved and pending account 
>>> creation), and performed two releases. The Storm community recently voted 
>>> to graduate[1] with 11 +1 votes. Of the 11 votes, 2 were from IPMC members:
>>>
>>>- Arvind Prabhakar
>>>- Suresh Srinivas
>>>
>>> I would now like to ask the IPMC to vote for the graduation of Apache Storm 
>>> to a top-level project.
>>>
>>> Please vote to indicate if Apache Storm is ready to graduate. The proposed 
>>> board resolution is included below.
>>>
>>> [ ] +1 Graduate Apache Storm as a TLP
>>> [ ] +0 No opinion
>>> [ ] -1 Do not graduate Apache Storm as a TLP because…
>>>
>>> This vote will be open for at least 72 hours.
>>>
>>> - Taylor
>>>
>>> [1] 
>>> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201408.mbox/%3c6ea90e5b-792f-4ec2-b5fc-086caf642...@apache.org%3e
>>>
>>>
>>>
>>> === Board Resolution ===
>>>
>>>X. Establish the Apache Storm 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 distributed, fault-tolerant,
>>>   and high-performance realtime computation.
>>>
>>>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>>   Committee (PMC), to be known as the "Apache Storm Project",
>>>   be and hereby is established pursuant to Bylaws of the
>>>   Foundation; and be it further
>>>
>>>   RESOLVED, that the Apache Storm Project be and hereby is
>>>   responsible for the creation and maintenance of software
>>>   related to distributed, fault-tolerant, and high-
>>>   performance realtime computation; and be it further
>>>
>>>   RESOLVED, that the office of "Vice President, Apache Storm" 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 Storm Project, and to have primary responsibility
>>>   for management of the projects within the scope of
>>>   responsibility of the Apache Storm 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 Storm Project:
>>>
>>> * Derek Dagit  (da...@apache.org)
>>> * Devaraj Das  (d...@apache.org)
>>> * Ted Dunning  (tdunn...@apache.org)
>>> * Robert Evans (bo...@apache.org)
>>> * Andy Feng(af...@apache.org)
>>> * P. Taylor Goetz  (ptgo...@apache.org)
>>> * Jason Jackson(jjack...@apache.org)
>>> 

Re: [VOTE] Graduate Apache Storm to a TLP

[Henry Saputra]

Hi Guys,

Question for Apache Storm PPMCs, with Apache Storm graduating, why is
the announcement happening at HortonWorks website:

  http://hortonworks.com/blog/apache-storm-graduates-top-level-project/

rather than in https://blogs.apache.org ?

- Henry



On Mon, Aug 18, 2014 at 2:02 PM, P. Taylor Goetz  wrote:
> Apache Storm has been incubating since September 2014. Since then we have 
> added 3 additional committers (with another 2 approved and pending account 
> creation), and performed two releases. The Storm community recently voted to 
> graduate[1] with 11 +1 votes. Of the 11 votes, 2 were from IPMC members:
>
> - Arvind Prabhakar
> - Suresh Srinivas
>
> I would now like to ask the IPMC to vote for the graduation of Apache Storm 
> to a top-level project.
>
> Please vote to indicate if Apache Storm is ready to graduate. The proposed 
> board resolution is included below.
>
> [ ] +1 Graduate Apache Storm as a TLP
> [ ] +0 No opinion
> [ ] -1 Do not graduate Apache Storm as a TLP because…
>
> This vote will be open for at least 72 hours.
>
> - Taylor
>
> [1] 
> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201408.mbox/%3c6ea90e5b-792f-4ec2-b5fc-086caf642...@apache.org%3e
>
>
>
> === Board Resolution ===
>
> X. Establish the Apache Storm 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 distributed, fault-tolerant,
>and high-performance realtime computation.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache Storm Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache Storm Project be and hereby is
>responsible for the creation and maintenance of software
>related to distributed, fault-tolerant, and high-
>performance realtime computation; and be it further
>
>RESOLVED, that the office of "Vice President, Apache Storm" 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 Storm Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache Storm 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 Storm Project:
>
>  * Derek Dagit  (da...@apache.org)
>  * Devaraj Das  (d...@apache.org)
>  * Ted Dunning  (tdunn...@apache.org)
>  * Robert Evans (bo...@apache.org)
>  * Andy Feng(af...@apache.org)
>  * P. Taylor Goetz  (ptgo...@apache.org)
>  * Jason Jackson(jjack...@apache.org)
>  * Flip Kromer  (mrf...@apache.org)
>  * David Lao(d...@apache.org)
>  * Nathan Marz  (nathanm...@apache.org)
>  * Michael G. Noll  (mig...@apache.org)
>  * Arvind Prabhakar (arv...@apache.org)
>  * James Xu (xumingm...@apache.org)
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that P. Taylor Goetz
>be appointed to the office of Vice President, Apache Storm, 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 Storm 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 Storm Project; and be it further
>
>RESOLVED, that the Apache Storm Project be and hereby
>is tasked with the migration and rationalization of the Apache
>Incubator Storm podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache
>Incubator Storm 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

Re: [PROPOSAL] Silk as new Incubator project

[Henry Saputra]

Thanks for the response, Konstantin.

Definitely glad to help as mentor.
I have added my name as one of the mentors in the list.

Still love to see the "Relationships to other Apache projects section"
in the proposal.

- Henry



On Sun, Sep 21, 2014 at 6:59 PM, Konstantin Boudnik  wrote:
> On Thu, Sep 18, 2014 at 10:21PM, Henry Saputra wrote:
>> Hi Cos,
>>
>> Looks like a good start of the proposal.
>>
>> How would this project relate to compare to existing ones like Apache
>> Spark, Storm, or Samza?
>
> The proposal will be updated shortly with these details.
>
>> Would love to have comparisons to existing ASF projects section to the 
>> proposal.
>>
>> Also, would you guys mind adding or soliciting more mentors?
>> Seemed like most of initial committers have not been involved in ASF
>> yet so may need some help to adjust to Apache way.
>
> Good point, Henry! Would you consider investing a few cycles on your own and
> join the mentors for this proposal? Thanks in advance!
>
> Cos
>
>>
>> - Henry
>>
>> On Thu, Sep 18, 2014 at 9:40 PM, Konstantin Boudnik  wrote:
>> > I would like to propose Silk as an Apache Incubator project. The new
>> > proposal is added to https://wiki.apache.org/incubator/SilkProposal and
>> > is duplicated below.
>> >
>> > --
>> > Regards,
>> >   Cos
>> >
>> >
>> > = Silk Apache Incubator Proposal =
>> >
>> > == Abstract ==
>> >
>> > Apache Silk will be a unified In-Memory Data Fabric providing 
>> > high-performance,
>> > distributed in-memory data management software layer between various data
>> > sources and user applications.
>> >
>> > == Proposal ==
>> >
>> > Apache Silk is written mostly in Java and Scala with small amount of C++ 
>> > code
>> > and will initially combine the following technologies under one unified
>> > umbrella:
>> >  * In-Memory Data Grid
>> >  * In-Memory Compute Grid
>> >  * In-Memory Streaming Processing
>> > This unified in-memory fabric will provide high-performance, distributed
>> > in-memory software layer that sits in between various data sources and user
>> > applica tions. Data sources can include SQL RDBMS, NoSQL, or HDFS. 
>> > Applications
>> > APIs will be available for Java (and Java-based scripting languages), 
>> > Scala,
>> > C++ and .NET (C#).
>> >
>> > GridGain Systems, Inc. submits this proposal to donate its Apache 
>> > 2.0-licensed
>> > open source project generally known as “GridGain In-Memory Computing 
>> > Platform”,
>> > its source code, documentation, and websites to the Apache Software 
>> > Foundation
>> > (“ASF”) with the goal of extending the vibrant open source community around
>> > this technology ultimately governed by “Apache Way”.  Proposed Naming
>> >
>> > We have been advised by the ASF mentors that the name “Silk” may not be 
>> > ideal
>> > because the name may be too generic and may not pass ASF legal check. Here 
>> > are
>> > the alternatives that we have come up with and any of those will be 
>> > acceptable
>> > for the project pending the ASF legal green light:
>> >  * Apache Silk (preferable name)
>> >  * Apache Sylk
>> >  * Apache Memstor
>> >  * Apache Ignite
>> >
>> > == Background & Rationale ==
>> >
>> > In-Memory Data Fabric is a natural and evolutionary consolidation of 
>> > various
>> > “in-memory technologies” from the last decade. From simple local caching
>> > (JSR-107), to distributed caching, to data grids and databases, to 
>> > streaming
>> > and plug-n-play acceleration - the in-memory space has grown quite
>> > dramatically.
>> >
>> > With rapid advances in NVRAM and significant price reduction of traditional
>> > DRAM on one hand, and growing sophistication and demand for faster data
>> > processing on another - many users of these silo-ed technologies and 
>> > products
>> > started to look for a “strategic approach” to in-memory - an in-memory data
>> > fabric - that would provide suitable APIs for different types of payloads: 
>> > from
>> > data caching, to data grids, to in-memory SQL data stores, to HPC, to 
>> > streaming
>> > processing.
>> >
>> > With expensive and proprietary in-memory computing products from companies 
>> > like
>> 

Re: [VOTE] Release Apache Flink 0.6.1-incubating

[Henry Saputra]

Forward my binding vote from dev@ list

+1 (binding)

- Henry

On Fri, Sep 19, 2014 at 6:20 AM, Ufuk Celebi  wrote:
> Please vote on releasing Apache Flink (incubating) 0.6.1-incubating.
>
> This will be the second release of the Apache Flink project under the
> Incubator. Besides minor bug fixes, this release addresses issues raised by
> Justin Mclean regarding the LICENSE and NOTICE files of the previous
> 0.6-incubating release.
>
> Vote on d...@flink-incubator.apache.org:
> http://mail-archives.apache.org/mod_mbox/incubator-flink-dev/201409.mbox/%3CCAKiyyaEd-Db-HwBnwf24wVtJ5FpE0UC1NfQ-0vnQ5SffQ3fSJQ%40mail.gmail.com%3E
>
> Vote result (4 binding +1s, no -1s):
> http://mail-archives.apache.org/mod_mbox/incubator-flink-dev/201409.mbox/%3CCAKiyyaH0u%2BVgL-1e8TCMRwnnKT88cMPfNo2kVup2ShUeS1rmCA%40mail.gmail.com%3E
>
> The tag to be voted on is release-0.6.1-rc0 (commit 0d3f3a1):
> https://git-wip-us.apache.org/repos/asf?p=incubator-flink.git;a=commit;h=0d3f3a172f98837db039f4ac539c5630e294580c
>
> The release artifacts to be voted on can be found at:
> http://people.apache.org/~uce/flink-0.6.1-incubating-rc0/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/uce.asc
>
> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapacheflink-1013/
>
>
> Please vote on releasing this package as Apache Flink 0.6.1-incubating.
>
> The vote will be open for at least 72 hours until:
>
> Wednesday, September 19, 7:00 am (PDT, UTC-7) or 4:00 pm (CEST, UTC+2)
> respectively.
>
> [ ] +1 Release this package as Apache Flink 0.6.1-incubating
> [ ] -1 Do not release this package because ...
>
> Thanks,
>
> The Apache Flink Team

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

Re: [PROPOSAL] Silk as new Incubator project

[Henry Saputra]

Hi Cos,

Looks like a good start of the proposal.

How would this project relate to compare to existing ones like Apache
Spark, Storm, or Samza?

Would love to have comparisons to existing ASF projects section to the proposal.

Also, would you guys mind adding or soliciting more mentors?
Seemed like most of initial committers have not been involved in ASF
yet so may need some help to adjust to Apache way.

- Henry

On Thu, Sep 18, 2014 at 9:40 PM, Konstantin Boudnik  wrote:
> I would like to propose Silk as an Apache Incubator project. The new
> proposal is added to https://wiki.apache.org/incubator/SilkProposal and
> is duplicated below.
>
> --
> Regards,
>   Cos
>
>
> = Silk Apache Incubator Proposal =
>
> == Abstract ==
>
> Apache Silk will be a unified In-Memory Data Fabric providing 
> high-performance,
> distributed in-memory data management software layer between various data
> sources and user applications.
>
> == Proposal ==
>
> Apache Silk is written mostly in Java and Scala with small amount of C++ code
> and will initially combine the following technologies under one unified
> umbrella:
>  * In-Memory Data Grid
>  * In-Memory Compute Grid
>  * In-Memory Streaming Processing
> This unified in-memory fabric will provide high-performance, distributed
> in-memory software layer that sits in between various data sources and user
> applica tions. Data sources can include SQL RDBMS, NoSQL, or HDFS. 
> Applications
> APIs will be available for Java (and Java-based scripting languages), Scala,
> C++ and .NET (C#).
>
> GridGain Systems, Inc. submits this proposal to donate its Apache 2.0-licensed
> open source project generally known as “GridGain In-Memory Computing 
> Platform”,
> its source code, documentation, and websites to the Apache Software Foundation
> (“ASF”) with the goal of extending the vibrant open source community around
> this technology ultimately governed by “Apache Way”.  Proposed Naming
>
> We have been advised by the ASF mentors that the name “Silk” may not be ideal
> because the name may be too generic and may not pass ASF legal check. Here are
> the alternatives that we have come up with and any of those will be acceptable
> for the project pending the ASF legal green light:
>  * Apache Silk (preferable name)
>  * Apache Sylk
>  * Apache Memstor
>  * Apache Ignite
>
> == Background & Rationale ==
>
> In-Memory Data Fabric is a natural and evolutionary consolidation of various
> “in-memory technologies” from the last decade. From simple local caching
> (JSR-107), to distributed caching, to data grids and databases, to streaming
> and plug-n-play acceleration - the in-memory space has grown quite
> dramatically.
>
> With rapid advances in NVRAM and significant price reduction of traditional
> DRAM on one hand, and growing sophistication and demand for faster data
> processing on another - many users of these silo-ed technologies and products
> started to look for a “strategic approach” to in-memory - an in-memory data
> fabric - that would provide suitable APIs for different types of payloads: 
> from
> data caching, to data grids, to in-memory SQL data stores, to HPC, to 
> streaming
> processing.
>
> With expensive and proprietary in-memory computing products from companies 
> like
> Oracle, SAP, Microsoft, and IBM -  the developers worldwide need an unhindered
> access to advanced open source in-memory software technology, the technology
> they can trust to develop with and deploy for critical applications.  Current
> Status
>
> Apache Silk will be based on the technology that is currently developed by
> GridGain Systems and available under Apache 2.0 license
> (http://www.gridgain.org). The software has been in development since 2007 and
> in production since 2009. It is currently used by over 500 production
> deployments with over 1,000,000 downloads to date, and with over 20,000,000
> GridGain nodes started in the last 5 years.
>
> == Initial Goals ==
>
> The number one goal during ASF incubation will coalesce around building a true
> active and vibrant community governed by the “Apache Way”. The initial
> development goals for Silk primarily revolve around migrating the existing 
> code
> base, documentation, and refactoring of the existing internal build, test &
> release processes. We believe these initial goals are sufficiently difficult 
> to
> be considered early milestones.
>
> Some of the specific initial goals include:
>  * Migrate the existing Silk code base to the ASF.
>  * Refactor development, testing, build and release processes to work in ASF.
>  * Attract developer and user interest in the new Apache Silk project.
>  * Road map the integration efforts with “sister” projects in ASF eco-system 
> like Storm and Spark.
>  * Incorporate externally developed features into the core Apache Silk 
> project.
>
> == Known Risks ==
>
> This proposal is not without its risks, some of which are outlined below.
>
> The current list of committers are primarily from GridGain Sy

Re: [VOTE] Graduate Apache Storm to a TLP

[Henry Saputra]

I assume +1 from Ted counted as mentor vote?


On Mon, Aug 18, 2014 at 6:24 PM, P. Taylor Goetz  wrote:
> Hi Justin,
>
> In the PPMC vote, we had one mentor +1 (Arvind Prabhakar), and one non-mentor 
> IPMC member +1 (Suresh Srinivas).
>
> -Taylor
>
>> On Aug 18, 2014, at 9:16 PM, Justin Mclean  wrote:
>>
>> Hi,
>>
>> How many +1 votes were by your mentors?
>>
>> Justin
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Graduate Apache Storm to a TLP

[Henry Saputra]

+1 (binding)

Good work guys, congrats!


- Henry

On Mon, Aug 18, 2014 at 2:02 PM, P. Taylor Goetz  wrote:
> Apache Storm has been incubating since September 2014. Since then we have 
> added 3 additional committers (with another 2 approved and pending account 
> creation), and performed two releases. The Storm community recently voted to 
> graduate[1] with 11 +1 votes. Of the 11 votes, 2 were from IPMC members:
>
> - Arvind Prabhakar
> - Suresh Srinivas
>
> I would now like to ask the IPMC to vote for the graduation of Apache Storm 
> to a top-level project.
>
> Please vote to indicate if Apache Storm is ready to graduate. The proposed 
> board resolution is included below.
>
> [ ] +1 Graduate Apache Storm as a TLP
> [ ] +0 No opinion
> [ ] -1 Do not graduate Apache Storm as a TLP because…
>
> This vote will be open for at least 72 hours.
>
> - Taylor
>
> [1] 
> http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201408.mbox/%3c6ea90e5b-792f-4ec2-b5fc-086caf642...@apache.org%3e
>
>
>
> === Board Resolution ===
>
> X. Establish the Apache Storm 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 distributed, fault-tolerant,
>and high-performance realtime computation.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache Storm Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache Storm Project be and hereby is
>responsible for the creation and maintenance of software
>related to distributed, fault-tolerant, and high-
>performance realtime computation; and be it further
>
>RESOLVED, that the office of "Vice President, Apache Storm" 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 Storm Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache Storm 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 Storm Project:
>
>  * Derek Dagit  (da...@apache.org)
>  * Devaraj Das  (d...@apache.org)
>  * Ted Dunning  (tdunn...@apache.org)
>  * Robert Evans (bo...@apache.org)
>  * Andy Feng(af...@apache.org)
>  * P. Taylor Goetz  (ptgo...@apache.org)
>  * Jason Jackson(jjack...@apache.org)
>  * Flip Kromer  (mrf...@apache.org)
>  * David Lao(d...@apache.org)
>  * Nathan Marz  (nathanm...@apache.org)
>  * Michael G. Noll  (mig...@apache.org)
>  * Arvind Prabhakar (arv...@apache.org)
>  * James Xu (xumingm...@apache.org)
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that P. Taylor Goetz
>be appointed to the office of Vice President, Apache Storm, 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 Storm 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 Storm Project; and be it further
>
>RESOLVED, that the Apache Storm Project be and hereby
>is tasked with the migration and rationalization of the Apache
>Incubator Storm podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache
>Incubator Storm 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

Re: [VOTE] Release Apache Flink 0.6-incubating

[Henry Saputra]

Forward my +1 vote from the dev@ list

+1 (binding)


- Henry


On Mon, Aug 18, 2014 at 1:12 PM, Robert Metzger  wrote:
> Hi all,
>
> This is to call for a vote for releasing Flink 0.6-incubating. This is the
> first release of the Apache Flink project inside the Incubator.
>
> Vote on d...@flink.incubator.apache.org:
> http://mail-archives.apache.org/mod_mbox/incubator-flink-dev/201408.mbox/%3CCAGr9p8AQWYhH4m37Pwt217ngaqZXJvU1qi82otX0PvBqTH3A_Q%40mail.gmail.com%3E
> 
>
> Vote result: (8 binding +1 votes, no -1's)
> http://mail-archives.apache.org/mod_mbox/incubator-flink-dev/201408.mbox/%3CCAGr9p8A44XhKMFQw_FvCwyvrv-eRH0pkeza%2BrSgYRCoVYf5ujw%40mail.gmail.com%3E
>
> The commit to be voted upon:
> *http://git-wip-us.apache.org/repos/asf/incubator-flink/commit/053f4c65
> *
>
> The artifacts to be voted on are located here:
> *http://people.apache.org/~rmetzger/flink-0.6-incubating-rc7/
> *
>
> The GPG key (D9839159) used to sign the release is available at:
> https://dist.apache.org/repos/dist/release/incubator/flink/KEYS
>
> A staged Maven repository is available for review at:
> *https://repository.apache.org/content/repositories/orgapacheflink-1011/
> *
>
> Please vote on releasing this package as Apache Flink 0.6-incubating.
>
> The vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Flink 0.6-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
> The Apache Flink Team

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

Re: [VOTE] Apache Drill 0.4.0-incubating release

[Henry Saputra]

Ah, I saw disclaimer in the website [1] which I thought enough for incubator.
But checking the branding guide [2] seems like incubator need to
include DISCLAIMER file along with NOTICE and LICENSE files, so this
could be blocker?
I think that is the one that could be blocker, but other probably
could be deferred to next release given Drill open tickets for them?

Thanks for detail review Justin, need to update my check tool.

[1] http://incubator.apache.org/drill/
[2] http://incubator.apache.org/guides/branding.html

On Thu, Aug 7, 2014 at 4:52 PM, Justin Mclean  wrote:
> (resending as it look like the original email got caught up in moderation)
>
> Hi
>
> -1 binding.
>
> There several issues with LICENSE and NOTICE that need to be fixed/explained 
> before I'd vote +1. I am concerned about the category B licences in 
> particular. The required DISCLAIMER file is also missing.
>
> - DISCLAIMER file missing
> - incorrect year in NOTICE file (should be 2014 not 2013)
> - make notice file more in line with standard NOTICE file [1]
> - LICENSE file is not correct - looks like quite a few things need to be 
> removed as they are not actually bundled in the source artefact. The LICENSE 
> file in the source artefact should only reference software that is actually 
> bundled in the source release.
> - LICENSE file doesn't need to contain references to Apache licensed software 
> only MIT and BSD software. Each bundled Apache software may modify the NOTICE 
> file.
> - LICENSE issue "The compiled Apache Drill distribution includes the 
> following sources/binaries." is incorrect as a source distribution shouldn't 
> normally contain binaries.
> - LICENSE refers to CDDL licensed, CPL licensed, EPL licensed and MPL 
> licensed software - all which are category B licences. Are these actually 
> included in the source release and if so how? And if they are included why 
> are they not in the NOTICE file (as per [2]) If not included why are these 
> mentioned in the the LICENCES file at all?
>
> What's good:
> - artefact contains incubating
> - signatures and md5 good
> - no binary files in source release (other than a few files used for testing)
> - source files have apache header (although some testing .json and the like 
> look to be missing headers)
> - can compile from source
>
> Thanks,
> Justin
>
> 1. http://www.apache.org/legal/src-headers.html#notice
> 2. http://www.apache.org/legal/3party.html
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Apache Drill 0.4.0-incubating release

[Henry Saputra]

Signatures files looks good
LICENSE looks good
NOTICE file needs to update year to 2014 => not a blocker but please
open ticket to track it
Version looks good
No 3rd party exec files

+1

- Henry


On Mon, Aug 4, 2014 at 7:07 AM, Jacques Nadeau  wrote:
> We've held a vote on drill-dev to release the 0.4.0-incubating release of
> Apache Drill.
>
> The vote thread can be found here:
> http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201407.mbox/%3CCAKa9qD%3DKQURAMcS3RQJbUABSU4%3DDEGSewK2s4MAAidu4c%3DOjBg%40mail.gmail.com%3E
>
> The vote passed with:
> +6 binding
> +7 non-binding
>
> A summary email can be found here:
> http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201408.mbox/%3CCAKa9qDnyKYS%3D3qbv3%3DfUrcuuNvBKRcvPt4AgWojLhy4tr2ZYLA%40mail.gmail.com%3E
>
> You can find the artifacts for the release at this location:
> http://people.apache.org/~jacques/apache-drill-0.4.0.rc1/
>
> Please vote on this release.
>
> Thanks,
> Jacques

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

Re: [VOTE] Release Apache Aurora 0.5.0 (incubating)

[Henry Saputra]

Awesome! Congrats guys!

- Henry

On Thu, Jul 31, 2014 at 6:56 PM, Jake Farrell  wrote:
> With four binding +1's and two non-binding +1's the vote for Apache Aurora
> 0.5.0 passes. Thanks everyone for taking the time to review and vote
>
> -Jake
>
>
> Binding
> ---
> Benjamin Hindman
> Jake Farrell
> Justin Mclean
> Henry Saputra
>
> Non-Binding
> ---
> Chris Aniszczyk
> Kevin Sweeney
>
>
>
> On Mon, Jul 28, 2014 at 8:47 PM, Kevin Sweeney  wrote:
>
>> Hi All,
>>
>> Please vote on releasing the following artifacts as Apache Aurora 0.5.0
>> incubating. This will be the first release for Aurora since entering the
>> Apache Incubator.
>>
>> The source artifact to be voted on is:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/aurora/0.5.0-rc2/apache-aurora-0.5.0-rc2-incubating.tar.gz
>>
>> The MD5 checksum of the release candidate can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/aurora/0.5.0-rc2/apache-aurora-0.5.0-rc2-incubating.tar.gz.md5
>>
>> The signature of the release candidate can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/aurora/0.5.0-rc2/apache-aurora-0.5.0-rc2-incubating.tar.gz.asc
>>
>> The GPG key used to sign the release are available at:
>> https://dist.apache.org/repos/dist/dev/incubator/aurora/KEYS
>>
>> Vote thread link from d...@aurora.incubator.apache.org mailing list:
>>
>> https://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201407.mbox/%3CCAAATh-aGP8pdbUsk7-R6ou--1V%3DbZ5G%3Dq4EX%2BxgQSL73xfRRzQ%40mail.gmail.com%3E
>>
>> Please vote on releasing this package as Apache Aurora 0.5.0 incubating.
>>
>> The vote is open for 72 hours, or until the necessary number of votes (3
>> +1) is reached.
>>
>> [ ] +1 Release this package as Apache Aurora 0.5.0 incubating
>> [ ] -1 Do not release this package because ...
>>
>> More information about the Aurora project can be found at
>> http://aurora.incubator.apache.org/
>>
>> Thank you for your participation
>>
>> Apache Aurora PPMC
>>

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

Re: [VOTE] Release Apache Aurora 0.5.0 (incubating)

[Henry Saputra]

Forward my VOTE from dev@ list

+1 (binding)

On Mon, Jul 28, 2014 at 5:47 PM, Kevin Sweeney  wrote:
> Hi All,
>
> Please vote on releasing the following artifacts as Apache Aurora 0.5.0
> incubating. This will be the first release for Aurora since entering the
> Apache Incubator.
>
> The source artifact to be voted on is:
> https://dist.apache.org/repos/dist/dev/incubator/aurora/0.5.0-rc2/apache-aurora-0.5.0-rc2-incubating.tar.gz
>
> The MD5 checksum of the release candidate can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/aurora/0.5.0-rc2/apache-aurora-0.5.0-rc2-incubating.tar.gz.md5
>
> The signature of the release candidate can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/aurora/0.5.0-rc2/apache-aurora-0.5.0-rc2-incubating.tar.gz.asc
>
> The GPG key used to sign the release are available at:
> https://dist.apache.org/repos/dist/dev/incubator/aurora/KEYS
>
> Vote thread link from d...@aurora.incubator.apache.org mailing list:
> https://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201407.mbox/%3CCAAATh-aGP8pdbUsk7-R6ou--1V%3DbZ5G%3Dq4EX%2BxgQSL73xfRRzQ%40mail.gmail.com%3E
>
> Please vote on releasing this package as Apache Aurora 0.5.0 incubating.
>
> The vote is open for 72 hours, or until the necessary number of votes (3 +1)
> is reached.
>
> [ ] +1 Release this package as Apache Aurora 0.5.0 incubating
> [ ] -1 Do not release this package because ...
>
> More information about the Aurora project can be found at
> http://aurora.incubator.apache.org/
>
> Thank you for your participation
>
> Apache Aurora PPMC

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

Re: [VOTE] Release Apache Metamodel incubating 4.2.0

[Henry Saputra]

As always, thanks Arvind :)

On Sunday, July 27, 2014, Arvind Prabhakar  wrote:

> +1 (binding, forward from dev vote)
>
> Regards,
> Arvind Prabhakar
>
>
> On Sun, Jul 27, 2014 at 8:55 AM, Kasper Sørensen <
> kasper.soren...@humaninference.com > wrote:
>
> > Hi All,
> >
> > Please vote on releasing the following artifacts as Apache MetaModel
> > version 4.2.0-incubating.
> > This will be the third incubator release for Metamodel in Apache.
> >
> > The Git tag to be voted on is v4.2.0-incubating:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.2.0-incubating
> >
> > The source artifact to be voted on is:
> >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1001/org/apache/metamodel/MetaModel/4.2.0-incubating/MetaModel-4.2.0-incubating-source-release.zip
> >
> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> >
> https://repository.apache.org/content/repositories/orgapachemetamodel-1001/org/apache/metamodel/MetaModel/4.2.0-incubating/
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/kaspersor.asc
> >
> > Release engineer public key id: 1FE1C2F5
> >
> > Vote thread link from d...@metamodel.incubator.apache.org 
> mailing list:
> > http://markmail.org/thread/wmvcudxe6yhijzxb
> >
> > Result thread link from d...@metamodel.incubator.apache.org
>  mailing list:
> > http://markmail.org/message/bikigx33epufc76i
> >
> > Please vote on releasing this package as Apache MetaModel
> 4.2.0-incubating.
> >
> > The vote is open for 72 hours, or until we get the needed number of votes
> > (3 +1).
> >
> > [ ] +1 Release this package as Apache MetaModel 4.2.0-incubating
> > [ ] -1 Do not release this package because ...
> >
> > More information about the MetaModel project can be found at
> > http://metamodel.incubator.apache.org/
> >
> > Thank you in advance for participating.
> >
> > Regards,
> > Kasper Sørensen
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> 
> > For additional commands, e-mail: general-h...@incubator.apache.org
> 
> >
> >
>

Re: [VOTE] Release Apache Metamodel incubating 4.2.0

[Henry Saputra]

Thanks for the review Justin

On Sunday, July 27, 2014, Justin Mclean  wrote:

> Hi,
>
> +1 binding
>
> - release artefact has incubating in the name
> - signatures and hashes correct
> - has DISCLAIMER
> - LICENCE and NOTICE good
> - all source files have correct header
> - no binaries in source release (except for tests)
> - can compile from source
> - tests pass
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> 
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
>
>

Re: [VOTE] Release Apache Metamodel incubating 4.2.0

[Henry Saputra]

Thx for the review John!

On Sunday, July 27, 2014, John D. Ament  wrote:

> +1 (binding)  Release looks good to me.
>
>
> On Sun, Jul 27, 2014 at 11:55 AM, Kasper Sørensen <
> kasper.soren...@humaninference.com > wrote:
>
> > Hi All,
> >
> > Please vote on releasing the following artifacts as Apache MetaModel
> > version 4.2.0-incubating.
> > This will be the third incubator release for Metamodel in Apache.
> >
> > The Git tag to be voted on is v4.2.0-incubating:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.2.0-incubating
> >
> > The source artifact to be voted on is:
> >
> >
> http://repository.apache.org/content/repositories/orgapachemetamodel-1001/org/apache/metamodel/MetaModel/4.2.0-incubating/MetaModel-4.2.0-incubating-source-release.zip
> >
> > Parent directory (including MD5, SHA1 hashes etc.) of the source is:
> >
> https://repository.apache.org/content/repositories/orgapachemetamodel-1001/org/apache/metamodel/MetaModel/4.2.0-incubating/
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/kaspersor.asc
> >
> > Release engineer public key id: 1FE1C2F5
> >
> > Vote thread link from d...@metamodel.incubator.apache.org 
> mailing list:
> > http://markmail.org/thread/wmvcudxe6yhijzxb
> >
> > Result thread link from d...@metamodel.incubator.apache.org
>  mailing list:
> > http://markmail.org/message/bikigx33epufc76i
> >
> > Please vote on releasing this package as Apache MetaModel
> 4.2.0-incubating.
> >
> > The vote is open for 72 hours, or until we get the needed number of votes
> > (3 +1).
> >
> > [ ] +1 Release this package as Apache MetaModel 4.2.0-incubating
> > [ ] -1 Do not release this package because ...
> >
> > More information about the MetaModel project can be found at
> > http://metamodel.incubator.apache.org/
> >
> > Thank you in advance for participating.
> >
> > Regards,
> > Kasper Sørensen
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> 
> > For additional commands, e-mail: general-h...@incubator.apache.org
> 
> >
> >
>

Re: [VOTE] Release Apache Metamodel incubating 4.2.0

[Henry Saputra]

Forward my vote from dev@ list:

+1 (binding)

- Henry

On Sun, Jul 27, 2014 at 8:55 AM, Kasper Sørensen
 wrote:
> Hi All,
>
> Please vote on releasing the following artifacts as Apache MetaModel version 
> 4.2.0-incubating.
> This will be the third incubator release for Metamodel in Apache.
>
> The Git tag to be voted on is v4.2.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.2.0-incubating
>
> The source artifact to be voted on is:
> http://repository.apache.org/content/repositories/orgapachemetamodel-1001/org/apache/metamodel/MetaModel/4.2.0-incubating/MetaModel-4.2.0-incubating-source-release.zip
>
> Parent directory (including MD5, SHA1 hashes etc.) of the source is: 
> https://repository.apache.org/content/repositories/orgapachemetamodel-1001/org/apache/metamodel/MetaModel/4.2.0-incubating/
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/kaspersor.asc
>
> Release engineer public key id: 1FE1C2F5
>
> Vote thread link from d...@metamodel.incubator.apache.org mailing list:
> http://markmail.org/thread/wmvcudxe6yhijzxb
>
> Result thread link from d...@metamodel.incubator.apache.org mailing list:
> http://markmail.org/message/bikigx33epufc76i
>
> Please vote on releasing this package as Apache MetaModel 4.2.0-incubating.
>
> The vote is open for 72 hours, or until we get the needed number of votes (3 
> +1).
>
> [ ] +1 Release this package as Apache MetaModel 4.2.0-incubating
> [ ] -1 Do not release this package because ...
>
> More information about the MetaModel project can be found at 
> http://metamodel.incubator.apache.org/
>
> Thank you in advance for participating.
>
> Regards,
> Kasper Sørensen
> -
> 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: Podling binding votes

[Henry Saputra]

Touché :)

On Friday, July 25, 2014, Tim Williams  wrote:

> On Fri, Jul 25, 2014 at 12:33 PM, Henry Saputra  > wrote:
> > This is conflicting from what the site said about governance of podling.
> > PPMC is a part of podling and responsible to manage the podling on behalf
> > of IPMC.
> >
> > I suppose you meant that their votes do not bind but saying it was never
> > part of the structure is misleading or we need to update the ASF website
> > about incubator roles page.
>
> The conflicting bit is how you two are resolving the pronoun "our" in
> Ross' statement below the PPMC is not a formal part of the ASF's
> formal structure the PPMC is a formal part of the IPMC's internal
> organization.
>
> --tim
>
> > On Friday, July 25, 2014, Ross Gardler  > wrote:
> >
> >> The PPMC is not, and never has been, a formally recognized part of our
> >> structure. But as I said that's a technicality in this context, the
> project
> >> (PPMC) are the people who really matter from the projects perspective,
> even
> >> though their votes are not binding.
> >>
> >> The thread seems to be in agreement in response to Justin's specific
> >> question.
> >>
> >> On 25 Jul 2014 01:20, "John D. Ament"  
> >> > wrote:
> >> >
> >> > Ross,
> >> >
> >> > The incubator website would be inclined to disagree, and seems to
> >> > acknowledge there is formally a PPMC at [1].
> >> >
> >> > Justin,
> >> >
> >> > I think formally, if you review [2] (you may also want to scroll down,
> >> and
> >> > review later parts of this page on voting), you'll see that the PPMC
> >> votes
> >> > really don't count for anything other than merit.  The IPMC vote is
> what
> >> > really counts.  If you follow that page verbatim, the votes by the
> IPMC
> >> are
> >> > the only ones that count.
> >> >
> >> > If you follow the alternative voting method, found at [3], you'll see
> >> that
> >> > votes via PPMC are acceptable if and only if the IPMC has agreed to
> such.
> >> >
> >> >
> >> > [1]: http://incubator.apache.org/guides/ppmc.html
> >> > [2]:
> >> >
> >>
> >>
> http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote
> >> > [3]:
> >> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> >> >
> >> >
> >> >
> >> > On Thu, Jul 24, 2014 at 7:48 PM, Ross Gardler <
> >> rgard...@opendirective.com  >
> >> > wrote:
> >> >
> >> > > There is no formal PPMC. When a podling is created all initial
> >> committers
> >> > > are equal. I guess some podlings might create the concept of a
> separate
> >> > > PPMC during incubation. I've never advised that in my own podlings
> >> > > (probably because I'm a believer in an absolute minimum barrier to
> >> entry).
> >> > > I guess it's up to individual projects and mentors just as our top
> >> level
> >> > > projects can decide if the PMC is the whole set or a subset of the
> >> > > committers
> >> > > On 25 Jul 2014 00:33, "Justin Mclean"  
> >> > wrote:
> >> > >
> >> > > > Hi,
> >> > > >
> >> > > > > As a mentor I've (nearly) always advised that if there are three
> >> IPMC
> >> > > > votes on the dev list then there is no need to make further noise
> on
> >> the
> >> > > > general list with unnecessary +1's. I therefore point out in the
> >> general@
> >> > > > vote mail that 3 binding (IPMC) +1's have been received and
> therefore
> >> > > there
> >> > > > is only a need to vote if there is an objection.
> >> > > > Fair enough + seem reasonable to me.
> >> > > >
> >> > > > > TECHNICALITY: PPMC votes are not binding (although they
> absolutely
> >> > > > should be considered as such by the project). Only IPMC votes are
> >> > > > considered binding at the foundational level since PPMC members
> are
> >> not
> >> > > yet
> >> > > > a member of a formal committee.
> >> > > > You need 3 +1 votes first on the podlings dev list, and PPMC
> votes do
> >> > > > count there, we wouldn't see a lot of podling releases otherwise.
> :-)
> >> > > Does
> >> > > > that mean any +1 vote (say by a committer or user) on the dev list
> >> also
> >> > > > counts if PPMC votes aren't actually considered binding? (I'd
> assume
> >> not
> >> > > > but again it's not clear from the document).
> >> > > >
> >> > > > 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: Podling binding votes

[Henry Saputra]

This is conflicting from what the site said about governance of podling.
PPMC is a part of podling and responsible to manage the podling on behalf
of IPMC.

I suppose you meant that their votes do not bind but saying it was never
part of the structure is misleading or we need to update the ASF website
about incubator roles page.

On Friday, July 25, 2014, Ross Gardler  wrote:

> The PPMC is not, and never has been, a formally recognized part of our
> structure. But as I said that's a technicality in this context, the project
> (PPMC) are the people who really matter from the projects perspective, even
> though their votes are not binding.
>
> The thread seems to be in agreement in response to Justin's specific
> question.
>
> On 25 Jul 2014 01:20, "John D. Ament"  > wrote:
> >
> > Ross,
> >
> > The incubator website would be inclined to disagree, and seems to
> > acknowledge there is formally a PPMC at [1].
> >
> > Justin,
> >
> > I think formally, if you review [2] (you may also want to scroll down,
> and
> > review later parts of this page on voting), you'll see that the PPMC
> votes
> > really don't count for anything other than merit.  The IPMC vote is what
> > really counts.  If you follow that page verbatim, the votes by the IPMC
> are
> > the only ones that count.
> >
> > If you follow the alternative voting method, found at [3], you'll see
> that
> > votes via PPMC are acceptable if and only if the IPMC has agreed to such.
> >
> >
> > [1]: http://incubator.apache.org/guides/ppmc.html
> > [2]:
> >
>
> http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote
> > [3]:
> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> >
> >
> >
> > On Thu, Jul 24, 2014 at 7:48 PM, Ross Gardler <
> rgard...@opendirective.com >
> > wrote:
> >
> > > There is no formal PPMC. When a podling is created all initial
> committers
> > > are equal. I guess some podlings might create the concept of a separate
> > > PPMC during incubation. I've never advised that in my own podlings
> > > (probably because I'm a believer in an absolute minimum barrier to
> entry).
> > > I guess it's up to individual projects and mentors just as our top
> level
> > > projects can decide if the PMC is the whole set or a subset of the
> > > committers
> > > On 25 Jul 2014 00:33, "Justin Mclean"  > wrote:
> > >
> > > > Hi,
> > > >
> > > > > As a mentor I've (nearly) always advised that if there are three
> IPMC
> > > > votes on the dev list then there is no need to make further noise on
> the
> > > > general list with unnecessary +1's. I therefore point out in the
> general@
> > > > vote mail that 3 binding (IPMC) +1's have been received and therefore
> > > there
> > > > is only a need to vote if there is an objection.
> > > > Fair enough + seem reasonable to me.
> > > >
> > > > > TECHNICALITY: PPMC votes are not binding (although they absolutely
> > > > should be considered as such by the project). Only IPMC votes are
> > > > considered binding at the foundational level since PPMC members are
> not
> > > yet
> > > > a member of a formal committee.
> > > > You need 3 +1 votes first on the podlings dev list, and PPMC votes do
> > > > count there, we wouldn't see a lot of podling releases otherwise. :-)
> > > Does
> > > > that mean any +1 vote (say by a committer or user) on the dev list
> also
> > > > counts if PPMC votes aren't actually considered binding? (I'd assume
> not
> > > > but again it's not clear from the document).
> > > >
> > > > Thanks,
> > > > Justin
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> 
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> 
> > > >
> > > >
> > >
>

Re: Podling binding votes

[Henry Saputra]

Yes, this is what I had seen and recommended to podlings I have been
involved with.


- Henry

On Thu, Jul 24, 2014 at 8:44 PM, P. Taylor Goetz  wrote:
> My interpretation (and it's just that) is:
>
> Example: Release Vote
>
> A podling votes to release (VOTE email to dev@project). The PPMC and 
> IPMC/PPMC (i.e. Mentors) member votes are binding at the PPMC level. This 
> means that those votes are binding and community votes are non-binding.
>
> If the PPMC vote passes, the release vote can proceed to the IPMC level (a 
> VOTE email to general@). At this point, PPMC votes are non-binding. Mentor 
> (since mentors are by definition IPMC members) and any non-mentor IPMC member 
> votes can carry over and are binding. Then it's a matter of getting enough 
> additional binding IPMC votes to meet the requirement. At this point, PPMC 
> and community votes are non-binding.
>
> Again, this is just my interpretation, and I may be off here.
>
> -Taylor
>
>> On Jul 24, 2014, at 6:57 PM, Justin Mclean  wrote:
>>
>> Hi,
>>
>> Anyone clarify this as it's not mentioned at [1].
>>
>> Whose votes are binding for releases on the podlings dev list? Obviously 
>> mentors and PPMC members, but are IPMC members votes binding? I would assume 
>> so but don't see it stated anywhere. Would Apache members votes be binding?
>>
>> Assuming IPMC votes are binding what happen if a podling release dev list 
>> vote got 3 +1 IPMC votes, would a voted need to done on general @ incubator 
>> or not?
>>
>> Thanks,
>> Justin
>>
>> 1.http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
>> -
>> 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] Argus as a new incubator project

[Henry Saputra]

+1 (binding)

Good luck guys, thanks for adding more diversity among mentors to help
ease up the concerns raised before.

- Henry

On Mon, Jul 21, 2014 at 9:03 AM, Owen O'Malley  wrote:
> Following the discussion earlier, I'm calling a vote to accept Argus as a
> new Incubator project.
>
>  The proposal draft is available at:
> https://wiki.apache.org/incubator/ArgusProposal, and is also included
>  below.
>
>  Vote is open for 72h and closes at 24 July 2014 at 10am PST.
>
>  [ ] +1 accept Argus in the Incubator
>  [ ] +/-0
>  [ ] -1 because...
>
> I'm +1.
>
> .. Owen

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

Re: [PROPOSAL] Apache Argus Proposal

[Henry Saputra]

Hi Owen,

Thanks for details explanation about the statement. Really appreciate
the clarification.

- Henry

On Wed, Jul 16, 2014 at 2:46 PM, Owen O'Malley  wrote:
> On Wed, Jul 16, 2014 at 11:29 AM, Henry Saputra 
> wrote:
>
>> HI,
>>
>> Just curious if you could give reference to "Apache encourages
>> disjoint teams to form independent projects, even when those projects
>> overlap in scope" statement ?
>>
>
> Henry,
> It generally comes from the "Community over Code," which is a phrase
> discussing how the focus is on how the people working on a project work
> together and not the code. The assumption is teams with healthy communities
> will build good code.
>
> In terms of documentation, it like most of Apache is learned by doing. In
> Nick Burch's talk "The Apache Way" at ApacheCon this year (
> http://events.linuxfoundation.org/sites/events/files/slides/TheApacheWay14.pdf)
> there was a slide about this:
>
> Don't pick winners, pick runners
> • Board doesn't say “We want X”
> • Developers say “X is cool”
> • We enable developers to do cool stuff
> • Apache developers are at the forefront of innovation
> • Not interested in a single runner
> • We want relay teams
> • Community is critical to the Apache Way
> • Apache is about supporting communities
>
> .. Owen
>
>
>> - Henry
>>
>> On Mon, Jul 14, 2014 at 7:16 PM, Selvamohan Neethiraj
>>  wrote:
>> > Apache Argus Proposal (http://wiki.apache.org/incubator/ArgusProposal)
>> >
>> > == Abstract ==
>> >
>> > Argus is a framework to enable, monitor and manage comprehensive data
>> security across the Hadoop platform.
>> >
>> > The name “Argus” is derived from Argus Panoptes, a 100-eyed giant in
>> Greek mythology, endowed with a role to keep “an eye” open and be an
>> effective watchman at all times.
>> >
>> > == Background ==
>> >
>> > The vision with Argus is to provide comprehensive security across the
>> Apache Hadoop ecosystem. With the advent of  Apache YARN, the Hadoop
>> platform can now support a true data lake architecture. Enterprises can
>> potentially run multiple workloads, in a multi tenant environment. Data
>> security within Hadoop needs to evolve to support multiple use cases for
>> data access, while also providing a framework for central administration of
>> security policies and monitoring of user access.
>> >
>> > XA Secure, a Hadoop security focused startup, developed the initial
>> technology behind Argus. XA Secure was acquired by Hortonworks, which now
>> is contributing the technology to the open source community to extend and
>> innovate.
>> >
>> > == Rationale ==
>> >
>> > Many of the projects in the Hadoop ecosystem have their own
>> authentication, authorization, and auditing components. There are no
>> central administration and auditing capabilities. We are looking to address
>> these enterprises security needs of central administration and
>> comprehensive security through the Argus project.
>> > Our initial focus would be around authorization and auditing, the longer
>> term vision would be to tie all aspects around data security within the
>> Hadoop platform.
>> >
>> > == Proposal Details ==
>> >
>> > The vision of Argus is to enable comprehensive data security across the
>> Hadoop platform. The goal is provide a single user interface or API to
>> manage security policies, monitor user access and policy changes history.
>> The framework would work with individual components in enforcing these
>> policies and in capturing relevant audit information.
>> > Initial Goals
>> > 1.  Donate the Argus source code and documentation to the
>> Apache Software Foundation
>> > 2.  Setup and standardize the open governance of the Argus
>> project
>> > 3.  Build a user and developer community
>> > 4.  Deeper Integration with Hadoop Platform
>> > a.  Enable integration with Apache Storm, Apache
>> Knox and Apache Falcon for authorization and auditing
>> > 5.  Configurable centralized storage of audit data into HDFS
>> > 6.  Enable framework to be run in both Linux and Windows
>> environments
>> > 7.  Rationalize install procedure, making it easier for
>> enterprises to deploy
>> >
>> > == Longer Term Goals ==
>> >
>> > In longer term, Argus should provide a comprehen

Re: [PROPOSAL] Apache Argus Proposal

[Henry Saputra]

> understand them correctly. I encourage you to address concerns raised on
> this thread about the complexion of the initial PMC and mentorships. There
> have been a few suggestions worth exploring.
>

+1 to Andrew's comment.

Let us be real for a moment, when all PPMCs including mentors and
committers are from same organizations, especially with project
related to security, what or who could provide sanity check when a
"competitor" contributor trying to contribute patch or someday be
active committer if all decision makers (PPMCs) are paid developers
from one commercial company?

In a happy perfect world, all individuals will put aside their
corporate hats when working with open source code, especially with
neutral org like ASF or Eclipse, but that is actually true.
Most of them would try to defend their employers "rights" to direct
the project to the vision that they want it to be.
The idea of having different orgs representing as initial team is
exactly to prevent this situation.

When I tried to champion the Apache MetaModel as incubator project I
did my homework to "solicit" mentors from different orgs to make sure
it is well represented.
I saw similar things with Apache Spark, and Brooklyn projects.

- Henry



>> Similar discussion can be made between no-sql projects like Apache HBase,
> Apache Accumulo and Apache Cassandra.
>
> Not similar at all. This isn't about choice, this is about trust. Security
> and trust are wedded inseparably.
>
>
>
> On Thu, Jul 17, 2014 at 1:03 PM, Don Bosco Durai 
> wrote:
>
>> Andrews, thanks for your feedback. My responses are inline.
>>
>> Regards
>>
>> Bosco
>>
>> On Jul 17, 2014, at 11:41 AM, Andrew Purtell  wrote:
>>
>> > Thank you for writing back with a detailed clarification.
>> >
>> > Regarding encryption at rest, HDFS is adding it as HDFS-6134, so likely
>> > there will be a new core feature option for the ecosystem to consider
>> > shortly.
>> >
>> > > I don’t feel one technology or one company or one small group or one
>> > approach can solve this problem. This has to be addressed by the
>> community
>> > working together. This would also require a lot of support from each
>> > dependent projects and lot of co-ordination. And there would be multiple
>> > security solutions available for the end users to pick from.
>> >
>> > Completely agreed. However, the desired community cooperation has both
>> > technical and political components. I think there are some concerns about
>> > how successful an outcome Argus may produce, informed by experience.
>> > Perhaps it would be worthwhile to address those concerns. Argus proposes
>> to
>>
>> The current Argus solution already has integration with the core Hadoop
>> components like HDFS, Hive and HBase. There are work in progress to support
>> additional Hadoop components, which includes Knox. Anytime, we cross
>> project boundaries, there were would be always challenges wrt technical and
>> political. Working this out within the community makes more sense, rather
>> than doing this outside. Not attempting would be counterproductive.
>>
>> > develop a common security infrastructure for the Hadoop ecosystem. In my
>> > opinion (and informed by personal experience) we have new incubating
>> Hadoop
>> > ecosystem security projects like Sentry and Knox and proposals such as
>> > Argus because Hadoop core is locked down. Argus et. al. are like the
>> > proverbial blocked river (user demand for features) seeking a new route
>> > around a landslide (obvious poisonous contention and litigation-via-JIRA
>> on
>> > every significant topic). I would be curious your thoughts on how to
>> avoid
>> > the same end state in the Argus project. In my opinion, it would be a
>> > tragedy if a potential solution ends up perpetuating the dysfunction it
>> > seeks to bypass to a greater proportion of Foundation projects instead. A
>> > Hadoop ecosystem project attempting to remain independent from the
>> > dysfunction of Hadoop core would be well advised to stay away from
>> adoption
>> > of Argus components (security is so critical) if the governance of Argus
>> I don’t believe Argus existence is because HDFS or any other component is
>> locked down or dysfunctional. Each component will continue to evolve  (core
>> features and security) overtime based on their priority, severity and
>> timeline. The option to externalize security is always a good thing. Option
>> to externalize is a well accepted notion in the community. Commercial
>> databases allow externalizing security, web applications externalize
>> authentication and authorization, there are vulnerability management
>> systems for file system/software version, etc. I don’t see a security
>> provider like Argus or Sentry extending the native security as a risk or
>> bad thing, instead, a good motivation for projects (particularly new) to
>> focus on their core features.
>>
>> I also don’t feel this is a short term user demand. Security requirement
>> changes on regular basis and as

Re: [PROPOSAL] Apache Argus Proposal

[Henry Saputra]

Definitely +1, active members, with lack diversity, are more useful.

My original comment was to suggest having mentors come from different
organizations so hopefully could help provide different perspectives
and inputs to the podling.
Never my intention to suggest false diversity to start an Apache
incubator project.

- Henry


On Wed, Jul 16, 2014 at 9:15 AM, Ted Dunning  wrote:
> On Wed, Jul 16, 2014 at 1:20 AM, Chris Douglas  wrote:
>
>> > So, I am fond of Henry's hope that the project will solicit a more
>> diversified
>> > set of mentors and initial committers.
>>
>> The committer and PPMC list should be honest. If there is no
>> diversity, that fact must be visible for it to be tracked.
>>
>> Initial committers are a dodge that demonstrates nothing about the
>> project's willingness to not only accept, but attract new ideas. The
>> viability of an OSS project is not inaccurately *defined* as its
>> ability to compete for that attention. Demanding pro forma adherence
>> to heuristics is a harmful lesson to podlings, unless the goal is to
>> teach them to evade accountability. -C
>
>
> +1 to this.
>
> Sham committers are more of a pain than lack of diversity, as much as I
> dislike sock-puppet projects.

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

Re: [PROPOSAL] Apache Argus Proposal

[Henry Saputra]

HI,

Just curious if you could give reference to "Apache encourages
disjoint teams to form independent projects, even when those projects
overlap in scope" statement ?

- Henry

On Mon, Jul 14, 2014 at 7:16 PM, Selvamohan Neethiraj
 wrote:
> Apache Argus Proposal (http://wiki.apache.org/incubator/ArgusProposal)
>
> == Abstract ==
>
> Argus is a framework to enable, monitor and manage comprehensive data 
> security across the Hadoop platform.
>
> The name “Argus” is derived from Argus Panoptes, a 100-eyed giant in Greek 
> mythology, endowed with a role to keep “an eye” open and be an effective 
> watchman at all times.
>
> == Background ==
>
> The vision with Argus is to provide comprehensive security across the Apache 
> Hadoop ecosystem. With the advent of  Apache YARN, the Hadoop platform can 
> now support a true data lake architecture. Enterprises can potentially run 
> multiple workloads, in a multi tenant environment. Data security within 
> Hadoop needs to evolve to support multiple use cases for data access, while 
> also providing a framework for central administration of security policies 
> and monitoring of user access.
>
> XA Secure, a Hadoop security focused startup, developed the initial 
> technology behind Argus. XA Secure was acquired by Hortonworks, which now is 
> contributing the technology to the open source community to extend and 
> innovate.
>
> == Rationale ==
>
> Many of the projects in the Hadoop ecosystem have their own authentication, 
> authorization, and auditing components. There are no central administration 
> and auditing capabilities. We are looking to address these enterprises 
> security needs of central administration and comprehensive security through 
> the Argus project.
> Our initial focus would be around authorization and auditing, the longer term 
> vision would be to tie all aspects around data security within the Hadoop 
> platform.
>
> == Proposal Details ==
>
> The vision of Argus is to enable comprehensive data security across the 
> Hadoop platform. The goal is provide a single user interface or API to manage 
> security policies, monitor user access and policy changes history. The 
> framework would work with individual components in enforcing these policies 
> and in capturing relevant audit information.
> Initial Goals
> 1.  Donate the Argus source code and documentation to the Apache 
> Software Foundation
> 2.  Setup and standardize the open governance of the Argus project
> 3.  Build a user and developer community
> 4.  Deeper Integration with Hadoop Platform
> a.  Enable integration with Apache Storm, Apache Knox and 
> Apache Falcon for authorization and auditing
> 5.  Configurable centralized storage of audit data into HDFS
> 6.  Enable framework to be run in both Linux and Windows 
> environments
> 7.  Rationalize install procedure, making it easier for 
> enterprises to deploy
>
> == Longer Term Goals ==
>
> In longer term, Argus should provide a comprehensive security framework for 
> Hadoop platform components, covering the following
> 1.  Centralized security administration to manage all security 
> related tasks in a central UI
> 2.  Fine grained authorization to do a specific action and/or 
> operation with Hadoop component/tool and managed through a central 
> administration tool
> a.  Standardize authorization method across all Hadoop 
> components
> b.  Enhanced support for different authorization methods 
> - Role based access control, attribute based access control etc
> c.  Enable tag based global policies
> 3.  Centralize auditing of user access and administrative actions 
> (security related) within all the components of Hadoop
>
> == Current Status ==
>
> Argus’ technology is currently being used by enterprises and is under active 
> development.
>
> The key components of Argus are:
> •   Enterprise Security Administration Portal
> ◦   A Java Web Application, designed for administration 
> of security policies from a single location for the entire hadoop cluster 
> (and even multiple hadoop clusters)
> •   Security Agents
> ◦   A light-weight Java Agent, which will be embedded 
> into the hadoop component (e.g. Hive, HBase and Hadoop) as an authorization 
> provider to enforce the security policies and also collect access events/logs.
> •   User/Group Synchronizer Module
> ◦   A standalone daemon which allows the user/group 
> information to be synched from the enterprise user repositories like LDAP/AD 
> to Argus local database. This user/group information in Argus local database 
> will help the security policy administrators
> ▪   to define security policies by  selecting 
> users/groups from a drop-down box 

Re: [PROPOSAL] Apache Argus Proposal

[Henry Saputra]

Hi Andrew, thanks for chiming in =)

I like your and Owen's opinion about initial members of an incubator project.
And also agree it is responsibility of the polling to achieve better
diversity during its time under Apache incubator.

For this particular proposal, however, the mentors mostly coming from
same organization.
Hopefully with this proposal announcement, the project could "solicit"
mentors from different organizations to help add check and balance.

- Henry

On Tue, Jul 15, 2014 at 2:22 PM, Andrew Purtell  wrote:
> I had started typing up a response to Henry's mail but will discard the
> beginning of it to say I agree with Owen. A new project coming into the
> incubator quite naturally could have the initial set of committers entirely
> from one organization. An organization donating an existing code base, for
> example.
>
> However, there has been recent discussion elsewhere that the Incubator
> should more closely consider if an incubating project has succeeded to grow
> a community beyond the initially limited group before declaring a project
> ready for graduation. (Refer to the discussion on the graduation of Apache
> Tez.) This position seems reasonable, and should naturally apply here. If a
> project exits graduation with the same lack of PMC/committer diversity with
> which it entered, this is in effect Apache-washing, in my opinion. A
> stacked PMC is no more open a community then one controlled by a BDFL and
> hosted on GitHub.
>
>
>
> On Tue, Jul 15, 2014 at 2:14 PM, Owen O'Malley  wrote:
>
>> On Tue, Jul 15, 2014 at 1:59 PM, Henry Saputra 
>> wrote:
>>
>> > Maybe we should start asking incubator project to try to build some
>> > kind of momentum or community before going to ASF incubator.
>> >
>>
>> Apache incubator is a great place for new projects to grow their community
>> and diversity. Once a project is established it is much harder to change
>> the infrastructure and there projects started on github are more likely to
>> stay on github. I think there is significant value in these projects being
>> done in the Apache Way.
>>
>>
>> >
>> > All but one PPMC members for this proposal would be from Hortonworks.
>> >
>>
>> Would you like to volunteer to help mentor?
>>
>>
>> > Just from high level it seems like it has similar goal as Apache Knox
>> > [1], what is the differences between the 2?
>> >
>>
>> I think Knox and Argus complement each other. Knox provides perimeter
>> security via proxy/gateway services, while Argus is providing fine grain
>> integrated authorization and auditing.
>>
>> .. Owen
>>
>
>
>
> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)

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

Re: [PROPOSAL] Apache Argus Proposal

[Henry Saputra]

Owen, thanks for the reply.

If possible I would like to have mentors coming from different
organizations to add some check and balance to the podling.
I think most of the incubator projects that have initial members from
one organization have diverse mentors from different organizations to
help provide more balance opinions and directions.

Unfortunately my plate is a bit full right now so I will have to pass
on mentoring the proposed project. Thanks for asking though =)

- Henry

On Tue, Jul 15, 2014 at 2:14 PM, Owen O'Malley  wrote:
> On Tue, Jul 15, 2014 at 1:59 PM, Henry Saputra 
> wrote:
>
>> Maybe we should start asking incubator project to try to build some
>> kind of momentum or community before going to ASF incubator.
>>
>
> Apache incubator is a great place for new projects to grow their community
> and diversity. Once a project is established it is much harder to change
> the infrastructure and there projects started on github are more likely to
> stay on github. I think there is significant value in these projects being
> done in the Apache Way.
>
>
>>
>> All but one PPMC members for this proposal would be from Hortonworks.
>>
>
> Would you like to volunteer to help mentor?
>
>
>> Just from high level it seems like it has similar goal as Apache Knox
>> [1], what is the differences between the 2?
>>
>
> I think Knox and Argus complement each other. Knox provides perimeter
> security via proxy/gateway services, while Argus is providing fine grain
> integrated authorization and auditing.
>
> .. Owen

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

Re: [PROPOSAL] Apache Argus Proposal

[Henry Saputra]

Maybe we should start asking incubator project to try to build some
kind of momentum or community before going to ASF incubator.

All but one PPMC members for this proposal would be from Hortonworks.
Personally I think this basically like hosting your project under
Hortonwork Github account.

I personally would like to have it open via Github to see if could
build more external contributors rather than shove it directly to
incubator directly.

Just from high level it seems like it has similar goal as Apache Knox
[1], what is the differences between the 2?

Thanks,

- Henry


[1] http://knox.apache.org

On Mon, Jul 14, 2014 at 7:16 PM, Selvamohan Neethiraj
 wrote:
> Apache Argus Proposal (http://wiki.apache.org/incubator/ArgusProposal)
>
> == Abstract ==
>
> Argus is a framework to enable, monitor and manage comprehensive data 
> security across the Hadoop platform.
>
> The name “Argus” is derived from Argus Panoptes, a 100-eyed giant in Greek 
> mythology, endowed with a role to keep “an eye” open and be an effective 
> watchman at all times.
>
> == Background ==
>
> The vision with Argus is to provide comprehensive security across the Apache 
> Hadoop ecosystem. With the advent of  Apache YARN, the Hadoop platform can 
> now support a true data lake architecture. Enterprises can potentially run 
> multiple workloads, in a multi tenant environment. Data security within 
> Hadoop needs to evolve to support multiple use cases for data access, while 
> also providing a framework for central administration of security policies 
> and monitoring of user access.
>
> XA Secure, a Hadoop security focused startup, developed the initial 
> technology behind Argus. XA Secure was acquired by Hortonworks, which now is 
> contributing the technology to the open source community to extend and 
> innovate.
>
> == Rationale ==
>
> Many of the projects in the Hadoop ecosystem have their own authentication, 
> authorization, and auditing components. There are no central administration 
> and auditing capabilities. We are looking to address these enterprises 
> security needs of central administration and comprehensive security through 
> the Argus project.
> Our initial focus would be around authorization and auditing, the longer term 
> vision would be to tie all aspects around data security within the Hadoop 
> platform.
>
> == Proposal Details ==
>
> The vision of Argus is to enable comprehensive data security across the 
> Hadoop platform. The goal is provide a single user interface or API to manage 
> security policies, monitor user access and policy changes history. The 
> framework would work with individual components in enforcing these policies 
> and in capturing relevant audit information.
> Initial Goals
> 1.  Donate the Argus source code and documentation to the Apache 
> Software Foundation
> 2.  Setup and standardize the open governance of the Argus project
> 3.  Build a user and developer community
> 4.  Deeper Integration with Hadoop Platform
> a.  Enable integration with Apache Storm, Apache Knox and 
> Apache Falcon for authorization and auditing
> 5.  Configurable centralized storage of audit data into HDFS
> 6.  Enable framework to be run in both Linux and Windows 
> environments
> 7.  Rationalize install procedure, making it easier for 
> enterprises to deploy
>
> == Longer Term Goals ==
>
> In longer term, Argus should provide a comprehensive security framework for 
> Hadoop platform components, covering the following
> 1.  Centralized security administration to manage all security 
> related tasks in a central UI
> 2.  Fine grained authorization to do a specific action and/or 
> operation with Hadoop component/tool and managed through a central 
> administration tool
> a.  Standardize authorization method across all Hadoop 
> components
> b.  Enhanced support for different authorization methods 
> - Role based access control, attribute based access control etc
> c.  Enable tag based global policies
> 3.  Centralize auditing of user access and administrative actions 
> (security related) within all the components of Hadoop
>
> == Current Status ==
>
> Argus’ technology is currently being used by enterprises and is under active 
> development.
>
> The key components of Argus are:
> •   Enterprise Security Administration Portal
> ◦   A Java Web Application, designed for administration 
> of security policies from a single location for the entire hadoop cluster 
> (and even multiple hadoop clusters)
> •   Security Agents
> ◦   A light-weight Java Agent, which will be embedded 
> into the hadoop component (e.g. Hive, HBase and Hadoop) as an authorization 
> provider to enforce the security policies and also collect access events/logs.
> • 

Re: [VOTE] Graduate Apache Tez from Apache Incubator to TLP

[Henry Saputra]

+1

Great job and hopefully see you guys as TLP soon =)

- Henry

On Mon, Jun 30, 2014 at 9:16 PM, Hitesh Shah  wrote:
> Hello folks
>
> Tez entered incubation in February, 2013. Since then, we have made progress 
> towards graduation[1]. The Tez community recently voted positively towards 
> graduation[2] with 27 +1s.
> Of the 27, there were 5 IPMC votes from our mentors:
> - Alan Gates
> - Arun C. Murthy
> - Chris Mattman
> - Chris Douglas
> - Jakob Homan
>
> Now, I would like to ask the IPMC to vote for the graduation of Apache Tez.
>
> Please VOTE to indicate if Apache Tez is ready to graduate as a Top Level 
> Project. The board resolution is included below.
>
> [ ] +1 Graduate Apache Tez as a TLP
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Tez as a TLP because…
>
> The vote will remain open for 72 hours.
>
> thanks
> — Hitesh Shah ( on behalf of Tez PPMC )
>
> [1] 
> http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3ccfc4fef8.16337a%25chris.a.mattm...@jpl.nasa.gov%3E
> [2] 
> http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3ccaoapips7pjs_6hinkwk0uv0hnnrydqcg639dpf9vojeuto9...@mail.gmail.com%3E
>
> Board Resolution:
> --
> X. Establish the Apache Tez 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 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 Tez Project", be
> and hereby is established pursuant to Bylaws of the Foundation;
> and be it further
>
> RESOLVED, that the Apache Tez 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 Tez" 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 Tez Project, and to have primary responsibility for
> management of the projects within the scope of responsibility
> of the Apache Tez 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 Tez Project:
>
>  * Alan Gates 
>  * Arun C. Murthy 
>  * Ashutosh Chauhan 
>  * Bill Graham 
>  * Bikas Saha 
>  * Chris Douglas 
>  * Chris Mattmann 
>  * Daryn Sharp 
>  * Devaraj Das 
>  * Gopal Vijayaraghavan 
>  * Gunther Hagleitner 
>  * Hitesh Shah 
>  * Jitendra Pandey 
>  * Jason Lowe 
>  * Jakob Homan 
>  * Julien Le Dem 
>  * Kevin Wilfong 
>  * Mike Liddell 
>  * Mohammad Kamrul Islam 
>  * Namit Jain 
>  * Nathan Roberts 
>  * Owen O’Malley 
>  * Rajesh Balamohan 
>  * Robert Evans 
>  * Rohini Palaniswamy 
>  * Siddharth Seth 
>  * Tassapol Athiapinya 
>  * Thomas Graves 
>  * Tom White 
>  * Vikram Dixit 
>  * Vinod Kumar Vavilapalli 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hitesh Shah be
> appointed to the office of Vice President, Apache Tez, 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 Tez Project be and hereby is
> tasked with the migration and rationalization of the Apache
> Incubator Tez podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Tez 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 Tez-0.4.1-incubating RC0

[Henry Saputra]

Thanks Siddharth!

On Fri, Jun 27, 2014 at 1:28 PM, Siddharth Seth  wrote:
> OK. I'm going to cancel this vote, and restart it on the Tez dev list.
>
>
> On Fri, Jun 27, 2014 at 12:21 PM, Henry Saputra 
> wrote:
>
>> It is encouraged to run the VOTE within dev@ list first to let PPMC
>> verify the release and to make sure it is working.
>> Mentors can help verify the release artifacts before going to general@
>> list for final approval from IPMCs.
>>
>> This will help IPMCs to catch small details that may have been missed
>> from the community.
>>
>> - Henry
>>
>>
>> On Fri, Jun 27, 2014 at 11:45 AM, Siddharth Seth  wrote:
>> > In the past, we haven't run a separate release vote for the Tez PPMC. A
>> > single vote has been used, on which the Tez PPMC also votes (although
>> > non-binding), and this has worked out well.
>> > There was a mail thread on the Tez dev list requesting feedback for this
>> > release -
>> >
>> http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3CCAOapipu-JZ=Tz24UiMfy=Cb44Asy+=7+vm+ljiihiozfovt...@mail.gmail.com%3E
>> >
>> > Things you may want to consider fixing or changing in a future release
>> >> - add "apache' to file name
>> >> - Remove KEYS from inside source artefact - you need it before running
>> >> un-tar/gzip.
>> >
>> > Will keep these in mind for the next release.
>> >
>> > Thanks for taking a look
>> > - Sid
>> >
>> >
>> > On Thu, Jun 26, 2014 at 9:33 PM, Justin Mclean > >
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> Has this release been voted upon by the PPMC? I can't see any votes or
>> >> vote result thread here:
>> >>
>> >>
>> http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/thread
>> >>
>> >> Otherwise everything is good.
>> >>
>> >> I checked:
>> >> - file name included incubating
>> >> - DISCLAIMER exists
>> >> - NOTICE and LICENSE are good
>> >> - no binary files in source release
>> >> - all source files have correct header
>> >> - can compile from source
>> >> - tests pass
>> >>
>> >> Things you may want to consider fixing or changing in a future release
>> >> - add "apache' to file name
>> >> - Remove KEYS from inside source artefact - you need it before running
>> >> un-tar/gzip.
>> >>
>> >> Thanks,
>> >> Justin
>> >> -
>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>
>> >>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

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

Re: [VOTE] Release Apache Tez-0.4.1-incubating RC0

[Henry Saputra]

It is encouraged to run the VOTE within dev@ list first to let PPMC
verify the release and to make sure it is working.
Mentors can help verify the release artifacts before going to general@
list for final approval from IPMCs.

This will help IPMCs to catch small details that may have been missed
from the community.

- Henry


On Fri, Jun 27, 2014 at 11:45 AM, Siddharth Seth  wrote:
> In the past, we haven't run a separate release vote for the Tez PPMC. A
> single vote has been used, on which the Tez PPMC also votes (although
> non-binding), and this has worked out well.
> There was a mail thread on the Tez dev list requesting feedback for this
> release -
> http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3CCAOapipu-JZ=Tz24UiMfy=Cb44Asy+=7+vm+ljiihiozfovt...@mail.gmail.com%3E
>
> Things you may want to consider fixing or changing in a future release
>> - add "apache' to file name
>> - Remove KEYS from inside source artefact - you need it before running
>> un-tar/gzip.
>
> Will keep these in mind for the next release.
>
> Thanks for taking a look
> - Sid
>
>
> On Thu, Jun 26, 2014 at 9:33 PM, Justin Mclean 
> wrote:
>
>> Hi,
>>
>> Has this release been voted upon by the PPMC? I can't see any votes or
>> vote result thread here:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/thread
>>
>> Otherwise everything is good.
>>
>> I checked:
>> - file name included incubating
>> - DISCLAIMER exists
>> - NOTICE and LICENSE are good
>> - no binary files in source release
>> - all source files have correct header
>> - can compile from source
>> - tests pass
>>
>> Things you may want to consider fixing or changing in a future release
>> - add "apache' to file name
>> - Remove KEYS from inside source artefact - you need it before running
>> un-tar/gzip.
>>
>> 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: We need two more IPMC votes (was Re: [VOTE] Release of Apache MRQL 0.9.2 incubating (RC2))

[Henry Saputra]

The mentors of the podling should be IPMCs and their votes are
binding. I recommend to solicit VOTEs from them to get the release
through.

- Henry

On Wed, Jun 25, 2014 at 12:42 AM, Leonidas Fegaras  wrote:
> Hello,
> It has been 5 days since we opened this vote for our second MRQL
> release. We have collected one IPMC vote (from Alan Cabrera) and we
> still need two more IPMC votes to approve the release.
> It would be greatly appreciated If someone could take a look
> at our release and vote on releasing Apache MRQL 0.9.2 incubating.
> Thank you
> Leonidas Fegaras
>
> On 06/20/2014 09:54 AM, Leonidas Fegaras wrote:
>>
>> Hello,
>> This is a call for a vote on Apache MRQL 0.9.2 incubating.
>> Apache MRQL is a query processing and optimization system for
>> large-scale, distributed data analysis, built on top of Apache Hadoop,
>> Apache Hama, and Apache Spark. This is our second release.
>> A vote was held on the MRQL developer mailing list and it passed with
>> four +1 PPMC votes, no -1 votes, and no 0 votes (see the vote thread
>> [1] and result thread [2]), and now requires a vote on this list.
>> The vote will be open for at least 72 hours and passes if a majority
>> of at least three +1 IPMC votes are cast.
>>
>> [ ] +1 Release this package as Apache MRQL 0.9.2-incubating
>> [ ] -1 Do not release this package because ...
>>
>> The release tarballs, including signatures, digests, etc can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/mrql/0.9.2-incubating-RC2/
>> The release candidate consists of the following source distribution
>> archives:
>> - mrql-dist-0.9.2-incubating-src.[tar.gz|zip]
>> SHA1 of TGZ: 9209 735B CAE2 D431 71BE  EB6F 985B 07F7 B0A3 E4A6
>> SHA1 of ZIP: 180F 0CE1 D09E 9B21 A08F  1BED 495E 8BB2 6486 CAF9
>> You can compile the sources using 'mvn clean install'.
>> In addition, the following supplementary binary distributions are
>> provided for user convenience at the same location:
>> - mrql-dist-0.9.2-incubating-bin.[tar.gz|zip]
>> SHA1 of TGZ: AC77 F97F 0C3C FACA C312  8C68 50B5 5474 DBFE 93C1
>> SHA1 of ZIP: F552 021C 2FF0 7343 5098  C16B 18B8 1AF8 9820 9675
>>
>> A staged Maven repository is available for review at:
>> https://repository.apache.org/content/repositories/orgapachemrql-1001/
>>
>> The release candidate has been signed through the key 798764F1 in:
>> http://www.apache.org/dist/incubator/mrql/KEYS
>>
>> The release candidate is based on the sources tagged with
>> MRQL-0.9.2-incubating-RC2 at:
>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=commit;h=f80a1e6fcb1e2a31063e568508ada3d9ef3466e3
>>
>> The list of fixed issues:
>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=blob_plain;f=RELEASE_NOTES;hb=f80a1e6fcb1e2a31063e568508ada3d9ef3466e3
>>
>> To learn more about Apache MRQL, please visit:
>> http://wiki.apache.org/mrql/
>> Thanks,
>> Leonidas Fegaras
>>
>> [1] http://markmail.org/message/eiqz44qovjy6f6sl
>> [2] http://markmail.org/message/eo3d64jx24v6oir2
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>> .
>>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Graduate Apache Celix as Top Level Project

[Henry Saputra]

Exercising my right to Vote ^_^  :

+0 (binding)

This seems like very small but active community but from my experience
as TLP a bit more active and diverse people to be successful.

- Henry

On Thu, Jun 19, 2014 at 7:26 AM, Alexander Broekhuis
 wrote:
> Hi All,
>
> Since entering Incubation in November 2010, the Celix podling been working
> towards graduation. The community has grown, releases have been made and
> new committers have been added.
> Over the last couple of months all items on the checklist for graduation
> have been ticked of [1].
> This resulted in a, positive, vote on te dev list of Celix itself [2]. Also
> the namesearch has been performed [3].
> As far as we can tell the project status is up to date [4], and Celix is
> ready for graduation.
>
> After the discussion in the [DISCUSS] thread on [5], some changes were made
> to the PMC list to have enough members for binding votes etc.
>
> Now I'd like to ask the IPMC to vote for the graduation of Celix.
>
> Please cast your vote:
>
> [ ] +1 Graduate the Apache Celix podling from Apache Incubator as a TLP
> [ ] +0 Indifferent to the graduation status of Apache Celix podling
> [ ] -1 Reject graduation of Apache Celix podling from Apache Incubator
> because ...
>
> The vote will be open for 72 hours, after which I will tally and post the
> results.
>
> Thanks in advance,
>
> Alexander Broekhuis
> (PPMC member of Apache Celix)
>
> [1]: http://incubator.apache.org/guides/graduation.html#checklist
> [2]: http://markmail.org/thread/7y3a2l6qqm56cvud
> [3]: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-50
> [4]: http://incubator.apache.org/projects/celix.html
> [5]: http://markmail.org/thread/7udzxyd7ey2nyqsr
>
> 
> X. Establish the Apache Celix 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 native implementation of the OSGi
>specification.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache Celix Project",
>be and hereby is established pursuant to Bylaws of the
>Foundation; and be it further
>
>RESOLVED, that the Apache Celix Project be and hereby is
>responsible for the creation and maintenance of software
>related to a native implementation of the OSGi
>specification;
>and be it further
>
>RESOLVED, that the office of "Vice President, Apache Celix" 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 Celix Project, and to have primary responsibility
>for management of the projects within the scope of
>responsibility of the Apache Celix 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 Celix Project:
>
>  * Alexander Broekhuis   
>  * Pepijn Noltes  
>  * Bjoern Petri
>  * Erik Jansman 
>  * Marcel Offermans   
>  * Roman Shaposhnik 
>  * Konstantin Boudnik 
>
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alexander Broekhuis
>be appointed to the office of Vice President, Apache Celix, 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 Celix 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 Celix Project; and be it further
>
>RESOLVED, that the Apache Celix Project be and hereby
>is tasked with the migration and rationalization of the Apache
>Incubator Celix podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache
>Incubator Celix podling encumbered upon the Apache Incubator
>Project are hereafter discharged.
>
> --
> Met vriendelijke groet,
>
> Alexander Broekhuis

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

Re: Tez graduation [Was: Request for mentor assessment]

[Henry Saputra]

Looks like the page is not updated because the proposal mentions more
diverse people [1]

[1] http://wiki.apache.org/incubator/TezProposal

On Fri, Jun 20, 2014 at 8:02 PM, Konstantin Boudnik  wrote:
> Ok, I've reached out to the Tez project and it seems that they are wokring w/
> Chris Mattmann's on the graduation process (per an email exchange
> http://s.apache.org/K7g). What has caught my attention is the PPMC composition
> which is pretty much uniformly represented by a group with the same
> affiliation. Given that this page 
> https://tez.incubator.apache.org/team-list.html
> is up to date.
>
> If I am reading https://incubator.apache.org/guides/graduation.html#community
> right, the PPMC and committers composition should be diversified. Is it a
> concern for graduation from the IPMC standpoint of view?
>
> Regards,
>   Cos
>
> On Mon, Jun 16, 2014 at 06:54PM, Chris Douglas wrote:
>> Tez is ready to graduate. Cos, if you can help us manage that process,
>> it'd certainly be appreciated. -C
>>
>> On Mon, Jun 16, 2014 at 12:53 PM, Konstantin Boudnik  wrote:
>> > I share the sentiment with NPanday - doesn't seem like anything is 
>> > happening
>> > there really.
>> >
>> > If it of an interest to the incubator, I will volunteer to help mentoring 
>> > Tez.
>> >
>> > Cos
>> >
>> >
>> > On Fri, Jun 13, 2014 at 12:55AM, Mattmann, Chris A (3980) wrote:
>> >> I think Tez needs some more help mentoring. I myself haven't had
>> >> as much time as possible so the more folks over there that can
>> >> help mentor the better.
>> >>
>> >> Good job starting this thread, Roman.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> -Original Message-
>> >> From: Roman Shaposhnik 
>> >> Reply-To: "general@incubator.apache.org" 
>> >> Date: Thursday, June 12, 2014 5:44 PM
>> >> To: "general@incubator.apache.org" 
>> >> Subject: Re: Request for mentor assessment
>> >>
>> >> >On Wed, Jun 11, 2014 at 5:47 PM, Henry Saputra 
>> >> >wrote:
>> >> >> Seems like NPanday should go to attic. One mentor I asked did not even
>> >> >> monitor it anymore
>> >> >
>> >> >I've had exactly the same experience. My plan here is to wait for folks
>> >> >to chime in on this thread and for those mentors who are MiA start
>> >> >different threads asking for additional (replacement) mentors.
>> >> >
>> >> >I really would like for things like retirement proposals to come from
>> >> >somebody who's spent time getting to know the community in greater
>> >> >details.
>> >> >
>> >> >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
>> >>
>> >
>> > -
>> > 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: Request for mentor assessment

[Henry Saputra]

Seems like NPanday should go to attic. One mentor I asked did not even
monitor it anymore

On Wednesday, June 11, 2014, Roman Shaposhnik  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
> 
>
>

Re: Call for Report Manager for June

[Henry Saputra]

Thanks for all the hard work John!

- Henry

On Sun, Jun 1, 2014 at 5:31 AM, John D. Ament  wrote:
> All,
>
> I'd like to up the ante on Roman's proposal.  After doing this job
> last month, I'd like to propose to split the responsibilities with
> someone for this month:
>
> - Report Manager is responsible for getting the incubator stuff
> together.  Legal, releases, new members, etc.
> - Shepherd Manager is responsible for keeping all the shepherds
> together and formatting any of their reports.
>
> Either side, and probably both, would need to help any podlings with
> getting their reports together.
>
> If anyone's interested in taking on some of the work, let us know.
>
> John
>
> On Sat, May 31, 2014 at 10:12 AM, Roman Shaposhnik  wrote:
>> Hi!
>>
>> John has been doing a splendid work helping out
>> as a report manager. I really hope he can help along
>> a few more times. That said, if there's anybody else
>> who would want to through his or her hat in the ring
>> and help out with the report -- please let us know by
>> Monday.
>>
>> 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
>

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

Re: Board Report Reminder

[Henry Saputra]

Cos, I will follow up with the post graduation steps that Tajo missed

On Sunday, June 8, 2014, Konstantin Boudnik  wrote:

> Interesting, looks like I got to shepherd a graduated project ;) Henry,
> let me
> know if you need any help with clearing out the situation.
>
> Regards,
>   Cos
>
> On Sat, Jun 07, 2014 at 10:36AM, Henry Saputra wrote:
> > Hi John,
> >
> > Tajo already graduated to TLP.
> >
> > Does the project miss some post graduation task to be removed from
> > reporting schedule?
> >
> > Thanks,
> >
> > Henry
> >
> > On Saturday, June 7, 2014, John D. Ament  > wrote:
> >
> > > Hi all
> > >
> > > Don't forget, board reports were due on June 04.  Shepherd reports are
> > > due tomorrow.
> > >
> > > The following podlings are considered to not have reported this month,
> > > thus far:
> > >
> > > Brooklyn
> > > DeviceMap
> > > Drill
> > > Kalumet
> > > MRQL
> > > S4
> > > Sentry
> > > Tajo
> > >
> > > John
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> 
> > > 
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> 
> > > 
> > >
> > >
>

Re: Board Report Reminder

[Henry Saputra]

Hi John,

Tajo already graduated to TLP.

Does the project miss some post graduation task to be removed from
reporting schedule?

Thanks,

Henry

On Saturday, June 7, 2014, John D. Ament  wrote:

> Hi all
>
> Don't forget, board reports were due on June 04.  Shepherd reports are
> due tomorrow.
>
> The following podlings are considered to not have reported this month,
> thus far:
>
> Brooklyn
> DeviceMap
> Drill
> Kalumet
> MRQL
> S4
> Sentry
> Tajo
>
> John
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> 
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
>
>

Re: [VOTE] fleece as new incubator project

[Henry Saputra]

+1

Good luck guys!

On Fri, Jun 6, 2014 at 12:31 AM, Romain Manni-Bucau
 wrote:
> Following the discussion earlier, I'm calling a vote to accept Fleece as a
> new Incubator project.
>
>  The proposal draft is available at:
> https://wiki.apache.org/incubator/Fleece, and is also included  below.
>
>  Vote is open for at least 72h and closes at the earliest on 09 June 09:30
>  GMT.
>
>  [ ] +1 accept Fleece in the Incubator
>  [ ] +/-0
>  [ ] -1 because...
>
>  Here's my +1.
>
> 
> Apache Fleece Proposal
>
> Abstract
>
> Apache Fleece is an implementation of JSR-353 (JavaTM API for JSON
> Processing).
>
> Proposal
>
> Apache Fleece will consist of a number of modules. Mainly an implementation
> of JSR-353 but also a set of usefule modules to help with the usage of
> JSR-353 (surely a mapping module and a jaxrs provider module).
>
> Background
>
> JSon being more and more important JavaEE 7 specified an API to read and
> create JSon objects/arrays.
>
> Apache Fleece builds on this specification a potential base to do Json at
> Apache (hopefully it will be integrated with CXF for instance).
>
> Rationale
>
> There is not yet a Json related project at Apache but a lot of projects
> rely on some specific implementions (jettison, jackson, others...).
> Proposing a default would be great. The other point is a set of Apache
> projects related to JavaEE (CXF, TomEE, Geronimo, Axis2...) will need an
> implementation. Having one built at Apache is a really nice to have.
>
> Initial Goals
>
> The initial goal of the Apache Fleece project is to get a JSR-353 compliant
> implementation
>
> Current Status
>
> Initial codebase was developped on github but designed to be integrated in
> Apache.
>
> Meritocracy
>
> Initial community will be mainly composed of already Apache committers so
> meritocracy is already something well known.
>
> Community
>
> Initial community will be composed of TomEE community for sure, hopefully
> CXF and potentially all JSon users of Apache.
>
> Initial committers
>
>- Romain Manni-Bucau (individual, ASF)
>- Jean-Louis Monteiro (individual, ASF)
>- Mark Struberg (individual, ASF member)
>- Gerhard Petracek (individual, ASF member)
>- David Blevins (individual, ASF member)
>- Sagara Gunathunga (ASF)
>
> Alignment
>
> Several Apache project will need a JSR-353 implementation. Having a project
> which can be shared is better than having a sub project of a particular
> project. Moreover this project makes sense "alone" since users can
> integrate it without any other dependencies and use it to read/generate
> Json in their project so it makes sense to create a dedicated project.
>
> Known Risks
>
> Main risk is to get a not so active project since the specification is not
> that big.
>
> Documentation
>
> There is no documentation to import today but it will be created using
> standard ASF tools (ASF CMS mainly).
>
> Initial Source
>
> Initial sources are on this git repository:
> https://github.com/rmannibucau/json-impl.git
>
> Source and IP Submission Plan
>
> Initial sources are under Apache license v2.
>
> Side note: it was really developed to be integrated in this project
> (without waiting it to be created).
>
> Required Resources
>
> Mailing Lists
>
>-
>
>- d...@fleece.incubator.apache.org - comm...@fleece.incubator.apache.org
>- priv...@fleece.incubator.apache.org
>
> Version Control
>
> It is proposed that the source code for the Apache Fleece project be hosted
> in the Apache Git repository, under the following directory:
>
>- git.apache.org/incubator-fleece.git
>
> Issue Tracking
>
> The following JIRA project would be required to track issues for the Apache
> Fleece project:
>
>- FLEECE
>
> Initial Committers
>
>- Romain Manni-Bucau
>- Jean-Louis Monteiro
>- Mark Struberg
>- Gerhard Petracek
>- David Blevins
>
> Sponsors
>
> Champion
>
>- Mark Struberg
>
> Nominated Mentors
>
>- Justin Mclean
>- Christian Grobmeier
>- Daniel Kulp
>
> Project Name
>
> Seems *Fleece* is the name which satisfies most of people but we can still
> ask for a new name if we feel it needed before being graduated.
> 
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau

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

Re: [VOTE] Apache Slider 0.30-incubating RC0

[Henry Saputra]

Hi Sumit,

Could you kindly send the link to the VOTE result thread from the dev list?

And also since you are not in Incubator PMC your vote is not binding
for the release.

- Henry

On Wed, May 28, 2014 at 11:37 AM, Sumit Mohanty
 wrote:
> Hello folks,
>
> This is a call for a vote on Apache Slider 0.30 incubating release.
>
> A vote was held on the developer mailing list and it passed with 5 +1s.
>
> http://mail-archives.apache.org/mod_mbox/slider-dev/201405.mbox/%3CCABCXrRSzL9f1D%2BWD7__ULT9ZOyV6wr-vFPfKRJgsWrUPpuZw7Q%40mail.gmail.com%3E
>
> Here's a summary of what's new in Slider 0.30:
> * Slider application registry that allow registration and discovery of
> application
>configuration and URLs (such as jmx endpoints and management UI) for
> client consumption.
> * Move to a .zip packaging for Slider application packages.
> * Richer metadata support for start/install ordering and arbitrary
> templates that can
>   be published after application activation.
> * Dynamic port allocation and registration
> * Updated application definition packages for HBase, Accumulo, and Storm.
>
> Git source tag:
> https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;a=shortlog;h=refs/tags/release-0.30-rc0
>
> Staging site:
> http://people.apache.org/~smohanty/slider-release-0.30-rc0/
>
> PGP release keys (signed using 791FDAB0)
> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0xECFC8276791FDAB0
>
> One can look into the issues fixed in this release at:
> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20%22Slider%200.30%22%20AND%20Status%20%3D%20Resolved
>
> Note that this is a source only release and we are voting on the source.
>
> Vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Here's my vote to start: +1 (binding)
>
> thanks
> Sumit
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

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

Re: [VOTE] Accept Parquet into the incubator

[Henry Saputra]

Hi Chris, could you re-send the tally up VOTE result with subject
prefixed with [RESULT] ?


- Henry

On Wed, May 21, 2014 at 3:56 PM, Chris Aniszczyk  wrote:
> With 18 +1 votes (and 10+ as binding votes), I'll consider this vote a
> success.
>
> I'll proceed with the next steps.
>
> Thank you!
>
>
>
> On Sun, May 18, 2014 at 3:57 PM, Todd Lipcon  wrote:
>
>> +1 from me (the proposed Champion)
>>
>> -Todd
>>
>>
>> On Sun, May 18, 2014 at 2:15 PM, Chris Aniszczyk > >wrote:
>>
>> > Based on the results of the discussion thread:
>> >
>> >
>> http://mail-archives.apache.org/mod_mbox/incubator-general/201405.mbox/%3CCAJg1wMRGhLu4P7LeVQB%2B5K0C-fr-pw2448uj%3D6-3zHag4F1EbA%40mail.gmail.com%3E
>> >
>> > I would like to call a vote on accepting Parquet into the incubator.
>> > https://wiki.apache.org/incubator/ParquetProposal
>> >
>> > [ ] +1 Accept Parquet into the Incubator
>> > [ ] +0 Indifferent to the acceptance of Parquet
>> > [ ] -1 Do not accept Parquet because ...
>> >
>> > The vote will be open until Thursday May 22nd 18:00 UTC.
>> >
>> > = Parquet Proposal =
>> >
>> > == Abstract ==
>> > Parquet is a columnar storage format for Hadoop.
>> >
>> > == Proposal ==
>> >
>> > We created Parquet to make the advantages of compressed, efficient
>> columnar
>> > data representation available to any project in the Hadoop ecosystem,
>> > regardless of the choice of data processing framework, data model, or
>> > programming language.
>> >
>> > == Background ==
>> >
>> > Parquet is built from the ground up with complex nested data structures
>> in
>> > mind, and uses the repetition/definition level approach to encoding such
>> > data structures, as popularized by Google Dremel (
>> > https://blog.twitter.com/2013/dremel-made-simple-with-parquet). We
>> believe
>> > this approach is superior to simple flattening of nested name spaces.
>> >
>> > Parquet is built to support very efficient compression and encoding
>> > schemes. Parquet allows compression schemes to be specified on a
>> per-column
>> > level, and is future-proofed to allow adding more encodings as they are
>> > invented and implemented. We separate the concepts of encoding and
>> > compression, allowing parquet consumers to implement operators that work
>> > directly on encoded data without paying decompression and decoding
>> penalty
>> > when possible.
>> >
>> > == Rationale ==
>> >
>> > Parquet is built to be used by anyone. We believe that an efficient,
>> > well-implemented columnar storage substrate should be useful to all
>> > frameworks without the cost of extensive and difficult to set up
>> > dependencies.
>> >
>> > Furthermore, the rapid growth of Parquet community is empowered by open
>> > source. We believe the Apache foundation is a great fit as the long-term
>> > home for Parquet, as it provides an established process for
>> > community-driven development and decision making by consensus. This is
>> > exactly the model we want for future Parquet development.
>> >
>> > == Initial Goals ==
>> >
>> >  * Move the existing codebase to Apache
>> >  * Integrate with the Apache development process
>> >  * Ensure all dependencies are compliant with Apache License version 2.0
>> >  * Incremental development and releases per Apache guidelines
>> >
>> > == Current Status ==
>> >
>> > Parquet has undergone 2 major releases:
>> > https://github.com/Parquet/parquet-format/releases of the core format
>> and
>> > 22 releases: https://github.com/Parquet/parquet-mr/releases of the
>> > supporting set of Java libraries.
>> >
>> > The Parquet source is currently hosted at GitHub, which will seed the
>> > Apache git repository.
>> >
>> > === Meritocracy ===
>> >
>> > We plan to invest in supporting a meritocracy. We will discuss the
>> > requirements in an open forum. Several companies have already expressed
>> > interest in this project, and we intend to invite additional developers
>> to
>> > participate. We will encourage and monitor community participation so
>> that
>> > privileges can be extended to those that contribute.
>> >
>> > === Community ===
>> >
>> > There is a large need for an advanced columnar storage format for Hadoop.
>> > Parquet is being used in production by many organizations (see
>> > https://github.com/Parquet/parquet-mr/blob/master/PoweredBy.md)
>> >
>> >  * Cloudera: https://twitter.com/HenryR/statuses/324222874011451392
>> >  * Criteo: https://twitter.com/julsimon/statuses/312114074911666177
>> >  * Salesforce:
>> https://twitter.com/TwitterOSS/statuses/392734610116726784
>> >  * Stripe: https://twitter.com/avibryant/statuses/391339949250715648
>> >  * Twitter: https://twitter.com/J_/statuses/315844725611581441
>> >
>> > By bringing Parquet into Apache, we believe that the community will grow
>> > even bigger.
>> >
>> > === Core Developers ===
>> >
>> > Parquet was initially developed as a collaboration between Twitter,
>> > Cloudera and Criteo.
>> >
>> > See
>> >
>> >
>> https://blog.twitter.com/2013/announcing-parquet-10-columnar-st

Re: [VOTE] Accept Parquet into the incubator

[Henry Saputra]

+1 binding

On Sunday, May 18, 2014, Chris Aniszczyk  wrote:

> Based on the results of the discussion thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201405.mbox/%3CCAJg1wMRGhLu4P7LeVQB%2B5K0C-fr-pw2448uj%3D6-3zHag4F1EbA%40mail.gmail.com%3E
>
> I would like to call a vote on accepting Parquet into the incubator.
> https://wiki.apache.org/incubator/ParquetProposal
>
> [ ] +1 Accept Parquet into the Incubator
> [ ] +0 Indifferent to the acceptance of Parquet
> [ ] -1 Do not accept Parquet because ...
>
> The vote will be open until Thursday May 22nd 18:00 UTC.
>
> = Parquet Proposal =
>
> == Abstract ==
> Parquet is a columnar storage format for Hadoop.
>
> == Proposal ==
>
> We created Parquet to make the advantages of compressed, efficient columnar
> data representation available to any project in the Hadoop ecosystem,
> regardless of the choice of data processing framework, data model, or
> programming language.
>
> == Background ==
>
> Parquet is built from the ground up with complex nested data structures in
> mind, and uses the repetition/definition level approach to encoding such
> data structures, as popularized by Google Dremel (
> https://blog.twitter.com/2013/dremel-made-simple-with-parquet). We believe
> this approach is superior to simple flattening of nested name spaces.
>
> Parquet is built to support very efficient compression and encoding
> schemes. Parquet allows compression schemes to be specified on a per-column
> level, and is future-proofed to allow adding more encodings as they are
> invented and implemented. We separate the concepts of encoding and
> compression, allowing parquet consumers to implement operators that work
> directly on encoded data without paying decompression and decoding penalty
> when possible.
>
> == Rationale ==
>
> Parquet is built to be used by anyone. We believe that an efficient,
> well-implemented columnar storage substrate should be useful to all
> frameworks without the cost of extensive and difficult to set up
> dependencies.
>
> Furthermore, the rapid growth of Parquet community is empowered by open
> source. We believe the Apache foundation is a great fit as the long-term
> home for Parquet, as it provides an established process for
> community-driven development and decision making by consensus. This is
> exactly the model we want for future Parquet development.
>
> == Initial Goals ==
>
>  * Move the existing codebase to Apache
>  * Integrate with the Apache development process
>  * Ensure all dependencies are compliant with Apache License version 2.0
>  * Incremental development and releases per Apache guidelines
>
> == Current Status ==
>
> Parquet has undergone 2 major releases:
> https://github.com/Parquet/parquet-format/releases of the core format and
> 22 releases: https://github.com/Parquet/parquet-mr/releases of the
> supporting set of Java libraries.
>
> The Parquet source is currently hosted at GitHub, which will seed the
> Apache git repository.
>
> === Meritocracy ===
>
> We plan to invest in supporting a meritocracy. We will discuss the
> requirements in an open forum. Several companies have already expressed
> interest in this project, and we intend to invite additional developers to
> participate. We will encourage and monitor community participation so that
> privileges can be extended to those that contribute.
>
> === Community ===
>
> There is a large need for an advanced columnar storage format for Hadoop.
> Parquet is being used in production by many organizations (see
> https://github.com/Parquet/parquet-mr/blob/master/PoweredBy.md)
>
>  * Cloudera: https://twitter.com/HenryR/statuses/324222874011451392
>  * Criteo: https://twitter.com/julsimon/statuses/312114074911666177
>  * Salesforce: https://twitter.com/TwitterOSS/statuses/392734610116726784
>  * Stripe: https://twitter.com/avibryant/statuses/391339949250715648
>  * Twitter: https://twitter.com/J_/statuses/315844725611581441
>
> By bringing Parquet into Apache, we believe that the community will grow
> even bigger.
>
> === Core Developers ===
>
> Parquet was initially developed as a collaboration between Twitter,
> Cloudera and Criteo.
>
> See
>
> https://blog.twitter.com/2013/announcing-parquet-10-columnar-storage-for-hadoop
>
> === Alignment ===
>
> We believe that having Parquet at Apache will help further the growth of
> the big-data community, as it will encourage cooperation within the greater
> ecosystem of projects spawned by Apache Hadoop. The alignment is also
> beneficial to other Apache communities (such as Hadoop, Hive, Avro).
>
> == Known Risks ==
>
> === Orphaned Products ===
>
> The risk of the Parquet project being abandoned is minimal. There are many
> organizations using Parquet in production, including Twitter, Cloudera,
> Stripe, and Salesforce (
> http://blog.cloudera.com/blog/2013/10/parquet-at-salesforce-com/).
>
> === Inexperience with Open Source ===
>
> Parquet has existed as a healthy open source for one year. During that
> 

Re: [PROPOSAL] Parquet

[Henry Saputra]

Cool, thanks! Looking forward for the VOTE thread :)

On Saturday, May 17, 2014, Chris Aniszczyk  wrote:

> Your request about the user list seems fine, no need to have multiple lists
> atm IMHO.
>
> The proposal has been updated accordingly, thanks!
> https://wiki.apache.org/incubator/ParquetProposal?action=recall&rev=21
>
>
>
> On Sat, May 17, 2014 at 9:33 AM, Henry Saputra 
> 
> >wrote:
>
> > Chris, could you please address my concern about user@ list
> >
> > - Henry
> >
> > On Fri, May 16, 2014 at 4:43 PM, Chris Aniszczyk 
> > wrote:
> > > SGTM Roman, thanks for volunteering!
> > >
> > > I'll start the vote on Sunday barring any issues.
> > >
> > >
> > > On Fri, May 16, 2014 at 11:56 AM, Roman Shaposhnik 
> > wrote:
> > >
> > >> Hi!
> > >>
> > >> proposal looks good to me and I am very much looking
> > >> for a voting thread.
> > >>
> > >> One small request, since I plan to spend a fair amount
> > >> of time on Parquet anyway, would you guys be ok
> > >> with adding me as an extra mentor so I can help
> > >> with that aspect of the project as well?
> > >>
> > >> Thanks,
> > >> Roman.
> > >>
> > >> P.S. Plus it has an added benefit of increasing diversity
> > >> of affiliations from the get go.
> > >>
> > >> On Mon, May 12, 2014 at 10:02 AM, Chris Aniszczyk <
> caniszc...@gmail.com
> > >
> > >> wrote:
> > >> > We would like to propose Parquet as an Apache Incubator project.
> > >> > https://wiki.apache.org/incubator/ParquetProposal
> > >> >
> > >> > Feel free to comment, we'll go for a vote in a week or two or
> whenever
> > >> > consensus has been reached on the proposal.
> > >> >
> > >> > I've posted posted the text of the proposal below:
> > >> >
> > >> > == Abstract ==
> > >> > Parquet is a columnar storage format for Hadoop.
> > >> >
> > >> > == Proposal ==
> > >> >
> > >> > We created Parquet to make the advantages of compressed, efficient
> > >> columnar
> > >> > data representation available to any project in the Hadoop
> ecosystem,
> > >> > regardless of the choice of data processing framework, data model,
> or
> > >> > programming language.
> > >> >
> > >> > == Background ==
> > >> >
> > >> > Parquet is built from the ground up with complex nested data
> > structures
> > >> in
> > >> > mind, and uses the repetition/definition level approach to encoding
> > such
> > >> > data structures, as popularized by Google Dremel (
> > >> > https://blog.twitter.com/2013/dremel-made-simple-with-parquet). We
> > >> believe
> > >> > this approach is superior to simple flattening of nested name
> spaces.
> > >> >
> > >> > Parquet is built to support very efficient compression and encoding
> > >> > schemes. Parquet allows compression schemes to be specified on a
> > >> per-column
> > >> > level, and is future-proofed to allow adding more encodings as they
> > are
> > >> > invented and implemented. We separate the concepts of encoding and
> > >> > compression, allowing parquet consumers to implement operators that
> > work
> > >> > directly on encoded data without paying decompression and decoding
> > >> penalty
> > >> > when possible.
> > >> >
> > >> > == Rationale ==
> > >> >
> > >> > Parquet is built to be used by anyone. We believe that an efficient,
> > >> > well-implemented columnar storage substrate should be useful to all
> > >> > frameworks without the cost of extensive and difficult to set up
> > >> > dependencies.
> > >> >
> > >> > Furthermore, the rapid growth of Parquet community is empowered by
> > open
> > >> > source. We believe the Apache foundation is a great fit as the
> > long-term
> > >> > home for Parquet, as it provides an established process for
> > >> > community-driven development and decision making by consensus. This
> is
> > >> > exactly the model we want for future Parquet development.
> > >> >
> > >> > == Initial Goa

Re: [PROPOSAL] Parquet

[Henry Saputra]

Chris, could you please address my concern about user@ list

- Henry

On Fri, May 16, 2014 at 4:43 PM, Chris Aniszczyk  wrote:
> SGTM Roman, thanks for volunteering!
>
> I'll start the vote on Sunday barring any issues.
>
>
> On Fri, May 16, 2014 at 11:56 AM, Roman Shaposhnik  wrote:
>
>> Hi!
>>
>> proposal looks good to me and I am very much looking
>> for a voting thread.
>>
>> One small request, since I plan to spend a fair amount
>> of time on Parquet anyway, would you guys be ok
>> with adding me as an extra mentor so I can help
>> with that aspect of the project as well?
>>
>> Thanks,
>> Roman.
>>
>> P.S. Plus it has an added benefit of increasing diversity
>> of affiliations from the get go.
>>
>> On Mon, May 12, 2014 at 10:02 AM, Chris Aniszczyk 
>> wrote:
>> > We would like to propose Parquet as an Apache Incubator project.
>> > https://wiki.apache.org/incubator/ParquetProposal
>> >
>> > Feel free to comment, we'll go for a vote in a week or two or whenever
>> > consensus has been reached on the proposal.
>> >
>> > I've posted posted the text of the proposal below:
>> >
>> > == Abstract ==
>> > Parquet is a columnar storage format for Hadoop.
>> >
>> > == Proposal ==
>> >
>> > We created Parquet to make the advantages of compressed, efficient
>> columnar
>> > data representation available to any project in the Hadoop ecosystem,
>> > regardless of the choice of data processing framework, data model, or
>> > programming language.
>> >
>> > == Background ==
>> >
>> > Parquet is built from the ground up with complex nested data structures
>> in
>> > mind, and uses the repetition/definition level approach to encoding such
>> > data structures, as popularized by Google Dremel (
>> > https://blog.twitter.com/2013/dremel-made-simple-with-parquet). We
>> believe
>> > this approach is superior to simple flattening of nested name spaces.
>> >
>> > Parquet is built to support very efficient compression and encoding
>> > schemes. Parquet allows compression schemes to be specified on a
>> per-column
>> > level, and is future-proofed to allow adding more encodings as they are
>> > invented and implemented. We separate the concepts of encoding and
>> > compression, allowing parquet consumers to implement operators that work
>> > directly on encoded data without paying decompression and decoding
>> penalty
>> > when possible.
>> >
>> > == Rationale ==
>> >
>> > Parquet is built to be used by anyone. We believe that an efficient,
>> > well-implemented columnar storage substrate should be useful to all
>> > frameworks without the cost of extensive and difficult to set up
>> > dependencies.
>> >
>> > Furthermore, the rapid growth of Parquet community is empowered by open
>> > source. We believe the Apache foundation is a great fit as the long-term
>> > home for Parquet, as it provides an established process for
>> > community-driven development and decision making by consensus. This is
>> > exactly the model we want for future Parquet development.
>> >
>> > == Initial Goals ==
>> >
>> > * Move the existing codebase to Apache
>> > * Integrate with the Apache development process
>> > * Ensure all dependencies are compliant with Apache License version 2.0
>> > * Incremental development and releases per Apache guidelines
>> >
>> > == Current Status ==
>> >
>> > Parquet has undergone 2 major releases:
>> > https://github.com/Parquet/parquet-format/releases of the core format
>> and
>> > 22 releases: https://github.com/Parquet/parquet-mr/releases of the
>> > supporting set of Java libraries.
>> >
>> > The Parquet source is currently hosted at GitHub, which will seed the
>> > Apache git repository.
>> >
>> > === Meritocracy ===
>> >
>> > We plan to invest in supporting a meritocracy. We will discuss the
>> > requirements in an open forum. Several companies have already expressed
>> > interest in this project, and we intend to invite additional developers
>> to
>> > participate. We will encourage and monitor community participation so
>> that
>> > privileges can be extended to those that contribute.
>> >
>> > === Community ===
>> >
>> > There is a large need for an advanced columnar storage format for Hadoop.
>> > Parquet is being used in production by many organizations (see
>> > https://github.com/Parquet/parquet-mr/blob/master/PoweredBy.md)
>> >
>> >  * Cloudera: https://twitter.com/HenryR/statuses/324222874011451392
>> >  * Criteo: https://twitter.com/julsimon/statuses/312114074911666177
>> >  * Salesforce:
>> https://twitter.com/TwitterOSS/statuses/392734610116726784
>> >  * Stripe: https://twitter.com/avibryant/statuses/391339949250715648
>> >  * Twitter: https://twitter.com/J_/statuses/315844725611581441
>> >
>> > By bringing Parquet into Apache, we believe that the community will grow
>> > even bigger.
>> >
>> > === Core Developers ===
>> >
>> > Parquet was initially developed as a collaboration between Twitter,
>> > Cloudera and Criteo.
>> >
>> > See
>> >
>> https://blog.twitter.com/2013/announcing-parquet-10-column

Re: Status of NPanday

[Henry Saputra]

I checked with one of the mentors and he claimed he has not been
mentoring the project for a while.

Seems like not much progress happening in the podling.

If any active mentors is still in this list I would propose checking
up with community if they still have energy or desire to continue.

- Henry

On Wed, May 14, 2014 at 5:12 PM, Roman Shaposhnik  wrote:
> Hi!
>
> after observing NPanday for quite a few month I am
> now very concerned about the state of this podling.
> It consistently misses reporting deadlines and even
> when reports arrive they don't seem to be signed
> off by a mentor. On top of that, the development
> activity seems to be quite low.
>
> I'm going to flag these issues to the board, but I'm
> also asking for the collective wisdom of IPMC on
> how to proceed.
>
> 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: [PROPOSAL] Parquet

[Henry Saputra]

Like most new projects coming to incubator I always check on how busy
is the existing user@ list in Parquet right now?

If most questions or concerns are related to development, I would
suggest to remove request for user@ list for now to get the project
focus on moving to ASF development infrastructure.

Other than that, proposal looks good and looking forward for VOTE thread.

Thanks,

Henry

On Wed, May 14, 2014 at 10:40 AM, Jake Farrell  wrote:
> Changed some of the mailing lists requested to match the format currently
> in use. One question I had was do we plan to merge parquet-mr and
> parquet-format into one parquet repo as listed in the proposal or keep them
> separated? Other than that looks good
>
> -Jake
>
>
> On Mon, May 12, 2014 at 1:02 PM, Chris Aniszczyk wrote:
>
>> We would like to propose Parquet as an Apache Incubator project.
>> https://wiki.apache.org/incubator/ParquetProposal
>>
>> Feel free to comment, we'll go for a vote in a week or two or whenever
>> consensus has been reached on the proposal.
>>
>> I've posted posted the text of the proposal below:
>>
>> == Abstract ==
>> Parquet is a columnar storage format for Hadoop.
>>
>> == Proposal ==
>>
>> We created Parquet to make the advantages of compressed, efficient columnar
>> data representation available to any project in the Hadoop ecosystem,
>> regardless of the choice of data processing framework, data model, or
>> programming language.
>>
>> == Background ==
>>
>> Parquet is built from the ground up with complex nested data structures in
>> mind, and uses the repetition/definition level approach to encoding such
>> data structures, as popularized by Google Dremel (
>> https://blog.twitter.com/2013/dremel-made-simple-with-parquet). We believe
>> this approach is superior to simple flattening of nested name spaces.
>>
>> Parquet is built to support very efficient compression and encoding
>> schemes. Parquet allows compression schemes to be specified on a per-column
>> level, and is future-proofed to allow adding more encodings as they are
>> invented and implemented. We separate the concepts of encoding and
>> compression, allowing parquet consumers to implement operators that work
>> directly on encoded data without paying decompression and decoding penalty
>> when possible.
>>
>> == Rationale ==
>>
>> Parquet is built to be used by anyone. We believe that an efficient,
>> well-implemented columnar storage substrate should be useful to all
>> frameworks without the cost of extensive and difficult to set up
>> dependencies.
>>
>> Furthermore, the rapid growth of Parquet community is empowered by open
>> source. We believe the Apache foundation is a great fit as the long-term
>> home for Parquet, as it provides an established process for
>> community-driven development and decision making by consensus. This is
>> exactly the model we want for future Parquet development.
>>
>> == Initial Goals ==
>>
>> * Move the existing codebase to Apache
>> * Integrate with the Apache development process
>> * Ensure all dependencies are compliant with Apache License version 2.0
>> * Incremental development and releases per Apache guidelines
>>
>> == Current Status ==
>>
>> Parquet has undergone 2 major releases:
>> https://github.com/Parquet/parquet-format/releases of the core format and
>> 22 releases: https://github.com/Parquet/parquet-mr/releases of the
>> supporting set of Java libraries.
>>
>> The Parquet source is currently hosted at GitHub, which will seed the
>> Apache git repository.
>>
>> === Meritocracy ===
>>
>> We plan to invest in supporting a meritocracy. We will discuss the
>> requirements in an open forum. Several companies have already expressed
>> interest in this project, and we intend to invite additional developers to
>> participate. We will encourage and monitor community participation so that
>> privileges can be extended to those that contribute.
>>
>> === Community ===
>>
>> There is a large need for an advanced columnar storage format for Hadoop.
>> Parquet is being used in production by many organizations (see
>> https://github.com/Parquet/parquet-mr/blob/master/PoweredBy.md)
>>
>>  * Cloudera: https://twitter.com/HenryR/statuses/324222874011451392
>>  * Criteo: https://twitter.com/julsimon/statuses/312114074911666177
>>  * Salesforce: https://twitter.com/TwitterOSS/statuses/392734610116726784
>>  * Stripe: https://twitter.com/avibryant/statuses/391339949250715648
>>  * Twitter: https://twitter.com/J_/statuses/315844725611581441
>>
>> By bringing Parquet into Apache, we believe that the community will grow
>> even bigger.
>>
>> === Core Developers ===
>>
>> Parquet was initially developed as a collaboration between Twitter,
>> Cloudera and Criteo.
>>
>> See
>>
>> https://blog.twitter.com/2013/announcing-parquet-10-columnar-storage-for-hadoop
>>
>> === Alignment ===
>>
>> We believe that having Parquet at Apache will help further the growth of
>> the big-data community, as it will encourage cooperation within the greate

Re: [PROPOSAL] Optiq

[Henry Saputra]

Yes, thanks updating the proposal. Really appreciate it.

- Henry

On Thu, May 8, 2014 at 11:03 AM, Julian Hyde  wrote:
> The “Relationships with Other Apache Products” section has been updated to 
> cover Optiq’s functional overlaps with existing Apache projects.
>
> https://wiki.apache.org/incubator/OptiqProposal#Relationships_with_Other_Apache_Products
>
> Julian
>
> On May 2, 2014, at 11:23 AM, Henry Saputra  wrote:
>
>> Ah sorry, I did not mean "asking to update", I meant "proposing to update".
>>
>> Thanks,
>>
>> - Henry
>>
>> On Fri, May 2, 2014 at 11:20 AM, Henry Saputra  
>> wrote:
>>> HI Ashutosh,
>>>
>>> Since there was a question/ comment about relationship with Apache
>>> MetaModel, I am asking to update the proposal to include this
>>> discussion in either "Relationships with Other Apache Products" or
>>> "Alignment" section before going for a VOTE.
>>>
>>> Apache Slider did the same thing with relation to Apache Twill and
>>> Apache Helix projects.
>>>
>>> Thanks,
>>>
>>> - Henry
>>>
>>> On Wed, Apr 30, 2014 at 3:21 PM, Ashutosh Chauhan  
>>> wrote:
>>>> I would like to propose Optiq as an Apache Incubator project.  I have
>>>> posted the proposal to https://wiki.apache.org/incubator/OptiqProposal and
>>>> posted the text of the proposal below.
>>>>
>>>> Ashutosh.
>>>>
>>>> = Optiq =
>>>> == Abstract ==
>>>>
>>>> Optiq is a framework that allows efficient translation of queries involving
>>>> heterogeneous and federated data.
>>>>
>>>> == Proposal ==
>>>>
>>>> Optiq is a highly customizable engine for parsing and planning queries on
>>>> data in a wide variety of formats. It allows database-like access, and in
>>>> particular a SQL interface and advanced query optimization, for data not
>>>> residing in a traditional database.
>>>>
>>>> == Background ==
>>>>
>>>> Databases were traditionally engineered in a monolithic stack, providing a
>>>> data storage format, data processing algorithms, query parser, query
>>>> planner, built-in functions, metadata repository and connectivity layer.
>>>> They innovate in some areas but rarely in all.
>>>>
>>>> Modern data management systems are decomposing that stack into separate
>>>> components, separating data, processing engine, metadata, and query
>>>> language support. They are highly heterogeneous, with data in multiple
>>>> locations and formats, caching and redundant data, different workloads, and
>>>> processing occurring in different engines.
>>>>
>>>> Query planning (sometimes called query optimization) has always been a key
>>>> function of a DBMS, because it allows the implementors to introduce new
>>>> query-processing algorithms, and allows data administrators to re-organize
>>>> the data without affecting applications built on that data. In a
>>>> componentized system, the query planner integrates the components (data
>>>> formats, engines, algorithms) without introducing unncessary coupling or
>>>> performance tradeoffs.
>>>>
>>>> But building a query planner is hard; many systems muddle along without a
>>>> planner, and indeed a SQL interface, until the demand from their customers
>>>> is overwhelming.
>>>>
>>>> There is an opportunity to make this process more efficient by creating a
>>>> re-usable framework.
>>>>
>>>> == Rationale ==
>>>>
>>>> Optiq allows database-like access, and in particular a SQL interface and
>>>> advanced query optimization, for data not residing in a traditional
>>>> database. It is complementary to many current Hadoop and NoSQL systems,
>>>> which have innovative and performant storage and runtime systems but lack a
>>>> SQL interface and intelligent query translation.
>>>>
>>>> Optiq is already in use by several projects, including Apache Drill, Apache
>>>> Hive and Cascading Lingual, and commercial products.
>>>>
>>>> Optiq's architecture consists of:
>>>>
>>>> An extensible relational algebra.
>>>> SPIs (service-provider interfaces) for metadata (schemas and tables),
>>>> planner rules, statistics, cos

Re: [VOTE] Accept Optiq into the incubator

[Henry Saputra]

+1 (binding)

Many ASF projects seemed to have dependency on Optiq already, so it is
good idea to bring it into ASF via incubator.


Note that looks like a typo in the VOTE email:

"[ ] +0 Indifferent to the acceptance of Stratosphere" should had been
"[ ] +0 Indifferent to the acceptance of Optiq"


- Henry


On Fri, May 9, 2014 at 11:03 AM, Ashutosh Chauhan  wrote:
> Based on the results of the discussion thread (
> http://mail-archives.apache.org/mod_mbox/incubator-general/201404.mbox/%3CCA%2BFBdFQA4TghLRdh9GgDKaMtKLQHxE_QZV%3DoZ7HfiDSA_jyqwg%40mail.gmail.com%3E
>  ),  I would like to call a vote on accepting Optiq into the incubator.
>
> [ ] +1 Accept Optiq into the Incubator
> [ ] +0 Indifferent to the acceptance of Stratosphere
> [ ] -1 Do not accept Optiq because ...
>
> The vote will be open until Tuesday May 13 18:00 UTC.
>
> https://wiki.apache.org/incubator/OptiqProposal
>
> = Optiq =
> == Abstract ==
>
> Optiq is a framework that allows efficient translation of queries involving
> heterogeneous and federated data.
>
> == Proposal ==
>
> Optiq is a highly customizable engine for parsing and planning queries on
> data in a wide variety of formats. It allows database-like access, and in
> particular a SQL interface and advanced query optimization, for data not
> residing in a traditional database.
>
> == Background ==
>
> Databases were traditionally engineered in a monolithic stack, providing a
> data storage format, data processing algorithms, query parser, query
> planner, built-in functions, metadata repository and connectivity layer.
> They innovate in some areas but rarely in all.
>
> Modern data management systems are decomposing that stack into separate
> components, separating data, processing engine, metadata, and query
> language support. They are highly heterogeneous, with data in multiple
> locations and formats, caching and redundant data, different workloads, and
> processing occurring in different engines.
>
> Query planning (sometimes called query optimization) has always been a key
> function of a DBMS, because it allows the implementors to introduce new
> query-processing algorithms, and allows data administrators to re-organize
> the data without affecting applications built on that data. In a
> componentized system, the query planner integrates the components (data
> formats, engines, algorithms) without introducing unncessary coupling or
> performance tradeoffs.
>
> But building a query planner is hard; many systems muddle along without a
> planner, and indeed a SQL interface, until the demand from their customers
> is overwhelming.
>
> There is an opportunity to make this process more efficient by creating a
> re-usable framework.
>
> == Rationale ==
>
> Optiq allows database-like access, and in particular a SQL interface and
> advanced query optimization, for data not residing in a traditional
> database. It is complementary to many current Hadoop and NoSQL systems,
> which have innovative and performant storage and runtime systems but lack a
> SQL interface and intelligent query translation.
>
> Optiq is already in use by several projects, including Apache Drill, Apache
> Hive and Cascading Lingual, and commercial products.
>
> Optiq's architecture consists of:
>
> An extensible relational algebra.
>  * SPIs (service-provider interfaces) for metadata (schemas and tables),
> planner rules, statistics, cost-estimates, user-defined functions.
>  * Built-in sets of rules for logical transformations and common
> data-sources.
>  * Two query planning engines driven by rules, statistics, etc. One engine
> is cost-based, the other rule-based.
>  * Optional SQL parser, validator and translator to relational algebra.
>  * Optional JDBC driver.
>
> == Initial Goals ==
>
> The initial goals are be to move the existing codebase to Apache and
> integrate with the Apache development process. Once this is accomplished,
> we plan for incremental development and releases that follow the Apache
> guidelines.
>
> As we move the code into the org.apache namespace, we will restructure
> components as necessary to allow clients to use just the components of
> Optiq that they need.
>
> A version 1.0 release, including pre-built binaries, will foster wider
> adoption.
>
> == Current Status ==
>
> Optiq has had over a dozen minor releases over the last 18 months. Its core
> SQL parser and validator, and its planning engine and core rules, are
> mature and robust and are the basis for several production systems; but
> other components and SPIs are still undergoing rapid evolution.
>
> === Meritocracy ===
>
> We plan to invest in supporting a meritocracy. We will discuss the
> requirements in an open forum. We encourage the companies and projects
> using Optiq to discuss their requirements in an open forum and to
> participate in development. We will encourage and monitor community
> participation so that privileges can be extended to those that contribute.
>
> Optiq's pluggable architecture encourag

Re: [VOTE] Release Apache Metamodel incubating 4.1.0-RC1

[Henry Saputra]

Thanks for reviewing the release RC, Justin.

Will open ticket to update year in the Notice file.

- Henry

On Sunday, May 4, 2014, Justin Mclean  wrote:

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

Re: [VOTE] Release Apache Metamodel incubating 4.1.0-RC1

[Henry Saputra]

Awesome, thx Arvind :)

On Saturday, May 3, 2014, Arvind Prabhakar  wrote:

> +1 (binding)
>
> * Signatures and checksums look good
> * Build successfully
> * Rat check looks good
>  * Top level files look good
>
> Regards,
> Arvind Prabhakar
>
>
> On Sat, May 3, 2014 at 9:53 AM, Kasper Sørensen <
> kasper.soren...@humaninference.com > wrote:
>
> > Hi All,
> >
> > Please vote on releasing the following candidate as Apache MetaModel
> > version 4.1.0-RC1-incubating.
> > This will be the second incubator release for Metamodel in Apache.
> >
> > The Git tag to be voted on is v4.1.0-RC1-incubating:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.1.0-RC1-incubating
> >
> > Source zip file can be found here:
> >
> >
> http://repository.apache.org/content/repositories/releases/org/apache/metamodel/MetaModel/4.1.0-RC1-incubating/MetaModel-4.1.0-RC1-incubating-source-release.zip
> > (Note: You may notice that the file(s) are in the 'releases' repository
> > and not in a staging repo. By mistake the staging directory was
> prematurely
> > released in Nexus. This was a mixup in the release procedure by the new
> > Release Engineer (me) - very sorry about that mistake).
> >
> > MD5 hash of the source zip file: ca79678bb109e96e057d5d9e49225088
> > SHA1 hash of the source zip file:
> d3ecb896cf6683fd3245896a830eac6ac6cc9591
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/kaspersor.asc
> >
> > Release engineer public key id: 1FE1C2F5
> >
> > Vote thread link from d...@metamodel.incubator.apache.org 
> > mailing list:
> > http://markmail.org/message/ttthjjl4lpfsghil
> >
> > Result thread link from 
> > d...@metamodel.incubator.apache.orgmailing list:
> > http://markmail.org/message/rxj75uc5h3ump2kw
> >
> > Please vote on releasing this package as Apache MetaModel
> > 4.1.0-RC1-incubating.
> >
> > The vote is open for 72 hours, or until we get the needed number of votes
> > (3 +1).
> >
> > [ ] +1 Release this package as Apache MetaModel 4.1.0-RC1-incubating
> > [ ] -1 Do not release this package because...
> >
> > More information about the MetaModel project can be found at
> > http://metamodel.incubator.apache.org/
> >
> > Thank you in advance for participating.
> >
> > Regards,
> > Kasper Sørensen
> > -
> > To unsubscribe, e-mail: 
> > general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: 
> > general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Apache Metamodel incubating 4.1.0-RC1

[Henry Saputra]

Forward my vote from Metamodel dev list

+1 binding



On Saturday, May 3, 2014, Kasper Sørensen <
kasper.soren...@humaninference.com> wrote:

> Hi All,
>
> Please vote on releasing the following candidate as Apache MetaModel
> version 4.1.0-RC1-incubating.
> This will be the second incubator release for Metamodel in Apache.
>
> The Git tag to be voted on is v4.1.0-RC1-incubating:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.1.0-RC1-incubating
>
> Source zip file can be found here:
>
> http://repository.apache.org/content/repositories/releases/org/apache/metamodel/MetaModel/4.1.0-RC1-incubating/MetaModel-4.1.0-RC1-incubating-source-release.zip
> (Note: You may notice that the file(s) are in the 'releases' repository
> and not in a staging repo. By mistake the staging directory was prematurely
> released in Nexus. This was a mixup in the release procedure by the new
> Release Engineer (me) - very sorry about that mistake).
>
> MD5 hash of the source zip file: ca79678bb109e96e057d5d9e49225088
> SHA1 hash of the source zip file: d3ecb896cf6683fd3245896a830eac6ac6cc9591
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/kaspersor.asc
>
> Release engineer public key id: 1FE1C2F5
>
> Vote thread link from d...@metamodel.incubator.apache.org 
> mailing list:
> http://markmail.org/message/ttthjjl4lpfsghil
>
> Result thread link from d...@metamodel.incubator.apache.org 
> mailing list:
> http://markmail.org/message/rxj75uc5h3ump2kw
>
> Please vote on releasing this package as Apache MetaModel
> 4.1.0-RC1-incubating.
>
> The vote is open for 72 hours, or until we get the needed number of votes
> (3 +1).
>
> [ ] +1 Release this package as Apache MetaModel 4.1.0-RC1-incubating
> [ ] -1 Do not release this package because...
>
> More information about the MetaModel project can be found at
> http://metamodel.incubator.apache.org/
>
> Thank you in advance for participating.
>
> Regards,
> Kasper Sørensen
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: 
> general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Metamodel incubating 4.1.0-RC1

[Henry Saputra]

Hi Justin,

We had this discussion before I think the conclusion is that as long as
long it is generated from internal source and not 3rd party it is allowed.
Someone else from IPMC could help clarifying this.

- Henry

On Saturday, May 3, 2014, Justin Mclean  wrote:

> Hi,
>
> +0 (binding) if the binary file question (see below) can be answered I'd
> vote +1
>
> Signatures and hashes all good
> DISCLAIMER correct
> Filename contains "incubating"
> NOTICE and LICENCE good (note that the year is wrong)
> All source file have correct headers (there's a few .csv, .xml and .txt
> files without headers that you may want to fix in a later release)
> Can compile from source
>
> I did notice a couple of binary files in the release - there's no jars or
> the like and most seem to be excel test files or similar. But the following
> file looks like a serialised java class - is that allowed?
>
>
> MetaModel-4.1.0-RC1-incubating/core/src/test/resources/metamodel-3.0-default-row.ser
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: 
> general-h...@incubator.apache.org
>
>

Re: [PROPOSAL] Optiq

[Henry Saputra]

Ah sorry, I did not mean "asking to update", I meant "proposing to update".

Thanks,

- Henry

On Fri, May 2, 2014 at 11:20 AM, Henry Saputra  wrote:
> HI Ashutosh,
>
> Since there was a question/ comment about relationship with Apache
> MetaModel, I am asking to update the proposal to include this
> discussion in either "Relationships with Other Apache Products" or
> "Alignment" section before going for a VOTE.
>
> Apache Slider did the same thing with relation to Apache Twill and
> Apache Helix projects.
>
> Thanks,
>
> - Henry
>
> On Wed, Apr 30, 2014 at 3:21 PM, Ashutosh Chauhan  
> wrote:
>> I would like to propose Optiq as an Apache Incubator project.  I have
>> posted the proposal to https://wiki.apache.org/incubator/OptiqProposal and
>> posted the text of the proposal below.
>>
>> Ashutosh.
>>
>> = Optiq =
>> == Abstract ==
>>
>> Optiq is a framework that allows efficient translation of queries involving
>> heterogeneous and federated data.
>>
>> == Proposal ==
>>
>> Optiq is a highly customizable engine for parsing and planning queries on
>> data in a wide variety of formats. It allows database-like access, and in
>> particular a SQL interface and advanced query optimization, for data not
>> residing in a traditional database.
>>
>> == Background ==
>>
>> Databases were traditionally engineered in a monolithic stack, providing a
>> data storage format, data processing algorithms, query parser, query
>> planner, built-in functions, metadata repository and connectivity layer.
>> They innovate in some areas but rarely in all.
>>
>> Modern data management systems are decomposing that stack into separate
>> components, separating data, processing engine, metadata, and query
>> language support. They are highly heterogeneous, with data in multiple
>> locations and formats, caching and redundant data, different workloads, and
>> processing occurring in different engines.
>>
>> Query planning (sometimes called query optimization) has always been a key
>> function of a DBMS, because it allows the implementors to introduce new
>> query-processing algorithms, and allows data administrators to re-organize
>> the data without affecting applications built on that data. In a
>> componentized system, the query planner integrates the components (data
>> formats, engines, algorithms) without introducing unncessary coupling or
>> performance tradeoffs.
>>
>> But building a query planner is hard; many systems muddle along without a
>> planner, and indeed a SQL interface, until the demand from their customers
>> is overwhelming.
>>
>> There is an opportunity to make this process more efficient by creating a
>> re-usable framework.
>>
>> == Rationale ==
>>
>> Optiq allows database-like access, and in particular a SQL interface and
>> advanced query optimization, for data not residing in a traditional
>> database. It is complementary to many current Hadoop and NoSQL systems,
>> which have innovative and performant storage and runtime systems but lack a
>> SQL interface and intelligent query translation.
>>
>> Optiq is already in use by several projects, including Apache Drill, Apache
>> Hive and Cascading Lingual, and commercial products.
>>
>> Optiq's architecture consists of:
>>
>> An extensible relational algebra.
>> SPIs (service-provider interfaces) for metadata (schemas and tables),
>> planner rules, statistics, cost-estimates, user-defined functions.
>> Built-in sets of rules for logical transformations and common data-sources.
>> Two query planning engines driven by rules, statistics, etc. One engine is
>> cost-based, the other rule-based.
>> Optional SQL parser, validator and translator to relational algebra.
>> Optional JDBC driver.
>> == Initial Goals ==
>>
>> The initial goals are be to move the existing codebase to Apache and
>> integrate with the Apache development process. Once this is accomplished,
>> we plan for incremental development and releases that follow the Apache
>> guidelines.
>>
>> As we move the code into the org.apache namespace, we will restructure
>> components as necessary to allow clients to use just the components of
>> Optiq that they need.
>>
>> A version 1.0 release, including pre-built binaries, will foster wider
>> adoption.
>>
>> == Current Status ==
>>
>> Optiq has had over a dozen minor releases over the last 18 months. Its core
>> SQL parser and validator, and its plannin

Re: [PROPOSAL] Optiq

[Henry Saputra]

HI Ashutosh,

Since there was a question/ comment about relationship with Apache
MetaModel, I am asking to update the proposal to include this
discussion in either "Relationships with Other Apache Products" or
"Alignment" section before going for a VOTE.

Apache Slider did the same thing with relation to Apache Twill and
Apache Helix projects.

Thanks,

- Henry

On Wed, Apr 30, 2014 at 3:21 PM, Ashutosh Chauhan  wrote:
> I would like to propose Optiq as an Apache Incubator project.  I have
> posted the proposal to https://wiki.apache.org/incubator/OptiqProposal and
> posted the text of the proposal below.
>
> Ashutosh.
>
> = Optiq =
> == Abstract ==
>
> Optiq is a framework that allows efficient translation of queries involving
> heterogeneous and federated data.
>
> == Proposal ==
>
> Optiq is a highly customizable engine for parsing and planning queries on
> data in a wide variety of formats. It allows database-like access, and in
> particular a SQL interface and advanced query optimization, for data not
> residing in a traditional database.
>
> == Background ==
>
> Databases were traditionally engineered in a monolithic stack, providing a
> data storage format, data processing algorithms, query parser, query
> planner, built-in functions, metadata repository and connectivity layer.
> They innovate in some areas but rarely in all.
>
> Modern data management systems are decomposing that stack into separate
> components, separating data, processing engine, metadata, and query
> language support. They are highly heterogeneous, with data in multiple
> locations and formats, caching and redundant data, different workloads, and
> processing occurring in different engines.
>
> Query planning (sometimes called query optimization) has always been a key
> function of a DBMS, because it allows the implementors to introduce new
> query-processing algorithms, and allows data administrators to re-organize
> the data without affecting applications built on that data. In a
> componentized system, the query planner integrates the components (data
> formats, engines, algorithms) without introducing unncessary coupling or
> performance tradeoffs.
>
> But building a query planner is hard; many systems muddle along without a
> planner, and indeed a SQL interface, until the demand from their customers
> is overwhelming.
>
> There is an opportunity to make this process more efficient by creating a
> re-usable framework.
>
> == Rationale ==
>
> Optiq allows database-like access, and in particular a SQL interface and
> advanced query optimization, for data not residing in a traditional
> database. It is complementary to many current Hadoop and NoSQL systems,
> which have innovative and performant storage and runtime systems but lack a
> SQL interface and intelligent query translation.
>
> Optiq is already in use by several projects, including Apache Drill, Apache
> Hive and Cascading Lingual, and commercial products.
>
> Optiq's architecture consists of:
>
> An extensible relational algebra.
> SPIs (service-provider interfaces) for metadata (schemas and tables),
> planner rules, statistics, cost-estimates, user-defined functions.
> Built-in sets of rules for logical transformations and common data-sources.
> Two query planning engines driven by rules, statistics, etc. One engine is
> cost-based, the other rule-based.
> Optional SQL parser, validator and translator to relational algebra.
> Optional JDBC driver.
> == Initial Goals ==
>
> The initial goals are be to move the existing codebase to Apache and
> integrate with the Apache development process. Once this is accomplished,
> we plan for incremental development and releases that follow the Apache
> guidelines.
>
> As we move the code into the org.apache namespace, we will restructure
> components as necessary to allow clients to use just the components of
> Optiq that they need.
>
> A version 1.0 release, including pre-built binaries, will foster wider
> adoption.
>
> == Current Status ==
>
> Optiq has had over a dozen minor releases over the last 18 months. Its core
> SQL parser and validator, and its planning engine and core rules, are
> mature and robust and are the basis for several production systems; but
> other components and SPIs are still undergoing rapid evolution.
>
> === Meritocracy ===
>
> We plan to invest in supporting a meritocracy. We will discuss the
> requirements in an open forum. We encourage the companies and projects
> using Optiq to discuss their requirements in an open forum and to
> participate in development. We will encourage and monitor community
> participation so that privileges can be extended to those that contribute.
>
> Optiq's pluggable architecture encourages developers to contribute
> extensions such as adapters for data sources, new planning rules, and
> better statistics and cost-estimation functions. We look forward to
> fostering a rich ecosystem of extensions.
>
> === Community ===
>
> Building a data management system requires a hi

Re: [PROPOSAL] Optiq

[Henry Saputra]

Unfortunately, similar projects entering Apache incubator are common things =(

Even though each original project proposers can argue about
differences in one way or another, it will eventually decided by
adoption and community growth, and at the end the quality of the
project itself.

Some other incoming projects had been in similar questions/concerns
regarding "competing" with existing ASF projects, e.g.: Twill vs
Slider, Samza vs Storm vs S4, and several others.


- Henry

On Thu, May 1, 2014 at 12:14 AM, Ted Dunning  wrote:
> I think that there is a huge difference between Metamodel and Optiq.
>
> In particular:
>
> - Optiq provides real SQL including nested queries, correlated sub-queries
> and so on
>
> - Metamodel uses a fluent Java API ... SQL parsing and transformation
> doesn't appear to be a goal
>
> - Optiq provides highly advanced query transformations including
> decorrelations based on estimated execution costs.
>
> - Metamodel appears to provide no significant query transformations
>
> - Optiq only provides query execution as a by-product for testing
>
> - Metamodel has query execution as a central goal
>
> - Optiq provides a form of type inferencing for SQL queries.  This is
> unique to Optiq as far as I know.
>
>
>
> On Thu, May 1, 2014 at 8:57 AM, Kasper Sørensen <
> kasper.soren...@humaninference.com> wrote:
>
>> I see a lot of conceptual similarity between Optiq and the Apache
>> MetaModel (incubator) project [1]. Maybe something can be done to align the
>> two projects, so that we avoid having two incubating projects that do
>> basically the same thing?
>>
>> Or maybe there's some glaring difference that I am missing? At least it
>> seems to me both to be projects that try to provide uniform querying
>> capabilities to a wide array of data backends. Both project also favor a
>> type-safe Java querying API instead of a String/SQL oriented query API.
>>
>> Regards,
>> Kasper Sørensen
>>
>> [1] http://metamodel.incubator.apache.org/
>>
>> 
>> From: Ashutosh Chauhan [hashut...@apache.org]
>> Sent: 01 May 2014 00:21
>> To: general@incubator.apache.org
>> Subject: [PROPOSAL] Optiq
>>
>> I would like to propose Optiq as an Apache Incubator project.  I have
>> posted the proposal to https://wiki.apache.org/incubator/OptiqProposal and
>> posted the text of the proposal below.
>>
>> Ashutosh.
>>
>> = Optiq =
>> == Abstract ==
>>
>> Optiq is a framework that allows efficient translation of queries involving
>> heterogeneous and federated data.
>>
>> == Proposal ==
>>
>> Optiq is a highly customizable engine for parsing and planning queries on
>> data in a wide variety of formats. It allows database-like access, and in
>> particular a SQL interface and advanced query optimization, for data not
>> residing in a traditional database.
>>
>> == Background ==
>>
>> Databases were traditionally engineered in a monolithic stack, providing a
>> data storage format, data processing algorithms, query parser, query
>> planner, built-in functions, metadata repository and connectivity layer.
>> They innovate in some areas but rarely in all.
>>
>> Modern data management systems are decomposing that stack into separate
>> components, separating data, processing engine, metadata, and query
>> language support. They are highly heterogeneous, with data in multiple
>> locations and formats, caching and redundant data, different workloads, and
>> processing occurring in different engines.
>>
>> Query planning (sometimes called query optimization) has always been a key
>> function of a DBMS, because it allows the implementors to introduce new
>> query-processing algorithms, and allows data administrators to re-organize
>> the data without affecting applications built on that data. In a
>> componentized system, the query planner integrates the components (data
>> formats, engines, algorithms) without introducing unncessary coupling or
>> performance tradeoffs.
>>
>> But building a query planner is hard; many systems muddle along without a
>> planner, and indeed a SQL interface, until the demand from their customers
>> is overwhelming.
>>
>> There is an opportunity to make this process more efficient by creating a
>> re-usable framework.
>>
>> == Rationale ==
>>
>> Optiq allows database-like access, and in particular a SQL interface and
>> advanced query optimization, for data not residing in a traditional
>> database. It is complementary to many current Hadoop and NoSQL systems,
>> which have innovative and performant storage and runtime systems but lack a
>> SQL interface and intelligent query translation.
>>
>> Optiq is already in use by several projects, including Apache Drill, Apache
>> Hive and Cascading Lingual, and commercial products.
>>
>> Optiq's architecture consists of:
>>
>> An extensible relational algebra.
>> SPIs (service-provider interfaces) for metadata (schemas and tables),
>> planner rules, statistics, cost-estimates, user-defined functions.
>> Built-in sets 

Re: [RESULT][VOTE] Accept Slider into the incubator

[Henry Saputra]

Congrats and welcome to ASF incubator guys!

- Henry

On Mon, Apr 28, 2014 at 10:43 AM, Steve Loughran  wrote:
> After the week's voting, here's the results.
>
> Binding +1s:
>
> Arun C Murthy
> Suresh Srinivas
> Vinod Kumar Vavilapalli
> Devaraj Das
> Jean-Baptiste Onofré
> Jakob Homan
>
> Non-binding +1s:
>
>
> P. Taylor Goetz
> larry mccay
>
>
> On and after April 25:
>
> Binding +1s:
> Mahadev Konar
>
> Non-binding +1s:
> Dilli Arumugam
> Edward J. Yoon
>
>
> Non-binding -0 :
>
> Andreas Neumann
>
> during the voting period:
> 6 binding +1s, two non-binding +1s and
> after
> 1 binding +1, 2 non-binding +1 and one -0.
>
> The vote has passed.
>
> I'm going to highlight the -0 as the team needs to make sure that Andreas's
> concerns are addressed,
> that we should be collaborating wherever we can -in our own code and YARN
> improvements.
>
> I'd also like to acknowledge the offers of Jean-Baptiste Onofré and Jakob
> Homan to help.
> Jean is already down as a mentor, but we'll pull Jakob in too, somehow.
>
> -Steve
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

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

Re: [VOTE] Accept Brooklyn into the Incubator

[Henry Saputra]

+1 (binding)

Good luck guys

On Monday, April 28, 2014, Chip Childers  wrote:

> Based on the previous discussion of accepting Brooklyn into the Apache
> Incubator as a podling, I'd like to call a vote for this now.
>
> [ ] +1 Accept Brooklyn into the Incubator
> [ ] +/-0 Indifferent to the acceptance of Brooklyn
> [ ] -1 Do not accept Brooklyn because...
>
> The proposal can be found here:
> https://wiki.apache.org/incubator/BrooklynProposal
>
> (For the IPMC members, I believe we typically "lock" the proposal page
> making it read-only during the voting.  I'm not sure how to do this, or
> if I'm remembering correctly.  Can someone clarify?  I'll watch that
> page to be sure there are no changes during the voting process.)
>
> -chip
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: 
> general-h...@incubator.apache.org
>
>

Re: [PROPOSAL] Brooklyn

[Henry Saputra]

Hi Alex,

Looking forward for Brooklyn as part of ASF incubator, awesome project.

Most existing projects that come to Apache incubator already had user
and dev lists, but most of the times the IPMCs encourage to have
initially dev@ list to focus on integration with ASF and also to
centralized discussion about the development of the project.

But, if both lists are active and have a lot of posts then by all
means go ahead to have both lists as proposed.

- Henry



On Thu, Apr 24, 2014 at 2:19 PM, Alex Heneveld
 wrote:
>
> Hi Henry,
>
> Thanks for the feedback.  We currently have both a dev and a user list, as
> Chip notes, and they are used by different people. That's why we thought we
> should move both across to apache as part of this proposal.
>
> Does that make sense in this situation?
>
> Best
> Alex
>
>
>
> On 24/04/2014 22:07, Chip Childers wrote:
>>
>> On Thu, Apr 24, 2014 at 12:59:15PM -0700, Henry Saputra wrote:
>>>
>>> Hi Chip,
>>>
>>> Like most initial incubator projects, I think you just need dev and
>>> private lists for start and maybe add user list later?
>>>
>>> - Henry
>>
>> I'll let the Brooklyn community speak up on that topic, since it's their
>> project.
>>
>> That said, I'd note that they are coming in as an existing community
>> with both a dev and user list in google groups.  It would be odd, IMO,
>> for that to change with a move to the ASF.
>>
>> -chip
>>
>> -
>> 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: [PROPOSAL] Brooklyn

[Henry Saputra]

Hi Chip,

Like most initial incubator projects, I think you just need dev and
private lists for start and maybe add user list later?

- Henry

On Wed, Apr 23, 2014 at 7:28 AM, Chip Childers  wrote:
> The Brooklyn project [1] community is interested in moving to the ASF.  They
> have worked within their community to create a proposal [2] for the
> Incubator, and have managed to get agreement from 2 IPMC members to
> mentor them if accepted (Matt Hogstrom and Alex Karasulu).
>
> This is the discussion thread for this proposal.  We would also like to
> solicit contributions from additional IPMC members willing to mentor the
> potential podling.  Anyone interested?
>
> -chip
>
> [1] http://brooklyncentral.github.io/
> [2] https://wiki.apache.org/incubator/BrooklynProposal
>
> Proposal follows:
>
> = Apache Brooklyn =
>
> == Abstract ==
>
> Brooklyn is a framework for modeling, monitoring, and managing
> applications through autonomic blueprints.
>
> == Proposal ==
>
> Brooklyn is about deploying and managing applications: composing a full
> stack for an application; deploying to cloud and non-cloud targets;
> using monitoring tools to collect key health/performance metrics;
> responding to situations such as a failing node; and adding or removing
> capacity to match demand.
>
> A Brooklyn blueprint defines an application, using a declarative YAML
> syntax supporting JVM plugins. A basic blueprint might comprise a single
> process, such as a web-application server running a WAR file or a SQL
> database and its associated DDL scripts. More complex blueprints
> encompass combinations of processes across multiple machines and
> services, such as a load-balancing HTTP server or SDN controller
> fronting a cluster of J2EE application servers, in turn connected to a
> resilient cluster of SQL database servers. Even larger clustered
> application running in multiple regions can be described, with features
> such as message buses with resilient brokers, cacheing tiers of NoSQL
> key-value store servers, a high-availability database cluster and
> multiple application components connected across these layers.
>
> One main benefit of these blueprints is that they are composable:
> best-practice blueprints for one process or pattern (e.g. a Cassandra
> cluster) can be incorporated in other blueprints (e.g. an application
> with a Cassandra cluster as one component). Another major benefit is
> that the blueprints can be treated as source code as part of an
> applications codebase: tested, tracked, versioned, and hardened as an
> integral part of the devops process. In some ways, Brooklyn is to
> run-time what Maven is to build-time.
>
> Brooklyn knows about Chef, Salt, and similar tools, and APT and Yum and
> plain old shell scripts, for deploying application components.
> Blueprints are built from a mixture of both off-the-shelf packages such
> as Tomcat, MySQL, Cassandra, and many more from our library; and
> components that are bespoke to individual applications; together with
> policies that allow the application to be self-managing.
>
> Brooklyn is built for the cloud, and will take a blueprint and deploy it
> to one of many supported clouds or even to multiple different clouds, or
> to private infrastructure (bring-your-own-node), or to other platforms.
> It will dynamically configure and connect all the different components
> of an application, e.g. so load balancers know where the web servers are
> and the web applications know where the database is.
>
> Brooklyn collects key metrics to monitor the health of applications; for
> example, by sending a request and measuring latency, or installing
> monitoring tools and using those to read a server’s management interface
> to determine the request queue length. These metrics can be fed into
> policies, which automatically take actions such as restarting a failed
> node, or scaling out the web tier if user demand exceeds capacity. This
> allows an application to be self-managing: to recover itself from simple
> failures, to scale out when demand increases and meet capacity; then
> scale in as demand drops and stop paying for spare capacity.
>
> In short, Brooklyn blueprints allow the best practices for deploying and
> managing complex software to be codified as part of the software
> development process.
>
> === Background ===
>
> Brooklyn is a product built from the ground up for application agility.
> This includes portability across non-cloud, cloud, and PaaS targets;
> devops-style infrastructure-as-code applied to applications; and
> real-time autonomic management based on promise theory. Some
> introductions to these concepts, associated tools, and open
> specifications may be useful.
>
> Cloud computing at its core is about provisioning resources on-demand.
> The most widely known aspect is IaaS (infrastructure-as-a-service) such
> as Amazon EC2, Softlayer, Google Cloud Platform, Apache CloudStack, or
> OpenStack. By leveraging the Apache jclouds project (and cont

Re: [ANNOUNCE] Apache Twill 0.2.0-incubating released

[Henry Saputra]

Congrats guys!

On Tue, Apr 22, 2014 at 12:36 PM, Terence Yim  wrote:
> Hi all,
>
> Forgot the disclaimer for the announcement. Here is the amendment to
> the announcement.
>
> Disclaimer:
> Apache Twill is an effort undergoing incubation at The Apache Software
> Foundation (ASF), sponsored by Incubator. Incubation is required of
> all newly accepted projects until a further review indicates that the
> infrastructure, communications, and decision making process have
> stabilized in a manner consistent with other successful ASF projects.
> While incubation status is not necessarily a reflection of the
> completeness or stability of the code, it does indicate that the
> project has yet to be fully endorsed by the ASF.
>
> Terence
>
> On Tue, Apr 22, 2014 at 1:47 AM, Terence Yim  wrote:
>> Hi all,
>>
>> The Apache Twill team is proud to announce the latest release of Apache
>> Twill 0.2.0-incubating.
>>
>> Apache Twill is an abstraction over Apache Hadoop® YARN that reduces
>> the complexity of developing and managing distributed applications
>> that runs on YARN. More details on Apache Twill can be found at
>> http://twill.incubator.apache.org/
>>
>> The release artifacts are available at:
>> https://dist.apache.org/repos/dist/release/incubator/twill/0.2.0-incubating/src/
>>
>> Maven artifacts have also been made available on
>> repository.apache.org.
>>
>> We would like to thank all the contributors that made this release possible.
>>
>> Thanks
>> Terence Yim on behalf of The Apache Twill Team

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

Re: [VOTE] Accept Stratosphere into the incubator

[Henry Saputra]

=
>> Currently, Stratosphere receives support from salaried developers, in
>> particular from graduate students at TU Berlin that are funded by the German
>> Research Council, the European Institute of Technology, and the European
>> Commission. These students work in their free time on Stratosphere in
>> addition to their employment.
>>
>> We expect that Stratosphere development will occur on both salaried and
>> volunteer time. We will recruit additional committers, including
>> non-salaried developers, and we will work to ensure that the project will
>> move forward independently of salaried developers.
>>
>> === Relationship with Other Apache Products ===
>> Stratosphere interfaces with several existing Apache projects: Apache
>> HBase for storage, Apache Hadoop (HDFS for storage, YARN for resource
>> management, and Stratosphere contains a generic wrapper for Hadoop MapReduce
>> input formats), and Apache Avro (for serialization). Stratosphere uses
>> Apache Maven and Apache Commons libraries internally. Stratosphere can be a
>> great compilation target for Apache Pig and Apache Hive, although such
>> functionality is not yet implemented.
>>
>> Stratosphere is also related with several projects undergoing incubation
>> in the Apache Incubation project, such as Tez, Drill, and Spark (graduated).
>> While all these projects target sufficiently different spaces and have
>> different architectures, it would be interesting to explore code reuse
>> possibilities. For example, we are currently basing our design for compiling
>> SQL to Stratosphere on the Optiq library, also used by Apache Drill.
>>
>> === An Excessive Fascination with the Apache Brand ===
>> We believe that the Apache brand will help us attract contributors to
>> Stratosphere, by giving us a well-defined, transparent development process
>> under a known brand. At the same time, Stratosphere already has a healthy
>> community and current funding guarantees the further codebase development
>> and growth of the project for the next 3-5 years. The reason for this
>> proposal is not to gain publicity, but to further strengthen the longevity
>> of the project as explained in the Rationale section.
>>
>> == Documentation ==
>>   * [[https://stratosphere.eu|Project website]]
>>   * [[http://stratosphere.eu/docs/0.4/|Documentation]]
>>   * [[https://github.com/stratosphere/stratosphere|Codebase]]
>>   * [[https://groups.google.com/forum/#!forum/stratosphere-dev|Mailing
>> list]]
>>
>> == Initial Source ==
>> Stratosphere is hosted on
>> [[https://github.com/stratosphere/stratosphere|GitHub]] . This is the
>> codebase that we will migrate to the Apache Foundation. The code was
>> previously hosted on a TU Berlin’s own git infrastructure. It has always
>> been Apache 2.0 licensed.
>>
>> === Source and Intellectual Property Submission Plan ===
>> All initial and past committers will sign a CLA with the ASF while the
>> incubator proposal for Stratosphere is being discussed. All organizations
>> that have employed Stratosphere contributors in the past will sign a SGA.
>> Current contributors will sign a CCLA. All major contributors are still
>> active in the project.
>>
>> === External Dependencies ===
>> All critical dependencies are, to the extend of our knowledge, from other
>> Apache projects. These include Apache Hadoop (for YARN and HDFS) and some
>> libraries (log4j, commons codec, junit and more). Our web frontend uses some
>> MIT-licensed JavaScript libraries.
>>
>> == Required Resources ==
>> === Mailing list ===
>> We will migrate our mailing lists to the following:
>>
>>   * us...@stratosphere.incubator.apache.org
>>   * d...@stratosphere.incubator.apache.org
>>   * priv...@stratosphere.incubator.apache.org
>>   * comm...@stratosphere.incubator.apache.org
>>
>> === Source control ===
>> We would like to use Git for source control and enable GitHib mirroring
>> functionality, where code reviews on GitHub are automatically forwarded to
>> the developer mailing list. (See also:
>> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and)
>>
>> === Issue tracking ===
>> We are currently using GitHub for issue tracking. We request an
>> Apache-hosted JIRA, and we will import existing issues there.
>>
>> == Initial committers ==
>>   * Stephan Ewen - stephan.e...@tu-berlin.de
>>   * Fabian Hueske - fabian.hue...@tu-berlin.de
>>   * Daniel Warneke - warn...@posteo.de
>>   * Robert Metzger - metrob...@gmail.com
>>   * Ufuk Celebi - u.cel...@fu-berlin.de
>>   * Aljoscha Krettek - aljoscha.kret...@gmail.com
>>   * Kostas Tzoumas - kostas.tzou...@tu-berlin.de
>>   * Sebastian Schelter  - s...@apache.org
>>
>> === Affiliations ===
>>   * Stephan Ewen (TU Berlin)
>>   * Fabian Hueske (TU Berlin)
>>   * Daniel Warneke (Amadeus IT Group)
>>   * Robert Metzger (TU Berlin)
>>   * Ufuk Celebi (FU Berlin)
>>   * Aljoscha Krettek (TU Berlin)
>>   * Kostas Tzoumas (TU Berlin)
>>   * Sebastian Schelter (TU Berlin)
>>
>> == Sponsors ==
>> === Champion ===
>> Alan Gates ( ga...@apache.org )
>>
>> === Nominated Mentors ===
>>   * Sean Owen ( sro...@apache.org ) (Note: Sean is an Apache member but
>> not currently on the IPC, he will need to request IPMC membership)
>>   * Ted Dunning ( tdunn...@apache.org )
>>   * Owen O'Malley ( omal...@apache.org )
>>   * Henry Saputra ( hsapu...@apache.org )
>>   * Ashutosh Chauhan (hashut...@apache.org)
>>
>> === Sponsoring Entity ===
>> The 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: [PROPOSAL] Stratosphere

[Henry Saputra]

Hi Upayavira,

Should we start VOTE as Stratosphere while asking for alternative names?

- Henry

On Mon, Apr 7, 2014 at 7:57 PM, Upayavira  wrote:
> I would suggest doing the vote and the name discussion simultaneously.
> Hopefully the name discussion can be resolved by the time infra is ready
> to do its stuff. It really is a good idea to avoid extra infra work, and
> multiple mailing list changes, if it can be helped.
>
> Upayavira
>
> On Tue, Apr 8, 2014, at 01:52 AM, Alan Gates wrote:
>> After talking with the proposers, the consensus is that the name will
>> need to change, and everyone is fine with that.  But the team wants to
>> make sure we take time to choose a new name that won’t run into legal
>> issues.  So we would prefer to start incubation now concurrent with the
>> name search rather than quickly pick a name now, hoping it will survive
>> the trademarks process.
>>
>> We realize this will cause some churn for infra, as we’ll end up changing
>> names on mailing lists, etc.  We’re open to suggestions on how to
>> minimize this.  So are we ok to start the vote?
>>
>> Alan.
>>
>> On Apr 7, 2014, at 9:01 AM, Shane Curcuru  wrote:
>>
>> > The brand issue is an important one to be aware of, but we shouldn't let 
>> > that block progress on evaluating the proposal or working with the 
>> > potential new community to see how they'd fit with The Apache Way.
>> >
>> > A couple of other notes:
>> >
>> > - Finding *factual* references to similar software product names is a good 
>> > thing to do up front, so we can be aware of any potential conflicts for 
>> > the future.  However it's not as useful to try to analyze what the 
>> > potential issues are on a public list.
>> >
>> > - The ASF is happy to host any like-minded project communities who are 
>> > willing to follow the core rules that we require of Apache branded 
>> > projects.  Part of that hosting is offering the stable APACHE house brand 
>> > for the project community, as well as assistance in securing and 
>> > maintaining their project identity.
>> >
>> > That said, we also have to recognize that where there are third parties 
>> > with pre-existing uses of similar software product names, we can't 
>> > necessarily offer the same level of defense for such a project name.
>> >
>> > Depending on the case, we may decide that a podling community is willing 
>> > to accept the risk of future conflicts, and that's fine - as long as in 
>> > those cases we recognize that we may be forced to change a project name in 
>> > the future *if* the issue ever comes up.
>> >
>> > The trick with trademarks are that in virtually all cases, "it depends". 
>> > The details matter - both on the legal details of some potential conflict 
>> > of names, *as well as* the actual behavior of the parties involved.  That 
>> > is: just because there is an apparent conflict of names does not always 
>> > mean that the two parties can't reach an agreement to each continue while 
>> > recognizing each other's brands.
>> >
>> > That being said, given the wide use of "stratos" as a name associated with 
>> > various cloud stuff these days, that I do recommend the proposal 
>> > submitters have a serious discussion about considering a new name.
>> >
>> >
>> > - Shane (not subscribed, reading on archives)
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>>
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity
>> to
>> which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified
>> that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender
>> immediately
>> and delete it from your system. Thank You.
>>
>> -
>> 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