Re: [VOTE] Graduate Zeppelin from the Incubator

[Suresh Marru]

+ 1 (binding).

Good work folks, looking forward to see the community engagement remains 
healthy. 

Suresh
> On Apr 16, 2016, at 5:01 AM, moon soo Lee  wrote:
> 
> Hi,
> 
> Apache Zeppelin started incubating about a year and 4 months ago
> (2014-12-23) and the members of the community think that it is ready to
> graduate from the incubator to be a TLP.
> 
> Since it's inception, Zeppelin community has made 3 releases, recruited 4
> PPMC and resolved 500+ issues [1] with 90+ contributors [2]. Now, community
> is very open, active and continuously growing.
> 
> The Apache Zeppelin community has discussed and voted on graduation to
> top level
> project.
> The vote passed with 22 +1 votes (9 binding) and no 0 or -1 votes.
> 
> Incubation Status:
> http://incubator.apache.org/projects/zeppelin.html
> Maturity Assessment:
> https://cwiki.apache.org/confluence/display/ZEPPELIN/Apache+Zeppelin+Project+Maturity+Model
> Discussion:
> https://s.apache.org/gLi0
> https://s.apache.org/GhqY (continue)
> Vote:
> https://s.apache.org/7hCK
> Result:
> https://s.apache.org/1rJD
> 
> Please vote on the resolution pasted below to graduate Apache Zeppelin
> from the incubator to top level project.
> 
> [ ] +1 Graduate Apache Zeppelin from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Zeppelin from the Incubator because
> 
> This vote will be open for at least 72 hours.
> Many thanks to our mentors and everyone else for the support,
> 
> [1] https://s.apache.org/eswD
> [2] https://s.apache.org/gi3o
> 
> Apache Zeppelin top-level project 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 a collaborative data analytics and
> visualization tool for general-purpose data processing systems.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Zeppelin Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that the Apache Zeppelin Project be and hereby is
> responsible for the creation and maintenance of software
> related to a collaborative data analytics and
> visualization tool for general-purpose data processing systems; and be it
> further
> 
> RESOLVED, that the office of "Vice President, Apache Zeppelin" 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 Zeppelin Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Zeppelin 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 Zeppelin Project:
> 
> * Alexander Bezzubov 
> * Anthony Corbacho 
> * Damien Corneau 
> * Felix Cheung 
> * Jongyoul Lee 
> * Kevin Sangwoo Kim 
> * Lee Moon Soo 
> * Mina Lee 
> * Prabhjyot Singh 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lee Moon Soo
> be appointed to the office of Vice President, Apache Zeppelin, 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 Zeppelin 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 Zeppelin Project; and be it further
> 
> RESOLVED, that the Apache Zeppelin Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Zeppelin podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Zeppelin podling encumbered upon the Apache Incubator
> Project are hereafter discharge.


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

Re: [VOTE] Accept Omid into the Apache Incubator

[Suresh Marru]

+ 1 (binding).

Suresh

> On Mar 23, 2016, at 6:31 PM, Daniel Dai  wrote:
> 
> Following the discussion earlier, I'm calling a vote to accept Omid as
> a new Incubator project.
> 
> [ ] +1 Accept Omid into the Incubator
> [ ] +0 Indifferent to the acceptance of Omid
> [ ] -1 Do not accept Omid because ...
> 
> The vote will be open for the next 72 hours.
> 
> https://wiki.apache.org/incubator/OmidProposal
> 
> Thanks,
> Daniel
> 
> = Omid Proposal =
> 
> === Abstract ===
> Omid is a flexible, reliable, high performant and scalable ACID
> transactional framework that allows client applications to execute
> transactions on top of MVCC key/value-based NoSQL datastores
> (currently Apache HBase) providing Snapshot Isolation guarantees on
> the accessed data.
> 
> === Proposal ===
> Omid is a flexible open-source transactional framework that provides
> ACID transactions with Snapshot Isolation guarantees on top of NoSQL
> datastores. In particular, the current codebase brings the concept of
> transactions to the popular Apache HBase datastore. Omid offers great
> performance, it is highly available, and scalable. Omid's current
> version is able to scale to thousands of clients triggering concurrent
> transactions on application data stored in HBase. Omid can scale
> beyond 100K transactions per second on mid-range hardware while
> incurring in a minimal impact on the speed of data access in the
> datastore. We’re currently experimenting with a prototype version that
> can improve the performance up to ~380K TPS.
> 
> Omid has been publicly available as an open-source project in Github
> under Apache License Version 2.0 since 2011 [1]. During these years,
> it has generated certain interest in the open source community,
> especially since the public presentation of the first version in
> Hadoop Summit 2013 [2]. Currently the Github project has 241 Stars and
> 93 forks. Yahoo Inc. submits this proposal to the Apache Software
> Foundation with the aim to transfer the Omid project -including its
> source code and documentation- to Apache in order to start the build
> of a stable open source community around it.
> 
> [1] https://github.com/yahoo/omid
> [2] Omid presentation at Hadoop Summit 2013:
> https://www.youtube.com/watch?v=Rhdmo9pVGgU&index=68&list=PLSAiKuajRe2luyqLU464Nxz4aQe7EPBus
> 
> === Background ===
> An Omid prototype was first released as an open-source project back in
> 2011. Inspired by Google Percolator [1], it offered a lock-free
> approach to transactions in NoSQL datastores (See [2]). However,
> during these years, the design of Omid has evolved significantly.
> Whilst the current open-sourced version maintains many aspects of the
> original implementation, it is the result of a major redesign of the
> first prototype released in 2011.
> 
> Omid has now a more decentralized design that does not sacrifice the
> consistency and performance of the original version. The current
> design also enables Omid to scale to thousands of clients executing
> transactions concurrently on application data stored in HBase.
> Internally, Omid still utilizes a lock-free approach to support
> multiple concurrent clients. Its design also relies on a centralized
> conflict detection component, the TSO, which now resolves in an
> efficient manner writeset collisions among concurrent transactions
> without having to piggyback commit information to the clients. Another
> important benefit of Omid is that it doesn't require any modification
> of the underlying key-value datastore, HBase in this case. Moreover,
> the recently added high availability algorithm allows to eliminate the
> single point of failure represented by the TSO in those system
> deployments requiring a higher degree of dependability. Last but not
> least, the provided user API is very simple, mimicking transaction
> managers in the relational world: begin, commit, rollback.
> 
> Omid is used internally at Yahoo. Sieve, Yahoo’s web-scale content
> management platform powering some of next-generation search and
> personalization products is using Omid as a transaction manager in its
> processing pipeline. Sieve essentially acts as a huge processing hub
> between content feeds and serving systems. It provides an environment
> for highly customizable, real-time, streamed information processing,
> with typical discovery-to-service latencies of just a few seconds. In
> terms of scale and availability, Omid’s new design was largely driven
> by Sieve’s requirements.
> 
> At Yahoo, we are also making an effort to disseminate the current
> status of the project through blog entries (See [3], [4] and [5]) and
> submissions to technical and academic conferences such as ATC 2016,
> Hadoop Summit 2016, HBaseConf 2016. Last but not least, Omid also
> appeared in a TechCrunch article in the last quarter of 2015 (See [6])
> 
> [1] D. Peng and F. Dabek, Large-scale Incremental Processing Using
> Distributed Transactions and Notifications. USENIX Symposium on
> Operati

Re: [VOTE] Accept Airflow into the Incubator

[Suresh Marru]

+ 1 (binding).

Suresh

> On Mar 24, 2016, at 11:00 PM, Siddharth Anand  
> wrote:
> 
> Following the discussion earlier:
>https://s.apache.org/AirflowDiscussion
> 
> I would like to call a VOTE for accepting Airflow as a new incubator project.
> 
> The proposal is available at: 
> https://wiki.apache.org/incubator/AirflowProposal
> 
> The proposal is also included at the bottom of this email.
> 
> Vote is open until at least Tues, 29 March 2016, 23:59:00 PDT
> [ ] +1 accept Airflow into the Apache Incubator
> [ ] ±0
> [ ] -1 because...
> 
> +1 (non-binding)
> 
> Thanks,
> -s (Sid)
> 
> 
> == Abstract ==
> 
> Airflow is a workflow automation and scheduling system that can be
> used to author and manage data pipelines.
> 
> == Proposal ==
> 
> Airflow provides a system for authoring and managing workflows a.k.a.
> data pipelines a.k.a. DAGs (Directed Acyclic Graphs). The developer
> authors DAGs in Python using an Airflow-provided framework. He/She
> then executes the DAG using Airflow’s scheduler or registers the DAG
> for event-based execution. A web-based UI provides the developer with
> a range of options for managing and viewing his/her data pipelines.
> Background
> 
> Airflow was developed at Airbnb to enable easier authorship and
> management of DAGs than were possible with existing solutions such as
> Oozie and Azkaban. For starters, both Oozie and Azkaban rely on one or
> more XML or property files to be bundled together to define a
> workflow. This separation of code and config can present a challenge
> to understanding the DAG - in Azkaban, a DAG’s structure is reflected
> by its file system tree and one can find himself/herself traversing
> the file system when inspecting or changing the structure of the DAG.
> Airflow workflows, on the other hand, are simply and elegantly defined
> in Python code, often a single file. Airflow merges the powerful
> Web-based management aspects of projects like Azkaban and Oozie with
> the simplicity and elegance of defining workflows in Python. Airflow,
> less than a year old in terms of its Open Source launch, is currently
> used in production environments in more than 30 companies and boasts
> an active contributor list of more than 100 developers, the vast
> majority of which (>95%) are outside of Airbnb.
> 
> We would like to share it with the ASF and begin developing a
> community of developers and users within Apache.
> 
> == Rationale ==
> 
> Many organizations (>30) already benefit from running Airflow to
> manage data pipelines. Our 100+ contributors continue to provide
> integrations with 3rd party systems through the implementation of new
> hooks and operators, both of which are used in defining the tasks that
> compose workflows.
> 
> == Current Status ==
> 
> === Meritocracy ===
> 
> Our intent with this incubator proposal is to start building a diverse
> developer community around Airflow following the Apache meritocracy
> model. Since Airflow was open-sourced in mid-2015, we have had fast
> adoption and contributions by multiple organizations the world over.
> We plan to continue to support new contributors and we will work to
> actively promote those who contribute significantly to the project to
> committers.
> 
> === Community ===
> 
> Airflow is currently being used in over 30 companies. We hope to
> extend our contributor base significantly and invite all those who are
> interested in building large-scale distributed systems to participate.
> 
> === Core Developers ===
> 
> Airflow is currently being developed by four engineers: Maxime
> Beauchemin, Siddharth Anand, Bolke de Bruin, and Chris Riccomini.
> Chris is a member of the Apache Samza PMC and a contributor to various
> Apache projects, including Apache Kafka and Apache YARN. Maxime,
> Siddharth, and Bolke have contributed to Airflow.
> 
> === Alignment ===
> The ASF is the natural choice to host the Airflow project as its goal
> of encouraging community-driven open-source projects fits with our
> vision for Airflow.
> 
> == Known Risks ==
> 
> === Orphaned Products ===
> 
> The core developers plan to work part time on the project. There is
> very little risk of Airflow being abandoned as all of our companies
> rely on it.
> 
> === Inexperience with Open Source ===
> 
> All of the core developers have experience with open source
> development. Chris is a member of the Apache Samza PMC and a
> contributor to various Apache projects, including Apache Kafka and
> Apache YARN. Bolke is contributor on multiple open source projects and
> a few Apache projects as well, including Apache Hive, Apache Hadoop,
> and Apache Ranger.
> 
> === Homogeneous Developers ===
> 
> The current core developers are all from different companies. Our
> community of 100 contributors hail from over 30 different companies
> from across the world.
> 
> === Reliance on Salaried Developers ===
> 
> Currently, the only developer paid to work on this project is Maxime.
> 
> === Relationships with Other Apache Prod

Re: [VOTE] Release taverna-language-0.15.1-incubating-RC5 and taverna-osgi-0.2.1-incubating-RC5

[Suresh Marru]

I did not get to too details, but the basics of LICENSE, NOTICE files and 
signatures all are tallying. 

I am + 1 (binding) for this release.

Suresh

> On Mar 10, 2016, at 6:55 PM, Stian Soiland-Reyes  wrote:
> 
> Hi folks,
> 
> With Justin revising his vote to +1 we just need one more binding +1 for
> this release candidate from the Taverna podling.
> 
> Would someone else have time for a quick review..?
> On 3 Mar 2016 16:13, "Pierce, Marlon"  wrote:
> 
>> Hello Incubator,
>> 
>> Apache Taverna is looking for new active mentors [1] and in the meantime
>> will need your help with this vote.
>> 
>> Thanks,
>> 
>> Marlon
>> 
>> [1]
>> https://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3CCAMBJEmW6ezFS7Dtsxo2FwSV7dXj1MPQ_=efuiqmkcvsqcj7...@mail.gmail.com%3E
>> 
>> 
>> 
>> On 3/2/16, 12:07 PM, "Stian Soiland-Reyes"  wrote:
>> 
>>> I am pleased to be calling this vote for the source release of
>>> 
>>> Apache Taverna Maven Parent 2-incubating
>>> Apache Taverna Language 0.15.1-incubating
>>> Apache Taverna OSGi plugin system 0.2.1-incubating
>>> 
>>> The Apache Taverna IPMC has voted in favour of this release with 5 IPMC
>> votes:
>>> 
>>> http://markmail.org/message/346xxkywuexw6z52
>>> http://mail-archives.apache.org/mod_mbox/taverna-dev/201603.mbox/<
>> cambjemvv0asztfxwkulqpood1-cfwfydpf320fq_rzgkcuj...@mail.gmail.com>
>>> 
>>> We now ask for the Incubator PMC to vote on this release candidate.
>>> 
>>> 
>>> Apache Taverna Language is a set of APIs for workflow definitions
>>> (SCUFL2) and workflow inputs/outputs/run (DataBundle), as consumed and
>>> produced by the Apache Taverna workflow system. The API includes
>>> support for working with Research Object Bundles, and loading/saving
>>> Taverna workflows in different formats.
>>> 
>>> Apache Taverna OSGi is a plugin system for OSGi with support for
>>> online updates, which can be used by Java desktop and command line
>>> applications.
>>> 
>>> 
>>> The release candidates to be voted over are available at:
>>> 
>>> 
>> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-parent-2-incubating-RC5/
>>> 
>> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-language-0.15.1-incubating-RC5/
>>> 
>> https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-osgi-0.2.1-incubating-RC5/
>>> 
>>> 
>>> Checksums:
>>> 
>>> md5sum:
>>> 8e7ee332896d314877af481b348dbf51
>>> apache-taverna-parent-2-incubating-source-release.zip
>>> 
>>> 6bd8ae9e2b1bc2e675e5573b87feaa2a
>>> apache-taverna-language-0.15.1-incubating-source-release.zip
>>> 
>>> 4d595212a813f62a0c16a31d3a872af4
>>> apache-taverna-osgi-0.2.1-incubating-source-release.zip
>>> 
>>> 
>>> sha1sum:
>>> d4b675763eb03bc5a9863db27779d725e1209af6
>>> apache-taverna-parent-2-incubating-source-release.zip
>>> 
>>> af3a14ec6d9386e9aa97309275f7b147be6f0a38
>>> apache-taverna-language-0.15.1-incubating-source-release.zip
>>> 
>>> 2e91b5176322c0e029e1a856f0752159b1564158
>>> apache-taverna-osgi-0.2.1-incubating-source-release.zip
>>> 
>>> 
>>> sha512sum:
>> 
>>> d5787ba7066d0d3b7c3b292434eb3de909c8ebaf43f0a3ea5e9dd25f0f19b5c1b7d508ffde97c0e6afd53265835d1aa4f22bb3187011b50b7f5aac99892bd0aa
>>> apache-taverna-parent-2-incubating-source-release.zip
>>> 
>> 
>>> 7cb4860abb4c57b91e81703a0d362d2824f10f1d2abe62c3df028fdca4f3ce33c4fe572c3349e629c8d409a7b25f3c86b79487d840c642a4b39e84432aa86c04
>>> apache-taverna-language-0.15.1-incubating-source-release.zip
>>> 
>> 
>>> 31b50a87243a01f3a5a657643d0f3b7f56d86fcc309df74392df3915ef8a787948ff8c74bc6a7684e6f9049b6430324373c50959ff658803dbc2d67d8a3dc45c
>>> apache-taverna-osgi-0.2.1-incubating-source-release.zip
>>> 
>>> 
>>> 
>>> To build the release candidates you need Apache Maven 3 and Java 8.
>>> 
>>> 
>>> Build the release candidate, in the above order, using:
>>> 
>>>   mvn clean install
>>> 
>>> 
>>> The release candidates correspond to the following git commits:
>>> 
>>> 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-maven-parent.git;a=commit;h=d34dd67fcfa11caead08008d37279b1ea546e3ec
>>> 
>>> 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-language.git;a=commit;h=66866a5454ed23262c055f65155d7a195c68a17d
>>> 
>>> 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-osgi.git;a=commit;h=0b7da331e81febade5ce2f4cf1f068013002b7aa
>>> 
>>> 
>>> Release candidates are signed with a GPG key available at:
>>> 
>>> https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS
>>> 
>>> A staged Maven repository is available for review at:
>>> 
>>> 
>> https://repository.apache.org/content/repositories/orgapachetaverna-1011/
>>> 
>>> The changelog for this release is available from JIRA:
>>> 
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333249&projectId=12318322
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333250&projectId=12318322
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332248&proj

GSoC Mentor ACK for PPMC vs Incubator PMC

[Suresh Marru]

Hi All,

Since there will be significant Incubator PPMC mentors, I will start a broader 
discussion on this topic. Please be cautious, I am cc’ing a private list and a 
public list, please only contain this thread to the topic and do not discuss 
any student proposals or other sensitive GSOC discussions on this thread. 

There seems to be a confusion on who should send ACK for mentors from Incubator 
projects. Refer to GSOC guides on com-dev site [1] for additional information.

I think its time for us to refresh our memories on why PMC acknowledging is 
needed in the first place. Here is my take:

* The PMC ACK serves as the filter to make sure mentors are part of the 
proposed project. The key here is for a mentor to be able to commit the student 
contributions, but also is knowledgable enough on the proposed project. An ACK 
from a fellow PMC member confirms the same.

* The PMC ACK also serves as a mechanism for the PMC as whole to be aware of 
the project being proposed. This is very important. If the mentor gets busy 
with life, the student should not be left under water, others on the projects 
should be able to pick up the slack.

A question often comes up: can a non-PMC and a non-Committer be a mentor? The 
reasoning often give is: they have been contributing to the project from a 
while and know enough to mentor a GSOC project but is officially not a 
committer. This question should be re-directed to the PMC, if someone is 
actively contributing to the project and can guide a GSOC project, they 
probably should have earned commit access by now or even better, be part of the 
PMC, time to fix that first. 

Secondly, lot of mentors self-acknowledge their request, they can rightfully do 
so since they are part go the PMC. This is not bad since the PMC list is cc’ed 
and lazy consensus can be assumed. But its not onerous to expect a three letter 
reply from others on the PMC which will ensure the community has interests in 
the project and not just a single mentor. 

Its important to understand that GSOC is about teaching students to contribute 
to open source and community is a big part of it. A single point of contact 
(mentor) ensures they will be guided, but it is not a mentor-student training 
excise. A good mentor should teach the students to work with the community and 
not just themselves.  

With this long background, my personal opinion for Incubator projects is to 
expect PPMC to acknowledge the mentor. If we go by the rule book, Incubator PMC 
should ACK the request, but in many cases the IPMC may not be able to step up 
and help the student with technical details but others on the PPMC will have a 
much better success at it. 

Finally, these are my opinions to make us think on the goals of a process which 
should take precedence over rule book. But Uli Stark as the ASF GSOC org admin 
reserves the final call on what he will require to validate mentors. 

Suresh
[1] - http://community.apache.org/ 

Re: [VOTE] Accept Beam into the Apache Incubator

[Suresh Marru]

s[bchamb...@google.com]
> * Craig Chambers  [chamb...@google.com]
> * Dan Halperin[dhalp...@google.com]
> * Davor Bonaci[da...@google.com]
> * Frances Perry   [f...@google.com]
> * James Malone[jamesmal...@google.com]
> * Jean-Baptiste Onofré[jbono...@apache.org]
> * Josh Wills  [jwi...@apache.org]
> * Kostas Tzoumas  [kos...@data-artisans.com]
> * Kenneth Knowles [k...@google.com]
> * Luke Cwik   [lc...@google.com]
> * Maximilian Michels  [m...@apache.org]
> * Stephan Ewen[step...@data-artisans.com]
> * Tom White   [t...@cloudera.com]
> * Tyler Akidau[taki...@google.com]
> * Robert Bradshaw [rober...@google.com]
> 
> == Additional Interested Contributors ==
> 
> * Debo Dutta  [dedu...@cisco.com]
> * Henry Saputra   [hsapu...@apache.org]
> * Taylor Goetz[ptgo...@gmail.com]
> * James Carman[ja...@carmanconsulting.com]
> * Joe Witt[joew...@apache.org]
> * Vaibhav Gumashta[vgumas...@hortonworks.com]
> * Prasanth Jayachandran   [pjayachand...@hortonworks.com]
> * Johan Edstrom   [seij...@gmail.com]
> * Hugo Louro  [hmclo...@gmail.com]
> * Krzysztof Sobkowiak [krzys.sobkow...@gmail.com]
> * Jeff Genender   [jgenen...@apache.org]
> * Edward J. Yoon  [edward.y...@samsung.com]
> * Hao Chen[h...@apache.org]
> * Byung-Gon Chun  [bgc...@gmail.com]
> * Charitha Elvitigala [charit...@apache.org]
> * Alexander Bezzubov  [b...@apache.org]
> * Tsuyoshi Ozawa  [oz...@apache.org]
> * Mayank Bansal   [maban...@gmail.com]
> * Supun Kamburugamuve [su...@apache.org]
> * Matthias Wessendorf [mat...@apache.org]
> * Felix Cheung[felixche...@apache.org]
> * Ajay Yadava [ajay.ya...@inmobi.com]
> * Liang Chen  [chenliang...@huawei.com]
> * Renaud Richardet[renaud (at) apache (dot) org]
> * Bakey Pan   [bakey1...@gmail.com]
> * Andreas Neumann [a...@apache.org]
> * Suresh Marru[sma...@apache.org]
> * Hadrian Zbarcea [hzbar...@gmail.com]
> 
> == Affiliations ==
> 
> The initial committers are from six organizations. Google developed Dataflow 
> and the Dataflow SDK, data Artisans developed the Flink runner, and Cloudera 
> (Labs) developed the Spark runner.
> 
> * Cloudera
>  * Tom White
> * Data Artisans
>  * Aljoscha Krettek
>  * Kostas Tzoumas
>  * Maximilian Michels
>  * Stephan Ewen
> * Google
>  * Ben Chambers
>  * Dan Halperin
>  * Davor Bonaci
>  * Frances Perry
>  * James Malone
>  * Kenneth Knowles
>  * Luke Cwik
>  * Tyler Akidau
>  * Robert Bradshaw
> * PayPal
>  * Amit Sela
> * Slack
>  * Josh Wills
> * Talend
>  * Jean-Baptiste Onofré
> 
> == Sponsors ==
> 
> === Champion ===
> 
> * Jean-Baptiste Onofre [jbono...@apache.org]
> 
> === Nominated Mentors ===
> 
> * Jean-Baptiste Onofre   [jbono...@apache.org]
> * Jim Jagielski  [j...@apache.org]
> * Venkatesh Seetharam[venkat...@apache.org]
> * Bertrand Delacretaz[bdelacre...@apache.org]
> * Ted Dunning[tdunn...@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: Apache Dataflow Incubator Proposal Wiki

[Suresh Marru]

Hi JB,

DataFlow (BEAM) is very interesting for Apache Airavata. Can you please add me 
(Suresh Marru) to the interested to contribute? 

Thanks,
Suresh

> On Jan 27, 2016, at 9:00 AM, Jean-Baptiste Onofré  wrote:
> 
> Hey Andreas,
> 
> of course you are interesting (I count on you ;))
> 
> I added your on the proposal.
> 
> Regards
> JB
> 
> On 01/27/2016 02:56 PM, Andreas Neumann wrote:
>> Hi,
>> 
>> I am very interested in this. Please also add my name to the list of
>> interested to contribute.
>> 
>> Cheers -Andreas.
>> 
>> On Wed, Jan 27, 2016 at 1:13 AM, Jean-Baptiste Onofré 
>> wrote:
>> 
>>> Great !
>>> 
>>> I added you on the proposal.
>>> 
>>> Thanks,
>>> Regards
>>> JB
>>> 
>>> 
>>> On 01/27/2016 10:11 AM, bakey pan wrote:
>>> 
>>>> Hi, I am developing one similar project like Dataflow and would be
>>>> happy to contribute.
>>>> 
>>>> 
>>>> Regards,
>>>> BakeyPan
>>>> 
>>>> 
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
>> 
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: [VOTE] Accept Mysos into the Apache Incubator

[Suresh Marru]

+ 1 (binding)

Suresh

> On May 28, 2015, at 12:14 PM, Jake Farrell  wrote:
> 
> Based on the earlier discussion in thread [1], I would like to call a VOTE
> to accept Mysos, an Apache Mesos framework for running MySQL instances, as
> a new Apache Incubator project.
> 
> The proposal is available on the wiki at [2] and is also attached below
> 
> The VOTE is open for at least the next 72 hours:
> 
>  [ ] +1 Accept Mysos into the Apache Incubator
>  [ ] ±0
>  [ ] -1 Do not accept Mysos into the Apache Incubator because...
> 
> I would like to get the voting started with my own +1
> 
> Thank you
> -Jake
> 
> [1]: http://s.apache.org/2vm
> [2]: https://wiki.apache.org/incubator/MysosProposal
> 
> 
> 
> Mysos Proposal
> 
> Abstract
> 
> Mysos is an Apache Mesos framework for running MySQL instances.
> 
> Proposal
> 
> Mysos runs on Apache Mesos (cluster manager) to dramatically simplify the
> management of MySQL instances. It is designed to offer:
> 
> Efficient hardware utilization through multi-tenancy (in
> performance-isolated containers)
> High reliability through preserving the MySQL state during failure and
> automatic backing up to/restoring from HDFS
> An automated self-service option for bringing up new MySQL clusters
> High availability through automatic MySQL master failover
> An elastic solution that allows users to easily scale up and down a MySQL
> cluster by changing the number of slave instances
> Background
> 
> Initial development of Mysos was done at Twitter, and its codebase was
> recently open sourced. This proposal is for Mysos to join the Apache
> Incubator.
> 
> Rationale
> 
> Mysos is built to be used by anyone who desires to run MySQL on Apache
> Mesos, and in the near-future it will take advantage of state primitives
> that are being added to the Mesos core:
> https://issues.apache.org/jira/browse/MESOS-1554
> 
> Furthermore, the rapid growth of Mysos community is empowered by open
> source. We believe the Apache Foundation is a great fit as the long-term
> home for Mysos, as it provides an established process for community-driven
> development and decision making by consensus.
> 
> 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
> Strengthen and grow the Mysos community
> Incremental development and releases per Apache guidelines
> Current Status
> 
> Mysos was originally born out of a project within Twitter. The original
> committers (Twitter) are working with Mesosphere and Percona to fully open
> source the code and make it ready for incubation at Apache.
> 
> The Mysos source is currently hosted at GitHub, which will be used to 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
> 
> By bringing Mysos into Apache, we believe that the community will grow even
> bigger.
> 
> Core Developers
> 
> Mysos was initially developed as a collaboration between Twitter and
> Mesosphere.
> 
> Alignment
> 
> We believe that having Mysos 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 Mesos.
> 
> Known Risks
> 
> Orphaned Products
> 
> Mysos is being used and developed by companies we work for so the companies
> have an interest in its continued vitality.
> 
> Given strong interest we've had since open sourcing Mysos, we anticipate
> we'll grow a sustainable community that will expand contributors and keep
> it active as the Mesos core evolves.
> 
> Inexperience with Open Source
> 
> Most of the committers have experience at Apache, whether it's through
> Apache Mesos, Aurora or other projects. Apache Mesos and Apache Aurora were
> both shepherded through the ASF incubator process and have graduated to
> become successful and diverse open source projects. We also have Jake
> Farrell as an ASF Champion to help us through incubation.
> 
> Homogenous Developers
> 
> Initial committers come from a number of companies. Our intention is
> increase the diversity of contributing developers and their affiliations,
> and we'll recognize contributions and contributors as the community grows
> at Apache. We encouraged by interest in the project thus far.
> 
> Reliance on Salaried Developers
> 
> It is expected that Mysos development will occur on both salaried time and
> on volunteer time, after hours. The majority of initial committers are paid
> by their employers to contribute to this project. However, they are all
> passionate about the project, and we are confident that the project will
> continue ev

Re: [VOTE] Accept Geode into the Apache Incubator

[Suresh Marru]

+ 1 (binding)

Suresh

> On Apr 20, 2015, at 1:46 AM, Roman Shaposhnik  wrote:
> 
> Following the discussion earlier in the thread:
>   http://s.apache.org/Oxt
> 
> I would like to call a VOTE for accepting Geode
> as a new incubator project.
> 
> The proposal is available at:
>https://wiki.apache.org/incubator/GeodeProposal
> and is also included at the bottom of this email.
> 
> Vote is open until at least Sunday, 26 April 2015, 23:59:00 PST
> 
> [ ] +1 accept Geode in the Incubator
> [ ] ±0
> [ ] -1 because...
> 
> Thanks,
> Roman.
> 
> == Abstract ==
> Geode is a data management platform that provides real-time,
> consistent access to data-intensive applications throughout widely
> distributed cloud architectures.
> 
> Geode pools memory (along with CPU, network and optionally local disk)
> across multiple processes to manage application objects and behavior.
> It uses dynamic replication and data partitioning techniques for high
> availability, improved performance, scalability, and fault tolerance.
> Geode is both a distributed data container and an in-memory data
> management system providing reliable asynchronous event notifications
> and guaranteed message delivery.
> 
> == Proposal ==
> The goal of this proposal is to bring the core of Pivotal Software,
> Inc.’s (Pivotal) Pivotal GemFireⓇ codebase into the Apache Software
> Foundation (ASF) in order to build a vibrant, diverse and
> self-governed open source community around the technology. Pivotal
> will continue to market and sell Pivotal GemFire based on Geode. Geode
> and Pivotal GemFire will be managed separately. This proposal covers
> the Geode source code (mainly written in Java), Geode documentation
> and other materials currently available on GitHub.
> 
> While Geode is our primary choice for a name of the project, in order
> to facilitate PODLINGNAMESEARCH we have come up with two alternatives:
>  * Haptic
>  * FIG
> 
> == Background ==
> GemFire is an extremely mature and robust product that can trace its
> legacy all the way back to one of the first Object Databases for
> Smalltalk: GemStone. The GemFire code base has been maintained by the
> same group of engineers as a closed source project. Because of that,
> even though the engineers behind GemFire are the de-facto knowledge
> leaders for distributed in-memory management, they have had little
> exposure to the open source governance process.The original
> company developing GemStone and GemFire was acquired by VMWare in 2010
> and later spun off as part of Pivotal Software in 2013. Today GemFire
> is used by over 600 enterprise customers. An example deployment
> includes China National Railways that uses Pivotal GemFire to run
> railway ticketing for the entire country of China with a 10 node
> cluster that manages 2 gigabytes "hot data" in memory, and 10 backup
> nodes for high availability and elastic scale.
> 
> == Rationale ==
> Modern-day data management architectures require a robust in-memory
> data grid solution to handle a variety of use cases, ranging from
> enterprise-wide caching to real-time transactional applications at
> scale. In addition, as memory size and network bandwidth growth
> continues to outpace those of disk, the importance of managing large
> pools of RAM at scale increases. It is essential to innovate at the
> same pace and Pivotal strongly believes that in the Big Data space,
> this can be optimally achieved through a vibrant, diverse,
> self-governed community collectively innovating around a single
> codebase while at the same time cross-pollinating with various other
> data management communities. ASF is the ideal place to meet these
> ambitious goals.
> 
> == Initial Goals ==
> Our initial goals are to bring Geode into the ASF, transition internal
> engineering processes into the open, and foster a collaborative
> development model according to the "Apache Way." Pivotal plans to
> develop new functionality in an open, community-driven way. To get
> there, the existing internal build, test and release processes will be
> refactored to support open development.
> 
> == Current Status ==
> Currently, the project code base is licensed for evaluation purposes
> and is available for download from Pivotal.io
> (https://network.pivotal.io/products/project-geode). The documentation
> and wiki pages are available as public GitHub repositories under
> Project Geode organization on GitHub
> (https://github.com/project-geode). Although Pivotal GemFire was
> developed as a proprietary, closed-source product, the internal
> engineering practices adopted by the development team lend themselves
> well to an open, collaborative and meritocratic environment.
> 
> The Pivotal GemFire team has always focused on building a robust end
> user community of paying and non-paying customers. The existing
> documentation along with StackOverflow and other similar forums are
> expected to facilitate conversions between our existing users so as to
> transform them into

Re: [VOTE} Climate Model Diagnostic Analyzer

[Suresh Marru]

+ 1 (binding).

Suresh

> On Apr 19, 2015, at 1:00 AM, Mattmann, Chris A (3980) 
>  wrote:
> 
> OK all, discussion has died down, we have 3 mentors, I think it’s
> time to proceed to a VOTE.
> 
> I am calling a VOTE now to accept the Climate Model Diagnostic
> Analyzer (CMDA) into the Apache Incubator. The VOTE is open for
> at least the next 72 hours:
> 
> [ ] +1 Accept Apache Climate Model Diagnostic Analyzer into the Apache
> Incubator.
> [ ] +0 Abstain.
> [ ] -1 Don’t accept Apache Climate Model Diagnostic Analyzer into the
> Apache Incubator
> because…
> 
> I’ll try and close the VOTE out on Friday.
> 
> Of course I am +1!
> 
> P.S. the text of the latest wiki proposal is pasted below:
> 
> Cheers,
> Chris
> 
> 
> = Apache ClimateModelDiagnosticAnalyzer Proposal =
> 
> == Abstract ==
> 
> The Climate Model Diagnostic Analyzer (CMDA) provides web services for
> multi-aspect physics-based and phenomenon-oriented climate model
> performance evaluation and diagnosis through the comprehensive and
> synergistic use of multiple observational data, reanalysis data, and model
> outputs.
> 
> == Proposal ==
> 
> The proposed web-based tools let users display, analyze, and download
> earth science data interactively. These tools help scientists quickly
> examine data to identify specific features, e.g., trends, geographical
> distributions, etc., and determine whether a further study is needed. All
> of the tools are designed and implemented to be general so that data from
> models, observation, and reanalysis are processed and displayed in a
> unified way to facilitate fair comparisons. The services prepare and
> display data as a colored map or an X-Y plot and allow users to download
> the analyzed data. Basic visual capabilities include 1) displaying
> two-dimensional variable as a map, zonal mean, and time series 2)
> displaying three-dimensional variable’s zonal mean, a two-dimensional
> slice at a specific altitude, and a vertical profile. General analysis can
> be done using the difference, scatter plot, and conditional sampling
> services. All the tools support display options for using linear or
> logarithmic scales and allow users to specify a temporal range and months
> in a year. The source/input datasets for these tools are CMIP5 model
> outputs, Obs4MIP observational datasets, and ECMWF reanalysis datasets.
> They are stored on the server and are selectable by a user through the web
> services.
> 
> === Service descriptions ===
> 
> 1. '''Two dimensional variable services'''
> 
> * Map of two-dimensional variable:  This services displays a two
> dimensional variable as a colored longitude and latitude map with values
> represented by a color scheme. Longitude and latitude ranges can be
> specified to magnify a specific region.
> 
> * Two dimensional variable zonal mean:  This service plots the zonal mean
> value of a two-dimensional variable as a function of the latitude in terms
> of an X-Y plot.
> 
> * Two dimensional variable time series:  This service displays the average
> of a two-dimensional variable over the specific region as function of time
> as an X-Y plot.
> 
> 2. '''Three dimensional variable services'''
> 
> * Map of a two dimensional slice of a three-dimensional variable:  This
> service displays a two-dimensional slice of a three-dimensional variable
> at a specific altitude as a colored longitude and latitude map with values
> represented by a color scheme.
> 
> * Three dimensional zonal mean:  Zonal mean of the specified
> three-dimensional variable is computed and displayed as a colored
> altitude-latitude map.
> 
> * Vertical profile of a three-dimensional variable:  Compute the area
> weighted average of a three-dimensional variable over the specified region
> and display the average as function of pressure level (altitude) as an X-Y
> plot.
> 
> 3. '''General services'''
> 
> * Difference of two variables:  This service displays the differences
> between the two variables, which can be either a two dimensional variable
> or a slice of a three-dimensional variable at a specified altitude as
> colored longitude and latitude maps
> 
> * Scatter and histogram plots of two variables:  This service displays the
> scatter plot (X-Y plot) between two specified variables and the histograms
> of the two variables. The number of samples can be specified and the
> correlation is computed. The two variables can be either a two-dimensional
> variable or a slice of a three-dimensional variable at a specific altitude.
> 
> * Conditional sampling:  This service lets user to sort a physical
> quantity of two or dimensions according to the values of another variable
> (environmental condition, e.g. SST) which may be a two-dimensional
> variable or a slice of a three-dimensional variable at a specific
> altitude. For a two dimensional quantity, the plot is displayed an X-Y
> plot, and for a two-dimensional quantity, plot is displayed as a
> colored-map.
> 
> 
> == Background and Rationale ==
> 

Re: [VOTE] Accept Taverna into the Apache Incubator

[Suresh Marru]

+ 1 (binding).

Suresh

@Andy a typo, "+1 accept Lens in the Incubator” -> “+1 accept taverna in the 
Incubator”.

On Oct 16, 2014, at 11:54 AM, Andy Seaborne  wrote:

> Following the discussion earlier in the thread:
> 
> https://www.mail-archive.com/general@incubator.apache.org/msg45241.html
> 
> I would like to call a Vote for accepting Taverna as a new incubator project.
> 
> The proposal is available at:
> 
> https://wiki.apache.org/incubator/TavernaProposal
> 
> Vote is open until at least Sunday, 19th October 2014, 23:59:00 UTC
> 
> [ ] +1 accept Lens in the Incubator
> [ ] ±0
> [ ] -1 because...
> 
> Only Votes from Incubator PMC members are binding, but everyone is welcome to 
> contribute to the process.
> 
>   Andy
> 
> -
> 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] Taverna workflow

[Suresh Marru]

Hi Stian,

Thank you for very nice elaborations. I really liked your honest views on where 
things are and where you want to be. As you might have experiences with Jena 
and other projects, apache is about community. It will take significant work to 
get pass the current tone of "us vs them" to “we". But you are on a great 
start. 

Also, Taverna with a long history will have to be ready for the challenge to 
build on the positives and overcome the “manchester - do it for me” inertia 
(from a core community building perspective). 

If you need a mentor, count me in. I actively contribute to Apache Airavata, 
and will be happy to bring our experiences from a similar journey. Infact Ross 
queried on airavata lists few years ago about potential taverna move to 
airavata/apache(Ross mentioned it further in this thread), good to see finally 
its happening. Integrating plugin community into the apache project (once its 
voted in) seems to be a low hanging fruit to diversify. 

David questions are right on. Two things you may want to consider addressing 
before you call for a vote are: listing of non-apache compatible license in the 
proposal and having adequate rights to change the license to Apache V2. 

Not a blocker for the proposal and voting, but a blocker for importing the code 
will be to have on file the University signed CCLA/SGA to donate the code. 

Echoing Chris, A hearty welcome!! 

Suresh

On Sep 25, 2014, at 12:34 PM, David Nalley  wrote:

>> 
>>> * Do you have any third party dependencies in the Taverna core that have
>>> incompatible licenses (like GPL)?
>> 
>> Unfortunately we do have a few of those, yes - the fact that we have
>> to move away from those was one of the things that we discussed a lot
>> in the Taverna community.
>> 
> 
> Can you make sure a comprehensive list of those currently incompatible
> list of dependencies is included in your proposal.
> 
>> 
>> Taverna 2 is licensed as LGPL 2.1, which meant we could use several
>> LGPL libraries like Hibernate and RShell. Hibernate can be replaced by
>> other JPA providers (with some code update to remove Hibernate
>> specific calls), while the RShell support would have to be moved out
>> to an separately installable plugin.
>> 
> 
> Do you have adequate rights to change the license wholesale?
> 
>> 
>> The Astronomy edition of Taverna includes a plugin called
>> AstroTaverna, which is GPL3 due to its inclusion of the Topcat and
>> STILTS dependencies.
>> 
>> The AstroTaverna community was therefore a bit sceptical about moving
>> to Apache - but we concluded that as they would keep maintaining
>> AstroTaverna as standalone plugins and instead of having multiple
>> downloads for different editions, with Taverna 3 move to a "Start
>> screen" that installs plugins from possibly third-party sites (Eclipse
>> style).
>> 
>> http://smtp.iaa.es/pipermail/astrotaverna-users/20140529/thread.html
>> 
>> 
>> Here luckily our plugin system (OSGi) will help us out - so those bits
>> that truly depend on GPL or LGPL would have to be maintained outside
>> Apache.  What perhaps we need to prepare a bit clearer is exactly
>> which plugins will be in the Apache transfer, and which would stay
>> outside.
>> 
>> 
> 
> This sounds like fragmenting your existing community before you really
> even get started. I believe the ASF is a great place, but I am not
> convinced it's the best place for everyone.
> 
>> The Taverna Workbench installers currently include platform-specific
>> binaries of OpenJDK 7, which is licensed under GPL 2 with classpath
>> exception. It is likely that under Apache we could not distribute
>> OpenJDK - but perhaps it would instead be allowed to distribute the
>> normal JDK binaries? (For Taverna 2 we did not distribute the normal
>> JDK as it can be seen as incompatible with GPL, which LGPL can be
>> upgraded to).  Do you know of any Apache projects that do this, like
>> perhaps OpenOffice?
>> 
>> An alternative is for the installer to download JDK on demand - but
>> would that require the installer itself (currently Install4j) to be
>> replaced?
>> 
>> 
>>> * Would you like developer-contributed plugins to be covered within a future
>>> "Apache Taverna" project?
>> 
>> As we've seen, keeping plugin developers on the "outside" of the
>> project has isolated them from the core development. We would
>> therefore like to encourage any new plugin developers to eventually
>> make their plugin a part of an Apache Taverna project - as we have
>> done historically with successful plugins. Apache's use of CLAs is I
>> must admit a bit of a hindrance to this as opposed to the Github
>> Laissez-faire style - - it has kept myself away from Apache projects
>> earlier when my suggested patch was deemed "significant" - yet the
>> legal department of the University spent 8 months reviewing that patch
>> and Apache's CLA before finally signing.
>> 
>> Yet we consider Taverna to be such a mature project that we want IP
>> and licensing to be done corre

Re: [Proposal] Taverna workflow

[Suresh Marru]

Hi Sitan,

I am also interested in knowing your responses to some of the questions below.

Looking through this list archives you will find that the issue of homogenous 
developers comes up every now and then. Its a welcoming move from Taverna team 
to pursue ASF as a potential home, but its important to understand on plans of 
diversifying core development beyond University of Manchester. 

Suresh

On Sep 23, 2014, at 1:54 PM, Marlon Pierce  wrote:

> Thanks, Stian, for submitting a well-developed proposal and for your interest 
> in Apache. I have a few questions:
> 
> * Can you say more about why you want to take Taverna to the ASF?
> 
> * What is your strategy for increasing the diversity of your committer base?
> 
> * Do you have any third party dependencies in the Taverna core that have 
> incompatible licenses (like GPL)?
> 
> * Would you like developer-contributed plugins to be covered within a future 
> "Apache Taverna" project?
> 
> My main goal here is to give the Incubator community a little more background 
> and foster discussion, which will be useful in attracting mentors, so don't 
> worry about "right" or "wrong" answers.
> 
> Marlon
> 
> On 9/23/14, 8:43 AM, Stian Soiland-Reyes wrote:
>> I hereby present the Apache Incubator proposal for the project Taverna.
>> 
>> 
>> Also available in rich text in the Taverna wiki (with more hyperlinks!):
>> 
>> http://dev.mygrid.org.uk/wiki/display/developer/Taverna+incubator+proposal
>> 
>> (Could someone grant me access to edit the Incubator wiki pages? My
>> wiki username is soilandreyes)
>> 
>> 
>> 
>> 
>> # Abstract
>> 
>> Taverna is an open source and domain-independent suite of tools used
>> to design and execute data-driven workflows.
>> 
>> 
>> # Proposal
>> 
>> The Taverna suite includes:
>> 
>> * Taverna Workbench, a Java-based desktop application for graphically
>> composing, editing and executing workflows of distributed web services
>> and local tools
>> * Taverna Commandline Tool which allows repeated execution of
>> parameterized workflow definitions
>> * Taverna Server provides a REST and SOAP API for executing workflows
>> * Taverna Player is a Ruby-based web interface towards the Server,
>> providing a high-level view of workflow executions and their results,
>> and allows further integrations with Ruby on Rails applications.
>> 
>> Taverna can browse and combine different service types, allowing
>> workflows to integrate steps of arbitrary REST and SOAP web services
>> with command line tools (local and SSH), scripts (Beanshell, R,
>> Jython) and finally visualize the results.
>> 
>> The goal of the Taverna suite is to help researchers to access
>> distributed datasets and processing capabilities by the construction
>> of pipelines, and also to simplify the execution of  these pipelines
>> in various environments.
>> 
>> The Taverna suite of products is already successful and in wide-use
>> across different domains. The software is currently licensed as LGPL
>> 2.1, with copyright owned by University of Manchester. External
>> contributors have all signed Apache-like CLAs.
>> 
>> 
>> # Background
>> 
>> Taverna workflows coordinate inputs and outputs between computational
>> processes and Web Services. The workflow is designed in a graphical
>> interface which shows the workflow as a series of boxes and arrows;
>> representing processes and their data connections. The different
>> processes in a workflow can be command line tools, REST and WSDL Web
>> Services; which are used for combining steps such as data acquisition,
>> filtering, cleaning, integrating, analysis and visualization. Taverna
>> calls these processes "services", as they generally are provided by
>> remote (third-party) servers.
>> 
>> These kind of computational workflows, also known as pipelines and
>> dataflows, focus on the movement of data rather than the execution
>> order of the underlying processes. Features such as implicit
>> iterations (where an input list of values causes multiple process
>> executions) and parallel invocations (independent processes are
>> executed as soon as their data is available) are intrinsic to a
>> dataflow system, not requiring any particular constructs by the
>> workflow designer.
>> 
>> As a visual programming environment, workflows aids collaboration and
>> reuse of workflows. At the highest level, a workflow represents the
>> conceptual level of an analysis, allowing understanding, discussion
>> and communication of the overall analysis protocol. More detail can be
>> revealed and modified for individual steps. At the individual process
>> level, the workflow defines execution specifics such as operations,
>> parameters and command line tools.
>> 
>> Sharing of the workflow definitions allows re-use and re-purposing of
>> the computational analysis. During workflow execution, provenance can
>> be collected from every step, allowing deep inspection of intermediate
>> values for the purpose of debugging and validation.
>> 
>> 

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

[Suresh Marru]

+ 1 (binding).

Suresh

On Jun 19, 2014, at 10: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: [DISCUSS] json as new incubator project

[Suresh Marru]

If Fleece is decided as the name, you can probably remove or edit the “Project 
Name” section on the proposal. 

Suresh

On Jun 3, 2014, at 2:57 AM, Romain Manni-Bucau  wrote:

> FYI I renamed the proposal fleece and here is the proposal:
> https://wiki.apache.org/incubator/Fleece.
> 
> 
> 
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
> 
> 
> 2014-06-01 14:27 GMT+02:00 Romain Manni-Bucau :
> 
>> Ok,
>> 
>> removed antlr, think few things need review/test/etc (typically unicode is
>> not yet supported) but at least DoS attacks are controlled" normally.
>> 
>> Next step for me: get an idea of the performances
>> 
>> 
>> 
>> 
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>> 
>> 
>> 2014-06-01 13:13 GMT+02:00 Christian Grobmeier :
>> 
>> On 1 Jun 2014, at 12:21, Romain Manni-Bucau wrote:
>>> 
 Hi Christian,
 
 updated the proposal page according to your comments (added you as
>>> mentor
 for now and merged initial/core dev  parts).
 
 Will try to import noggit parser (actually I was in thr process of
>>> removing
 antlr which was mainly here to get started quickly so if noggit avoids
>>> me
 to rewrite a new state machine it will be very nice)
>>> 
>>> I keep fingers crossed. Not sure if it will help you though, but it is
>>> really
>>> fast in what it does.
>>> 
>>> Cheers
>>> 
>>> 
 
 
 Romain Manni-Bucau
 Twitter: @rmannibucau
 Blog: http://rmannibucau.wordpress.com/
 LinkedIn: http://fr.linkedin.com/in/rmannibucau
 Github: https://github.com/rmannibucau
 
 
 2014-06-01 10:46 GMT+02:00 Christian Grobmeier :
 
> On 1 Jun 2014, at 0:31, Justin Mclean wrote:
> 
> Hi,
>> 
>> About the name any proposition is welcomed. I though to "brace" BTW.
>>> 
>> 
>> Apache Argonaut sounds good but I assume that name is in common use so
>> perhaps Argus (the ship builder), or perhaps Fleece?
>> 
> 
> I actually once wrote an article called "Json and the golden fleece"
>>> (just
> in german),
> so I would like this reference too.
> 
> I was a little bit involved in that JSR (not very active to be honest)
>>> and
> developed
> a JSON component myself before the JSR was in the making, so I have an
> interest in it.
> Unfortunately I have very limited time to help actively. Anyway if
>>> there
> is trouble
> to finding an additional mentor, I will step up.
> 
> On the proposal i see two sections called "initial committers" and one
> "core developer". I would like to suggest to remove the section "core
> developer" and on of the "initial committers" blocks.
> 
> I would like to also suggest to look into Noggit:
> http://svn.apache.org/repos/asf/labs/noggit/
> which is more or less used in a later form in Solr.
> 
> As sponsoring entity it might even make sense to look at Apache
>>> Commons,
> as the component will be small.
> It would also relax the naming problem, as it would most likely be
>>> named
> Apache Commons Json then.
> 
> Cheers,
> Christian
> 
> 
> 
> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> 
> ---
> http://www.grobmeier.de
> The Zen Programmer: http://bit.ly/12lC6DL
> @grobmeier
> GPG: 0xA5CC90DB
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 
>>> 
>>> 
>>> ---
>>> http://www.grobmeier.de
>>> The Zen Programmer: http://bit.ly/12lC6DL
>>> @grobmeier
>>> GPG: 0xA5CC90DB
>>> 
>>> -
>>> 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

[RESULT] [VOTE] Graduate Apache Stratos as a TLP

[Suresh Marru]

Thanks every one for voting, this VOTE is now closed with the following tally:

+ 1’s
Suresh Marru *
Steve Loughran *
Chip Childers *
Lakmal Warusawithana
Sanjiva Weerawarana *
Jake Farrell *
Lahiru Sandaruwan
Noah Slater *
Isuru Perera
Melan Nimesh
Imesh Gunaratne
Nirmal Fernando
Afkham Azeez *
Deepal jayasinghe *
Alan Cabrera *
Paul Fremantle *

* Indicated a IPMC member.

No -1’s and 0’s.

With a positive endorsement from IPMC, I will now submit this
recommendation for board consideration.

Cheers,
Suresh

P.S Please excuse if this is duplicate, I couldn't tell if my previous email 
made it during email downtimes. 

On May 4, 2014, at 3:31 AM, Paul Fremantle  wrote:

> +1
> 
> Paul
> 
> 
> On Sat, May 3, 2014 at 7:19 PM, Alan Cabrera  wrote:
> 
>> +1 - binding
>> 
>> 
>> Regards,
>> Alan
>> 
>> On May 1, 2014, at 8:03 PM, Suresh Marru  wrote:
>> 
>>> Please VOTE to indicate if Apache Stratos is ready to graduate as a Top
>> Level Project. The board resolution is included below.
>>> 
>>> [ ] +1 Graduate Apache Stratos as a TLP
>>> [ ] +0 Don't care.
>>> [ ] -1 Don't graduate Apache Stratos as a TLP because…
>>> 
>>> Cheers,
>>> Suresh
>> 
>> 
> 
> 
> -- 
> Paul Fremantle
> Co-Founder and CTO, WSO2
> Member of the Apache Software Foundation
> OASIS WS-RX TC Co-chair
> 
> blog: http://pzf.fremantle.org
> twitter: @pzfreo


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

[VOTE] Graduate Apache Stratos as a TLP

[Suresh Marru]

Please VOTE to indicate if Apache Stratos is ready to graduate as a Top Level 
Project. The board resolution is included below. 

[ ] +1 Graduate Apache Stratos as a TLP
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Stratos as a TLP because…

Cheers,
Suresh

=== Board Resolution ==

Establish the Apache Stratos 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 Stratos Project",
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

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

  Ant Elder (antel...@apache.org)
  Paul Fremantle (p...@apache.org)
  Jonathan Marsh (jonathanma...@apache.org)
  Afkham Azeez (az...@apache.org)
  Peter Linnell (plinn...@apache.org)
  Lakmal Warusawithana (lak...@apache.org)
  Damitha Kumarage (dami...@apache.org)
  Samisa Abeysinghe (sam...@apache.org)
  Nirmal Fernando (nirmal070...@apache.org)
  Sajith Kariyawasam (saj...@apache.org)
  Lahiru Sandaruwan (lahi...@apache.org)
  Isuru Haththotuwa (isu...@apache.org)
  Madhura Mendis (madh...@apache.org)
  Mariangela Hills (mariang...@apache.org)
  Suresh Marru (sma...@apache.org)
  Chip Childers (chipchild...@apache.org)
  Joe Brockmeier (j...@apache.org)
  Noah Slater (nsla...@apache.org)
  Nandana Mihindukulasooriya (nand...@apache.org)
  Isuru Perera (is...@apache.org)
  Reka Thirunavakurussu (r...@apache.org)
  Deepal Jayasinghe (dee...@apache.org)
  Debo Dutta (dedu...@apache.org)
  Udara Liyanage (ud...@apache.org)
  Manula Chathurika Thantriwatte (man...@apache.org)
  Imesh Gunaratne (im...@apache.org)
  Pradeep Fernando (pradee...@apache.org)
  Chris Snow (cs...@apache.org)
  Melan Nimesh (me...@apache.org)
 Jason Daly (jasondaly...@apache.org)
 Chanaka Jayasena (chan...@apache.org)
 Jeffrey Nguyen (jeffr...@apache.org)
 Anh Tu Nguyen (t...@apache.org)

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

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

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Stratos 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] Graduate Apache Stratos as a TLP

[Suresh Marru]

On May 1, 2014, at 10:36 AM, Marlon Pierce  wrote:

> I also do not wish to be on the PMC after graduation [1]

ACK. Will remove from the vote email.

Suresh

> 
> Marlon
> 
> [1]
> http://mail-archives.apache.org/mod_mbox/incubator-stratos-dev/201404.mbox/%3C533C0454.3000304%40iu.edu%3E
> 
> On 5/1/14 10:21 AM, Suresh Marru wrote:
>> Stratos PPMC,
>> 
>> Can you verify if all the names listed are indeed PMC? I would assume so 
>> since stratos has been following PPMC=Committer. 
>> 
>> Suresh
>> 
>> On May 1, 2014, at 10:15 AM, sebb  wrote:
>> 
>>> This reminds me:
>>> 
>>> I assume the podling is aware that the names listed in the proposed
>>> board resolution will become the initial PMC?
>>> i.e. everyone listed in the resolution will become a PMC member (and 
>>> committer).
>>> 
>>> There was at least one recent graduation where this was not understood.
>>> They expected some of the names to have committer status but not be on the 
>>> PMC.
>>> 
>>> 
>>> On 29 April 2014 11:27, Mohammad Noureldin  wrote:
>>>> Hi Suresh
>>>> 
>>>>  Thanks a lot for including me in the list of members when graduating.
>>>> Unfortunately I didn't have enough time to help and I don't think that will
>>>> change soon enough on the level that I can consider myself as an active
>>>> member, hence I would like my name to be removed
>>>> 
>>>> Good luck with the graduation procedure and many thanks again for bringing
>>>> such project to the ASF
>>>> +1 from me
>>>> 
>>>> Azeez
>>>> 
>>>> 
>>>> On Mon, Apr 28, 2014 at 6:20 PM, Suresh Marru  wrote:
>>>> 
>>>>> Hi All,
>>>>> 
>>>>> Since entering Incubation in June 2013, the stratos podling has evolved
>>>>> and is now ready to self-govern. The community has extensively debated
>>>>> graduation readiness [1] and overwhelmingly voted positively [2]. As far
>>>> as
>>>>> I can tell the project status is up to date [3]. The name search has
>>>>> concluded with approval [4] and trademark/website/branding  have been
>>>>> discussed at various times and the donor (WSO2) has willingly co-operated
>>>>> and all queries were satisfactorily resolved (please refer to dev and
>>>>> private list discussions).
>>>>> 
>>>>> This thread is to start a IPMC discussion on Stratos TLP readiness and
>>>>> identity and address any remaining issues (if exist). Below is the draft
>>>>> resolution.
>>>>> 
>>>>> I want to take a tangent and convey my personal appreciation for hands-on
>>>>> and diligent mentoring from Noah, Chip and Ant (especially Noah). I have
>>>>> learnt some more in the process and I recommend first time mentors to surf
>>>>> startos lists for precedence.
>>>>> 
>>>>> Cheers,
>>>>> Suresh
>>>>> (Stratos Mentor)
>>>>> 
>>>>> [1] - http://markmail.org/thread/6tm4bh6rezcxxy45
>>>>> [2] - http://markmail.org/message/gqxp7t4ylatfahgz
>>>>> [3] - http://incubator.apache.org/projects/stratos.html
>>>>> [4] - https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-45
>>>>> 
>>>>> 
>>>>> === Board Resolution ==
>>>>> 
>>>>> Establish the Apache Stratos 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 Stratos Project",
>>>>> be and hereby is established pursuant to Bylaws of the
>>>>> Foundation; and be it further
>>>>> 
>>>>> RESOLVED, that the Apache Stratos Project be and hereby is
>

Re: [DISCUSS] Graduate Apache Stratos as a TLP

[Suresh Marru]

On May 1, 2014, at 10:26 AM, sebb  wrote:

> On 1 May 2014 15:16, Suresh Marru  wrote:
>> Since there were no issues raised on the DISCUSS thread, I will start the 
>> graduation vote now.
> 
> There was 1 issue:
> 
> Mohammad Noureldin does not want to be part of the initial PMC
> 
> Also I asked if the podling is aware that the initial PMC is as per
> the resolution.

Thanks for the alert Sebb, our emails criss-crossed. I removed Mohammad 
Noureldin from the Vote email draft and waiting for podling to confirm on your 
initial PMC query.

Suresh

> 
>> Suresh
>> 
>> On Apr 29, 2014, at 11:07 AM, Sanjiva Weerawarana  wrote:
>> 
>>> +1 to graduate.
>>> 
>>> I'd like to echo Paul's sentiments .. thanks for the support and nudging!
>>> 
>>> Sanjiva.
>>> 
>>> 
>>> On Tue, Apr 29, 2014 at 3:40 PM, Paul Fremantle  wrote:
>>> 
>>>> I'd like to add my thanks to the mentors. Very useful and effective and
>>>> hard working on behalf of Stratos.
>>>> 
>>>> I support this: +1.
>>>> 
>>>> Paul
>>>> 
>>>> 
>>>> On Tue, Apr 29, 2014 at 10:02 AM, Afkham Azeez  wrote:
>>>> 
>>>>> +1 from me
>>>>> 
>>>>> Azeez
>>>>> 
>>>>> 
>>>>> On Mon, Apr 28, 2014 at 6:20 PM, Suresh Marru  wrote:
>>>>> 
>>>>>> Hi All,
>>>>>> 
>>>>>> Since entering Incubation in June 2013, the stratos podling has evolved
>>>>>> and is now ready to self-govern. The community has extensively debated
>>>>>> graduation readiness [1] and overwhelmingly voted positively [2]. As
>>>> far
>>>>> as
>>>>>> I can tell the project status is up to date [3]. The name search has
>>>>>> concluded with approval [4] and trademark/website/branding  have been
>>>>>> discussed at various times and the donor (WSO2) has willingly
>>>> co-operated
>>>>>> and all queries were satisfactorily resolved (please refer to dev and
>>>>>> private list discussions).
>>>>>> 
>>>>>> This thread is to start a IPMC discussion on Stratos TLP readiness and
>>>>>> identity and address any remaining issues (if exist). Below is the
>>>> draft
>>>>>> resolution.
>>>>>> 
>>>>>> I want to take a tangent and convey my personal appreciation for
>>>> hands-on
>>>>>> and diligent mentoring from Noah, Chip and Ant (especially Noah). I
>>>> have
>>>>>> learnt some more in the process and I recommend first time mentors to
>>>>> surf
>>>>>> startos lists for precedence.
>>>>>> 
>>>>>> Cheers,
>>>>>> Suresh
>>>>>> (Stratos Mentor)
>>>>>> 
>>>>>> [1] - http://markmail.org/thread/6tm4bh6rezcxxy45
>>>>>> [2] - http://markmail.org/message/gqxp7t4ylatfahgz
>>>>>> [3] - http://incubator.apache.org/projects/stratos.html
>>>>>> [4] - https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-45
>>>>>> 
>>>>>> 
>>>>>> === Board Resolution ==
>>>>>> 
>>>>>> Establish the Apache Stratos 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 Stratos Project",
>>>>>> be and hereby is established pursuant to Bylaws of the
>>>>>> Foundation; and be it further
>>>>>> 
>>>>>> RESOLVED, that the Apache Stratos Project be and hereby is
>>>>>> responsible for the creation and maintenance of software
&g

Re: [DISCUSS] Graduate Apache Stratos as a TLP

[Suresh Marru]

Stratos PPMC,

Can you verify if all the names listed are indeed PMC? I would assume so since 
stratos has been following PPMC=Committer. 

Suresh

On May 1, 2014, at 10:15 AM, sebb  wrote:

> This reminds me:
> 
> I assume the podling is aware that the names listed in the proposed
> board resolution will become the initial PMC?
> i.e. everyone listed in the resolution will become a PMC member (and 
> committer).
> 
> There was at least one recent graduation where this was not understood.
> They expected some of the names to have committer status but not be on the 
> PMC.
> 
> 
> On 29 April 2014 11:27, Mohammad Noureldin  wrote:
>> Hi Suresh
>> 
>>   Thanks a lot for including me in the list of members when graduating.
>> Unfortunately I didn't have enough time to help and I don't think that will
>> change soon enough on the level that I can consider myself as an active
>> member, hence I would like my name to be removed
>> 
>> Good luck with the graduation procedure and many thanks again for bringing
>> such project to the ASF
>> +1 from me
>> 
>> Azeez
>> 
>> 
>> On Mon, Apr 28, 2014 at 6:20 PM, Suresh Marru  wrote:
>> 
>>> Hi All,
>>> 
>>> Since entering Incubation in June 2013, the stratos podling has evolved
>>> and is now ready to self-govern. The community has extensively debated
>>> graduation readiness [1] and overwhelmingly voted positively [2]. As far
>> as
>>> I can tell the project status is up to date [3]. The name search has
>>> concluded with approval [4] and trademark/website/branding  have been
>>> discussed at various times and the donor (WSO2) has willingly co-operated
>>> and all queries were satisfactorily resolved (please refer to dev and
>>> private list discussions).
>>> 
>>> This thread is to start a IPMC discussion on Stratos TLP readiness and
>>> identity and address any remaining issues (if exist). Below is the draft
>>> resolution.
>>> 
>>> I want to take a tangent and convey my personal appreciation for hands-on
>>> and diligent mentoring from Noah, Chip and Ant (especially Noah). I have
>>> learnt some more in the process and I recommend first time mentors to surf
>>> startos lists for precedence.
>>> 
>>> Cheers,
>>> Suresh
>>> (Stratos Mentor)
>>> 
>>> [1] - http://markmail.org/thread/6tm4bh6rezcxxy45
>>> [2] - http://markmail.org/message/gqxp7t4ylatfahgz
>>> [3] - http://incubator.apache.org/projects/stratos.html
>>> [4] - https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-45
>>> 
>>> 
>>> === Board Resolution ==
>>> 
>>> Establish the Apache Stratos 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 Stratos Project",
>>>  be and hereby is established pursuant to Bylaws of the
>>>  Foundation; and be it further
>>> 
>>>  RESOLVED, that the Apache Stratos 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, Stratos" 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 Stratos Project, and to have primary responsibility
>>>  for management of the projects within the scope of
>>>  responsibility of the Apache Stratos 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 Stratos Project:
>>> 
>>>   Mohammad Nour (mn...@apache.org)
>>>   Ant Elder (antel...@apache.org)
>>>   Paul Fremantle (p

Re: [DISCUSS] Graduate Apache Stratos as a TLP

[Suresh Marru]

Since there were no issues raised on the DISCUSS thread, I will start the 
graduation vote now.

Suresh

On Apr 29, 2014, at 11:07 AM, Sanjiva Weerawarana  wrote:

> +1 to graduate.
> 
> I'd like to echo Paul's sentiments .. thanks for the support and nudging!
> 
> Sanjiva.
> 
> 
> On Tue, Apr 29, 2014 at 3:40 PM, Paul Fremantle  wrote:
> 
>> I'd like to add my thanks to the mentors. Very useful and effective and
>> hard working on behalf of Stratos.
>> 
>> I support this: +1.
>> 
>> Paul
>> 
>> 
>> On Tue, Apr 29, 2014 at 10:02 AM, Afkham Azeez  wrote:
>> 
>>> +1 from me
>>> 
>>> Azeez
>>> 
>>> 
>>> On Mon, Apr 28, 2014 at 6:20 PM, Suresh Marru  wrote:
>>> 
>>>> Hi All,
>>>> 
>>>> Since entering Incubation in June 2013, the stratos podling has evolved
>>>> and is now ready to self-govern. The community has extensively debated
>>>> graduation readiness [1] and overwhelmingly voted positively [2]. As
>> far
>>> as
>>>> I can tell the project status is up to date [3]. The name search has
>>>> concluded with approval [4] and trademark/website/branding  have been
>>>> discussed at various times and the donor (WSO2) has willingly
>> co-operated
>>>> and all queries were satisfactorily resolved (please refer to dev and
>>>> private list discussions).
>>>> 
>>>> This thread is to start a IPMC discussion on Stratos TLP readiness and
>>>> identity and address any remaining issues (if exist). Below is the
>> draft
>>>> resolution.
>>>> 
>>>> I want to take a tangent and convey my personal appreciation for
>> hands-on
>>>> and diligent mentoring from Noah, Chip and Ant (especially Noah). I
>> have
>>>> learnt some more in the process and I recommend first time mentors to
>>> surf
>>>> startos lists for precedence.
>>>> 
>>>> Cheers,
>>>> Suresh
>>>> (Stratos Mentor)
>>>> 
>>>> [1] - http://markmail.org/thread/6tm4bh6rezcxxy45
>>>> [2] - http://markmail.org/message/gqxp7t4ylatfahgz
>>>> [3] - http://incubator.apache.org/projects/stratos.html
>>>> [4] - https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-45
>>>> 
>>>> 
>>>> === Board Resolution ==
>>>> 
>>>> Establish the Apache Stratos 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 Stratos Project",
>>>>  be and hereby is established pursuant to Bylaws of the
>>>>  Foundation; and be it further
>>>> 
>>>>  RESOLVED, that the Apache Stratos 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, Stratos" 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 Stratos Project, and to have primary responsibility
>>>>  for management of the projects within the scope of
>>>>  responsibility of the Apache Stratos 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 Stratos Project:
>>>> 
>>>>   Mohammad Nour (mn...@apache.org)
>>>>   Ant Elder (antel...@apache.org)
>>>>   Paul Fremantle (p...@apache.org   )
>>>>   Jonathan Marsh (jonathanma...@apache.org)
>>>>   Afkh

Re: [VOTE] Release HDT version 0.0.1.incubating (RC3)

[Suresh Marru]

Hi Rahul,

+ 1 for the release. 

I found few non-blocking improvements you want to make for next release. I 
debated if they need to be fixed now, but creating JIRA’s and assuring to be 
fixed for next release should do.

* The NOTICE file has Eclipse icon and SLF4J license url’s, both of them are 
not needed. Please see [1] - “It is strongly recommended that the NOTICE 
contains only these legally important contents.”

* The src bundled the site, all .settings, .classpath, .project files. All 
these should be removed. Its not advised to use a eclipse checkout to bundle 
the source. 

* I do not see any maven artifacts being published, is this intentional? You 
can refer to [2] if this needs to be done. 

Suresh
[1] - 
http://incubator.apache.org/guides/releasemanagement.html#best-practice-notice
[2] - http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env

On Apr 18, 2014, at 10:48 AM, Rahul Sharma  wrote:

> Hi,
> 
> I would like to call for a vote for Apache Hadoop Development Tools
> (incubating), version 0.0.1.incubating. The vote has happened of the dev
> mailing list and the community has approved the forth release candidate(RC3)
> for Apache Hadoop Development Tools (incubating), version
> 0.0.1.incubating.The release has Zookeper and HDFS features from the
> *hadoop-eclipse-merge* codebase.The issues raised for previous release
> candidates have been addressed in this release.
> 
> Please vote on releasing this package as Apache Hadoop Development Tools
> 0.0.1.incubating.
> 
> [ ] +1 Release this package as Apache HDT 0.0.1.incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
> 
> PPMC Vote thread :
> *http://apache.markmail.org/message/pm73p3xxcgt4zz6e
> *
> 
> Vote Result :
> http://apache.markmail.org/message/ykycte3demsxnzz7
> 
> Source and binary files:
> http://people.apache.org/~rsharma/hdt-0.0.1.incubating-rc3/
> 
> The tag to be voted upon:
> https://git-wip-us.apache.org/repos/asf?p=incubator-hdt
> .git;a=commit;h=3672346b937b9cec029ac3e362f276ea64f1af92
> 
> PGP keys used to sign the release:
> https://dist.apache.org/repos/dist/dev/incubator/hdt/KEYS
> 
> Some guideline to verify release can be found at :
> http://apache.markmail.org/message/qj3srhvozapbwmq6
> 
> regards,
> Rahul


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

Re: [Vote] IPMC - Release Apache Stratos 4.0.0 - Incubating RC1

[Suresh Marru]

- 1, there are no incubator disclaimers among other concerns raised on the dev 
list.

I suggest to close this vote and take it back to the dev list.

Suresh

On Apr 30, 2014, at 2:36 AM, Imesh Gunaratne  wrote:

> Correction: Friday, May 2, 2014 at 11:30:00 PM PDT, Saturday, May 3, 2014
> at 12:00:00 Noon IST.
> 
> Thanks
> 
> 
> On Wed, Apr 30, 2014 at 12:02 PM, Imesh Gunaratne  wrote:
> 
>> Hi All,
>> 
>> This is the first release candidate of Apache Stratos 4.0.0-incubating.
>> 
>> This is the IPMC vote, the PPMC vote [1] passed with 9 binding +1s.
>> 
>> This release fixes the following issues:
>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12326291&styleName=Html&projectId=12314521
>> 
>> *** Please download, test and vote. The vote runs for 72 hours, until
>> Friday, May 2, 2014 at 11:30:00 PM PDT, Sunday, Saturday, May 3, 2014 at
>> 12:00:00 Noon IST.
>> 
>> Note that we are voting upon the source (tag), binaries are provided for
>> convenience.
>> 
>> *Source & binary distribution files:*
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/stratos/releases/4.0.0-incubating-rc1/
>> 
>> *Maven staging repo:*
>> https://repository.apache.org/content/repositories/orgapachestratos-1004/
>> 
>> *The tag to be voted upon:*
>> 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-stratos.git;a=tag;h=cd5f427d4c77380ae24c85971c3d7a1a1c4497b3
>> 
>> *Tree view of the tag:*
>> 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-stratos.git;a=tree;h=refs/tags/4.0.0-incubating-rc1;hb=refs/tags/4.0.0-incubating-rc1
>> 
>> Stratos KEYS file containing PGP keys we use to sign the release:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/stratos/releases/4.0.0-incubating-rc1/KEYS
>> 
>> *Testing procedure:*
>> https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Testing+Procedure
>> 
>> [1]
>> https://www.mail-archive.com/dev@stratos.incubator.apache.org/msg07871.html
>> 
>> [ ] +1
>> [ ] 0
>> [ ] -1 (explain why)
>> 
>> Thanks
>> 
>> 
>> 
>> --
>> Imesh Gunaratne
>> 
>> Technical Lead, WSO2
>> Committer & PPMC Member, Apache Stratos
>> 
> 
> 
> 
> -- 
> Imesh Gunaratne
> 
> Technical Lead, WSO2
> Committer & PPMC Member, Apache Stratos


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

Re: [VOTE] Release HDT version 0.0.1.incubating (RC3)

[Suresh Marru]

Hi Rahul,

Sorry for the impasse. I will review this release and vote accordingly.

Suresh

On Apr 28, 2014, at 10:46 AM, Rahul Sharma  wrote:

> Dear General,
> 
> The vote has already run for over 10 days but still  we are still short by
> 1 IPMC vote. We have been able to gather only 2 votes till date. I have
> already asked  a couple of times before but it did not work out. Now I am
> not sure how to proceed further. Can some one please help us out ?
> 
> regards
> Rahul
> 
> Guys, we are still short by 1 IPMC vote. Can someone help us out ?
> 
> regards
> Rahul
> Guys, we are still short by 1 IPMC vote. Can someone help us out ?
> 
> regards
> Rahul
> 
> 
> On Thu, Apr 24, 2014 at 10:52 AM, Rahul Sharma  wrote:
> 
>> Thanks Justin  for the feedback. We will address the issues going further.
>> 
>> We are still looking out for 1 more vote from IPMC.
>> 
>> thanks
>> Rahul
>> 
>> 
>> 
>> On Thu, Apr 24, 2014 at 4:42 AM, Justin Mclean 
>> wrote:
>> 
>>> Hi,
>>> 
>>> +1 (binding)
>>> 
>>> My issue seems to be out of memory/heap space related. Adding typical
>>> JAVA_OPT/MAVEN_OPTS settings to README in future releases could be helpful.
>>> 
>>> I also noticed a few warnings when building re runtime configuration.
>>> They can be fixed like so [1].
>>> 
>>> It may also be that the version number is missing from
>>> tycho-maven-plugin? [2].
>>> 
>>> Thanks,
>>> Justin
>>> 
>>> 1.
>>> http://wiki.eclipse.org/Tycho/Reference_Card#Target_runtime_environment
>>> 2. http://wiki.eclipse.org/Tycho/Reference_Card#Enabling_tycho
>>> -
>>> 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

[DISCUSS] Graduate Apache Stratos as a TLP

[Suresh Marru]

Hi All,

Since entering Incubation in June 2013, the stratos podling has evolved and is 
now ready to self-govern. The community has extensively debated graduation 
readiness [1] and overwhelmingly voted positively [2]. As far as I can tell the 
project status is up to date [3]. The name search has concluded with approval 
[4] and trademark/website/branding  have been discussed at various times and 
the donor (WSO2) has willingly co-operated and all queries were satisfactorily 
resolved (please refer to dev and private list discussions).

This thread is to start a IPMC discussion on Stratos TLP readiness and identity 
and address any remaining issues (if exist). Below is the draft resolution. 

I want to take a tangent and convey my personal appreciation for hands-on and 
diligent mentoring from Noah, Chip and Ant (especially Noah). I have learnt 
some more in the process and I recommend first time mentors to surf startos 
lists for precedence. 

Cheers,
Suresh 
(Stratos Mentor) 

[1] - http://markmail.org/thread/6tm4bh6rezcxxy45
[2] - http://markmail.org/message/gqxp7t4ylatfahgz
[3] - http://incubator.apache.org/projects/stratos.html
[4] - https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-45


=== Board Resolution ==

Establish the Apache Stratos 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 Stratos Project",
  be and hereby is established pursuant to Bylaws of the
  Foundation; and be it further

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

   Mohammad Nour (mn...@apache.org)
   Ant Elder (antel...@apache.org)
   Paul Fremantle (p...@apache.org  )
   Jonathan Marsh (jonathanma...@apache.org)
   Afkham Azeez (az...@apache.org)
   Peter Linnell (plinn...@apache.org)
   Lakmal Warusawithana (lak...@apache.org)
   Damitha Kumarage (dami...@apache.org)
   Samisa Abeysinghe (sam...@apache.org)
Nirmal Fernando (nirmal070...@apache.org)
Sajith Kariyawasam (saj...@apache.org)
   Lahiru Sandaruwan (lahi...@apache.org)
   Isuru Haththotuwa (isu...@apache.org)
Madhura Mendis (madh...@apache.org)
Mariangela Hills (mariang...@apache.org)
Marlon Pierce (mpie...@apache.org)
Suresh Marru (sma...@apache.org)
Chip Childers (chipchild...@apache.org)
Joe Brockmeier (j...@apache.org)
Noah Slater (nsla...@apache.org)
Nandana Mihindukulasooriya (nand...@apache.org)
Isuru Perera (is...@apache.org)
Reka Thirunavakurussu (r...@apache.org)
Deepal Jayasinghe (dee...@apache.org)
Debo Dutta (dedu...@apache.org)
Udara Liyanage (ud...@apache.org)
Manula Chathurika Thantriwatte (man...@apache.org)
Imesh Gunaratne (im...@apache.org)
Pradeep Fernando (pradee...@apache.org)
Chris Snow (cs...@apache.org)
Melan Nimesh (me...@apache.org)
Jason Daly (jasondaly...@apache.org)
Chanaka Jayasena (chan...@apache.org)
Jeffrey Nguyen (jeffr...@apache.org)
Anh Tu Nguyen (t...@apache.org)

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

  RESOLVED, that the Apac

Re: [VOTE] Accept Slider into the incubator

[Suresh Marru]

Champion on this proposal Vinod Kumar Vavilapalli doesn't seem to be on the
IPMC but since he is a member its just a customary to ask and get inducted.

Can this be addressed?

Suresh


On Thu, Apr 17, 2014 at 9:01 AM, Steve Loughran wrote:

> I'd like to call a vote on accepting Slider into the incubator
>
>
> https://wiki.apache.org/incubator/SliderProposal
>
> [ ] +1 Accept Slider into the Incubator
> [ ] +0 Indifferent to the acceptance of Slider
> [ ] -1 Do not accept Slider because …
>
>
> The vote will be open until Thursday April 24 13:00 UTC
>
> -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.
>

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

[Suresh Marru]

+ 1 (binding).

Suresh

On Feb 10, 2014, at 11:27 PM, Chris Mattmann  wrote:

> Hi Everyone,
> 
> This is a new VOTE to decide if Apache Spark 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.
> 
> Thanks!
> 
> [ ] +1 Graduate Apache Spark from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache Spark from the Incubator because..
> 
> Here is my +1 binding for graduation.
> 
> Cheers,
> Chris
> 
>  snip
> 
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the
> public, related to fast and flexible large-scale data analysis
> on clusters.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Spark Project", be
> and hereby is established pursuant to Bylaws of the Foundation;
> and be it further
> 
> RESOLVED, that the Apache Spark Project be and hereby is
> responsible for the creation and maintenance of software
> related to fast and flexible large-scale data analysis
> on clusters; and be it further RESOLVED, that the office
> of "Vice President, Apache Spark" be and hereby is created,
> the person holding such office to serve at the direction of
> the Board of Directors as the chair of the Apache Spark
> Project, and to have primary responsibility for management
> of the projects within the scope of responsibility
> of the Apache Spark Project; and be it further
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Spark Project:
> 
> * Mosharaf Chowdhury 
> * Jason Dai 
> * Tathagata Das 
> * Ankur Dave 
> * Aaron Davidson 
> * Thomas Dudziak 
> * Robert Evans 
> * Thomas Graves 
> * Andy Konwinski 
> * Stephen Haberman 
> * Mark Hamstra 
> * Shane Huang 
> * Ryan LeCompte 
> * Haoyuan Li 
> * Sean McNamara 
> * Mridul Muralidharam 
> * Kay Ousterhout 
> * Nick Pentreath 
> * Imran Rashid 
> * Charles Reiss 
> * Josh Rosen 
> * Prashant Sharma 
> * Ram Sriharsha 
> * Shivaram Venkataraman 
> * Patrick Wendell 
> * Andrew Xia 
> * Reynold Xin 
> * Matei Zaharia 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matei Zaharia be
> appointed to the office of Vice President, Apache Spark, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification, or
> until a successor is appointed; and be it further
> 
> RESOLVED, that the Apache Spark Project be and hereby is
> tasked with the migration and rationalization of the Apache
> Incubator Spark podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Spark podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
> 
> 
> 
> 
> 


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

Re: Github pull request hooks

[Suresh Marru]

Hi Daniel (and Sergio and others for all the comments),

You rock for such a quick implementation. I think we would like to have enable 
this for Airavata projects. I will run it by the PMC and if we have a general 
agreement I will create a INFRA jira.

Thanks again,
Suresh

On Feb 10, 2014, at 10:05 AM, Daniel Gruno  wrote:

> Oh well, I went ahead and implemented this :3
> 
> GitHub comments that either include a JIRA ticket name or are made on a
> PR whose title includes a JIRA ticket name, will result in a comment
> being made in that specific JIRA ticket, similar to what is posted on
> the ML. This will result in some double posting, as you'll get both a
> GitHub email and a JIRA email on the ML when this happens. If you don't
> want this, lemme know and I can filter your project out.
> 
> We will not make it so that new tickets are created, you'll have to
> create a ticket first before this will work. This is an old policy
> decision that I'm not going to go 180 on just yet.
> 
> With regards,
> Daniel.
> 
> On 02/10/2014 02:49 PM, Daniel Gruno wrote:
>> cc'ing infra, as this is really an infra topic.
>> Yes, it is possible - anything is possible, but it will require quite a
>> lot of work from Infra to make this possible.
>> 
>> I would suggest you create a new JIRA ticket with this _wish_ and label
>> is as Git+Wilderness, and I'll try to figure out whether we can support
>> this or not.
>> 
>> With regards,
>> Daniel.
>> 
>> On 02/10/2014 02:44 PM, Suresh Marru wrote:
>>> Daniel & Jake,
>>> 
>>> This is simply nice, appreciate your efforts in integrating this on a quick 
>>> turn around. Can I become more greedy and ask a follow on question/request?
>>> 
>>> In addition to (or arguably in place of) dev list emails, is it possible to 
>>> have ASF JIRA tickets updated with github PR’s? I mean similar to git and 
>>> svn commits if a pull request is created with a title including issue 
>>> number (like PROJECT-), then it might be useful to have a comment added 
>>> to the JIRA. This of course raises another question of duplicate emails to 
>>> the dev list for these PR's. 
>>> 
>>> I am looking to address this scenario: A contributor would like to provide 
>>> a patch to an issue created in a project JIRA; creates a github PR; all 
>>> discussion of PR is recorded on the JIRA; once a consensus (direct or 
>>> assumed lazy) is reached, a committer/pmc member will merge the PR closing 
>>> both github PR and resolving JIRA.
>>> 
>>> Comments on usefulness of this? I am sure I am missing something here.
>>> 
>>> Thanks,
>>> Suresh
>>> 
>>> On Feb 8, 2014, at 6:51 AM, Daniel Gruno  wrote:
>>> 
>>>> Let me just get some information across to podlings wondering about this
>>>> new GitHub stuff we've added, and what is supported so far:
>>>> 
>>>> - It is now possible to relay new GitHub PRs, comments on PRs and
>>>> closing/reopening of PRs to your mailing list.
>>>> 
>>>> - It is also possible for all committers in a project to close PRs with
>>>> a commit message to the master/trunk branch of a project saying, for
>>>> instance, "this closes #1234 on GitHub" in the commit message.
>>>> 
>>>> - This GitHub feature is currently only supported for projects/podlings
>>>> that have their primary source repository in Git. If you have an SVN
>>>> mirror instead, we are not fully able to support GitHub PR relaying at
>>>> the time being, but will support it in the near future.
>>>> 
>>>> - You have to request PR comments to be enabled for your project,
>>>> preferably via a JIRA ticket (at
>>>> https://issues.apache.org/jira/browse/INFRA ). By default, hooks have
>>>> been set up so that only PR opening/closing gets passed on. New setups
>>>> will include relaying of comments, but if your project has been set up
>>>> for a web hook in the past, you must request it be set up with comment
>>>> notification. This is a new default setting, and all projects that now
>>>> request PR notifications will automatically receive comments on PRs in
>>>> their respective mailing list as well. If you are unsure whether your
>>>> project is set up for relaying GitHub messages (and you want this), make
>>>> a new JIRA ticket to have it set up, rather one ticket too many than one
>>>> too few.
>>&

Re: Github pull request hooks

[Suresh Marru]

Daniel & Jake,

This is simply nice, appreciate your efforts in integrating this on a quick 
turn around. Can I become more greedy and ask a follow on question/request?

In addition to (or arguably in place of) dev list emails, is it possible to 
have ASF JIRA tickets updated with github PR’s? I mean similar to git and svn 
commits if a pull request is created with a title including issue number (like 
PROJECT-), then it might be useful to have a comment added to the JIRA. 
This of course raises another question of duplicate emails to the dev list for 
these PR's. 

I am looking to address this scenario: A contributor would like to provide a 
patch to an issue created in a project JIRA; creates a github PR; all 
discussion of PR is recorded on the JIRA; once a consensus (direct or assumed 
lazy) is reached, a committer/pmc member will merge the PR closing both github 
PR and resolving JIRA.

Comments on usefulness of this? I am sure I am missing something here.

Thanks,
Suresh

On Feb 8, 2014, at 6:51 AM, Daniel Gruno  wrote:

> Let me just get some information across to podlings wondering about this
> new GitHub stuff we've added, and what is supported so far:
> 
> - It is now possible to relay new GitHub PRs, comments on PRs and
> closing/reopening of PRs to your mailing list.
> 
> - It is also possible for all committers in a project to close PRs with
> a commit message to the master/trunk branch of a project saying, for
> instance, "this closes #1234 on GitHub" in the commit message.
> 
> - This GitHub feature is currently only supported for projects/podlings
> that have their primary source repository in Git. If you have an SVN
> mirror instead, we are not fully able to support GitHub PR relaying at
> the time being, but will support it in the near future.
> 
> - You have to request PR comments to be enabled for your project,
> preferably via a JIRA ticket (at
> https://issues.apache.org/jira/browse/INFRA ). By default, hooks have
> been set up so that only PR opening/closing gets passed on. New setups
> will include relaying of comments, but if your project has been set up
> for a web hook in the past, you must request it be set up with comment
> notification. This is a new default setting, and all projects that now
> request PR notifications will automatically receive comments on PRs in
> their respective mailing list as well. If you are unsure whether your
> project is set up for relaying GitHub messages (and you want this), make
> a new JIRA ticket to have it set up, rather one ticket too many than one
> too few.
> 
> - Comments _should_ now be nested, so that each new comment has an email
> reference to the original PR issue, meaning they will nest in mod_mbox
> and your email client if you have nesting/threading enabled.
> 
> - We may, in the future, add the possibility to filter out certain
> comments from being relayed to the ML (such as jenkins workflows etc),
> but this will all depend on how this initial phase goes along.
> 
> With regards,
> Daniel.
> 
> On 02/07/2014 10:02 PM, Daniel Gruno wrote:
>> We had a bit of a snafu on adding PR titles to the subject lines, but
>> it's been taken care of now.
>> 
>> With regards,
>> Daniel.
>> 
>> On 02/07/2014 09:57 PM, Henry Saputra wrote:
>>> Ah looks like the missing PR title only happen for the emails
>>> describing comments from the Github pull requests.
>>> 
>>> - Henry
>>> 
>>> On Fri, Feb 7, 2014 at 12:55 PM, Henry Saputra  
>>> wrote:
 Hi Jake,
 
 Looks like all the emails from the PR has the same subject:
 "[GitHub] incubator-spark pull request:"
 
 Is there a way to get the Title of the pull request included in the
 Subject line?
 
 Thanks,
 
 Henry
 
 On Fri, Feb 7, 2014 at 8:30 AM, Jake Farrell  wrote:
> I just wanted to follow up on my previous comments about the Github
> webhooks not posting comments, Daniel Gruno and I have been debugging the
> Github webhooks we had in place to send pull request notifications and we
> have fixed it so comments for issues and pull requests will now go to the
> dev@ lists. If anyone replies to this mail it will stay on the dev@ list.
> 
> -Jake
> 
> 
> NOTE: This still remains a project/PMC responsibility to ensure
> communication is recorded as this is coming from a 3rd party we do not
> control. Communications should be encouraged to occur on our mailing 
> lists.
> We (infra) are working to make things easier and allow for better
> integrations and are always open to anyone wanting to help contribute to
> these efforts.
>>> 
>>> -
>>> 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.apa

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

[Suresh Marru]

+ 1 (binding).

Suresh

On Jan 31, 2014, at 9:04 PM, Matei Zaharia  wrote:

> Hi folks,
> 
> The Apache Spark community has VOTEd to graduate from the Apache incubator 
> (vote thread: http://s.apache.org/kq, discussion thread: 
> http://s.apache.org/aEQ).
> 
> I’m now calling an official IPMC VOTE to make this happen as well. Here’s the 
> community tally:
> 
> +1
> Matei Zaharia
> Reynold Xin
> Tathagata Das
> Sean McNamara
> Patrick Wendell
> Mark Hamstra
> Chris Mattmann *
> Tom Graves
> Henry Saputra *
> Andy Konwinski
> Josh Rosen
> Mosharaf Chowdhury
> Mridul Muralidharan
> Nick Pentreath
> Andrew Xia
> Haoyuan Li
> Sandy Ryza
> Sebastian Schelter *
> Kostas Sakellis
> Christopher Nguyen
> Aaron Davidson
> Shivaram Venkataraman
> Kay Ousterhout
> Evan Sparks
> Xuefeng Wu
> Konstantin Boudnik
> Rahul Chugh
> Prashant Sharma
> Stephen Haberman
> Prabeesh K.
> Saisai Shao
> Junfeng Feng
> Jason Dai
> Stevo Slavic
> Heiko Braun
> Xia Zhu
> Manoj Awasthi
> 
> +0
> (none)
> 
> -1
> (none)
> 
> * indicates IPMC member
> 
> We’ve made three releases in the incubator, added new committers and IPMC 
> members, checked off the various requirements to migrate the development 
> process to the ASF, and more generally worked to build this community in the 
> Apache way.
> 
> Please VOTE to graduate Apache Spark from the incubator. I’ll leave the VOTE 
> open for 96 hours, until February 4th, 2014. The graduation resolution is 
> pasted below.
> 
> Thanks!
> 
> Matei and the Apache Spark community
> 
>  snip
> 
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the
> public, related to fast and flexible large-scale data analysis
> on clusters.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Spark Project", be
> and hereby is established pursuant to Bylaws of the Foundation;
> and be it further
> 
> RESOLVED, that the Apache Spark Project be and hereby is
> responsible for the creation and maintenance of software
> related to efficient cluster management, resource isolation
> and sharing across distributed applications; and be it further
> RESOLVED, that the office of "Vice President, Apache Spark" be
> and hereby is created, the person holding such office to serve
> at the direction of the Board of Directors as the chair of the
> Apache Spark Project, and to have primary responsibility for
> management of the projects within the scope of responsibility
> of the Apache Spark Project; and be it further
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Spark Project:
> 
> * Mosharaf Chowdhury 
> * Jason Dai 
> * Tathagata Das 
> * Ankur Dave 
> * Aaron Davidson 
> * Thomas Dudziak 
> * Robert Evans 
> * Thomas Graves 
> * Andy Konwinski 
> * Stephen Haberman 
> * Mark Hamstra 
> * Shane Huang 
> * Ryan LeCompte 
> * Haoyuan Li 
> * Sean McNamara 
> * Mridul Muralidharam 
> * Kay Ousterhout 
> * Nick Pentreath 
> * Imran Rashid 
> * Charles Reiss 
> * Josh Rosen 
> * Prashant Sharma 
> * Ram Sriharsha 
> * Shivaram Venkataraman 
> * Patrick Wendell 
> * Andrew Xia 
> * Reynold Xin 
> * Matei Zaharia 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matei Zaharia be
> appointed to the office of Vice President, Apache Spark, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification, or
> until a successor is appointed; and be it further
> 
> RESOLVED, that the Apache Spark Project be and hereby is
> tasked with the migration and rationalization of the Apache
> Incubator Spark podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Spark podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
> 
>  
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: Incubator ApacheCon presentations

[Suresh Marru]

These are great topics Marvin, looking foreword for them.

Hi All,

I am planning to propose a talk targeted for recently graduated incubator 
podlings. Along with sharing my own experiences, I want to highlight importance 
of giving back to IPMC by hanging around and helping future podlings, and most 
importantly some of the pitfalls to avoid once we move into self-governance 
mode. 

Any volunteers to join in co-presenting this talk or contributing to the 
content? We don’t need to overwhelm the mailing list and choose to directly 
email me at smarru at a.o

Thanks,
Suresh

On Jan 29, 2014, at 8:04 PM, Marvin Humphrey  wrote:

> Greets,
> 
> I'm planning to propose two presentations for ApacheCon Denver: one on
> releases, and one overview of the Incubator.
> 
>_Releasing Apache Software_
> 
>This presentation will explore technical, procedural, legal and cultural
>aspects of releasing Apache software; the distinction between "releasing"
>and "distributing"; the relationship between Apache's source releases and
>binary artifacts; evolving consensus as to what liberties may be taken
>with "incubating" releases; and how codifying the release process helps to
>fortify the the Apache brand.
> 
>Audience: Apache committers
> 
>Level: intermediate
> 
> 
>_Getting the Most Out of the Incubator_
> 
>Knowing what to expect from the incubation process is of great benefit for
>both contributors to projects currently under incubation and those
>considering bringing a project to Apache.  We'll cover the major stages of
>incubation, the institutions and roles that incubating projects must
>interact with, and how to get the most out for what you put in.
> 
>Audience: Anyone with an interest in the Incubator.
> 
>Level: beginner
> 
> Thoughts, feedback?  Anybody else submitting talks?
> 
> 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: [VOTE] Graduation of Apache Open Climate Workbench from the Incubator

[Suresh Marru]

+ 1 (binding).

Suresh

P.S. Apologies to the podling, I have been tardy due to extended time off’s and 
could not help out recently, but great to see the project graduating. 

On Jan 15, 2014, at 12:46 PM, Chris Mattmann  wrote:

> Hi Folks,
> 
> The Apache Open Climate Workbench community has VOTEd to graduate
> from the Apache Incubator.
> 
> I'm now calling an official IPMC VOTE to make this happen as well.
> Here's the community tally:
> 
> +1
> --
> Chris Mattmann*
> Michael Joyce
> Denis Nadeau
> Cameron Goodale
> Paul Ramirez*
> Chris Douglas*
> Andrew Hart*
> 
> +0
> -
> 
> -1
> -
> 
> 
> * - indicates IPMC member
> 
> We've made 3 releases of the software, have added new committers and
> PPMC members and in general done great work to build this community
> in the Apache way. 
> 
> Please VOTE to graduate Apache Open Climate Workbench from the Incubator.
> I'll leave the VOTE open for the next week and tally the results after
> then.
> The graduation resolution is pasted below.
> 
> Thanks!
> 
> Cheers,
> Chris
> 
> 
> ---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 the preparation, evaluation and analysis of massive
> climate remote sensing and model output data.
> 
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>Committee (PMC), to be known as the "Apache Open Climate Workbench
> Project", be
>and hereby is established pursuant to Bylaws of the Foundation;
>and be it further
> 
>RESOLVED, that the Apache Open Climate Workbench Project be and hereby
> is
>responsible for the creation and maintenance of software
>related to preparation, evaluation and analysis of massive
> climate remote sensing and model output data; and be it further
> 
>RESOLVED, that the office of "Vice President, Apache Open Climate
> Workbench", 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 Open Climate Workbench Project, and to have primary
> responsibility for
>management of the projects within the scope of responsibility
>of the Apache Open Climate Workbench 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 Open Climate Workbench Project:
> 
> * Andrew Hart 
> * Maziyar Boustani 
> * Christopher Douglas 
> * Chris Jack 
> * Dan Crichton 
> * Denis Nadeau 
> * estani 
> * Cameron Goodale 
> * Alex Goodman 
> * Huikyo Lee 
> * Jason Peter Evans 
> * Jinwon Kim 
> * Michael James Joyce 
> * Laura Carriere 
> * Lluis Fita Borrell 
> * Luca Cinquini 
> * Chris Mattmann 
> * Nick Kew 
> * Paul Loikith 
> * Paul Michael Ramirez 
> * Paul Zimdars 
> * M. V. S. Rama Rao 
> * J Sansay 
> * Shakeh Khudikyan 
> * Suresh Marru 
> * Duane Waliser 
> * Kim Whitehall 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Michael Joyce be
>   appointed to the office of Vice President, Apache Open Climate
> Workbench,
> 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 Open Climate Workbench Project be and hereby
> is
>   tasked with the migration and rationalization of the Apache
>   Incubator Open Climate Workbench podling; and be it further
> 
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Open Climate Workbench podling encumbered upon the Apache
> Incubator
>   Project are hereafter discharged.
> 
> 
> ---snip
> 
> 
> 
> 
> -Original Message-
> From: Michael Joyce 
> Reply-To: "d...@climate.incubator.apache.org"
> 
> Date: Wednesday, January 15, 2014 9:41 AM
> To: dev 
> Subject: Re: [VOTE] Graduation of Apache Open Climate Workbench from the
> Incubator
> 
>> Hay everyone,
>> 
>> Just a quick follow up to provide a summary of the vote.
>> 
>> +1
>> --
>> Chris Mattmann
>> Michael Joyce
>> Denis Nadeau
>> Cameron Goodale
>> Paul Ramirez
>> Chris Douglas
>> Andrew

Re: [VOTE] Accept DataFu into the Incubator

[Suresh Marru]

+ 1 (binding).

Suresh
On Dec 31, 2013, at 3:39 PM, Jakob Homan  wrote:

> Incubator-
> 
> Following the discussion earlier, I'm calling a vote to accept DataFu as a
> new Incubator project.
> 
> The proposal draft is available at:
> https://wiki.apache.org/incubator/DataFuProposal, and is also included
> below.
> 
> Vote is open for at least 96h and closes at the earliest on 4 Jan 13:00
> PDT.  I'm letting the vote run an extra day as we're in the holiday season.
> 
> [ ] +1 accept DataFu in the Incubator
> [ ] +/-0
> [ ] -1 because...
> 
> Here's my binding +1.
> -Jakob
> 
> ---
> Abstract
> 
> DataFu makes it easier to solve data problems using Hadoop and higher level
> languages based on it.
> 
> Proposal
> 
> DataFu provides a collection of Hadoop MapReduce jobs and functions in
> higher level languages based on it to perform data analysis. It provides
> functions for common statistics tasks (e.g. quantiles, sampling), PageRank,
> stream sessionization, and set and bag operations. DataFu also provides
> Hadoop jobs for incremental data processing in MapReduce.
> 
> Background
> 
> DataFu began two years ago as set of UDFs developed internally at LinkedIn,
> coming from our desire to solve common problems with reusable components.
> Recognizing that the community could benefit from such a library, we added
> documentation, an extensive suite of unit tests, and open sourced the code.
> Since then there have been steady contributions to DataFu as we encountered
> common problems not yet solved by it. Others outside LinkedIn have
> contributed as well. More recently we recognized the challenges with
> efficient incremental processing of data in Hadoop and have contributed a
> set of Hadoop MapReduce jobs as a solution.
> 
> DataFu began as a project at LinkedIn, but it has shown itself to be useful
> to other organizations and developers as well as they have faced similar
> problems. We would like to share DataFu with the ASF and begin developing a
> community of developers and users within Apache.
> 
> Rationale
> 
> There is a strong need for well tested libraries that help developers solve
> common data problems in Hadoop and higher level languages such as Pig,
> Hive, Crunch, Scalding, etc.
> 
> Current Status
> 
> Meritocracy
> 
> Our intent with this incubator proposal is to start building a diverse
> developer community around DataFu following the Apache meritocracy model.
> Since DataFu was initially open sourced in 2011, it has received
> contributions from both within and outside LinkedIn. We plan to continue
> support for new contributors and work with those who contribute
> significantly to the project to make them committers.
> 
> Community
> 
> DataFu has been building a community of developers for two years. It began
> with contributors from LinkedIn and has received contributions from
> developers at Cloudera since very early on. It has been included included
> in Cloudera’s Hadoop Distribution and Apache Bigtop. We hope to extend our
> contributor base significantly and invite all those who are interested in
> solving large-scale data processing problems to participate.
> 
> Core Developers
> 
> DataFu has a strong base of developers at LinkedIn. Matthew Hayes initiated
> the project in 2011, and aside from continued contributions to DataFu has
> also contributed the sub-project Hourglass for incremental MapReduce
> processing. Separate from DataFu he has also open sourced the White
> Elephant project. Sam Shah contributed a significant portion of the
> original code and continues to contribute to the project. William Vaughan
> has been contributing regularly to DataFu for the past two years. Evion Kim
> has been contributing to DataFu for the past year. Xiangrui Meng recently
> contributed implementations of scalable sampling algorithms based on
> research from a paper he published. Chris Lloyd has provided some important
> bug fixes and unit tests. Mitul Tiwari has also contributed to DataFu.
> Mathieu Bastian has been developing MapReduce jobs that we hope to include
> in DataFu. In addition he also leads the open source Gephi project.
> 
> Alignment
> 
> The ASF is the natural choice to host the DataFu project as its goal of
> encouraging community-driven open-source projects fits with our vision for
> DataFu. Additionally, other projects DataFu integrates with, such as Apache
> Pig and Apache Hadoop, and in the future Apache Hive and Apache Crunch, are
> hosted by the ASF and we will benefit and provide benefit by close
> proximity to them.
> 
> Known Risks
> 
> Orphaned Products
> 
> The core developers have been contributing to DataFu for the past two
> years. There is very little risk of DataFu being abandoned given its
> widespread use within LinkedIn.
> 
> Inexperience with Open Source
> 
> DataFu was started as an open source project in 2011 and has remained so
> for two years. Matt initiated the project, and additionally is the creator
> of the open

Re: LICENSE and NOTICE Role Models

[Suresh Marru]

On Dec 10, 2013, at 6:15 PM, P. Taylor Goetz  wrote:

> In the process of preparing the LICENSE and NOTICE files for Storm, I started 
> looking at what other Apache projects (both incubator and TLPs) have done.
> 
> It seems like approaches are all over the map. I've even seen projects that 
> don't have a NOTICE.
> 
> My question to any mentors and PMC members is are there any projects that 
> stand out as having done a really good job at this? (I understand that every 
> circumstance is different.)

I would not call these role models or any where near, but for Apache Airavata, 
we spent months during incubation to get the L&N files right (thanks to our 
patient mentors). If useful here are the pointers:

Source L&N files (essentially there are no third party sources bundled, hence 
ALV2 only):
https://svn.apache.org/repos/asf/airavata/trunk/LICENSE
https://svn.apache.org/repos/asf/airavata/trunk/NOTICE

The binary distribution bundles a whole bunch of dependencies and we had to 
manually traverse through every bundled jar:
https://svn.apache.org/repos/asf/airavata/trunk/modules/distribution/airavata-server/src/main/resources/LICENSE
https://svn.apache.org/repos/asf/airavata/trunk/modules/distribution/airavata-server/src/main/resources/NOTICE

Note: In recent past there have been more clarifications on NOTICE file needing 
to be even more minimalistic, we did not yet adhere to these policies yet. So 
recently released incubator projects might have better examples. 

Suresh

> 
> One project that stood out to me was Cassandra. Storm actually shares some of 
> the same dependencies, so I found their approach helpful.
> 
> - Taylor
> -
> 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: December 2013 Report Timeline

[Suresh Marru]

On Thu, Dec 5, 2013 at 10:47 PM, Marvin Humphrey wrote:

> On Thu, Dec 5, 2013 at 6:56 PM, Andreas Neumann  wrote:
> > I just added the report for Twill. This was a day late because the
> > reporting schedule was initially set up quarterly instead of monthly, and
> > we were under the impression that our first report is due in January. The
> > schedule was fixed earlier today, and our report is now available.
>
> Thank you for being conscientious about the reporting process!
>
> > One thing that I realized is that Twill does not have a shepherd
> assigned.
> > Who would be the shepherd for Twill?
>
> Shepherds are now assigned well in advance of the report via a script,
> assign_shepherds.py.  There are three shepherd volunteers that the script
> randomly assigned a light load this cycle: Dave Fisher, Suresh Marru, and
> Andrei Savu.  Andrei is a Mentor for Twill.  Dave has been spending a lot
> of
> time and thought collaborating in the release voting threads.
>
> Suresh, can you take on shepherding for Twill this month?
>

Sure Marvin, I will take this one.

Suresh


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

Re: December 2013 Report Timeline

[Suresh Marru]

On Dec 5, 2013, at 10:47 PM, Marvin Humphrey  wrote:

> On Thu, Dec 5, 2013 at 6:56 PM, Andreas Neumann  wrote:
>> I just added the report for Twill. This was a day late because the
>> reporting schedule was initially set up quarterly instead of monthly, and
>> we were under the impression that our first report is due in January. The
>> schedule was fixed earlier today, and our report is now available.
> 
> Thank you for being conscientious about the reporting process!
> 
>> One thing that I realized is that Twill does not have a shepherd assigned.
>> Who would be the shepherd for Twill?
> 
> Shepherds are now assigned well in advance of the report via a script,
> assign_shepherds.py.  There are three shepherd volunteers that the script
> randomly assigned a light load this cycle: Dave Fisher, Suresh Marru, and
> Andrei Savu.  Andrei is a Mentor for Twill.  Dave has been spending a lot of
> time and thought collaborating in the release voting threads.
> 
> Suresh, can you take on shepherding for Twill this month?

Yes Marvin, I will take this one.

Suresh

> 
> 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: [VOTE] Apache Helix as TLP Resolution

[Suresh Marru]

+ 1 (binding).

Good to see Helix hatch out of incubation. 

Suresh

On Nov 20, 2013, at 8:07 PM, Olivier Lamy  wrote:

> Hi,
> Here the vote for Apache Helix as TLP graduation.
> 
> The vote result for dev@helix.i.a.o is available here:
> http://markmail.org/message/22orwjy2v3d4af67
> 
> Vote open for 72H
> [+1]
> [0]
> [-1]
> 
> 
> X. Resolution to establish the Apache Helix Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests
> of the Foundation and consistent with the Foundation's purpose to
> establish a Project Management Committee charged with the creation and
> maintenance of open-source software related to cluster management
> system for managing partitioned and replicated resources in
> distributed data systems.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "The Apache Helix Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that The Apache Helix Project be and hereby is responsible
> for the creation and maintenance of a software project related to
> cluster management system for managing partitioned and replicated
> resources in distributed data systems; and be it further
> 
> RESOLVED, that the office of "Vice President, Helix" 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 Helix Project, and
> to have primary responsibility for management of the projects within
> the scope of responsibility of The Apache Helix 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 Helix Project:
> 
> * Olivier Lamy olamy
> * Patrick Hunt phunt
> * Mahadev Konar mahadev
> * Owen O'Malley omalley
> * Kishore Gopalakrishna kishoreg
> * Zhen Zhang zzhang
> * Shi Lu slu
> * Kapil Surlaker ksurlaker
> * Bob Schulman rms
> * Swaroop Jagadish swaroop-aj
> * Rahul Aggarwal rahula
> * Terence Yim chtyim
> * Santiago Perez santip
> * Vinayak Borkar vinayakb
> * Shirshanka Das sdas
> * Kanak Biscuitwala kanak
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be
> and hereby is appointed to the office of Vice President, Helix, 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 Helix Project be and hereby is
> tasked with the migration and rationalization of the Apache Incubator
> Helix podling; and be it further
> 
> RESOLVED, that all responsibility pertaining to the Apache Incubator
> Helix podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
> 
> -- 
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
> 
> -
> 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: Transition Incubator dist area

[Suresh Marru]

On Nov 18, 2013, at 12:38 PM, Marvin Humphrey  wrote:

> On Mon, Nov 18, 2013 at 6:15 AM, Jake Farrell  wrote:
>> The artifacts that have been left behind by the TLP's should be moved to
>> archive.apache.org/dist as dist should only contain the most recent
>> releases to not overload the mirrors. I agree that we should send out an
>> email to pmcs@ and give a window for moving the releases over to the
>> correct location.
> 
> This is getting too complicated.  The problem of our own dist area requiring
> complicated configuration is separate from the problem of graduating TLPs
> leaving a mess behind in the Incubator, and also separate from the problem of
> TLPs having too many artifacts on the mirrors.  Infra has asked us to solve a
> specific problem, and I want to be responsive to Infra's request.
> 
> Since no one has volunteered, I'm just going to take care of the dist dir
> situation myself.  There won't be any additional space requirements imposed on
> the mirrors, though I don't know whether there might be a pointless one-time
> sync cost caused by file datestamp changes.

Thanks for taking care of it Marvin. I was planning to volunteer but do not 
have good internet until Friday. If anything is left over by Friday (11/22), I 
can volunteer to finish it up then.

Suresh

> 
> After that, we can nudge the graduated TLPs to come back and pick up after
> themselves.
> 
> 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: Cultivating Outstanding IP Stewards

[Suresh Marru]

On Nov 13, 2013, at 1:14 PM, Marvin Humphrey  wrote:

> On Tue, Nov 12, 2013 at 11:58 PM, ant elder  wrote:
>> So, we _can_ let podlings have their own binding release votes and we
>> could do our own "pTLP" type experiments without even needing to go to
>> the board. We should try that. Not for every podling but just for
>> select ones where the circumstances mean it will work better than the
>> current approach. If there are no major objections to some experiments
>> with this approach then i'd like to start trying one.
> 
> +1 to run an experiment.  The position that Roy has taken changes the
> equation.
> 
> While a number of people have expressed a preference for the approach of
> electing more podling contributors directly onto the IPMC, in practice it
> remains uncertain whether the IPMC is capable of identifying, nominating and
> voting in enough candidates -- as evidenced by some threads currently in
> progress on private@incubator.
> 
> I propose that the experiment take the following form:
> 
> 1.  The initial PPMC shall be composed exclusively of IPMC members.
> 2.  PPMC votes are binding for every release except the first.
> 3.  One IPMC vote is required for each release after the first.
> 
> I believe that this model provides sufficient oversight because the first
> release must cross a high bar, and because it changes the dynamics of
> electing PPMC members: even core contributors will now have to earn PPMC
> membership, demonstrating to an initial PPMC composed of IPMC members that
> they understand the Apache Way well enough to steward their project.

+ 1, I like this balance and caveats. 

In my personal view (which I am not generalizing), getting the first release is 
very time consuming but educational and very much worth it. I do not look at it 
as one month or so for a release is unreasonable, but rather think it as, one 
month amortized over quality subsequent releases. Which ever approach or policy 
changes we take, we still need patient incumbents and overly patient mentors. 
The only way mentors scale is to teach the process and groom new teachers. 
Ofcourse not many students will like the teachers until they also become 
teachers. Atleast this happened to me, I appreciate my mentors more now then 
when I was a student :) 

Suresh

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

[Suresh Marru]

+1 (binding).

Suresh

On Nov 7, 2013, at 4:04 PM, Andreas Neumann  wrote:

> The discussion about the Weave proposal has calmed. As the outcome of the
> discussion, we have chosen a new name for the project, Twill. I would like
> to call a vote for Twill to become an incubated project.
> 
> The proposal is pasted below, and also available at:
> https://wiki.apache.org/incubator/TwillProposal
> 
> Let's keep this vote open for three business days, closing the voting on
> Tuesday 11/12.
> 
> [ ] +1 Accept Twill into the Incubator
> [ ] +0 Don't care.
> [ ] -1 Don't accept Twill because...
> 
> -Andreas.
> 
> = Abstract =
> 
> Twill is an abstraction over Apache Hadoop® YARN that reduces the
> complexity of developing distributed applications, allowing developers to
> focus more on their business logic.
> 
> = Proposal =
> 
> Twill is a set of libraries that reduces the complexity of developing
> distributed applications. It exposes the distributed capabilities of Apache
> Hadoop® YARN via a simple and intuitive programming model similar to Java
> threads. Twill also has built-in capabilities required by many distributed
> applications, such as real-time application logs and metrics collection,
> application lifecycle management, and network service discovery.
> 
> = Background =
> 
> Hadoop YARN is a generic cluster resource manager that supports any type of
> distributed application. However, YARN’s interfaces are too low level for
> rapid application development. It requires a great deal of boilerplate code
> even for a simple application, creating a high ramp up cost that can turn
> developers away.
> 
> Twill is designed to improve this situation with a programming model that
> makes running distributed applications as easy as running Java threads.
> With the abstraction provided by Twill, applications can be executed in
> process threads during development and unit testing and then be deployed to
> a YARN cluster without any modifications.
> 
> Twill also has built-in support for real-time application logs and metrics
> collection, delegation token renewal, application lifecycle management, and
> network service discovery. This greatly reduces the pain that developers
> face when developing, debugging, deploying and monitoring distributed
> applications.
> 
> Twill is not a replacement for YARN, it’s a framework that operates on top
> of YARN.
> 
> = Rationale =
> 
> Developers who write YARN applications typically find themselves
> implementing the same (or similar) boilerplate code over and over again
> for every application. It makes sense to distill this common code into a
> reusable set of libraries that is perpetually maintained and improved by a
> diverse community of developers.
> 
> Twill’s simple thread-like programming model will enable many Java
> programmers to develop distributed applications. We believe that this
> simplicity will attract developers who would otherwise be discouraged by
> complexity, and many new use cases will emerge for the usage of YARN.
> 
> Incubating Twill as an Apache project makes sense because Twill is a
> framework built on top of YARN, and Twill uses Apache Zookeeper, HDFS,
> Kafka, and other Apache software (see the External Dependencies section).
> 
> = Current Status =
> 
> Twill was initially developed at Continuuity under the name of Weave. The
> Weave codebase is currently hosted in a public repository at github.com,
> which will seed the Apache git repository after renaming to Twill.
> 
> == Meritocracy ==
> 
> Our intent with this incubator proposal is to start building a diverse
> developer community around Twill following the Apache meritocracy model.
> Since Twill was initially developed in early 2013, we have had fast
> adoption and contributions within Continuuity. We are looking forward to
> new contributors. We wish to build a community based on Apache's
> meritocracy principles, working with those who contribute significantly to
> the project and welcoming them to be committers both during the incubation
> process and beyond.
> 
> == Community ==
> 
> Twill is currently being used internally at Continuuity and is at the core
> of our products. We hope to extend our contributor base significantly and
> we will invite all who are interested in simplifying the development of
> distributed applications to participate.
> 
> == Core Developers ==
> 
> Twill is currently being developed by five engineers at Continuuity:
> Terence Yim, Andreas Neumann, Gary Helmling, Poorna Chandra and Albert
> Shau.
> Terence Yim is an Apache committer for Helix, Andreas is an Apache
> committer and PMC member for Oozie, and Gary Helmling is an Apache
> committer and PMC member for HBase. Poorna Chandra and Albert Shau have
> made many contributions to Twill.
> 
> == Alignment ==
> 
> The ASF is the natural choice to host the Twill project as its goal of
> encouraging community-driven open source projects fits with our vision for
> Twill.
> 
> Additionally, many other

Re: [VOTE] Graduate Apache Marmotta as TLP

[Suresh Marru]

+ 1.

Congrats and all the best as a TLP,
Suresh

On 11/4/13, 3:59 AM, "Jakob Frank"  wrote:

>Hi all,
>
>the Marmotta podling, whose goal is to provide an Open Platform for
>Linked Data, entered incubation in December 2012. Since then, the
>codebase has stabilized and two releases were published following ASF
>policies and guidelines.
>The community has grown, two new committers have joined the development
>team and more people joined the mailing lists.
>
>The last incubator report lists Marmotta as "Ready to graduate" [1], the
>Marmotta community has decided to take this step [2] and agreed on a
>Graduation Resolution Draft [3] which is also attached below.
>
>The resolution draft was posted to general@incubator.a.o for discussion
>[4] and raised no concerns, now please cast your votes:
>
>[ ]  +1 Graduate the Marmotta podling from Incubator
>[ ]  +0 Indifferent to graduation status of the Marmotta podling
>[ ]  -1 Reject graduation of the Marmotta podling from Incubator
>because...
>
>The vote will be open for at least 72 hours starting now.
>
>
>Best,
>Jakob
>on behalf of the Marmotta community
>
>[1] 
>[2] 
>[3] 
>[4] 
>
>Apache Marmotta Graduation Resolution
>=
>
>X. Establish the Apache Marmotta Project
>
>   WHEREAS, the Board of Directors deems it to be in the best
>   interests of the Foundation and consistent with the
>   Foundation's purpose to establish a Project Management
>   Committee charged with the creation and maintenance of
>   open-source software, for distribution at no charge to
>   the public, related to an open platform for Linked Data.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Marmotta Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Marmotta Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to an open platform for Linked Data;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Marmotta" 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 Marmotta Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Marmotta 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 Marmotta Project:
>
> * Peter Ansell 
> * Fabian Christ   
> * Sergio Fernández 
> * Jakob Frank   
> * Dietmar Glachs  
> * Thomas Kurz   
> * Nandana Mihindukulasooriya  
> * Raffaele Palmieri 
> * Sebastian Schaffert  
> * Rupert Westenthaler 
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jakob Frank
>   be appointed to the office of Vice President, Apache Marmotta, 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 Marmotta Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Marmotta podling; and be it further
>
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Marmotta 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 Stratos 3.0.0 Incubating RC4

[Suresh Marru]

+ 1 (binding).

Suresh


On 10/25/13, 1:23 PM, "Lahiru Sandaruwan"  wrote:

>Hi all,
>
>
>This is the forth release candidate for Apache Stratos  3.0.0-incubating,
>the very first Stratos release at Apache.
>
>This is the IPMC vote. The PPMC vote [1] passed, with 9 binding +1s,
>including 2 from mentors/IPMC (Ant Elder and Chip Childers) and no -1s.
>
>
>This release fixes the following issues(Same as RC1):
>
>
>https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314521&;
>version=12324964
>
>&version=12324964>
>
>*** Please download, test and vote. The vote runs for 72 hours, until
>Monday, 10.30 am PST, 11.00 am IST.
>
>Note that we are voting upon the source (tag), binaries are provided for
>convenience.
>
>
>This wiki page[1] explains Downloading the Release Candidate, Verifying
>the
>Candidate, Building Apache Stratos from source, and Carrying out a Smoke
>Test.
>
>We have explained configuring guides[2] and user guides[3] at wiki.
>
>Further, [4], [5], and [6] blogs also explain the testing release
>candidate
>packs using scripts in EC2 and Openstack IaaSes.
>The reason for not providing sample cartridges is that we test Cartridges
>based on Ubuntu cloud images and therefore we cannot distribute those with
>the release. Hence the blog posts [5] and [6].
>
>Thanks.
>
>Binary files and source files:
>
>https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-
>rc4/ting-rc1/>
>
>-rc1/>
>
>Maven staging repos:
>
>
>
>https://repository.apache.org/content/repositories/orgapachestratos-174/
>
>
>
>The tag to be voted upon:
>
>
>https://git-wip-us.apache.org/repos/asf?p=incubator-stratos.git;a=tag;h=ab
>166c282897d9db4d3f22863e67fdc8ddcccd61
>
>Tree view of the tag,
>
>https://git-wip-us.apache.org/repos/asf?p=incubator-stratos.git;a=tree;h=6
>61b5e19e00497431f552468535052751f115303;hb=c042d6df7becda9f38100aeb7c130b2
>a8870cb46
>
>aff4979db295625e6951534712bb3b6bbc65273>
>
>Stratos KEYS file containing PGP keys we use to sign the release:
>
>https://dist.apache.org/repos/dist/dev/incubator/stratos/3.0.0-incubating-
>rc1/KEYS
>
>
>[1] https://cwiki.apache.org/confluence/display/STRATOS/Testing+Procedure
>[2] https://cwiki.apache.org/confluence/display/STRATOS/Getting+Started
>[3] https://cwiki.apache.org/confluence/display/STRATOS/User+Guide
>[4]
>http://imesh.gunaratne.org/a/1/blog/getting-started-with-apache-stratos-in
>cubating-initial-release/
>[5]
>http://dineshmethsiri.blogspot.com/2013/09/create-ec2-apache-stratos-ami.h
>tml
>[6]
>http://melannj.blogspot.com/2013/09/quick-start-apache-stratos-from-ec2.ht
>ml
>
>
>Thanks.
>
>
>-rc1/KEYS>
>
>[ ] +1
>
>[ ] 0
>[ ] -1 (explain why)
>
>-- 
>--
>Lahiru Sandaruwan
>Software Engineer,
>Platform Technologies,
>WSO2 Inc., http://wso2.com
>lean.enterprise.middleware
>
>email: lahi...@wso2.com cell: (+94) 773 325 954
>blog: http://lahiruwrites.blogspot.com/
>twitter: http://twitter.com/lahirus
>linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146



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

Re: [VOTE] Usergrid BaaS Stack for Apache Incubator

[Suresh Marru]

+ 1 (binding).

Good project and I will vote nevertheless, but given there is interest, why not 
have a 3rd Mentor on board? This is not essential but as discussed at various 
times, makes release and other IPMC binding decisions easy. 

I do not want to trigger a discussion on, if we want to change the proposal 
after the VOTE started, but hopefully adding a 3rd mentor should be 
non-controversial. May be we can volunteer/obligate the champion to double duty 
as Mentor as well :) 

Suresh

On Sep 23, 2013, at 8:44 AM, Jim Jagielski  wrote:

> After a useful and successful proposal cycle, I would like to propose
> a VOTE on accepting Usergrid, a multi-tenant Backend-as-a-Service
> stack for web & mobile applications based on RESTful APIs, as an Apache
> Incubator podling.
> 
> Voting to run for 72+ hours...
> 
> Here is a link to the proposal:
>  https://wiki.apache.org/incubator/UsergridProposal
> 
> It is also pasted below:
> 
> = Usergrid Proposal =
> 
> == Abstract ==
> 
> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile
> applications, based on RESTful APIs.
> 
> 
> == Proposal ==
> 
> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed
> of an integrated distributed NoSQL database, application layer and client
> tier with SDKs for developers looking to rapidly build web and/or mobile
> applications. It provides elementary services (user registration &
> management, data storage, file storage, queues) and retrieval features (full
> text search, geolocation search, joins) to power common app features.
> 
> It is a multi-tenant system designed for deployment to public cloud
> environments (such as Amazon Web Services, Rackspace, etc.) or to run on
> traditional server infrastructures so that anyone can run their own private
> BaaS deployment.
> 
> For architects and back-end teams, it aims to provide a distributed, easily
> extendable, operationally predictable and highly scalable solution. For
> front-end developers, it aims to simplify the development process by
> enabling them to rapidly build and operate mobile and web applications
> without requiring backend expertise.
> 
> 
> == Background ==
> 
> Developing web or mobile applications obviously necessitates writing and
> maintaining more than just front-end code. Even simple applications can
> implicitly rely on server code being run to store users, perform database
> queries, serve images and video files, etc. Developing and maintaining such
> backend services requires skills not always available or expected of app
> development teams. Beyond that, the proliferation of apps inside of
> companies leads to the creation of many different, ad-hoc, unequally
> maintained backend solutions created by employees and contractors alike and
> hosted on a wide variety of environments. This is causing poor resource
> usage, operational issues, as well as security, privacy & compliance
> concerns.
> 
> In response to this problem, companies have long tried to standardize their
> server-side stack or unify them behind an ESB or API strategy.
> Backends-as-a-Service follow a similar approach but their unique
> characteristic is strongly tying  1) a persistence tier (typically a
> database), 2) a server-side application tier delivering a set of common
> services and 3) a set of client-side application interface mechanisms. For
> example, a BaaS could package 1) MongoDB with 2) a node.js application that
> offers access through 3) WebSockets. In the case of Usergrid, the trifecta
> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API.
> 
> The Backend-as-a-Service approach has steadily gained popularity in the last
> few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com,
> each operating tens of thousands of apps for tens of thousands of
> developers. The trend has already reached large organizations as well, with
> global companies such as Korea Telecom internally building a privately-run
> BaaS platform. But so far, there have been limited options for developers
> that want a non-proprietary, open option for hosting and providing these
> services themselves, or for enterprise and government users who want to
> provide these capabilities from their own data centers, especially on a very
> large scale.
> 
> 
> == Rationale ==
> 
> The issue this proposal deals with is implicit in the name.
> Backend-as-a-Service platforms are usually offered solely as proprietary
> cloud services. They are typically closed sourced, hosted on public clouds,
> and require subscription payment. Usergrid opens the playing field, by
> making a fully-featured BaaS platform freely available to all. This includes
> developers that previously could not afford them, such as mobile
> enthusiasts, small boutiques, and cost-sensitive startups. This also
> includes large companies that benefit from a reference implementation they
> can deploy in trust, or extend to their needs without losing time writing
> less-vetted, less-p

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

[Suresh Marru]

On Sep 23, 2013, at 2:57 PM, Andrew Bayer  wrote:

> Reminder - it'd be great to get more eyes and make sure we're not missing
> anything for graduation. Thanks!

+ 1 (already voted on PPMC list, just cheer leading for others to look over)

Andrew,

Since 5 IPMC member/mentors already voted on the Podling dev list, I do not 
think any further votes are needed. But as you put it rightly, more eyes and 
reviews will be better. I would just put a end time to close the vote. Since 
the next board meeting is 3 weeks away, no hurry though. 

Suresh

> 
> A.
> 
> 
> On Fri, Sep 20, 2013 at 5:00 PM, Andrew Bayer wrote:
> 
>> argh, line breaks all vanished in weird ways. Here's a better format:
>> 
>> The Apache jclouds project entered incubation in April of 2013, and since
>> then has shipped two releases, added a committer, and transitioned
>> thoroughly into the Apache Way for decision-making, development process,
>> etc. Our website[1] conforms, so far as we can tell, with Apache's
>> standards, the existing jclouds registered trademark has been transferred
>> to the ASF[2], we've decided on a set of project bylaws[4], and now we've
>> held a vote[5] on a graduation resolution[6, and below] to be added to the
>> agenda for the next ASF board meeting.
>> The vote has passed[7] with 7 binding PPMC +1s and 4 binding mentor +1s,
>> so on behalf of the Apache jclouds project, I'd like to request the IPMC's
>> approval for our graduation. Thanks!
>> 
>> Please cast your vote:
>> 
>> [ ] +1 Graduate the Apache jclouds podling from Apache Incubator as a TLP
>> [ ] +0 Indifferent to the graduation status of Apache jclouds podling
>> [ ] -1 Reject graduation of Apache jclouds podling from Apache Incubator
>> because ...
>> 
>> The vote will be open for 72 hours, until 5pm PDT on Monday, September
>> 23rd.
>> 
>> [1]: http://jclouds.incubator.apache.org/
>> [2]: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-37
>> [3]: http://apache.markmail.org/thread/q6sqwspp55sjtk2v
>> [4]: https://wiki.apache.org/jclouds/Bylaws
>> [5]: http://markmail.org/thread/vnnvej3q7sla3btl
>> [6]: https://wiki.apache.org/jclouds/GraduationCharter
>> [7]: http://apache.markmail.org/thread/55d6vle5be43gwtv
>> 
>> Thanks again -
>> The Apache jclouds project
>> 
>> ---
>> 
>> WHEREAS, the Board of Directors deems it to be in the best
>> interests of the Foundation and consistent with the Foundation's
>> purpose to establish a Project Management Committee charged with
>> the creation and maintenance of open-source software related to
>> providing a cloud agnostic library for the JVM that enables
>> developers to access a variety of supported cloud providers using
>> one API, for distribution at no charge to the public.
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> Committee (PMC), to be known as the "The Apache jclouds Project",
>> be and hereby is established pursuant to Bylaws of the
>> Foundation; and be it further
>> 
>> RESOLVED, that The Apache jclouds Project be and hereby is
>> responsible for the creation and maintenance of a software
>> project related to providing a cloud agnostic library for the JVM
>> that enables developers to access a variety of supported cloud
>> providers using one API; and be it further
>> 
>> RESOLVED, that the office of "Vice President, jclouds" 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
>> jclouds Project, and to have primary responsibility for
>> management of the projects within the scope of responsibility of
>> The Apache jclouds 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 jclouds Project:
>> 
>> * Adrian Cole (adrianc...@apache.org)
>> * Andrew Bayer(aba...@apache.org)
>> * Andrew Gaul (g...@apache.org)
>> * Andrew Phillips (andr...@apache.org)
>> * Becca Wood  (silky...@apache.org)
>> * Everett Toews   (ever...@apache.org)
>> * David Nalley(ke4...@apache.org)
>> * Ignasi Barrera  (n...@apache.org)
>> * Ioannis Canellos(ioca...@apache.org)
>> * Matt Stephenson (matts...@apache.org)
>> 
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andrew Bayer be and
>> hereby is appointed to the office of Vice President, jclouds, 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 jclouds Project be and hereby
>> is tasked with the migration and rationalization of the Apache
>> Incubator jclouds podling; and be it further
>> 
>> RESOLVED, that all responsibility pertaining to the Apache
>> Incubator jclouds podling encumbered upon the Apache Incubator
>> PMC are hereafter dischar

Re: [VOTE] Accept Storm into the Incubator

[Suresh Marru]

+ 1 (binding).

Good to see the project coming to ASF. 

Suresh

On Sep 12, 2013, at 3:19 PM, Doug Cutting  wrote:

> Discussion about the Storm proposal has subsided, issues raised now
> seemingly resolved.
> 
> I'd like to call a vote to accept Storm as a new Incubator podling.
> 
> The proposal is included below and is also at:
> 
>  https://wiki.apache.org/incubator/StormProposal
> 
> Let's keep the vote open for four working days, until 18 September.
> 
> [ ] +1 Accept Storm into the Incubator
> [ ] +0 Don't care.
> [ ] -1 Don't accept Storm because...
> 
> Doug
> 
> 
> = Storm Proposal =
> 
> == Abstract ==
> 
> Storm is a distributed, fault-tolerant, and high-performance realtime
> computation system that provides strong guarantees on the processing
> of data.
> 
> == Proposal ==
> 
> Storm is a distributed real-time computation system. Similar to how
> Hadoop provides a set of general primitives for doing batch
> processing, Storm provides a set of general primitives for doing
> real-time computation. Its use cases span stream processing,
> distributed RPC, continuous computation, and more. Storm has become a
> preferred technology for near-realtime big-data processing by many
> organizations worldwide (see a partial list at
> https://github.com/nathanmarz/storm/wiki/Powered-By). As an open
> source project, Storm’s developer community has grown rapidly to 46
> members.
> 
> == Background ==
> 
> The past decade has seen a revolution in data processing. MapReduce,
> Hadoop, and related technologies have made it possible to store and
> process data at scales previously unthinkable. Unfortunately, these
> data processing technologies are not realtime systems, nor are they
> meant to be. The lack of a "Hadoop of realtime" has become the biggest
> hole in the data processing ecosystem. Storm fills that hole.
> 
> Storm was initially developed and deployed at BackType in 2011. After
> 7 months of development BackType was acquired by Twitter in July 2011.
> Storm was open sourced in September 2011.
> 
> Storm has been under continuous development on its Github repository
> since being open-sourced. It has undergone four major releases (0.5,
> 0.6, 0.7, 0.8) and many minor ones.
> 
> 
> == Rationale ==
> 
> Storm is a general platform for low-latency big-data processing. It is
> complementary to the existing Apache projects, such as Hadoop. Many
> applications are actually exploring using both Hadoop and Storm for
> big-data processing. Bringing Storm into Apache is very beneficial to
> both Apache community and Storm community.
> 
> The rapid growth of Storm community is empowered by open source. We
> believe the Apache foundation is a great fit as the long-term home for
> Storm, as it provides an established process for community-driven
> development and decision making by consensus. This is exactly the
> model we want for future Storm 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 ==
> 
> Storm has undergone four major releases (0.5, 0.6, 0.7, 0.8) and many
> minor ones. Storm 0.9 is about to be released. Storm is being used in
> production by over 50 organizations. Storm codebase is currently
> hosted at github.com, 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 ===
> 
> The need for a low-latency big-data processing platform in the open
> source is tremendous. Storm is currently being used by at least 50
> organizations worldwide (see
> https://github.com/nathanmarz/storm/wiki/Powered-By), and is the most
> starred Java project on Github. By bringing Storm into Apache, we
> believe that the community will grow even bigger.
> 
> === Core Developers ===
> 
> Storm was started by Nathan Marz at BackType, and now has developers
> from Yahoo!, Microsoft, Alibaba, Infochimps, and many other companies.
> 
> === Alignment ===
> 
> In the big-data processing ecosystem, Storm is a very popular
> low-latency platform, while Hadoop is the primary platform for batch
> processing. We believe that it will help the further growth of
> big-data community by having Hadoop and Storm aligned within Apache
> foundation. The alignment is also beneficial to other Apache
> communities (such as Zookeeper, Thrift, Mesos). We could include
> additional sub-projects, Storm-on-YARN and Storm-on-Mesos, in the near
> future.
> 
> == Known Risks ==
> 
> === Orphaned Products ===
> 
> The risk o

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

[Suresh Marru]

On Sep 2, 2013, at 10:22 AM, Jordan Zimmerman  
wrote:

> I thought so. But wasn't sure. I just listed votes as I got them. I.e. if 
> they said binding or not. 

Hi Jordon,

We don't need to worry for this vote, but in general relying on voter's 
statement is not a good idea. An authoritative resource to verify the binding 
and non-binding votes is [1].

Suresh 

[1] - http://people.apache.org/committers-by-project.html#incubator-pmc

> 
> 
> Jordan Zimmerman
> 
> On Sep 2, 2013, at 7:13 AM, "Alan D. Cabrera"  wrote:
> 
>> Not sure if this is a big deal but a bunch of the people in the "lower 13" 
>> are IPMC members.
>> 
>> 
>> Regards,
>> Alan
>> 
>> On Aug 31, 2013, at 8:49 AM, Jordan Zimmerman  
>> wrote:
>> 
>>> The vote to graduate Apache Curator as a Top Level Project has passed:
>>> 
>>> +1 binding (7)
>>>   Chris Mattmann
>>>   Enis Söztutar
>>>   Suresh Marru
>>>   Arvind Prabhakar
>>>   Matt Franklin
>>>   Roman Shaposhnik
>>>   Chip Childers
>>> 
>>> +1 (13)
>>>   Patrick Hunt
>>>   Jordan Zimmerman
>>>   Jay Zarfoss 
>>>   Eric Tschetter
>>>   Luciano Resende
>>>   Mahadev Konar
>>>   Ioannis Canellos
>>>   Henry Saputra
>>>   Ashish Paliwal
>>>   Ant Elder
>>>   Andrei Savu
>>>   Alan D. Cabrera
>>>   Evaristo Josec
>>> 
>>> +0 (none)
>>> 
>>> -1 (none)
>>> 
>>> I will send an email to the Board asking to include the resolution in the 
>>> agenda for the next Board meeting. Thanks to everyone!
>>> 
>>> -Jordan
>>> -
>>> 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: [VOTE] Graduate Apache Curator as an Apache Top Level Project

[Suresh Marru]

+ 1 (binding).

Good overview of the progress during incubation, All the best as a TLP.

Suresh

On Aug 28, 2013, at 1:44 PM, Jordan Zimmerman  
wrote:

> This message is opening a VOTE to graduate the Apache Curator podling from 
> the Apache Incubator as an Apache Top Level Project.
> 
> Apache Curator entered the Incubator in April of 2013. We have made 
> significant progress with the project since moving to Apache. We currently 
> have 4 committers listed on our status page [1] including 2 who were accepted 
> after the podling was formed.  A VOTE was held on the curator-dev group with 
> 8 binding +1 and 2 non-binding +1 votes for graduation [2]. A VOTE was also 
> held to adopt the graduation resolution (below) with 7 +1 votes for 
> acceptance [3]. According to Ohloh, Curator has a "large, active development 
> team" [4].
> 
> During incubation, Curator:
> * Produced 4 releases
> * Added 2 new Committer/PPMC members and showed constant community activities
> * Cleared IP on code
> * Developed roadmap(s) for major and minor releases in a community process [5]
> * Established that Apache Curator is a suitable name [6]
> * Showed that its community is active, healthy, and growing and has 
> demonstrated the ability to self-govern using accepted Apache practices
> 
> Please cast your vote:
> [ ] +1 Graduate the Apache Curator podling from Apache Incubator as a TLP
> [ ] +0 Indifferent to the graduation status of Apache Curator podling
> [ ] -1 Reject graduation of Apache Curator podling from Apache Incubator 
> because ...
> 
> We'll run the vote for at least 72 hours.
> 
> [1] http://curator.incubator.apache.org/team-list.html#Contributors
> [2] 
> http://mail-archives.apache.org/mod_mbox/incubator-curator-dev/201308.mbox/%3C44CD80F8-10B1-4FBA-A9D9-6DDEA7280FA5%40jordanzimmerman.com%3E
> [3] 
> http://mail-archives.apache.org/mod_mbox/incubator-curator-dev/201308.mbox/%3C3859DF43-460C-406E-B816-DD9F4049B4DC%40jordanzimmerman.com%3E
> [4] http://www.ohloh.net/p/apache-curator/factoids#FactoidTeamSizeLarge
> [5] 
> https://issues.apache.org/jira/browse/CURATOR#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
> [6] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-28
> 
> Sincerely,
> 
> The Apache Curator Team
> 
> Resolution:
> 
> X. Establish the Apache Curator Project
> 
>   WHEREAS, the Board of Directors deems it to be in the best
>   interests of the Foundation and consistent with the
>   Foundation's purpose to establish a Project Management
>   Committee charged with the creation and maintenance of
>   open-source software, for distribution at no charge to 
>   the public, related to a library and tools for working with 
>   Apache ZooKeeper.
> 
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Curator Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
> 
>   RESOLVED, that the Apache Curator Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to a library and tools for working with Apache ZooKeeper;
>   and be it further
> 
>   RESOLVED, that the office of "Vice President, Apache Curator" be
>   and hereby is created, the person holding such office to
>   serve at the direction of the Board of Directors as the chair
>   of the Apache Curator Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Curator Project; and be it further
> 
>   RESOLVED, that the persons listed immediately below be and
>   hereby are appointed to serve as the initial members of the
>   Apache Curator Project:
> 
> * Jordan Zimmerman (randgalt)
> * Jay Zarfoss (zarfide)
> * Eric Tschetter (cheddar)
> * Ioannis Canellos (iocanel)
> * Patrick Hunt (phunt)
> * Mahadev Konar (mahadev)
> * Luciano Resende (lresende)
> * Enis Söztutar (enis)
> 
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jordan Zimmerman
>   be appointed to the office of Vice President, Apache Curator, to
>   serve in accordance with and subject to the direction of the
>   Board of Directors and the Bylaws of the Foundation until
>   death, resignation, retirement, removal or disqualification,
>   or until a successor is appointed; and be it further
> 
>   RESOLVED, that the initial Apache Curator PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache Curator Project; and be it further
> 
>   RESOLVED, that the Apache Curator Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Curator podling; and be it further
> 
>   RESOLVED, that al

Re: [VOTE] Release Apache jclouds-1.6.2-incubating RC2

[Suresh Marru]

+ 1 (binding) 

JClouds PPMC,

The release verification script is handy, should consider sharing it with 
general list, it could be could possibly be improved and tuned to project 
specific verifications. 

Suresh

On Aug 22, 2013, at 9:06 AM, Andrew Phillips  wrote:

> Hi all
> 
> This is the third release candidate for Apache jclouds
> 1.6.2-incubating, the second jclouds release at Apache.
> 
> This is the IPMC vote. The PPMC vote [1] passed, with one +1 from
> mentors (Olivier Lamy). Please use the separate [DISCUSS] thread for
> anything but votes.
> 
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324574&styleName=Html&projectId=12314430
> 
> *** Please download, test and vote by Tuesday, August 27th, 06:00 PDT /
> 09:00 EDT / 15:00 CET.
> 
> Note that we are voting upon the source (tag), binaries are provided
> for convenience.
> 
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/jclouds/1.6.2-incubating-rc2/
> 
> Maven staging repos:
> https://repository.apache.org/content/repositories/orgapachejclouds-102/
> 
> The tags to be voted upon:
> - jclouds -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=1a74b20b5d3b632a0a27195722dc39a2f4014275
> 
> - jclouds-labs -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=7d5baa5edb66ff2f221ecccffeaffb56e6188ccd
> 
> - jclouds-labs-openstack -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs-openstack.git;a=tag;h=c18518ff4b16388e472d635fcd1e377af70c23db
> 
> - jclouds-chef -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=d28af2d458ecc1f783b096bff097d78016155dc4
> 
> - jclouds-karaf -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=b5779131dbfd8baebf28d84372510adac42c0743
> 
> - jclouds-cli -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=5f9bdaf5c16450187a43e7591795e9ffb7674127
> 
> jclouds KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/incubator/jclouds/KEYS
> 
> [ ] +1
> [ ] 0
> [ ] -1 (explain why)
> 
> Thanks to all involved for their time!
> 
> ap
> 
> [1] http://markmail.org/message/2r66vkuhgg4quw5r


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

Re: [VOTE] Release Apache jclouds-1.6.2-incubating RC1

[Suresh Marru]

+ 1 (binding). 

The sigs checked out fine, the KEYS file is on public location. L, N & D files 
are correct. I will post some detailed notes tomorrow to the dev list. Good job 
with the release @AP. 

Suresh


On Aug 12, 2013, at 4:03 PM, Andrew Phillips  wrote:

> Hi all
> 
> This is the second release candidate for Apache jclouds 1.6.2-incubating, the 
> second jclouds release at Apache.
> 
> This is the IPMC vote. The PPMC vote [1] passed, with one +1 from mentors 
> (Olivier Lamy). Please use the separate [DISCUSS] thread for anything but 
> votes.
> 
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324574&styleName=Html&projectId=12314430
> 
> *** Please download, test and vote by Thursday, August 15th, 13:00 PDT / 
> 16:00 EDT / 22:00 CET.
> 
> Note that we are voting upon the source (tag), binaries are provided for 
> convenience.
> 
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/jclouds/1.6.2-incubating-rc1/
> 
> Maven staging repos:
> https://repository.apache.org/content/repositories/orgapachejclouds-067/
> (jclouds, jclouds-labs, jclouds-chef, jclouds-karaf, jclouds-cli)
> https://repository.apache.org/content/repositories/orgapachejclouds-068/
> (jclouds-labs-openstack)
> 
> Note: Nexus automatically created new a staging repos for 
> jclouds-labs-openstack.
> 
> The tags to be voted upon:
> - jclouds -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=71e453164cdd6afa8b5a290850cd1450a6415634
> - jclouds-labs -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=011c34a4b4ed52551025fc022d1d788f6f0cfb79
> - jclouds-labs-openstack -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs-openstack.git;a=tag;h=750989eb8054b13f7387bf11b3fb79bf13351ed7
> - jclouds-chef -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=9a781f9e86a4a2774c25f05d1d4bd0de266d0791
> - jclouds-karaf -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=da38878e0df4497b3b963866b4cabf335ce2f6fe
> - jclouds-cli -
> https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=9e6714db88f33636597d1d413a223c7b16aab7ac
> 
> jclouds KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/incubator/jclouds/KEYS
> 
> [ ] +1
> [ ] 0
> [ ] -1 (explain why)
> 
> Thanks!
> 
> ap
> 
> [1] http://apache.markmail.org/thread/lt7xbuby4lgtio66


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

Re: [VOTE] Accept Samza into the Incubator

[Suresh Marru]

+ 1 (binding).

Suresh

On Jul 26, 2013, at 3:52 PM, Jakob Homan  wrote:

> Incubator-
> 
> Following the discussion earlier this week, I'm calling a vote to accept
> Samza as a new Incubator project.
> 
> The proposal draft is available at:
> https://wiki.apache.org/incubator/SamzaProposal,
> and is also included below. It is identical as what was proposed in the
> discussion except for removing the user list, per Marvin's suggestion.
> 
> Vote is open for at least 96h and closes at the earliest on 30 July 13:00
> PDT.  I'm letting the vote run an extra day as we're bookending the weekend
> and I want to give everybody a reasonable workweek margin.
> 
> [ ] +1 accept Samza in the Incubator
> [ ] +/-0
> [ ] -1 because...
> 
> Here's my binding +1
> 
> -Jakob
> 
> 
> 
> Abstract
> 
> Samza is a stream processing system for running continuous computation on
> infinite streams of data.
> 
> Proposal
> 
> Samza provides a system for processing stream data from publish-subscribe
> systems such as Apache Kafka. The developer writes a stream processing
> task, and executes it as a Samza job. Samza then routes messages between
> stream processing tasks and the publish-subscribe systems that the messages
> are addressed to.
> 
> Background
> 
> Samza was developed at LinkedIn to enable easier processing of streaming
> data on top of Apache Kafka. Current use cases include content processing
> pipelines, aggregating operational log data, data ingestion into
> distributed database infrastructure, and measuring user activity across
> different aggregation types.
> 
> Samza is focused on providing an easy to use framework to process streams.
> It uses Apache YARN to provide a mechanism for deploying stream processing
> tasks in a distributed cluster. Samza also takes advantage of YARN to make
> decisions about stream processor locality, co-partition of streams, and
> provide security. Apache Kafka is also leveraged to provide a mechanism to
> pass messages from one stream processor to the next. Apache Kafka is also
> used to help manage a stream processor's state, so that it can be recovered
> in the event of a failure.
> 
> Samza is written in Scala. It was developed internally at LinkedIn to meet
> our particular use cases, but will be useful to many organizations facing a
> similar need to reliably process large amounts of streaming data.
> Therefore, we would like to share it the ASF and begin developing a
> community of developers and users within Apache.
> 
> Rationale
> 
> Many organizations can benefit from a reliable stream processing system
> such as Samza. While our use case of processing events from a large website
> like LinkedIn has driven the design of Samza, its uses are varied and we
> expect many new use cases to emerge. Samza provides a generic API to
> process messages from streaming infrastructure and will appeal to many
> users.
> 
> Current Status
> 
> Meritocracy
> 
> Our intent with this incubator proposal is to start building a diverse
> developer community around Samza following the Apache meritocracy model.
> Since Samza was initially developed in late 2011, we have had fast adoption
> and contributions by multiple teams at LinkedIn. We plan to continue
> support for new contributors and work with those who contribute
> significantly to the project to make them committers.
> 
> Community
> 
> Samza is currently being used internally at LinkedIn. We hope to extend our
> contributor base significantly and invite all those who are interested in
> building large-scale distributed systems to participate.
> 
> Core Developers
> 
> Samza is currently being developed by four engineers at LinkedIn: Jay
> Kreps, Jakob Homan, Sriram Subramanian, and Chris Riccomini. Jakob is an
> ASF Member, Incubator PMC member and PMC member on Apache Hadoop, Kafka and
> Giraph. Jay is a member of the Apache Kafka PMC and contributor to various
> Apache projects. Chris has been an active contributor for several projects
> including Apache Kafka and Apache YARN. Sriram has contributed to Samza, as
> well as Apache Kafka.
> 
> Alignment
> 
> The ASF is the natural choice to host the Samza project as its goal of
> encouraging community-driven open-source projects fits with our vision for
> Samza. Additionally, many other projects with which we are familiar with
> and expect Samza to integrate with, such as Apache ZooKeeper, YARN, HDFS
> and log4j are hosted by the ASF and we will benefit and provide benefit by
> close proximity to them.
> 
> Known Risks
> 
> Orphaned Products
> 
> The core developers plan to work full time on the project. There is very
> little risk of Samza being abandoned as it is part of LinkedIn's internal
> infrastructure.
> 
> Inexperience with Open Source
> 
> All of the core developers have experience with open source development.
> Jay and Chris has been involved with several open source proj

Re: Shepherd assignments July 2013

[Suresh Marru]

Hi Marvin,

Can you also once recap the timelines you are expecting the podlings reports, 
shepherd reviews, and draft summary, and submission to board?

Suresh

On Jul 2, 2013, at 10:23 AM, Marvin Humphrey  wrote:

> Greets,
> 
> Here are shepherd assignments for the July 2013 report:
> 
>SHEPHERD   PODLING
>--
>Alan Cabrera   jclouds
>Alan Cabrera   Open Climate Workbench
>Alan Cabrera   ODF Toolkit
>Dave FisherJSPWiki
>Dave FisherStratos
>Matt Franklin  Falcon
>Matt Franklin  Tashi
>Matt Franklin  VXQuery
>Ross Gardler   DeviceMap
>Ross Gardler   Marmotta
>Ross Gardler   Ripple
>Matt Hogstrom  Mesos
>Matt Hogstrom  Provisionr
>Matt Hogstrom  Spark
>Benson Marguilies  Chukwa
>    Benson Marguilies  Kafka
>Benson Marguilies  MetaModel
>Suresh Marru   Celix
>Suresh Marru   Helix
>Suresh Marru   MRQL
>Roman Shaposhnik   Knox
>Roman Shaposhnik   Tajo
>Roman Shaposhnik   Tez
> 
> Matt Franklin: I interpreted "(Happy to take any podling)" as "willing
> to handle any podlings" (plural) and assigned you three.
> 
> All: Please speak up if there are any issues.
> 
> Thanks as always, shepherds.
> 
> 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: Stratos backlog

[Suresh Marru]

Thanks Christian, Startos changes look good and should have been published 
earlier.

Suresh

On Jun 25, 2013, at 5:00 AM, Christian Grobmeier  wrote:

> Hi,
> 
> i just published something for Wave and found some CMS backlog from
> Stratos. Its now published too. You may want to correct it, if you
> don't feel this was ready for publishing.
> 
> Cheers
> 
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
> 
> -
> 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 Stratos proposal as an incubating project

[Suresh Marru]

On Jun 17, 2013, at 3:19 AM, Greg Stein  wrote:

> On Mon, Jun 17, 2013 at 12:27 AM, Marvin Humphrey
>  wrote:
>> ...
>> It's inconceivable to me that this will have an ounce of impact on either
>> someone of Sanjiva's accomplishments or a future podling with the momentum of
>> Stratos, but to ensure that my positive assessment is communicated
>> unequivocally to one and all in the VOTE tally as it was during the PROPOSAL
>> thread, I hereby change the value of my vote from -0 to +0.9.
> 
> I never worried about the "vote impact", and your change was not requested.
> 
> My concern was that your pedantism caused two *highly* qualified (and
> IMO, unimpeachable) people to issue a mea culpa in response to your
> email. That was unjustified, and highly unnecessary when looking at
> the actual edit that was performed.
> 
> Sure, I could also say "Ross/Sanjiva: grow a pair. Don't apologize."
> But I like those guys, so I never said that ;-)
> 
> I dislike that the atmosphere puts them into a position where they
> feel a need to apologize. Personally speaking, it feels uncooperative
> and rules-based rather than "what can we do, to get our goals
> accomplished?"

With great respects to all of you, I only see the positive impact of this 
discussion. 

As many alternatives/mid course corrections to incubator/incubation are being 
discussed its even more important to tighten the loose screws to keep this 
vehicle moving smoothly. Changing proposal has been one of the nagging issues 
and Marvin's raised concern and people of the stature of Ross and Sanjiva's 
instant response only gets it strongly. Greg, Ross, Sanjiva make invaluable  
contributions to the foundation and you do it yet again. Thank you. 

I think Marvin did a head start at his "job". He might run sledge on small 
things or go soft on big issues, but we still should appreciate him 
volunteering during turbulence and let him go at it at liberal. 

When bringing proposals or release votes to this highly flammable list, its 
easier to predict weather than what gets ignited here. Thanks to generosity of 
Sanjiva and WSO2, the branding issue is resolved elegantly and now looking 
forward for this egg to incubate and hatch quickly. 

Suresh

> 
> It felt like the *goal* was lost, in favor of "oh, boo hoo, a small
> [favorable] edit was made".
> 
> IMO, the proper response would be "+1, great proposal. (as an aside,
> all: please do not edit once voting is underway)". ... And step back
> and consider the other end of the spectrum: say the proposal was
> edited several times during the voting process. The IPMC is
> highly-qualified to say "meh. nothing substantive. let's run with it."
> ... or they could "holy crap. everything changed. we need to run
> another vote."
> 
> I stand behind Sanjiva and what he/WSO2 are doing. I don't like seeing
> him put into a position where he does the Right Thing, then feels a
> need to apologize for it. I'd like to see us move past that.
> 
> -g
> 
> -
> 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 Stratos proposal as an incubating project

[Suresh Marru]

+ 1 (binding)

Suresh

On Jun 14, 2013, at 5:49 PM, Ross Gardler  wrote:

> I would like to invite the IPMC vote to accept the Stratos proposal [1].
> 
> I want to clarify that this vote is for the Stratos project to enter
> the incubator as a standard podling under the existing incubation
> policy. The acceptance or otherwise of the probationary TLP idea is a
> separate issue that will be explored during the first month of
> incubation, potentially resulting in a further IPMC vote.
> 
> This vote is *only* for accepting the Stratos project as a podling.
> 
> [ ] +1 Accept the Stratos project as an incubating project
> [ ] +0
> [ ] -1 Do not accept the Stratos project as an incubating project
> because... (provide reason)
> 
> It's late on Friday evening here in the UK. I'll let this vote run
> well into next week to allow for the weekend.
> 
> Thank you for your votes.
> Ross
> 
> -
> 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] Accept Stratos as an Apache Incubation Project

[Suresh Marru]

e ASF we are signalling that the door is wide open for
>> external contributors.
>> 
>> == Known Risks ==
>> Stratos has largely been developed by sponsored developers employed at
>> a single organization - WSO2.  Seeking a broader community of
>> contributors is a top goal of contributing Stratos to Apache.
>> WSO2 plans to continue to offer services and commercial support
>> packages for Stratos, so there is a financial incentive to broaden
>> Stratos’ appeal.  This may provide the misinterpretation that Stratos
>> remains merely a WSO2 technology.  However, WSO2’s main business
>> strategy is to build and support higher level PaaS offerings
>> (including the WSO2 middleware stack) on top of a common PaaS
>> framework, as provided by Stratos.  This includes a WSO2 StratosLive
>> option which is a public PaaS based on WSO2 Stratos.
>> Compatibility with a wide variety of IaaS and other ecosystem
>> partners, and setting, conforming to or advancing a set of open
>> standards, will be necessary to ensure Stratos gains traction as a
>> uniting force in the industry.
>> PaaS is on the uphill swing of the hype curve at present.  For the
>> project to succeed it needs to focus on concrete long-term value to
>> those using or deploying the PaaS.
>> The project was previously named and trademarked as “WSO2 Stratos”,
>> but the contributors do not believe that this name has built a strong
>> industry brand, and the transition to the name “Apache Stratos” should
>> not induce significant confusion. WSO2 has no intention of continuing
>> to use this mark. We will also work with VP Brand Management to ensure
>> the Stratos mark is secure within the ASF.
>> == Binaries ==
>> Latest binaries are available at
>> [[http://dist.wso2.org/downloads/stratos/2.0.0/|http://dist.wso2.org/downloads/stratos/2.0.0/]]
>> == Code ==
>> The code is currently available in the following SVN repository locations
>> * 
>> [[https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/build/stratos2|https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/build/stratos2]]
>> * 
>> [[https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/stratos|https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/stratos]]
>> * 
>> [[https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/load-balancer|https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/load-balancer]]
>> * 
>> [[https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/products/stratos2/|https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/products/stratos2/]]
>> * 
>> [[https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/products/elb/|https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/products/elb/]]
>> == Documentation ==
>> * 
>> [[http://docs.wso2.org/wiki/display/Stratos200/WSO2+Stratos+Documentation|http://docs.wso2.org/wiki/display/Stratos200/WSO2+Stratos+Documentation]]
>> * [[http://docs.wso2.org/wiki/display/Stratos200/Quick+Start+Guide|Quick
>> start guide]]
>> == External Dependencies ==
>> All components and dependent components are licensed under the Apache
>> or compatible license, and many of the components reside at the ASF.
>> == Cryptography ==
>> The software does not implement any cryptographic algorithms. However,
>> to perform secured messaging and data movement and SSL communications,
>> the software depends upon third party security libraries. These
>> external libraries depend in turn on Java Security and Bounce Castle
>> libraries. Apache Cryptographic steps will be followed to register the
>> use of these libraries.
>> == Required Resources ==
>> === Mailing Lists ===
>> 1. d...@stratos.incubator.apache.org - for developer/user discussions,
>> JIRA change notifications & continuous build/test notifications
>> 2. comm...@stratos.incubator.apache.org - for commit mails
>> === Other Resources ===
>> 1. A Git repository
>> 2. A JIRA issue tracker: short code "Stratos"
>> 
>> == Initial Committers ==
>> || '''Name''' || '''Email''' || '''Affiliation''' || '''iCLA''' ||
>> || Paul Fremantle || p...@apache.org || Individual, wso2.com || yes ||
>> || Jonathan Marsh || jonat...@wso2.com || Individual, wso2.com || ||
>> || Peter Linnell  || plinn...@apache.org || Individual, suse.com || ||
>> || Afkham Azeez || az...@apache.org || Individual wso2.com || yes ||
>> || Lakmal Warusawithana || lak...

Re: [VOTE] Accept Apache HotdoG into the Incubator

[Suresh Marru]

+ 1 (binding).

Suresh

On Jun 12, 2013, at 2:22 PM, "Ramirez, Paul M (398J)" 
 wrote:

> All,
> 
> I'd like to call a VOTE for the acceptance of Apache HotdoG into the 
> Incubator. I'll leave the VOTE open for the rest of the week and close it out 
> Monday, June 17th early am PT.
> 
> [ ] +1 Accept Apache HotdoG into the Incubator
> [ ] +0 Don't care.
> [ ] -1 Don't accept Apache HotdoG because...
> 
> Full Proposal is pasted at the end of this email. Only VOTEs from Incubator 
> PMC members are binding, but all are welcome to express their thoughts.
> 
> This is a second pass at this vote as I canceled it to pull in more mentors. 
> The following people voted on the first pass:
> 
> Henry Saputra +1 (binding)
> Chris Mattmann + 1 (binding)
> 
> Thanks!
> Paul Ramirez
> 
> P.S. +1 from me (binding)
> 
> 
> = HotdoG Proposal =
> 
> == Abstract ==
> 
> The HotdoG project is an effort and suite of tools to convert HDF/HDF-EOS 
> format into GeoTIFF format. This is the first of a potential series of 
> incoming projects originating from The HDF Group -- the non-profit 
> organization is interested in evaluating the ASF as a potential home for many 
> of its projects. The HDF Group is an independently funded organization that 
> started many years ago with major investment from NASA as the Hierarchical 
> Data Format (HDF), version 4 and now version 5, is the ''de facto'' remote 
> sensing data format for NASA missions, and an increasing number of other 
> disciplines including bio medicine, radio astronomy, climate science, and 
> other domains.
> 
> HDF is both a data and metadata format, as well as a model for representing 
> and access information. There are numerous downstream tools that can read and 
> write HDF data, including a growing number of Geospatial data tools 
> (ESRI-based, and also OpenGeo and other community led efforts). In addition, 
> major interoperability efforts are also occurring between the remote sensing 
> community and the climate modeling community (which has traditionally favored 
> NetCDF as opposed to HDF) because of the efforts in HDF5 to leverage a common 
> data format and model.
> 
> HotdoG is poised to be a first of its kind in the form of bringing one of the 
> major 2 data formats for science to the ASF (the other being the NetCDF 
> format).
> 
> == Proposal ==
> HotdoG is a software converter that converts Earth Science data in 
> HDF/HDF-EOS format into GeoTIFF format. Doing so easily enables users of 
> remote sensing data to interoperate with common GIS tools (like WebGIS, Web 
> Processing, image analysis, and geo computational tools). We feel that the 
> project is an incremental step, and an appropriate focus with tangible 
> success possibilities by restraining our focus to HDF/HDF-EOS to GeoTIFF 
> conversion.
> 
> There are numerous interesting paths that we can take the toolkit in -- as 
> conversion from remotely sensed data to GeoTIFF involves ensuring that the 
> HDF-EOS metadata elements can be appropriately represented using GeoTIFF 
> headers, and the associated format. Furthermore, capturing the HDF's 
> appropriate geo datum in GeoTIFF will be another important challenge.
> 
> == Background ==
> 
> GeoTIFF is a data and metadata standard for Earth science applications. It is 
> based on binary Tagged Image File Format (TIFF).  A GeoTIFF file has 
> geographic (or cartographic) data embedded as tags within the TIFF file that 
> are used to geo-locate the image. This is required for correct integration of 
> the image in Geographic Information Systems (GIS) and other popular tools 
> like Google Earth Pro.
> 
> In the recent years, GeoTIFF has gained popularity as a visualization format 
> among NASA HDF Earth science user communities according to the NASA data 
> user's survey. However, the conversion from HDF to GeoTIFF is not 
> straightforward for end users because NASA HDF data products are diverse and 
> organized in many different ways. For example, go to http://hdfeos.org/zoo 
> and you'll see many scripting language examples because no single script can 
> correctly visualize all NASA HDF data.
> 
> == Rationale ==
> 
> The HEG tool is limited to some NASA HDF-EOS2 products (no support for 
> HDF-EOS5 products) and it is not an open-source tool. The latest GDAL 
> (version 1.9.2 and above) is an open-source tool but it cannot handle many 
> non-HDF-EOS NASA HDF products such as TRMM (pure HDF4) and Aquarius (pure 
> HDF5) correctly and automatically.
> 
> == Initial Goals ==
> 
> We'll improve GDAL to support NASA HDF products better by handling 
> geo-location information and physical meaning of data correctly and 
> automatically.
> 
> We'll handle NASA products intelligently so novice users don't have to supply 
> many options or figure out the details about the data products. For advanced 
> users, we'll give a full control of accessing HDF products in many different 
> ways so that the converted GeoTIFF file is scientifically valid and 

Re: [VOTE] Accept Apache MetaModel into the Apache incubator

[Suresh Marru]

+ 1 (binding)

All the best,
Suresh
On Jun 6, 2013, at 6:30 PM, Henry Saputra  wrote:

> Hi All,
> 
> I'd like to call a VOTE for acceptance of MetaModel into the Apache
> incubator.
> The vote will close on June 12, 2013 at 6:00 PM (PST).
> 
> [] +1 Accept MetaModel into the Apache incubator
> [] +0 Don't care.
> [] -1 Don't accept MetaModel into the incubator because...
> 
> Full proposal is pasted at the bottom on this email, and the corresponding 
> wiki
> is:
> http://wiki.apache.org/incubator/MetaModelProposal.
> 
> Only VOTEs from Incubator PMC members are binding, but all are welcome to
> express their thoughts.
> 
> Thanks,
> 
> Henry Saputra
> Champion for Apache MetaModel
> 
> 
> P.S. Here's my +1 (binding)
> 
> 
> -
> 
> = MetaModel – uniform data access across datastores =
> 
> Proposal for Apache Incubator
> 
> == Abstract ==
> 
> MetaModel is a data access framework, providing a common interface for
> exploration and querying of different types of datastores.
> 
> == Proposal ==
> 
> MetaModel provides a uniform meta-model for exploring and querying the
> structure of datastores, covering but not limited to relational databases,
> various data file formats, NoSQL databases, Salesforce.com, SugarCRM and
> more. The scope of the project is to stay domain-agnostic, so the
> meta-model will be concerned with schemas, tables, columns, rows,
> relationships etc.
> 
> On top of this meta-model a rich querying API is provided which resembles
> SQL, but built using compiler-checked Java language constructs. For
> datastores that do not have a native SQL-compatible query engine, the
> MetaModel project also includes an abstract Java-based query engine
> implementation which individual datastore-modules can adapt to fit the
> concrete datastore.
> 
> === Background ===
> 
> The MetaModel project was initially developed by eobject.dk to service the
> DataCleaner application (http://datacleaner.org). The main requirement was
> to perform data querying and modification operations on a wide range of
> quite different datastores. Furthermore a programmatic query model was
> needed in order to allow different components to influence the query plan.
> 
> In 2009, Human Inference acquired the eobjects projects including
> MetaModel. Since then MetaModel has been put to extensive use in the Human
> Inference products. The open source nature of the project was reinforced,
> leading to a significant growth in the community.
> 
> MetaModel has successfully been used in a number of other open source
> projects as well as mission critical commercial software from Human
> Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org.
> 
> === Rationale ===
> 
> Different types of datastores have different characteristics, which always
> lead to the interfaces for these being different from one another.
> Standards like JDBC and the SQL language attempt to standardize data
> access, but for some datastore types like flat files, spreadsheets, NoSQL
> databases and more, such standards are not even implementable.
> 
> Specialization in interfaces obviously has merit for optimized usage, but
> for integration tools, batch applications and or generic data modification
> tools, this myriad of specialized interfaces is a big pain. Furthermore,
> being able to query every datastore with a basic set of SQL-like features
> can be a great productivity boost for a wide range of applications.
> 
> === Initial goals ===
> 
> MetaModel is already a stable project, so initial goals are more oriented
> towards an adaption to the Apache ecosystem than about functional changes.
> 
> We are constantly adding more datastore types to the portfolio, but the
> core modules have not had drastic changes for some time.
> 
> Our focus will be on making ties with other Apache projects (such as POI,
> Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project
> to something more rememberable.
> This includes comply with Apache Software Foundation license for third
> party dependencies.
> 
> == Current status ==
> 
> === Meritocracy ===
> 
> We intend to do everything we can to encourage a meritocracy in the
> development of MetaModel. Currently most important development and design
> decisions have been made at Human Inference, but with an open window for
> anyone to participate on mailing lists and discussion forums. We believe
> that the approach going forward should be more encouraging by sharing all
> the design ideas and discussions in the open, not only just the topics that
> have been “dragged” into the open by third parties.  We believe that
> meritocracy will be further stimulated by granting the control of the
> project to an independent committee.
> 
> === Community ===
> 
> The community around MetaModel already exists, but we believe it will grow
> substantially by becoming an Apache project. With MetaModel used in a wide
> range of both open and closed source

Re: [PROPOSAL] Apache Spark for the Incubator

[Suresh Marru]

On May 31, 2013, at 2:03 PM, "Mattmann, Chris A (398J)" 
 wrote:

> Hi Folks,
> 
> I'm pleased to bring you a proposal to the Apache Incubator for the Apache
> Spark project: https://wiki.apache.org/incubator/SparkProposal
> 
> The work originates from the Berkeley AMPLab and through a number of
> industry
> participants, and other institutions. Spark is a framework for large-scale
> data 
> analysis on clusters, with a particular focus on low latency operations.
> The
> source code is written in Scala, and provides a number of APIs and bindings
> in various programming languages.
> 
> The proposal text is copied to the bottom of this email. I'm going to leave
> this thread open for the next week for discussion. Once it's died down,
> I'll
> call an official VOTE.
> 
> Suresh, Ross G. -- heads up -- this project may be of interest to you both
> and would welcome you guys as additional mentors. We currently have 3
> mentors
> committed to the project, but would love to have more.

Thanks Chris for the alert. Great proposal indeed, if the podling needs help I 
am in.

Suresh


> People interested in
> contributing should declare their interest here on the general@incubator
> thread
> and those potential contributors will be discussed by the incoming Spark
> community.
> 
> Questions -- let's hear em'! :)
> 
> Cheers,
> Chris
> ("Champion", incoming Apache Spark)
> 
> === Abstract ===
> Spark is an open source system for large-scale data analysis on clusters.
> 
> === Proposal ===
> Spark is an open source system for fast and flexible large-scale data
> analysis. Spark provides a general purpose runtime that supports
> low-latency execution in several forms. These include interactive
> exploration of very large datasets, near real-time stream processing, and
> ad-hoc SQL analytics (through higher layer extensions). Spark interfaces
> with HDFS, HBase, Cassandra and several other storage storage layers, and
> exposes APIs in Scala, Java and Python.
> Background
> Spark started as U.C. Berkeley research project, designed to efficiently
> run machine learning algorithms on large datasets. Over time, it has
> evolved into a general computing engine as outlined above. Spark¹s
> developer community has also grown to include additional institutions,
> such as universities, research labs, and corporations. Funding has been
> provided by various institutions including the U.S. National Science
> Foundation, DARPA, and a number of industry sponsors. See:
> https://amplab.cs.berkeley.edu/sponsors/ for full details.
> 
> === Rationale ===
> As the number of contributors to Spark has grown, we have sought for a
> long-term home for the project, and we believe the Apache foundation would
> be a great fit. Spark is a natural fit for the Apache foundation: Spark
> already interoperates with several existing Apache projects (HDFS, HBase,
> Hive, Cassandra, Avro and Flume to name a few). The Spark team is familiar
> with the Apache process and and subscribes to the Apache mission - the
> team includes multiple Apache committers already. Finally, joining Apache
> will help coordinate the development effort of the growing number of
> organizations which contribute to Spark.
> 
> == Initial Goals ==
> The initial goals will most likely be to move the existing codebase to
> Apache and integrate with the Apache development process. Furthermore, we
> plan for incremental development, and releases along with the Apache
> guidelines.
> 
> === Current Status ===
> == Meritocracy ==
> The Spark project already operates on meritocratic principles. Today,
> Spark has several developers and has accepted multiple major patches from
> outside of U.C. Berkeley. While this process has remained mostly informal
> (we do not have an official committer list), an implicit organization
> exists in which individuals who contribute major components act as
> maintainers for those modules. If accepted, the Spark project would
> include several of these participants as committers from the onset. We
> will work to identify all committers and PPMC members for the project and
> to operate under the ASF meritocratic principles.
> 
> === Community ===
> Acceptance into the Apache foundation would bolster the already strong
> user and developer community around Spark. That community includes dozens
> of contributors from several institutions, a meetup group with several
> hundred members, and an active mailing list composed of hundreds of users.
> Core Developers
> The core developers of our project are listed in our contributors and
> initial PPMC below. Though many exist at UC Berkeley, there is a
> representative cross sampling of other organizations including Quantifind,
> Microsoft, Yahoo!, ClearStory Data, Bizo, Intel, Tagged and Webtrends.
> 
> 
> === Alignment ===
> Our proposed effort aligns with several ongoing BIGDATA and U.S. National
> priority funding interests including the NSF and its Expeditions program,
> and the DARPA XDATA project. Our indu

Re: [VOTE] Accept Apache BeanShell in the Incubator

[Suresh Marru]

+ 1 (binding)

Suresh

On May 24, 2013, at 3:23 AM, Simone Tripodi  wrote:

> Dear ASF members,
> 
> We would like to propose BeanShell for the incubator.
> 
> The proposal draft is available at:
> https://wiki.apache.org/incubator/BeanShellProposal,
> follows below the proposal
> 
> Open is open for at least 72h and closes approximately on May 27th at 8:20am 
> GMT
> 
> [ ] +1 accept BeanShell in the Incubator
> [ ] +/-0
> [ ] -1 because (provide a reason)
> 
> Many thanks in advance, all the best!
> -Simo
> 
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
> 
> ~~~
> 
> = BeanShell =
> == Abstract ==
> The following proposal is about BeanShell, see JSR-274: The BeanShell
> Scripting Language implementation.
> 
> == Proposal ==
> BeanShell is a small, free, embeddable Java source interpreter with
> object scripting language features, written in Java. BeanShell
> dynamically executes standard Java syntax and extends it with common
> scripting conveniences such as loose types, commands, and method
> closures like those in Perl and JavaScript.
> Users can use BeanShell interactively for Java experimentation and
> debugging as well as to extend your applications in new ways.
> Scripting Java lends itself to a wide variety of applications
> including rapid prototyping, user scripting extension, rules engines,
> configuration, testing, dynamic deployment, embedded systems, and even
> Java education.
> BeanShell is small and embeddable, so users can call BeanShell from
> Java applications to execute Java code dynamically at run-time or to
> provide extensibility in applications. Alternatively, users can use
> standalone BeanShell scripts to manipulate Java applications; working
> with Java objects and APIs dynamically. Since BeanShell is written in
> Java and runs in the same VM as application, users can freely pass
> references to "live" objects into scripts and return them as results.
> 
> == Background ==
> BeanShell is a long living project born in the 2000 thanks to Patrick
> Niemeyer initial effort, who is still maintaining the project, with
> the help of Daniel Leuck and contributions voluntarily sent by users.
> 
> == Rationale ==
> Currently there are no projects hosted by the ASF focused on providing
> JSR-274 implementation, moving the existing BeanShell project under
> the Apache umbrella would mean the ASF provides the JSR-274 reference
> implementation.
> 
> = Current Status =
> == Meritocracy ==
> The historical BeanShell team believes in meritocracy and always acted
> as a community. Mailing list, open issue tracker and other
> communication channels have always been adopted since its first
> release. The adoption in a larger community, such as Apache, is the
> natural evolution for BeanShell. Moreover, the Apache standards will
> enforce the existing BeanShell community practices and will be a
> foundation for future committers involvement.
> 
> == Core Developers ==
> In alphabetical order:
> 
> * Daniel Leuck ,
> * Patrick Niemeyer 
> * Pedro Giffuni 
> * Simone Tripodi 
> 
> == Alignment ==
> Main aim of the project is to develop and maintain a fully flavored
> JSR-274 implementation that can be used by other Apache projects that
> need a Java  Scripting Language.
> 
> = Known Risks =
> == Orphaned Products ==
> The increasing number of BeanShell adopters and the raising interest
> for the JSR-274 technology let us believe that there is a minimal risk
> for this work to being abandoned from the community.
> 
> Moreover, BeanShell has been already used by the following projects for years:
> 
> * Apache OpenOffice
> * Apache Maven
> * Apache JMeter
> 
> == Inexperience with Open Source ==
> All of the committers have experience working in one or more open
> source projects inside and outside ASF.
> 
> == Homogeneous Developers ==
> The list of initial committers are geographically distributed across
> the world with no one company being associated with a majority of the
> developers.  Many of these initial developers are experienced Apache
> committers already  and all are experienced with working in
> distributed development communities.
> 
> == Reliance on Salaried Developers ==
> To the best of our knowledge, none of the initial committers are being
> paid to develop code for this project. BeanShell has already proven
> its capability to attract external developers.
> 
> == Relationships with Other Apache Products ==
> A number of existing ASF projects already benefit from BeanShell
> implementation, including Apache OpenOffice, Apache Maven and Apache
> JMeter. It is hoped that members of those projects will be interested
> in contributing to and adopting this implementation.
> 
> == An Excessive Fascination with the Apache Brand ==
> Even if the BeanShell community recognizes the power and the
> attractiveness  of 

Re: If I were king of the forest

[Suresh Marru]

On May 8, 2013, at 2:40 PM, Alan Cabrera  wrote:
> One last suggested refinement:
> 
> At least two mentors, but perhaps not allow more than three, where the 
> third is generally a backup for the others in a transition period, such 
> as one of the mentors looking to shed their responsibilities. One point 
> that has come out of the discussion has been a lack of clear 
> responsibility. Adding more mentors dilutes that responsibility. Two 
> allows one as backup for the other.
 
 Yes, this was what I was thinking as well.  Two active mentors, maybe one 
 or two inactive ones but since they officially declared themselves 
 inactive the active mentor know not to assume anything of them.
>>> 
>>> I may be incorrect in my understanding of the official ASF policy here
>>> [1], but WRT a release, doesn't it require at least 3 +1 votes of the
>>> appropriate PMC (in the case of podlings, the IPMC)?  If the mentors
>>> were limited to 2 within the podlings, then would that leave all podling
>>> in a position of having to get a third +1 from the IPMC?
>> 
>> We're the IPMC, we can change the rules if we need to.
> 
> Oh, I see this is an ASF rule.  Maybe we should have three active mentors?

Three active mentors is fine. But I personally would rather prefer a trip to 
general for the 3rd vote just to get diverse perspectives. But again this is 
debatable in the light of unattended release threads, but I am looking at the 
positive learning aspect here. But I am not a good judge of whats best because 
I hardly have spent time to verify releases outside the projects I am 
mentoring. I am eager to hear from people like Sebb who provide outstanding 
release verification in this forum. Will a lazy consensus IPMC time be as 
motivating (for taking time to verify releases) as the required 3rd vote? 

In any case, I will not divert the topic and dilute the just of the entire 
thread. Looking foreword to see all these threads converge into some actionable 
form soon. 

Suresh

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


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

Re: If I were king of the forest

[Suresh Marru]

On May 8, 2013, at 3:31 AM, Alan Cabrera  wrote:

> If I were king of the forest, I would be to fire all the mentors.  All 
> except, of course, me, because I'm the king.  :) All the ex-mentors would 
> become emeritus mentors that can be reinstated merely by asking.

There is a fundamental flaw here, there is no mention of how the king can be 
impeached and a new king be sworn in :). kidding, great thoughts Alan, more 
below. 

> Those emeritus mentors who wish to remain mentors must acknowledge that they 
> will perform their duties as out lined in a clearly defined document.  All 
> mentors must be IPMC members, period.  People who wish to become mentors that 
> are not in the IPMC must be a novice mentor, whose mentorship is not counted 
> as an active mentor, for at least one podling's incubation.  ASF members can 
> become IPMC members.  Non-ASF members must mentor a project before becoming 
> an IPMX member.
> 
> The champion role would be removed.  
> 
> Shepherd roles would be removed.

I certainly agree that this simple structure will be more sustainable then the 
work around layers which we have seen slowly gets diluted. 

> Podlings would be required to have a minimum of two active mentors.  A mentor 
> is free to become inactive but must explicitly state this else the mentor 
> risks being removed for not performing their duties.  Podlings that do not 
> have the minimum of two active mentors are put on hold until they find enough 
> mentors to fill the quota.  Being put on hold means that no committers can be 
> added, no PPMC members can be added, and no releases can be performed.  It 
> does not stop development.
> 
> People starting threads must provide editorial summaries else the thread is 
> considered to be a tree falling in the forest.  If you can't commit to 
> providing summaries then you shouldn't start threads that waste people's time.
> 
> Releases need +1 votes from the two active mentors.  A subsequent 72 hour 
> quiet period would follow for IPMC members to vote as well.

I am assuming (or rather hoping) the third vote will happen on the general 
list. Which ever form the incubator (or lack of) shapes into, the general list 
is were I have seen the most cross-fertizliation happens. I agree that we need 
to address releases not getting attention, I felt the release trips to general 
were extremely educational. During incubation, this process felt too painful 
and furstrating but looking back, release process and gets vastly improvised 
during these iterations. And once set out on a right tone, its a matter of 
incrementally maintaining it.

> I would make hard decisions and actively retire inactive projects.
> 
> I would start more tooling initiatives to automate even more mundane tasks 
> that are a drag to incubation.

+ 1. 

Constructive wishes over all,

Suresh

> 
> 
> What we would gain is transparency and simplicity.  There would be no false 
> expectations.  Podlings would know where they stand.  Work would be equitably 
> distributed.
> 
> 
> No more layers.  No more additional roles.  No more shuffling.  The solution 
> is not more process and more complexity.
> 
> But I am not the king.  It is my sincere hope that we drop useless, imho, 
> baby steps that only serve to churn up email storms and ill will, and take 
> the bold steps needed to re-invigorate this, most critical, project of the 
> ASF.
> 
> Just my 2 cents.
> 
> 
> Regards,
> Alan
> 


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

Re: Would like to be added to Climate incubator group

[Suresh Marru]

On May 6, 2013, at 2:15 PM, Michael Joyce  wrote:

> Hello!
> 
> I just wanted to check up on this. Is there anything I need to do to help
> get this resolved?
> 
> Thanks much!
> 
> 
> On Mon, Apr 29, 2013 at 8:41 PM, Michael Joyce  wrote:
> 
>> Hello!
>> 
>> I'm part of the Open Climate Workbench podling and need to be added to the
>> incubator group for commits. Can you help me out?

Hi Michael,

If I am understanding your request correctly, you were listed as the Initial 
Committers when the Climate Proposal [1] was approved and you are wanting to 
have the right commit bits right? I just added you to incubator unix group, I 
see you are already added to climate group in asf-authorization-template. Try a 
commit to climate svn. 

Cheers,
Suresh 

[1] - http://wiki.apache.org/incubator/ClimateProposal


>> 
>> Thanks much
>> 


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

Re: Looking for a Champion

[Suresh Marru]

Yes this is the right list for soliciting champion and mentors. 

Suresh

On May 6, 2013, at 7:04 PM, Tom Everett  wrote:

> Good afternoon.
> 
> I have a project which I am hoping to submit to the incubator, and I
> understand from the documentation that it is recommended to identify a
> champion prior to the incubator application. Is this mailing list an
> appropriate place to solicit for such a person?
> 
> 
> 
> -- 
> A better world shall emerge based on faith and understanding  - Douglas
> MacArthur


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

Re: [VOTE] Accept jclouds into the Apache Incubator

[Suresh Marru]

t gmail dot com
> * Andrew Bayer, abayer at apache dot org
> * Ioannis Canellos, iocanel at gmail dot com
> * Adrian Cole, adrianc at netflix dot com 
> * Andrew Gaul, gaul at maginatics dot com
> * Andrew Phillips, aphillips at qrmedia dot com
> * Matt Stephenson, mattstep at mattstep dot net
> * Everett Toews, everett dot toews at rackspace dot com
> * Becca Wood, silkysun at silkysun dot net
> 
> == Affiliations ==
> 
> * Ignasi Barrera, Abiquo
> * Andrew Bayer, Cloudera
> * Ioannis Canellos, Red Hat
> * Adrian Cole, Netflix
> * Andrew Gaul, Maginatics
> * Matt Stephenson, Google
> * Everett Toews, Rackspace  
> 
> == Sponsors ==
> === Champion ===
> 
> * Brian McCallister, Apache Software Foundation
> 
> === Mentors ===
> 
> * Brian McCallister, Apache Software Foundation
> * Tom White, Apache Software Foundation
> * Henning Schmiedehausen, Apache Software Foundation
> * David Nalley, Apache Software Foundation
> * Jean-Baptiste Onofré, Apache Software Foundation
> * Mohammad Nour El-Din, Apache Software Foundation
> * Olivier Lamy, Apache Software Foundation
> * Tomaz Muraus, Apache Software Foundation
> * Suresh Marru, Apache Software Foundation
> * Carlos Sanchez, Apache Software Foundation
> 
> === Sponsoring Entity ===
> 
> The jclouds contributors and community request sponsorship from the Incubator.
> 


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

Re: [PROPOSAL] jclouds Proposal for Incubator

[Suresh Marru]

On Apr 16, 2013, at 9:04 PM, Matt Stephenson  wrote:

> Thanks to everyone stepping up to be a mentor!  I personally do 300 jumping
> jacks in the name of jclouds on a weekly basis, so we're cutting our
> mentors a great deal!

+ 1 the 2 hours/week mentor time is to make sure podling committers do the 
jumping jacks :). 

Adrian, Matt, I am vary of the time commitment and onboard with it.

Cheers,
Suresh

> 
> I really like our proposal, but I'm biased.  Obviously we wanna be a part
> of Apache, so this kind of acceptance by the community is amazingly great
> news!
> 
> 
> Matt
> 
> 
> On Tue, Apr 16, 2013 at 5:17 PM, Adrian Cole  wrote:
> 
>> Thanks, Suresh.  Airavata looks like it has context for collaboration with
>> jclouds for sure.
>> 
>> WRT mentoring, I was going to warn you.. all mentors have implicitly signed
>> up for 2 hours/week on process guidance and 35 jumping jacks.
>> 
>> -A
>> 
>> 
>> On Tue, Apr 16, 2013 at 4:59 PM, Suresh Marru  wrote:
>> 
>>> Nice Proposal, looking forward to see jcloud flourish in Apache. Glad to
>>> see such a overwhelming mentor support.
>>> 
>>> I am interested to see this as an abstraction for Apache Airavata, I do
>>> not think you need more mentors, but I will be happy to help as needed as
>>> well (either onboard as mentor or on this list).
>>> 
>>> Cheers,
>>> Suresh
>>> 
>>> On Apr 16, 2013, at 7:51 PM, Adrian Cole  wrote:
>>> 
>>>> Tomaz and Olivier (and David)
>>>> 
>>>> You guys are awesome to offer help.  I thought maybe 5 was the number
>> of
>>>> mentors we needed, but I heard a sentiment of "the more the merrier"
>> So,
>>>> I'm adding any apache member with experience with incubation that
>> offers
>>> to
>>>> help us.  Seems a better problem to have more advice than less, and
>> now a
>>>> fleet of apache members can take holiday and we can still get enough
>>> votes
>>>> to release something :)
>>>> 
>>>> Cheers, thanks for the kind words, and lets do this!
>>>> -A
>>>> 
>>>> 
>>>> On Tue, Apr 16, 2013 at 4:45 PM, Tomaz Muraus 
>> wrote:
>>>> 
>>>>> Agreed and best of luck from the Apache Libcloud PMC :)
>>>>> 
>>>>> If you are looking for additional mentors I'm also more than happy to
>>> help.
>>>>> 
>>>>> (I would add myself under "volunteer" section on the wiki, but it
>> looks
>>>>> like I don't have the necessary permissions).
>>>>> 
>>>>> On Tue, Apr 16, 2013 at 12:19 PM, David Nalley  wrote:
>>>>> 
>>>>>> On Tue, Apr 16, 2013 at 2:34 PM, Rebecca Wood 
>>>>> wrote:
>>>>>>> Dear ASF members,
>>>>>>> We would like to propose the jclouds project to the Incubator.  The
>>>>>> jclouds Proposal is available at:
>>>>>>> 
>>>>>>> http://wiki.apache.org/incubator/jcloudsProposal
>>>>>>> 
>>>>>>> We welcome your feedback and suggestions.
>>>>>> 
>>>>>> Excited to see jclouds proposal.
>>>>>> If you are looking for additional mentors, I'd be happy to step up.
>>>>>> 
>>>>>> --David
>>>>>> 
>>>>>> -
>>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>>> 
>>>>>> 
>>>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
>> 


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

Re: [PROPOSAL] jclouds Proposal for Incubator

[Suresh Marru]

Nice Proposal, looking forward to see jcloud flourish in Apache. Glad to see 
such a overwhelming mentor support.

I am interested to see this as an abstraction for Apache Airavata, I do not 
think you need more mentors, but I will be happy to help as needed as well 
(either onboard as mentor or on this list).

Cheers,
Suresh

On Apr 16, 2013, at 7:51 PM, Adrian Cole  wrote:

> Tomaz and Olivier (and David)
> 
> You guys are awesome to offer help.  I thought maybe 5 was the number of
> mentors we needed, but I heard a sentiment of "the more the merrier"  So,
> I'm adding any apache member with experience with incubation that offers to
> help us.  Seems a better problem to have more advice than less, and now a
> fleet of apache members can take holiday and we can still get enough votes
> to release something :)
> 
> Cheers, thanks for the kind words, and lets do this!
> -A
> 
> 
> On Tue, Apr 16, 2013 at 4:45 PM, Tomaz Muraus  wrote:
> 
>> Agreed and best of luck from the Apache Libcloud PMC :)
>> 
>> If you are looking for additional mentors I'm also more than happy to help.
>> 
>> (I would add myself under "volunteer" section on the wiki, but it looks
>> like I don't have the necessary permissions).
>> 
>> On Tue, Apr 16, 2013 at 12:19 PM, David Nalley  wrote:
>> 
>>> On Tue, Apr 16, 2013 at 2:34 PM, Rebecca Wood 
>> wrote:
 Dear ASF members,
 We would like to propose the jclouds project to the Incubator.  The
>>> jclouds Proposal is available at:
 
 http://wiki.apache.org/incubator/jcloudsProposal
 
 We welcome your feedback and suggestions.
>>> 
>>> Excited to see jclouds proposal.
>>> If you are looking for additional mentors, I'd be happy to step up.
>>> 
>>> --David
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
>> 


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

Re: [VOTE] recommend Apache DeltaSpike for graduating out of the incubator

[Suresh Marru]

+ 1 (binding).

All the best as a TLP,
Suresh

On Mar 30, 2013, at 12:54 PM, Mark Struberg  wrote:

> Hi!
> 
> The Apache DeltaSpike podling is a project which contains common CDI 
> Extensions which are portable among many different Java EE containers and 
> even run on standalone CDI containers.  
> 
> We are now incubating since December 2011 and believe we are ready for 
> graduation. We've shipped 3 releases and already see wide adoption in the 
> industry.
> We've already done an internal VOTE on the proposal which passed with a big 
> majority [1].
> 
> 
> The voices who raised concerns were mainly afraid of DeltaSpike not being 
> 'finished' yet. But graduation doesn't mean that the product is final and 
> switches to maintenance, but that it is vital and there is an active 
> community around it. And this is certainly the case as shown by the 21 votes 
> we got the last days.
> 
> 
> Our status file [2] got updated recently and I consider the podling 
> namesearch task as completed [3].
> 
> 
> Thus I'd like to ask the IPMC to VOTE on recommending the attached graduation 
> proposal to the board.
> 
> [+1] yes, go forward
> 
> [+0] meh, don't care
> [-1] nope, because there's a blocker ${blocker_reason}
> 
> 
> The VOTE is open for 72h 
> 
> 
> txs and LieGrue,
> strub
> 
> 
> 
> [1] http://markmail.org/message/bmhr5woxidmgheco
> [2] http://incubator.apache.org/projects/deltaspike.html
> 
> [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-31
> 
> 
>  
> Proposed Board Resolution Report
> X. Establish the Apache DeltaSpike Project
> 
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of 
> open-source software related to creating a set
> of portable CDI (JSR-299) Extensions
> for distribution at no charge to the public.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache DeltaSpike Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that the Apache DeltaSpike Project be and hereby is
> responsible for the creation and maintenance of open-source 
> software related to creating a set of portable CDI Extensions; 
> and be it further
> 
> RESOLVED, that the office of "Vice President, Apache DeltaSpike" 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 DeltaSpike Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache DeltaSpike 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 DeltaSpike Project:
> 
> Gerhard Petracek 
> Mark Struberg 
> Pete Muir 
> Jason Porter 
> Shane Bryzak 
> Rudy de Busscher  Christian Kaltepoth 
> Arne Limburg 
> Charles Moulliard 
> Cody Lerum 
> Romain Mannu-Buccau 
> Matthew Jason Benson 
> Jim Jagielski 
> David Blevins 
> Ken Finnigan 
> John D. Ament 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Struberg
> be appointed to the office of Vice President, Apache DeltaSpike, 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 DeltaSpike 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 DeltaSpike Project; and be it further
> 
> RESOLVED, that the Apache DeltaSpike Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator DeltaSpike podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator DeltaSpike podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
> 
> 
> 
> https://cwiki.apache.org/confluence/display/DeltaSpike/Graduation+Proposal
> 
> -
> 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 CloudStack from Incubator

[Suresh Marru]

+ 1 (binding)

Great going in a short time (given the size of the project), All the best as a 
TLP,
Suresh

On Mar 14, 2013, at 12:47 PM, Chip Childers  wrote:

> Apache CloudStack entered the Incubator in April of 2012. We have made
> significant progress with the project since moving over to Apache. 
> 
> We have 31 committers and 13 PPMC members listed on our status page at [1], 
> not including the 8 mentors that helped guide our community through 
> incubation.  
> 16 of the committers and 7 of the PPMC members were added after the podling 
> was
> formed. One mentor joined the project after the podling started.  3 of the 
> initial
> committers that were not in the initial PPMC have now joined the PPMC. 7 of 
> our 
> mentors will be remaining with the project as it transitions into a TLP.
> 
> We have verified that Apache CloudStack is a suitable name [2], and the
> CloudStack marks are being donated from Citrix to the ASF.
> 
> We completed two releases (Apache CloudStack 4.0.0-incubating and Apache 
> CloudStack 4.0.1-incubating) and are currently preparing for two more (4.0.2 
> and 4.1.0).
> 
> Our community has created a set of bylaws for the project [3].
> 
> The community of Apache CloudStack is active, healthy, and growing and has
> demonstrated the ability to self-govern using accepted Apache practices.
> 
> After holding a discussion [4][5], the Apache CloudStack community 
> subsequently 
> voted overwhelmingly to graduate [6], collecting 55 +1 votes (including 
> 4 from IPMC members), and no +0 or -1 votes.
> 
> IPMC members voting +1 in the project-level thread are:
> * Mohammad Nour El-Din (IPMC/mentor) [7]
> * Noah Slater (IPMC/mentor) [8]
> * Alex Karasulu (IPMC/mentor) [9]
> * Brett Porter (IPMC/mentor) [10]
> 
> Please cast your votes:
> 
> [ ] +1 Graduate Apache CloudStack from Apache Incubator
> [ ] +0 Indifferent to graduation status of Apache CloudStack
> [ ] -1 Reject graduation of Apache CloudStack from Apache Incubator because...
> 
> -chip
> 
> 
> [1] http://incubator.apache.org/projects/cloudstack.html
> [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-23
> [3] https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
> [4] 
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3C20130213145014.GE800%40USLT-205755.sungardas.corp%3E
> [5] http://markmail.org/message/3nluchj5q5waguws
> [6] http://markmail.org/message/ntf777ctbhdytijp
> [7] 
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAOvkMoa4yK-L7T7OjER2pfWAAtkrOnZOe-icMPkoesWgAUDPbg%40mail.gmail.com%3E
> [8] 
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3CCAPaJBx6f4a58xky0jmVjn=xcyvxuu4dxduetqsr9ovwj80n...@mail.gmail.com%3E
> [9] 
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3ccadwpi+gfnodtuydyuy8vzm3rttzbsbq1krzzukwe4-t_qnn...@mail.gmail.com%3E
> [10] 
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201303.mbox/%3c6f99d33d-641a-4b7d-8387-a420f8a88...@apache.org%3E
> 
> 
> Proposed Resolution:
> 
> X. Establish the Apache CloudStack 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 and supporting Infrastructure-as-a-Service (IaaS)
> cloud computing platforms.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache CloudStack Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache CloudStack Project be and hereby is responsible
> for the creation and maintenance of software related to providing and 
> supporting Infrastructure-as-a-Service (IaaS) cloud computing platforms.
> 
> RESOLVED, that the office of "Vice President, Apache CloudStack" 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 CloudStack Project, and 
> to
> have primary responsibility for management of the projects within the scope
> of responsibility of the Apache CloudStack 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 CloudStack 
> Project:
> 
> * Joe Brockmeier 
> * Will Chan 
> * Chip Childers 
> * Mohammad Nour El-Din 
> * Sebastien Goasguen 
> * Matt Richard Hogstrom 
> * Wido den Hollander 
> * Alex Huang 
> * Jim Jagielski 
> * Alex Karasulu 
> * John Kinsella 
> * Kevin Kluge 
> * Olivier Lamy 
> * David Nalley 
> * Brett Porter 
> * Noah Slater 
> * Marcus Sorensen 
> * Edison Su 
> * Hugo Trippaers 
> * Chiradeep Vittal 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, tha

Re: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator

[Suresh Marru]

On Mar 15, 2013, at 6:25 PM, ant elder  wrote:

> On Fri, Mar 15, 2013 at 1:28 PM, Alex Karasulu  wrote:
> 
>> On Fri, Mar 15, 2013 at 3:01 PM, ant elder  wrote:
>> 
>>> On Fri, Mar 15, 2013 at 12:16 PM, Alex Karasulu >>> wrote:
>>> 
 On Fri, Mar 15, 2013 at 10:21 AM, Edward J. Yoon <
>> edwardy...@apache.org
> wrote:
 
>> could you please close the "Create MRQL" tasks in the Infra Jira
>>> until
>> the situation has been cleared up. Whenever this all has been
>> sorted
>> out you can reopen the issues.
> 
> Sure.
> 
> Since this might not be fixed soon, proposal can be changed
> (especially corporation volunteers). And, thank you for your
> suggestion, but I'm already in initial committers list.
> 
> To IPMC, I would request you to focus more on reviewing Proposal in
> the future. The opportunity of MRQL should not be faded by my
>> mistake.
> 
> 
 Bravo! There was no malice in the vote, just a simple mistake. If need
>>> be I
 or Mo can take on the Champion role.
 
 Are there others from the IPMC that would be interested in mentoring
>>> MRQL?
 
 --
 Best Regards,
 -- Alex
 
>>> 
>>> The champion role is really just to help the proposal through any
>>> discussion prior to being accepted as a poddling so thats been done and
>> it
>>> makes little difference now.
>> 
>> 
>> True. I'm totally down with your reasoning.
>> 
>> But don't you think it might be a formality we need to comply with, even if
>> it does not make sense at this stage?
>> 
>> 
> There has been a vote, which passed with enough binding votes, no one has
> -1'd, and no one has retracted their vote. Lets wait till Monday and if the
> majority vote still passes just carry on with the additional mentors. I
> hope no one does -1, theres several experienced mentors now so nothing
> really to be gained from forcing some new vote.
> 
>   ...ant

I fully agree. I had a chance also to look at the proposal closely, so will +1 
if the vote is re-opened, but I see no need for it. Its in the hands of 
competent mentors and the podling is ready to get on board.

Suresh



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

Re: Looking for a volunteer to finalize the March report

[Suresh Marru]

Nice report Matt, it looks very good summary. Thanks for volunteering to pull 
this together and shepherding a good number of podlings.

Suresh

On Mar 15, 2013, at 4:24 PM, Matt Franklin  wrote:

> Last call for comments on the report.  I will commit it to SVN later
> this evening.
> 
> On Thu, Mar 14, 2013 at 9:24 AM, Matt Franklin  
> wrote:
>> I have added a draft commentary to the report in the wiki.  Since we
>> had no shepherd self-organization, I am asking for an immediate set of
>> volunteers who can review the podlings and provide shepherd comments
>> before Friday evening, when I will send the report to the board on
>> Benson's behalf.  If you have time and are willing, reply to this
>> thread with which podlings you would like to review and add your name
>> to the wiki.  Additionally, there are quite a few reports that need
>> mentor sign-off.  All mentors, please review your podling reports and
>> add your X.
>> 
>> On Wed, Mar 13, 2013 at 5:28 PM, Matt Franklin  
>> wrote:
>>> Working on it now.  Will have it ready in the morning for review &
>>> comment and will submit it to the board on Friday.
>>> 
>>> -Matt
>>> 
>>> On Mon, Mar 11, 2013 at 9:52 AM, Benson Margulies  
>>> wrote:
 Thanks!
 
 
 On Mon, Mar 11, 2013 at 7:28 AM, Matt Franklin 
 wrote:
 
> On Monday, March 11, 2013, Benson Margulies wrote:
> 
>> If no one else is willing to take this on, I will finalize the report on
>> Wednesday 13 March in the EDT evening, and it will contain what it
> contains
>> at that moment.
> 
> 
> I can do it.
> 
> 
>> 
>> 
>> On Sat, Mar 9, 2013 at 2:39 PM, Benson Margulies  
>>> wrote:
>> 
>>> Folks,
>>> 
>>> I will be travelling the week of 18 March, with somewhat uncertain
>>> networking and state of jet lag.
>>> 
>>> Would someone else be willing to tie off the report and deliver it to
> the
>>> board's doorstep?
>>> 
>>> --benson
>>> 
>>> 
>> 
> 
> 
> -
> 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 EasyAnt into Ant

[Suresh Marru]

+ 1 (binding)

Suresh

On Mar 12, 2013, at 11:06 AM, Nicolas Lalevée  
wrote:

> Hi,
> 
> The EasyAnt community would like to graduate as an subproject of Ant.
> 
> The Ant PMC has just accepted:
> http://mail-archives.apache.org/mod_mbox/ant-dev/201303.mbox/%3CBD5DB6B8-13BC-421F-800C-CE6CB21D7BF4%40hibnet.org%3E
> 
> The goal is to make EasyAnt a subproject of Ant, just like Ivy and IvyDE are.
> - EasyAnt code will be brought into Ant's svn tree.
> - EasyAnt committers will become Ant committers but not part of the PMC (on 5 
> committers, 3
> are already Ant ones, and 2 are part of Ant's PMC)
> - The Ant PMC will be responsible for the code, the community, the next 
> releases of EasyAnt.
> 
> Easyant has been incubating since 31/01/2011.
> A release has been done the 27/02/2013.
> 
> Some usefull links:
> - the EasyAnt project incubator page:
> http://incubator.apache.org/projects/easyant.html
> - the archive of the mailing lists
> http://mail-archives.apache.org/mod_mbox/incubator-easyant-commits/
> http://mail-archives.apache.org/mod_mbox/incubator-easyant-dev/
> - the release
> http://www.apache.org/dist/incubator/easyant
> 
> Please cast your votes over the graduation of Easyant as a subproject of Ant.
> 
> cheers,
> Nicolas
> -
> 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: Joining IPMC member

[Suresh Marru]

Hi Edward,

As you might know, generally speaking for PMC's merit is not transferable. But 
IPMC has one exception any member of the foundation can simply ask to be added 
(it still goes through the normal workflow of board acknowledgement and such, 
but without a formal IPMC voting). If the requester is not a member, IPMC also 
has to discuss and vote based on contributions, interest to help out just like 
any other PMC. Such requests to join should go to the private list. See [1]  
"Mentors MUST be on the IPMC. Any prospective Mentors who are not yet on the 
IPMC should ask to be added (by election). Email the application to 
priv...@incubator.apache.org. This process may take a few days."

I can see the source of your confusion both for asking on the general list and 
also interpreting an officer can be a champion. Its a misunderstanding, no 
worries. Your enthusiasm to help MRQL is certainly appreciated and once we have 
a IPMC member volunteer to champion the podling, everything should be back on 
track. I do not think MRQL will be hampered, just a delay. Its parked on the 
runway waiting to take off soon. Meanwhile sit back relax and have fun hacking. 
 

Suresh

[1] - http://incubator.apache.org/guides/mentor.html

On Mar 15, 2013, at 12:51 AM, Edward J. Yoon  wrote:

> The reason of opening here is that I see mails like "Request to join
> IPMC"[1]. Moreover I already sent a mail to private@ at Feb 27.
> 
> 1. 
> http://mail-archives.apache.org/mod_mbox/incubator-general/201202.mbox/%3c87945f79-c905-4cdf-af5b-d7a9b54f3...@gmail.com%3E
> 
> On Fri, Mar 15, 2013 at 1:25 AM, Suresh Marru  wrote:
>> On Mar 14, 2013, at 3:26 AM, Edward J. Yoon  wrote:
>> 
>>>>> understand why virtually all ASF projects adhere to that convention
>>>>> now?
>>> 
>>> P.S., It's been 6 years since I uploaded my first patch on HBase. I
>>> still don't know many things but I'm continuously learning from you
>>> guys ;-)
>> 
>> Hi Edward,
>> 
>> I do not think any one is questioning your credibility as a committer, or 
>> pmc member. I think Marvin hit it right and straight forward way. At ASF one 
>> of the few things (and primarily the only thing) like adding to a PMC is 
>> handled on private lists. Given that you have been contributing since 6 
>> years you are certainly expected to know it. It is not healthy to side track 
>> the issue with your contributions or citing emotional reasons.
>> 
>> Suresh
>> 
>> 
>>> On Thu, Mar 14, 2013 at 4:07 PM, Edward J. Yoon  
>>> wrote:
>>>> Yes, I think I'm not familiar with handling issues like personnel, and
>>>> somewhat emotional person.
>>>> 
>>>> However, I want to helping people who want to contribute to ASF or
>>>> collaborate with ASF projects in the future.
>>>> 
>>>> On Thu, Mar 14, 2013 at 3:46 PM, Marvin Humphrey  
>>>> wrote:
>>>>> Edward, are you not familiar with our custom of handling personnel
>>>>> matters on private lists? It has not always been that way, but do you
>>>>> understand why virtually all ASF projects adhere to that convention
>>>>> now?
>>>>> 
>>>>> Marvin Humphrey
>>>>> 
>>>>> On Wed, Mar 13, 2013 at 11:15 PM, Edward J. Yoon  
>>>>> wrote:
>>>>>> Hi,
>>>>>> 
>>>>>> I just noticed that Mentor must be members of the Incubator PMC[1].
>>>>>> Regarding MRQL podling, I'm not only Champion but also want to be a
>>>>>> Mentor for MRQL project.
>>>>>> 
>>>>>> Please add me to IPMC.
>>>>>> 
>>>>>> 1. 
>>>>>> http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor
>>>>>> 
>>>>>> --
>>>>>> Best Regards, Edward J. Yoon
>>>>>> @eddieyoon
>>>>>> 
>>>>>> -
>>>>>> 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: [INVALID][RESULT][VOTE] Accept MRQL into the Incubator

[Suresh Marru]

On Mar 14, 2013, at 9:25 PM, Edward J. Yoon  wrote:

> Maybe 3 including myself?

Hi Edward,

As you have previously pointed out Champion and Mentors are required to be IPMC 
members [1], [2]. So sorry you cannot be counted as a mentor/champion for MRQL. 

Since you have asked to be added to IPMC [3], I assume you realize you are not 
part of IPMC. Casting a binding vote on EasyAnt graduation [3] is not right.  
Please avoid creating such confusions. 

Suresh

[1] - 
http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor
[2] - 
http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Champion
[3] - http://markmail.org/message/ldoyqm3o5eifyzrl
[4] - http://markmail.org/message/dxqqa2cf6cpvoeyp

> or If we need to recruit one more Mentor and
> re-open the vote with properly updated proposal, Please let us know.
> 
> I apologize that I made a mistake here. I was confused with this comment[1].
> 
> 1. http://markmail.org/message/k6s56f5wlxgqhq3k
> 
> On Fri, Mar 15, 2013 at 10:06 AM, Marvin Humphrey
>  wrote:
>> On Thu, Mar 14, 2013 at 4:48 PM, Dave Fisher  wrote:
>>> Are the five binding votes from IPMC members?
>>> 
>>> It is not 5.
>> 
>> For the record, there were 4 binding IPMC votes in favor.
>> 
>>  Mohammed Nour El-Din
>>  Alex Karasulu
>>  Tommaso Teofili
>>  Chris Mattmann
>> 
>>> Also, should proposals with only 1 valid Mentor be acceptable?
>> 
>> In addition to Alex Karasulu, Mohammed Nour El-Din had volunteered,
>> but seems to have been left off the version of the proposal which was
>> VOTEd on. So unless Mohammed has withdrawn, MRQL has 2 Mentors.
>> 
>> Marvin Humphrey
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> 
> 
> -- 
> Best Regards, Edward J. Yoon
> @eddieyoon
> 
> -
> 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: Joining IPMC member

[Suresh Marru]

On Mar 14, 2013, at 3:26 AM, Edward J. Yoon  wrote:

>>> understand why virtually all ASF projects adhere to that convention
>>> now?
> 
> P.S., It's been 6 years since I uploaded my first patch on HBase. I
> still don't know many things but I'm continuously learning from you
> guys ;-)

Hi Edward,

I do not think any one is questioning your credibility as a committer, or pmc 
member. I think Marvin hit it right and straight forward way. At ASF one of the 
few things (and primarily the only thing) like adding to a PMC is handled on 
private lists. Given that you have been contributing since 6 years you are 
certainly expected to know it. It is not healthy to side track the issue with 
your contributions or citing emotional reasons. 

Suresh


> On Thu, Mar 14, 2013 at 4:07 PM, Edward J. Yoon  wrote:
>> Yes, I think I'm not familiar with handling issues like personnel, and
>> somewhat emotional person.
>> 
>> However, I want to helping people who want to contribute to ASF or
>> collaborate with ASF projects in the future.
>> 
>> On Thu, Mar 14, 2013 at 3:46 PM, Marvin Humphrey  
>> wrote:
>>> Edward, are you not familiar with our custom of handling personnel
>>> matters on private lists? It has not always been that way, but do you
>>> understand why virtually all ASF projects adhere to that convention
>>> now?
>>> 
>>> Marvin Humphrey
>>> 
>>> On Wed, Mar 13, 2013 at 11:15 PM, Edward J. Yoon  
>>> wrote:
 Hi,
 
 I just noticed that Mentor must be members of the Incubator PMC[1].
 Regarding MRQL podling, I'm not only Champion but also want to be a
 Mentor for MRQL project.
 
 Please add me to IPMC.
 
 1. 
 http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor
 
 --
 Best Regards, Edward J. Yoon
 @eddieyoon
 
 -
 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
>>> 
>> 
>> 
>> 
>> --
>> Best Regards, Edward J. Yoon
>> @eddieyoon
> 
> 
> 
> -- 
> Best Regards, Edward J. Yoon
> @eddieyoon
> 
> -
> 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 Provisionr into the Apache Incubator

[Suresh Marru]

+ 1 (binding).

Suresh 

On Mar 2, 2013, at 6:35 PM, Andrei Savu  wrote:

> Hi Guys,
> 
> I'd like to call a VOTE for acceptance of Provisionr into the Apache
> Incubator.
> 
> The vote will close on March 8.
> 
> [] +1 Accept Provisionr into the Apache incubator
> [] +0 Don't care.
> [] -1 Don't accept Provisionr into the incubator because...
> 
> Full proposal is pasted at the bottom on this email, and the corresponding
> wiki is http://wiki.apache.org/incubator/ProvisionrProposal
> 
> Only VOTEs from Incubator PMC members are binding, but all are welcome to
> express their thoughts.
> 
> Thanks,
> Andrei Savu
> 
> --
> Provisionr Proposal
> 
> == Abstract ==
> 
> Provisionr is an effort to develop a service that can be used to create and
> manage pools of virtual machines on multiple clouds. Our focus is on
> semi-automated workflows and cloud portability.
> 
> == Proposal ==
> 
> Provisionr solves the problem of cloud portability by hiding completely the
> APIs and only focusing on building a cluster that matches the same set of
> assumptions on all clouds, assumptions like: running a specific operating
> system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed
> packages and binaries, sane dns settings (forward & reverse ip resolution -
> as needed for Hadoop), ntp settings, networking settings, firewall, ssh
> admin access, vpn access etc.
> 
> As a secondary goal Provisionr should also provide primitives for building
> automatic or semi-automatic workflows for configuring services, workflows
> that assume that all the machines share a common set of characteristics as
> described above.
> 
> == Background ==
> 
> Creating clusters on cloud infrastructure is non-trivial because careful
> orchestration is required. To make it easy to deploy services we need to
> start from a foundation that matches a common set of assumptions on
> multiple providers.
> 
> == Rationale ==
> 
> This project started as a re-write of the core of Apache Whirr but has a
> different target being more focused on semi-automated workflows and cloud
> portability.
> 
> == Initial Goals ==
> 
> * Build a community
> * Provide an excellent user experience for semi-automatic workflows (e.g.
> using Rundeck)
> * Implement a REST service and a Web Console
> * Add support for more providers
> 
> == Current Status ==
> 
> Provisionr had four releases on [[
> https://github.com/axemblr/axemblr-provisionr/wiki|GitHub]] and it's used
> to deploy Hadoop clusters on-demand at Axemblr and infrastructure for
> testing / QA.
> 
> === 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 ===
> 
> The community interested in cloud service infrastructure is currently
> spread across many smaller projects, and one of the main goals of this
> project is to build a vibrant community to share best practices and build
> common infrastructure.
> 
> === Core developers ===
> 
> Core developers are very experienced in the Apache ecosystem. To achieve
> more diversity of developers, we will be eager to recruit developers from
> diverse companies.
> 
> * Andrei Savu - asavu at apache dot org  (Apache Whirr PMC)
> * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC)
> * Alex Ciminian -  alex.ciminian at gmail dot org
> 
> === Alignment ===
> 
> Provisionr complements Apache Whirr and later on it should provide a robust
> foundation for more advanced functionalities.
> 
> == Known Risks ==
> 
> === Orphaned products ===
> 
> The contributors have significant open source experience and the project is
> being used as part of a commercial product, so the risk of being orphaned
> is relatively low. We plan to mitigate this risk by recruiting additional
> committers.
> 
> === Inexperience with Open Source ===
> 
> Most of the initial committers have experience working on open source
> projects. Andrei Savu and Ioan Eugen Stan have experience as committers and
> PMC members on other Apache projects.
> 
> === Homogenous Developers ===
> 
> We are committed to recruiting additional committers from other companies
> based on their contributions to the project.
> 
> === Reliance on Salaried Developers ===
> 
> It is expected that Provisionr development will occur on both salaried time
> and on volunteer time, after hours. The majority of initial committers are
> paid by their employer to contribute to this project. However, they are all
> passionate about the project, and we are confident that the project will
> continue even if no salaried developers contribute to the project. We are
> committed to recruiting additional committers including non-salaried
> developers.
> 
> === Relationships with Other Apache 

[jira] [Comment Edited] (PODLINGNAMESEARCH-26) Establish whether "Apache Open Climate Workbench" is a suitable name

[Suresh Marru (JIRA)]

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

Suresh Marru edited comment on PODLINGNAMESEARCH-26 at 3/3/13 11:30 PM:


Searched for "open climate workbench" on Bing resulted in 3,230,000 results, 
first 5 pages did not show any software other than podling related. There is 
one website climatebench.com which is not active. Climatebench is close in 
resemblance but it doesn't look like is a software related. Looking through who 
is record, it is registered to firstfloridacapital.com which doesn't look like 
is a IT organization. 

  was (Author: smarru):
Searched for "" on Bing resulted in 3,230,000 results, first 5 pages did 
not show any software other than podling related. There is one website 
climatebench.com which is not active. Climatebench is close in resemblance but 
it doesn't look like is a software related. Looking through who is record, it 
is registered to firstfloridacapital.com which doesn't look like is a IT 
organization. 
  
> Establish whether "Apache Open Climate Workbench" is a suitable name
> 
>
> Key: PODLINGNAMESEARCH-26
> URL: 
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-26
> Project: Podling Suitable Names Search
>  Issue Type: Suitable Name Search
>Reporter: Chris A. Mattmann
>
> A suitable name search is required in order for Open Climate Workbench to 
> graduate from the incubation. 
> Apache Open Climate Workbench is a system that allows for easy comparison of 
> climate model outputs (regional, and global, but focused on reigional) and 
> remote sensing/satellite observations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[jira] [Commented] (PODLINGNAMESEARCH-26) Establish whether "Apache Open Climate Workbench" is a suitable name

[Suresh Marru (JIRA)]

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

Suresh Marru commented on PODLINGNAMESEARCH-26:
---

Searched for "" on Bing resulted in 3,230,000 results, first 5 pages did not 
show any software other than podling related. There is one website 
climatebench.com which is not active. Climatebench is close in resemblance but 
it doesn't look like is a software related. Looking through who is record, it 
is registered to firstfloridacapital.com which doesn't look like is a IT 
organization. 

> Establish whether "Apache Open Climate Workbench" is a suitable name
> 
>
> Key: PODLINGNAMESEARCH-26
> URL: 
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-26
> Project: Podling Suitable Names Search
>  Issue Type: Suitable Name Search
>Reporter: Chris A. Mattmann
>
> A suitable name search is required in order for Open Climate Workbench to 
> graduate from the incubation. 
> Apache Open Climate Workbench is a system that allows for easy comparison of 
> climate model outputs (regional, and global, but focused on reigional) and 
> remote sensing/satellite observations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Re: [VOTE] Accept Tajo into the Apache Incubator

[Suresh Marru]

+ 1 (binding).

Happy Incubating,
Suresh

On Feb 28, 2013, at 10:11 AM, Hyunsik Choi  wrote:

> Hi Folks,
> 
> I'd like to call a VOTE for acceptance of Tajo into the Apache incubator.
> The vote will close on Mar 7 at 6:00 PM (PST).
> 
> [] +1 Accept Tajo into the Apache incubator
> [] +0 Don't care.
> [] -1 Don't accept Tajo into the incubator because...
> 
> Full proposal is pasted at the bottom on this email, and the corresponding
> wiki is http://wiki.apache.org/incubator/TajoProposal.
> 
> Only VOTEs from Incubator PMC members are binding, but all are welcome to
> express their thoughts.
> 
> Thanks,
> Hyunsik
> 
> PS: From the initial discussion, the main changes are that I've added 4 new
> committers. Also, I've revised some description of Known Risks because the
> initial committers have been diverse.
> 
> 
> Tajo Proposal
> 
> = Abstract =
> 
> Tajo is a distributed data warehouse system for Hadoop.
> 
> 
> = Proposal =
> 
> Tajo is a relational and distributed data warehouse system for Hadoop. Tajo
> is designed for low-latency and scalable ad-hoc queries, online aggregation
> and ETL on large-data sets by leveraging advanced database techniques. It
> supports SQL standards. Tajo is inspired by Dryad, MapReduce, Dremel,
> Scope, and parallel databases. Tajo uses HDFS as a primary storage layer,
> and it has its own query engine which allows direct control of distributed
> execution and data flow. As a result, Tajo has a variety of query
> evaluation strategies and more optimization opportunities. In addition,
> Tajo will have a native columnar execution and and its optimizer. Tajo will
> be an alternative choice to Hive/Pig on the top of MapReduce.
> 
> 
> = Background =
> 
> Big data analysis has gained much attention in the industrial. Open source
> communities have proposed scalable and distributed solutions for ad-hoc
> queries on big data. However, there is still room for improvement. Markets
> need more faster and efficient solutions. Recently, some alternatives
> (e.g., Cloudera's Impala and Amazon Redshift) have come out.
> 
> 
> = Rationale =
> 
> There are a variety of open source distributed execution engines (e.g.,
> hive, and pig) running on the top of MapReduce. They are limited by MR
> framework. They cannot directly control distributed execution and data
> flow, and they just use MR framework. So, they have limited query
> evaluation strategies and optimization opportunities. It is hard for them
> to be optimized for a certain type of data processing.
> 
> 
> = Initial Goals =
> 
> The initial goal is to write more documents to describe Tajo's internal. It
> will be helpful to recruit more committers and to build a solid community.
> Then, we will make milestones for short/long term plans.
> 
> 
> = Current Status =
> 
> Tajo is in the alpha stage. Users can execute usual SQL queries (e.g.,
> selection, projection, group-by, join, union and sort) except for nested
> queries. Tajo provides various row/column storage formats, such as CSV,
> RowFile (a row-store file we have implemented), RCFile, and Trevni, and it
> also has a rudimentary ETL feature to transform one data format to another
> data format. In addition, Tajo provides hash and range repartitions. By
> using both repartition methods, Tajo processes aggregation, join, and sort
> queries over a number of cluster nodes. To evaluate the performance, we
> have carried out benchmark test using TPC-H 1TB on 32 cluster nodes.
> 
> 
> == Meritocracy ==
> 
> We will discuss the milestone and the future plan in an open forum. We plan
> to encourage an environment that supports a meritocracy. The contributors
> will have different privileges according to their contributions.
> 
> 
> == Community ==
> 
> Big data analysis has gained attention from open source communities,
> industrial and academic areas. Some projects related to Hadoop already have
> very large and active communities. We expect that Tajo also will establish
> an active community. Since Tajo already works for some features and is in
> the alpha stage, it will attract a large community soon.
> 
> 
> == Core Developers ==
> 
> Core developers are a diverse group of developers, many of which are very
> experienced in open source and the Apache Hadoop ecosystem.
> 
> * Eli Reisman 
> 
> * Henry Saputra 
> 
> * Hyunsik Choi 
> 
> * Jae Hwa Jung 
> 
> * Jihoon Son 
> 
> * Jin Ho Kim 
> 
> * Roshan Sumbaly 
> 
> * Sangwook Kim 
> 
> * Yi A Liu 
> 
> 
> == Alignment ==
> 
> Tajo employs Apache Hadoop Yarn as a resource management platform for large
> clusters. It uses HDFS as a primary storage layer. It already supports
> Hadoop-related data formats (RCFile, Trevni) and will support ORC file. In
> addition, we have a plan to integrate Tajo with other products of Hadoop
> ecosystem. Tajo's modules are well organized, and these modules can also be
> used for other projects.
> 
> 
> = Known Risks =
> 
> == Orphaned Products ==
> 
> Most of codes have been develo

Re: no shepherds assignments this time?

[Suresh Marru]

Same here. I have been waiting to see my if any reports I need to pay 
attention. Since we know what shepherd resources we have, can the assignments 
be made earlier?

Suresh

On Feb 13, 2013, at 4:40 PM, Matt Franklin  wrote:

> On Sun, Feb 10, 2013 at 8:24 PM, Benson Margulies  
> wrote:
>> Sorry, I'm really buried. I'll send some out.
> 
> The wiki format is hard to read, but it doesn't look like I got any
> assignments this month.  Anyone want to throw some my way, or do I
> have a bye?
> 
>> 
>> On Sun, Feb 10, 2013 at 6:06 PM, Roman Shaposhnik  wrote:
>>> Hi!
>>> 
>>> I didn't get the usual memo -- is this expected?
>>> 
>>> 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

Re: [VOTE] Accept Apache Open Climate Workbench into the Incubator

[Suresh Marru]

 ==
> All seed code and other contributions will be handled through the normal
> Apache contribution process. Mattmann has been authorized by NASA JPL to
> lead the contribution of RCMES and CDX into the Incubator via his existing
> Apache CLA, and a Software Grant to be provided.
> 
> We will also contact other related efforts for possible cooperation and
> contributions.
> 
> == External Dependencies ==
> Our project depends on a number of external libraries with various
> licensing conditions. An initial list of such dependencies is shown below.
> ||'''Library''' ||'''License''' ||
> ||[[http://www.ncl.ucar.edu/|NCAR NCL]]||MIT compat||
> ||[[http://www.pyngl.ucar.edu/Nio.shtml|PyNIO]]||MIT compat||
> ||[[http://www.pyngl.ucar.edu/|PyNGL]]||MIT compat||
> ||[[http://matplotlib.sourceforge.net/|Matplotlib]]||Modified
> PSF license||
> ||[[http://scipy.org/|Scipy]]||MIT compat||
> ||[[http://numpy.scipy.org/|NumPy]]||MIT compat||
> ||[[http://www.hdfgroup.org/HDF5/|HDF5]]||BSD||
> ||[[http://www.unidata.ucar.edu/software/netcdf/|NetCDF]]||MI
> T||
> 
> 
> == Cryptography ==
> The project itself will not use cryptography, but it is possible that some
> of the external software libraries will include cryptographic code to
> handle features present in various science data formats. If we need to
> provide an export control statement regarding cryptographic code per
> Apache policy, we will follow a similar approach by Mattmann in
> [[http://lucene.apache.org/nutch/|Apache Nutch]] and by Jukka Zitting lead
> this effort in Apache Tika. Mattmann is familiar with this process.
> 
> == Required Resources ==
> Mailing lists
> 
> * d...@climate.incubator.apache.org
> * comm...@climate.incubator.apache.org
> * priv...@climate.incubator.apache.org
> 
> Subversion Directory
> 
> * https://svn.apache.org/repos/asf/incubator/climate
> 
> Issue Tracking
> 
> * JIRA CLIMATE (CLIMATE)
> 
> Other Resources
> 
> * CLIMATE Wiki http://cwiki.apache.org/CLIMATE
> * Review Board instance - CLIMATE
> * Jenkins instance - CLIMATE
> 
> == Initial Committers ==
> ||'''Name''' ||'''Email''' ||'''Affiliation''' ||'''CLA''' ||
> ||Chris A. Mattmann ||mattmann at apache dot org
> ||[[http://www.jpl.nasa.gov/|NASA Jet Propulsion Laboratory]] ||yes ||
> ||Cameron E. Goodale ||goodale at apache dot org
> ||[[http://www.jpl.nasa.gov/|NASA Jet Propulsion Laboratory]] ||yes ||
> ||Paul Ramirez ||pramirez at apache dog org
> ||[[http://www.jpl.nasa.gov/|NASA Jet Propulsion Laboratory]] ||yes ||
> ||Andrew F. Hart ||ahart at apache dot org
> ||[[http://www.jpl.nasa.gov/|NASA Jet Propulsion Laboratory]] ||yes ||
> ||Jinwon Kim||jkim at atmos dot ucla dot edu
> ||[[http://jifresse.ucla.edu|UCLA Joint Institute for Regional Earth
> System Science and Engineering]] || no||
> ||Duane Waliser||duane dot waliser at jpl dot nasa dot gov
> ||[[http://www.jpl.nasa.gov/|NASA Jet Propulsion Laboratory]] || no ||
> ||Huikyo Lee||Huikyo dot Lee at jpl dot nasa dot
> gov||[[http://www.jpl.nasa.gov/|NASA Jet Propulsion Laboratory]] || no ||
> ||Paul Loikith|| Paul dot C dot Loikith at jpl dot nasa dot gov
> ||[[http://www.jpl.nasa.gov/|NASA Jet Propulsion Laboratory]] || no ||
> ||Daniel J. Crichton||crichton at apache dot
> org||[[http://www.jpl.nasa.gov/|NASA Jet Propulsion Laboratory]] || yes ||
> ||Kim Whitehall||Kim dot D dot Whitehall at jpl dot nasa dot gov
> ||[[http://www.physics1.howard.edu/~pmisra/HUPAS/HUPAS/HUPAS%20Jenkins.html
> |Howard University]] || no ||
> ||Paul Zimdars||pzimdars at apache dot
> org||[[http://www.jpl.nasa.gov/|NASA Jet Propulsion Laboratory]] || yes ||
> ||Chris Jack||cjack at csag dot uct dot ac dot
> za||[[http://www.csag.uct.ac.za/|University of Cape Town]] || no ||
> ||Bruce Hewitson||hewitson at csag dot uct dot ac dot
> za||[[http://www.csag.uct.ac.za/|University of Cape Town]] || no ||
> ||Lluis Fita Borrell||l dot fitaborrell at unsw dot edu dot
> au||[[http://unsw.edu.au/|University of New South Wales]] || yes ||
> ||Jason Evans||jason dot evans at unsw dot edu dot
> au||[[http://unsw.edu.au/|University of New South Wales]] || no ||
> ||Estani Gonzalez||estanislao dot gonzalez at met dot fu-berlin dot de
> ||[[http://www.geo.fu-berlin.de/met/|Free University Berlin]] || yes ||
> ||Luca Cinquini||luca dot cinquini at jpl dot nasa dot gov
> ||[[http://www.jpl.nasa.gov/|NASA Jet Propulsion Laboratory]] || yes ||
> ||J. Sanjay||sanjay at tropmet dot res dot in ||
> [[http://tropmet.res.in/|Indian 

Re: [DISCUSS] Apache Open Climate Workbench

[Suresh Marru]

On Jan 27, 2013, at 1:56 PM, "Mattmann, Chris A (388J)" 
 wrote:

> Hey Suresh,
> 
> Thanks a ton man and great to hear!
> 
> To your comment below:
> 
> On 1/27/13 5:56 AM, "Suresh Marru"  wrote:
> 
>> Hi Chris,
>> 
>> Great proposal, I am personally looking forward to see more of these
>> federal government and international collaboration efforts adopt open
>> community process. Impressive to see this project is pulling together
>> initial developers from government and universities of US, South Africa,
>> UK, Germany and India (I will hope all of them will be able to get their
>> CLA's cleared). You are really scraping the black ice on bureaucratic
>> highways and preventing at least some reinventing wheels with valuable
>> tax payers money in multiple countries.
>> 
>> Will this system evaluate and be inclusive of the community earth system
>> modeling community?
> 
> Yep this proposal includes some of those that are directly involved in
> that community including Tsengdar Lee, as well as members of the Earth
> System Grid Federation. We will definitely be inclusive and are happy to
> have involvement.

Sounds very good. I am unable to resist my itch, so will like to jump on the 
band wagon as a committer. Please let me know if I can add myself to the 
proposal wiki. 

Thanks,
Suresh

> Thanks!
> 
> Cheers,
> Chris
> 
>> 
>> Suresh
>> 
>> On Jan 26, 2013, at 2:48 PM, "Mattmann, Chris A (388J)"
>>  wrote:
>> 
>>> Hi Everyone!
>>> 
>>> I bring to the Incubator a new proposal for the Apache Open Climate
>>> Workbench (incubating) project. I've added the proposal to the Incubator
>>> wiki here:
>>> 
>>> http://wiki.apache.org/incubator/ClimateProposal
>>> 
>>> 
>>> The project is a distributed, scalable approach for the rapid comparison
>>> of remote sensing data (e.g., from NASA) with that of climate model
>>> output
>>> generated by major US and international activities including the US
>>> National Climate Assessment, the Coordinated Regional Downscaling
>>> Experiment (CORDEX), the North American Regional Climate Change
>>> Assessment
>>> Program (NARCCAP) the Intergovernmental Panel on Climate Change (IPCC).
>>> Much of the software to be donated and evolved here at Apache as a
>>> community includes core dependencies to several Apache projects (OODT,
>>> Hadoop/HIVE, Sqoop, Tika), and to several key toolkits in the Python
>>> software community including NumPy, SciPy, Matplotlib, NCAR NCL, etc.
>>> 
>>> We welcome your feedback over the next week or so for discussion and
>>> look
>>> forward to it!
>>> 
>>> Cheers,
>>> Chris Mattmann
>>> Proposed Mentor and Champion
>>> 
>>> ---proposal text
>>> 
>>> = Apache Open Climate Workbench, tool for scalable comparison of remote
>>> sensing observations to climate model outputs, regionally and globally.
>>> =
>>> === Abstract ===
>>> The Apache Open Climate Workbench proposal desires to contribute an
>>> existing community of software related to the analysis and evaluation of
>>> climate models, and related to the use of remote sensing data in that
>>> process. 
>>> 
>>> Specifically, we will bring a fundamental software toolkit for analysis
>>> and evaluation of climate model output against remote sensing data. The
>>> toolkit is called the [[http://rcmes.jpl.nasa.gov|Regional Climate Model
>>> Evaluation System (RCMES)]]. RCMES provides two fundamental components
>>> for
>>> the easy, intuitive comparison of climate model output against remote
>>> sensing data. The first component called RCMED (for "Regional Climate
>>> Model Evaluation Database") is a scalable cloud database that decimates
>>> remote sensing data and renalysis data related to climate using Apache
>>> OODT extractors, Apache Tika, etc. These transformations make
>>> traditionally heterogeneous upstream remote sensing data and climate
>>> model
>>> output homogeneous and unify them into a data point model of the form
>>> (lat, lng, time, value, height) on a per parameter basis. Latitude (lat)
>>> and Longitude (lng) are in WGS84 format, but can be reformatted on the
>>> fly. time is in ISO 8601 format, a string sortable format independent of
>>> underlying store. value carries with it units, related to interpretation
>>> and height allows

[jira] [Commented] (INCUBATOR-125) How-to guide for "Assembling LICENSE and NOTICE"

[Suresh Marru (JIRA)]

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

Suresh Marru commented on INCUBATOR-125:


Marvin, great job in putting together this short and concise document. I think 
it will also be useful to mention about the DISCLAIMER file requirement [1] for 
the incubator podlings.
[1] - http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer

> How-to guide for "Assembling LICENSE and NOTICE"
> 
>
> Key: INCUBATOR-125
> URL: https://issues.apache.org/jira/browse/INCUBATOR-125
> Project: Incubator
>  Issue Type: Improvement
>  Components: site
>Reporter: Marvin Humphrey
> Attachments: licensing_howto.mdtext
>
>
> While the ASF provides reference documentation for LICENSE and NOTICE,
> confusion persists and existing versions vary widely in quality.
> To address these problems, we should augment the reference documentation with
> a "how-to" guide which provides formulaic instructions for assembling LICENSE
> and NOTICE under common conditions.
> One key feature of this how-to should be a mapping of approved licenses to
> what they require as far as NOTICE.  This mapping will help PMCs determine
> when the licensing information of a dependency contains a "required third
> party notice" which must be added to NOTICE.
> There are at least four possible locations where this how-to might live:
> *   www.apache.org/dev/licensing_howto.html -- probably the best location,
> considering the intended audience.
> *   www.apache.org/legal/licensing_howto.html -- if legal wants it.
> *   incubator.apache.org/guides/licensing_howto.html -- probably not ideal,
> because the information applies to TLPs as well as podlings and we have a
> problem with duplication.
> *   Somewhere on community.apache.org -- in theory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

Re: [DISCUSS] Apache Open Climate Workbench

[Suresh Marru]

Hi Chris,

Great proposal, I am personally looking forward to see more of these federal 
government and international collaboration efforts adopt open community 
process. Impressive to see this project is pulling together initial developers 
from government and universities of US, South Africa, UK, Germany and India (I 
will hope all of them will be able to get their CLA's cleared). You are really 
scraping the black ice on bureaucratic highways and preventing at least some 
reinventing wheels with valuable tax payers money in multiple countries. 

Will this system evaluate and be inclusive of the community earth system 
modeling community?

Suresh

On Jan 26, 2013, at 2:48 PM, "Mattmann, Chris A (388J)" 
 wrote:

> Hi Everyone!
> 
> I bring to the Incubator a new proposal for the Apache Open Climate
> Workbench (incubating) project. I've added the proposal to the Incubator
> wiki here:
> 
> http://wiki.apache.org/incubator/ClimateProposal
> 
> 
> The project is a distributed, scalable approach for the rapid comparison
> of remote sensing data (e.g., from NASA) with that of climate model output
> generated by major US and international activities including the US
> National Climate Assessment, the Coordinated Regional Downscaling
> Experiment (CORDEX), the North American Regional Climate Change Assessment
> Program (NARCCAP) the Intergovernmental Panel on Climate Change (IPCC).
> Much of the software to be donated and evolved here at Apache as a
> community includes core dependencies to several Apache projects (OODT,
> Hadoop/HIVE, Sqoop, Tika), and to several key toolkits in the Python
> software community including NumPy, SciPy, Matplotlib, NCAR NCL, etc.
> 
> We welcome your feedback over the next week or so for discussion and look
> forward to it!
> 
> Cheers,
> Chris Mattmann
> Proposed Mentor and Champion
> 
> ---proposal text
> 
> = Apache Open Climate Workbench, tool for scalable comparison of remote
> sensing observations to climate model outputs, regionally and globally. =
> === Abstract ===
> The Apache Open Climate Workbench proposal desires to contribute an
> existing community of software related to the analysis and evaluation of
> climate models, and related to the use of remote sensing data in that
> process. 
> 
> Specifically, we will bring a fundamental software toolkit for analysis
> and evaluation of climate model output against remote sensing data. The
> toolkit is called the [[http://rcmes.jpl.nasa.gov|Regional Climate Model
> Evaluation System (RCMES)]]. RCMES provides two fundamental components for
> the easy, intuitive comparison of climate model output against remote
> sensing data. The first component called RCMED (for "Regional Climate
> Model Evaluation Database") is a scalable cloud database that decimates
> remote sensing data and renalysis data related to climate using Apache
> OODT extractors, Apache Tika, etc. These transformations make
> traditionally heterogeneous upstream remote sensing data and climate model
> output homogeneous and unify them into a data point model of the form
> (lat, lng, time, value, height) on a per parameter basis. Latitude (lat)
> and Longitude (lng) are in WGS84 format, but can be reformatted on the
> fly. time is in ISO 8601 format, a string sortable format independent of
> underlying store. value carries with it units, related to interpretation
> and height allows for different values for different atmospheric vertical
> levels. All of RCMES is built on Apache OODT, Apache Sqoop/Apache Hadoop
> and Apache Hive, along with hooks to PostGIS and MySQL (traditional
> relational databases). The second component of the system, RCMET (for
> "Regional Climate Model Evaluation Toolkit") provides facilities for
> connecting to RCMED, dynamically obtaining remote sensing data for a
> space/time region of interest, grabbing associated model output (that the
> user brings, or from the Earth System Grid Federation) of the same form,
> and then regridding the remote sensing data to be on the model output
> grid, or the model output to be on the remote sensing data grid. The
> regridded data spatially is then temporally regridded using techniques
> including seasonal cycle compositing (e.g., all summer months, all
> Januaries, etc.), or by daily, monthly, etc. The uniform model output and
> remote sensing data are then analyzed using pluggable metrics, e.g.,
> Probability Distribution Functions (PDFs), Root Mean Squared Error (RMSE),
> Bias, and other (possibly user-defined) techniques, computing an analyzed
> comparison or evaluation. This evaluation is then visualized by plugging
> in to the NCAR NCL library for producing static plots (histograms, time
> series, etc.)
> 
> We also have performed a great deal of work in packaging RCMES to make the
> system easy to deploy. We have working Virtual Machines (VMWare VMX and
> Virtual Box OVA compatible formats) and we also have an installer built on
> Python Buildout (http://buildout.org/) called "

Re: [VOTE] - Apache Clerezza Graduation Resolution

[Suresh Marru]

Hi Tommaso,

As per the template [1], the first paragraph of the resolution should have 
${DESCRIPTION-AND-SCOPE} you currently only have the project name which is not 
introduced until the second paragraph. 

May be you want to consider changing:
>   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 Apache Clerezza platform.

to 

>   WHEREAS, the Board of Directors deems it to be in the best
>   interests of the Foundation and consistent with the
>   Foundation's purpose to establish a Project Management
>   Committee charged with the creation and maintenance of
>   open-source software, for distribution at no charge to
>   the public, related to an OSGi-based modular application and set of
>   components for building RESTFul Semantic Web applications and
> services.


Cheers,
Suresh 

[1]  - 
https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt


On Jan 18, 2013, at 6:02 AM, Tommaso Teofili  wrote:

> Hi all,
> 
> as per [VOTE][RESULT] on clerezza-dev@i.a.o mailing list [1] and after
> having successfully completed podling name search [2] I'm opening the vote
> for the below Apache Clerezza TLP graduation resolution.
> 
> X. Establish the Apache Clerezza 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 Apache Clerezza platform.
> 
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Clerezza Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
> 
>   RESOLVED, that the Apache Clerezza Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to an OSGi-based modular application and set of
>   components for building RESTFul Semantic Web applications and
> services;
>   and be it further
> 
>   RESOLVED, that the office of "Vice President, Apache Clerezza" 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 Clerezza Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Clerezza 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 Clerezza Project:
> 
> * Reto Bachmann-Gmuer 
> * Tsuyoshi Ito 
> * Hasan Hasan   
> * Tommaso Teofili 
> * Bertrand Delacretaz   
> * Florent André   
> * Rupert Westenthaler 
> * Daniel Spicar  
> 
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hasan Hasan
>   be appointed to the office of Vice President, Apache Clerezza, 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 Clerezza 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 Clerezza Project; and be it further
> 
>   RESOLVED, that the Apache Clerezza Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Clerezza podling; and be it further
> 
>   RESOLVED, that all responsibilities pertaining to the Apache
>   Incubator Clerezza podling encumbered upon the Apache Incubator
>   Project are hereafter discharged.
> 
> Please cast your votes:
> [ ] +1 Graduate Apache Clerezza podling from Apache Incubator
> [ ] +0 Indifferent to the graduation status of Apache Clerezza podling
> [ ] -1 Reject graduation of Apache Clerezza podling from Apache Incubator
> because ...
> 
> Vote is open for the next 72 hours thus it'll close on January 21st at
> 12.00 CET.
> 
> Regards,
> Tommaso
> 
> 
> [1] :
> http://mail-archives.apache.org/mod_mbox/incubator-clerezza-dev/201301.mbox/%3CCAGnSx07PHaN9nbRrbFzFpRQyODuj1XJXnAEXYffyMxWD47m0Gw%40mail.gmail.com%3E
> [2] : https://issues.apache.org/jira/b

Re: Thoughts about formalizing the role of shepherd

[Suresh Marru]

One comment or worry I have is, so far the shepherd comments have been very 
useful, but we have to be cognizant of the fact that shepherds are very less 
informed then mentors (by design). So the shepherd comments have to be really 
constructive. There is a risk of some delicate conversations offending mentors 
who volunteer lot of energy on the ground -- especially if a shepherd (without 
too much context) makes a strong recommendation. I am not sure this will be the 
case, but just a caution. In any case,  please do not take my comments 
seriously as I am fairly new to both shepherding and mentoring.

+ 0 -- With much much insights, I will refrain any strong opinions on 
formalizing shepherds and will remain neutral.

Suresh

On Jan 13, 2013, at 11:46 AM, Benson Margulies  wrote:

> Right now, a shepherd assignment is a temporary job. It starts as the
> reports for a cycle begin to come in, and it ends when the shepherd
> feels that he or she has done what makes sense in terms of reporting
> to the community and, in some cases, delivering some constructive
> nudges to the projects.
> 
> I've been thinking about an alternative, but it may not be popular.
> 
> In my alternative, the IPMC organizes itself as follows:
> 
> At the top of the pyramid, tied down to the Aztec altar, is me, the chairman.
> 
> Next down are the 'vice-chairs', currently known as the shepherds.
> Each of these people is responsible for a group of projects, dispersed
> across the reporting cycle. The shepherd, at least, tunes into the
> reports, but also checks in during the three-month reporting period --
> particularly if we have identified issues that the project needs to
> address.
> 
> Next we have the mentors, who are 'inside' the projects, offering
> guidance, coaching, and supervision. However, the fact is that we
> don't have enough volunteers to have multiple, active, tuned-in
> mentors for all of the projects all of the time.
> 
> Last, but hardly least, are the freelance members of the committee,
> who tune in on things like release reviews.
> 
> If we adopted this plan, we'd add a shepherd slot to the metadata for
> each project, and I, as chair, would take action if the designated
> shepherd wasn't available to do a review for a project in a reporting
> cycle. Either I'd do it myself, or I'd put out a call for assistance.
> 
> I'm not going to defend this scheme tooth-and-nail. If folks prefer
> the current approach, I'll focus on fixing the schedule to make it
> easier to make it work.
> 
> -
> 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: The report/review cycle

[Suresh Marru]

Thanks Benson for the clarification, now the timeline fully makes sense to me.

Suresh

On Jan 13, 2013, at 6:50 PM, Benson Margulies  wrote:

> On Sun, Jan 13, 2013 at 6:34 PM, Suresh Marru  wrote:
>> Hi Benson,
>> 
>> + 1 for this time line, it really helps to have shepherds a day or two. I am 
>> sorry I couldn't get my shepherd reports in this time with post-holiday 
>> catchup and sickness.
>> 
>> I do not want to add too much to the process, but want to understand the 
>> buffer between shepherd comments and your consolidated summary to the board.
>> 
>> Working backwards:
>> * Friday (before the board meeting week) VP IPMC submits the consolidated 
>> report to the board.
>> * Shepherds review the mentor signed off reports and other activity and add 
>> comments - Tentatively Due by ?
>> * Podling's draft the report and mentors sign off by Wednesday (a week 
>> before the board meets).
>> 
>> I do think we have to leave it to each podling how they work through the 
>> reporting process, but having a suggested timeline and workflow at [1] might 
>> help the new podlings understand how the report funnels to the board.
> 
> I don't think that shepherds need to wait around for mentors.
> 
> Try this timeline:
>   T1 T2T3
>  T4
>||  |
>|
> friday beforewedfriday before wed
> friday before board meeting
> board meeting
> board meeting
> 
> T1: podlings deliver report content
> T1->T2: mentors and shepherds review, comment, signoff
> T2->T3: chair summarizes, IPMC reviews
> T3->T4: chair makes small repairs in case of last minute comments or input
> 
> As you write below, how projects get their reports together, and
> whether they anticipate the need for mentor signoff, is up to them.
> 
> 
>> 
>> Something like... PPMC drafts the reports in the dev list -> Mentors iterate 
>> any comments and sign off -> Shepherds review and provide any kudos external 
>> advice/comments -> IPMC chair compiles the report with a over all summary 
>> (with an appendix of all podling reports) -> Added to the board agenda -> 
>> Board members shepherd through the IPMC report -> (feedback follows back?)
>> 
>> It might be also helpful to explain in the same document, once the project 
>> graduates how the process cuts short into ...TLP PMC chair drafts the report 
>> (with feedback from PMC) ->  Added to the board agenda -> Board members 
>> shepherd the PMC report -> feedback is sent to PMC private list
>> 
>> Cheers,
>> Suresh
>> [1] - http://incubator.apache.org/guides/ppmc.html
>> 
>> On Jan 13, 2013, at 7:52 AM, Benson Margulies  wrote:
>> 
>>> This time around, the timing was as follows:
>>> 
>>> Wed 09-01-2013: Deadline for podling reports
>>> 
>>> Friday 11-01-2013: Practical board deadline
>>> 
>>> Wed 16-01-2013: Board meeting
>>> 
>>> In other words, we had a two day window for shepherds to digest
>>> reports, then go dig around to fill in their picture.
>>> 
>>> Now, maybe things were unusually bad because of folks out for the new
>>> year until 07-01-2013. But, still, I feel as if we don't have enough
>>> time to react to reports (or the lack of reports) before we need to
>>> have the board report in place.
>>> 
>>> What do people think of making the podling reporting deadline be a
>>> full week before the board's deadline? The board wants a weekend to
>>> review reports before they meet; I'd like a weekend for us to review
>>> reports before we need to get them delivered to the board.
>>> 
>>> -
>>> 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: The report/review cycle

[Suresh Marru]

Hi Benson,

+ 1 for this time line, it really helps to have shepherds a day or two. I am 
sorry I couldn't get my shepherd reports in this time with post-holiday catchup 
and sickness.

I do not want to add too much to the process, but want to understand the buffer 
between shepherd comments and your consolidated summary to the board. 

Working backwards:
* Friday (before the board meeting week) VP IPMC submits the consolidated 
report to the board.
* Shepherds review the mentor signed off reports and other activity and add 
comments - Tentatively Due by ?
* Podling's draft the report and mentors sign off by Wednesday (a week before 
the board meets).

I do think we have to leave it to each podling how they work through the 
reporting process, but having a suggested timeline and workflow at [1] might 
help the new podlings understand how the report funnels to the board.
 
Something like... PPMC drafts the reports in the dev list -> Mentors iterate 
any comments and sign off -> Shepherds review and provide any kudos external 
advice/comments -> IPMC chair compiles the report with a over all summary (with 
an appendix of all podling reports) -> Added to the board agenda -> Board 
members shepherd through the IPMC report -> (feedback follows back?)

It might be also helpful to explain in the same document, once the project 
graduates how the process cuts short into ...TLP PMC chair drafts the report 
(with feedback from PMC) ->  Added to the board agenda -> Board members 
shepherd the PMC report -> feedback is sent to PMC private list

Cheers,
Suresh
[1] - http://incubator.apache.org/guides/ppmc.html

On Jan 13, 2013, at 7:52 AM, Benson Margulies  wrote:

> This time around, the timing was as follows:
> 
> Wed 09-01-2013: Deadline for podling reports
> 
> Friday 11-01-2013: Practical board deadline
> 
> Wed 16-01-2013: Board meeting
> 
> In other words, we had a two day window for shepherds to digest
> reports, then go dig around to fill in their picture.
> 
> Now, maybe things were unusually bad because of folks out for the new
> year until 07-01-2013. But, still, I feel as if we don't have enough
> time to react to reports (or the lack of reports) before we need to
> have the board report in place.
> 
> What do people think of making the podling reporting deadline be a
> full week before the board's deadline? The board wants a weekend to
> review reports before they meet; I'd like a weekend for us to review
> reports before we need to get them delivered to the board.
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: [VOTE] retire photark

[Suresh Marru]

+ 1

Suresh

On Dec 19, 2012, at 8:52 PM, Benson Margulies  wrote:

> Having received no traffic on the discussion thread, and in particular
> no traffic at all from the PPMC, I hereby call a vote to retire
> photark.
> 
> [+1]
> 
> -
> 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

Drill Report - Shepherds View

[Suresh Marru]

I was pleased to a detailed report by the Drill PPMC and sign off by all the 
Mentors. Email discussions like the thread "What do you want out of Apache 
Drill" [1], should help the podling engage the community. Since the report is 
detailed, I will skip adding kudos to all the points but over all, Drill seems 
to be doing very well. Couple of suggestions for the project to consider 

* Its only 3 months into the incubation so too early to complain, but the 
project should consider release early and release often. Do not wait too long 
to make a release.
* The mailing list traffic is good, but the JIRA traffic is lower than what I 
expected. Since there is a good interest shown by community, putting effort in 
listing the issues and breaking down the tasks might translate the community 
interest into contributions. 

Cheers,
Suresh

[1]  - 
http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201212.mbox/browser

Re: Advice on inviting Apache insight to NSF SI2 meeting?

[Suresh Marru]

Hi Jim,

Its great to hear you will be able me make it. I am sure NSF will greatly 
appreciate your perspectives. We will be happy to provide a case study from 
Airavata. 

Suresh

On Dec 3, 2012, at 11:12 AM, Jim Jagielski  wrote:

> I am certainly close, if they think I'd be a suitable person.
> 
> On Dec 1, 2012, at 10:13 AM, Ross Gardler  wrote:
> 
>> Anyone able to help the NSF out at a meeting in DC in Jan?
>> 
>> See below for more info.
>> 
>> On a personal note I've noticed an increased, and genuine, interest in how 
>> to improve the impact of publicly funded research outputs from the NSF in 
>> the last couple of years. We are even seeing important components turning up 
>> in the Incubator. I hope we can send someone able to help them understand 
>> how we do things around here. It's your (US) tax dollars going into this 
>> work.
>> 
>> I'd normally do this myself but I have a clash on these dates.
>> 
>> Let me know privately if you are interested and I'll help you/them figure 
>> out who the best fit is.
>> 
>> Ross
>> 
>> Sent from my tablet
>> 
>> -- Forwarded message --
>> From: "James Howison" 
>> Date: Nov 30, 2012 9:31 PM
>> Subject: Advice on inviting Apache insight to NSF SI2 meeting?
>> To: "Ross Gardler" 
>> 
>> Hi Ross,
>> 
>> I'm organizing a panel at an upcoming meeting for the PIs of all the 
>> projects funded by the SI2 funding program at the NSF (SI2, or SI^2, is the 
>> main Scientific Software funding program at the moment).
>> 
>> The panel is going to focus on Software Impact, and I'd like to have someone 
>> who can inject an understanding of the importance of community, including 
>> Incubator considerations such as non-salaried developers etc.  We're also 
>> considering adopting the DOAP way of describing the projects and their 
>> infrastructure as a way of helping projects and the program overall 
>> catalogue their activities.
>> 
>> The meeting is in DC in January Jan 17 and half-day 18th.  Does anyone from 
>> Apache come to mind (including yourself) that would be relevant either with 
>> experience in Incubation, or from the DOAP/catalogue.  Do you think your 
>> experience with SIMAL would be relevant here, might you be interested?
>> 
>> Best regards,
>> James Howison
>> 
>> 
>> 
>> --
>> James Howison
>> Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
>> 
>> 
> 
> 
> -
> 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: checking on the shepherd inventory (or, 3.14159 IPMC members ...)

[Suresh Marru]

On Dec 2, 2012, at 10:28 AM, Benson Margulies  wrote:

> http://wiki.apache.org/incubator/IncubatorShepherds is the official
> list of willing shepherds.
> 
> I would be exceedingly grateful for additional volunteers here, and of
> course of someone needs to leave the list, please edit yourself out.

Hi Benson,

I added my name to the wiki, I will be willing to help as  needed. But if there 
is a choice, I prefer java based middleware, especially the big data, hadoop 
family of podlings.

Suresh

> -
> 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: Mentor needed for Hadoop Development Tools

[Suresh Marru]

Thanks Chris, realized I will be in good company which added to my motivation 
:) 

Hi Adam,

I added myself to the wiki.

Looking forward for the project to take life,
Suresh

On Nov 27, 2012, at 8:43 PM, "Mattmann, Chris A (388J)" 
 wrote:

> +1 great to hear that you are on board, Suresh.
> 
> Cheers,
> Chris
> 
> On Nov 27, 2012, at 6:08 PM, Adam Berry wrote:
> 
>> 
>> Fantastic, thanks for the offer.
>> 
>> Could you add your information to the proposal wiki, or go ahead and send it 
>> to me and I'll add it.
>> 
>> Cheers,
>> Adam
>> 
>> On Nov 27, 2012, at 2:41 PM, Suresh Marru wrote:
>> 
>>> Hi Adam,
>>> 
>>> I am in general interested on the distributed application debugging. I can 
>>> see some overlap with Airavata project as well. I think I can help out and 
>>> volunteer to mentor the project.
>>> 
>>> Cheers,
>>> Suresh
>>> 
>>> On Nov 27, 2012, at 12:40 PM, Adam Berry  wrote:
>>> 
>>>> Hi IPMC members,
>>>> 
>>>> we find ourselves in need of an additional mentor for this project, which 
>>>> we are currently in the process of on boarding.
>>>> 
>>>> You can see the proposal on the wiki at 
>>>> http://wiki.apache.org/incubator/HadoopDevelopmentToolsProposal.
>>>> 
>>>> Cheers,
>>>> Adam
>>> 
>>> 
>>> -
>>> 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: Mentor needed for Hadoop Development Tools

[Suresh Marru]

Hi Adam,

I am in general interested on the distributed application debugging. I can see 
some overlap with Airavata project as well. I think I can help out and 
volunteer to mentor the project.

Cheers,
Suresh
 
On Nov 27, 2012, at 12:40 PM, Adam Berry  wrote:

> Hi IPMC members,
> 
> we find ourselves in need of an additional mentor for this project, which we 
> are currently in the process of on boarding.
> 
> You can see the proposal on the wiki at 
> http://wiki.apache.org/incubator/HadoopDevelopmentToolsProposal.
> 
> Cheers,
> Adam


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

Re: How to grow podling communities

[Suresh Marru]

Apologies for the cross post, but I am including press since Eric has some 
constructive observations here. 

On Nov 27, 2012, at 1:44 AM, Eric Johnson  wrote:

> I'm mostly just a lurker on this list, having thought about bringing a 
> project to Apache about 24 months ago[1], realizing we didn't quite have the 
> demand/community. Since then I've been lurking, wanting to see when/whether 
> it makes sense to attempt it again, reflecting on the state of the project 
> I'm working on.
> 
> From where I'm sitting, I think the incubator actually should do much more 
> here. Big picture - bunch of developers with some cool code come to possible 
> the foremost organization for open source projects. They start incubating, 
> and discover that part of their incubation process is to market themselves to 
> grow their community, and yet not much help arrives to do that. On top of 
> that, (a) the developers likely have weak marketing skills, (b) don't have a 
> budget for marketing & travel, (c) aren't given any tips from others more 
> experienced about what kinds of resources they should scare up and which 
> efforts they should focus on first.
> 
> I see the incubator process ought to play three roles:
> 
> a) teaching the Apache rules/community/approach
> 
> b) teaching optimal open source project hygiene (which includes items listed 
> below, such as quick turn-around on patch reviews, decent website, tutorials, 
> public mailing list discussion) - and actually include "grading" on the 
> quality of those items before graduation.
> 
> c) assistance and reporting on "marketing". What the heck does this mean?
> 
> I think the incubator currently has parts (a) & (b) down. Not so much for ©

Eric, I sure do appreciate your ideas below, but don't forget incubator helps 
in making legally complaint releases. Releases distinguish incubator from 
apache labs. And making frequent releases and announcing them is one the best 
marketing technique which sells open source software. In that sense,  of course 
the developers have great skill at this aspect of marketing :)

Suresh  

> For example:
> 
> What does it mean to do "press"? What would you include in a press release? 
> Where would you send it?
> 
> Apache has so many projects, shouldn't it do a monthly "highlight on _" 
> report, calling out a top level project, and a project being incubated? 
> Automatic publicity! Expect incubating projects to participate in one of 
> those "highlight" reports before graduating
> 
> What community events should a team focus on? What have teams done in the 
> past? What has worked? What hasn't worked? Do we know why it worked or didn't 
> work? Is this information being recorded anywhere?
> 
> Encourage teams to shamelessly request "reference" users that they can post 
> to their websites. Solicit "endorsements" from "neutral" third parties.
> 
> I've seen ideas tossed around on the incubator list, but generally nothing 
> concrete, so it feels to me like the projects are left drifting in the wind, 
> trying to figure this stuff out for themselves.
> 
> That's silly, because Apache has such huge name recognition in the software 
> world, it should be *easy* to draw attention to incubating projects. Except 
> that at the moment, the best way to follow what's incubating seems to be 
> hopping on this general list, where you will see when projects submit 
> proposals, see them voted on, and see when they get in trouble. That's a lot 
> of noise for a small amount of signal. Capturing that signal publicly might 
> help bring visibility to the projects to follow.
> 
> For example, why doesn't the incubator have a twitter feed where the status 
> of incubating projects gets reported? Something that everyone can follow, and 
> discover when new projects are proposed, when projects are at risk, and when 
> they think about graduating?
> 
> Recognizing that everyone here has limited resources, I don't think what's 
> needed here is much more than a little bit of capturing existing known data 
> on a wiki page or three, perhaps a twitter feed, and some small amount of 
> nudging by mentors. At least as a start!
> 
> Eric.
> 
> [1] https://wiki.apache.org/incubator/gXMLProposal
> 
> On 11/26/12 8:03 PM, Alan Cabrera wrote:
>> I wonder if we can ask that incubation proposals include how they intend to 
>> get the message out there.  What channels are relevant for the project?  I 
>> guess what are their marketing plans.
>> 
>> Eventually, we'd have a collection of old incubation proposals that new 
>> podlings could use to garner ideas on how to market and grow their community.
>> 
>> 
>> Regards,
>> Alan
>> 
>> On Nov 26, 2012, at 5:50 PM, Ross Gardler wrote:
>> 
>>> Growing community is about "getting the message out there". There has to be 
>>> someone in the project who wants to do that. Some techniques are:
>>> 
>>> - press
>>> - community events
>>> - mentoring (that is mentoring of potential new committers)
>>> - fast turnar

Re: What constitute a successful project?

[Suresh Marru]

On Nov 27, 2012, at 3:08 AM, Eric Yang  wrote:

> Apache is a non-profit organization.  If we restrict our thinking model to
> metrics of how many developers, and how many patches are committed in
> pre-defeined time limit.  There is no software that is gong to succeed in
> this evaluation other than commercial software.  Paid developers are
> contributing to the software that meeting cooperate interests at rapid
> pace, and smaller companies will work together until cooperate interests
> tear apart the software, or the funding eventually dry up and the software
> cease to exist, and the community will eventually fall apart.  Good
> software usually comes down to a few individuals who work hard to enable
> the community to flourish.  Many of the good software takes decades to
> develop from hobby projects.  I will accept the voting result from IPMC,
> and I wish IPMC would use better human sense to enable future project to
> flourish.

Hi Eric,

Its good to see Jukka and Ant stepping up as mentors, may be that will give you 
Chukwa one more chance. From browsing through the private list and the general 
list, I see lots of philosophical arguments and how you will bring in your 
patches now that legal review at your employer is over. Ofcourse you mention 
new volunteers too. But so far I haven't seen an answer from you or other 
Chukwa PPMC "what have you done previously to grow the community, what did not 
work and what is the change in plan now"? I see multiple variants of this 
question has been asked quite a few times in the last couple of days and I am 
eager to see an answer from the Chukwa PPMC.

Suresh


> Chris Douglas resigned from mentor position, therefore, Chukwa will need a
> new mentor, and one of Chukwa contributor Sourygna Luangsay volunteer to be
> the motivator for Chukwa development if Chukwa is voted to stay for another
> 6 months.
> 
> regards,
> Eric
> 
> On Mon, Nov 26, 2012 at 10:20 PM, Bernd Fondermann <
> bernd.fonderm...@gmail.com> wrote:
> 
>> On Tue, Nov 27, 2012 at 1:25 AM, Jukka Zitting 
>> wrote:
>>> Hi,
>>> 
>>> On Mon, Nov 26, 2012 at 10:53 PM, Alan Cabrera 
>> wrote:
 As I mentioned in an earlier email, we did have this conversation seven
 months ago.  We came to a consensus to give it another try.  We even
>> added
 a few committers a "bit early" with the hopes that they would infuse
>> the project
 with more energy.
>>> 
>>> That doesn't take away the fact that there are still people who are
>>> clearly interested in continuing work on the project. Instead of
>>> telling the community to pick up their toys and leave, I'd much rather
>>> ask them to come up with a credible alternative. The failure of past
>>> attempts to grow the community does not necessarily mean that future
>>> attempts will also fail, so I'd give the community the benefit of
>>> doubt as long as there are new ideas and people willing to try them.
>>> 
>>> If I understand correctly the problems in Chukwa are two-fold: 1) the
>>> community isn't diverse, i.e. there are only few people involved, and
>>> 2) the community isn't active, in that even the involved people don't
>>> have too many cycles to spend on the project.
>>> 
>>> Thus I'd raise the following questions to Eric and others who want to
>>> keep Chukwa alive at the ASF:
>>> 
>>> a) Is it reasonable to expect existing community members to become
>>> more active in near future? If yes, will such increased activity be
>>> sustainable over a longer period of time?  Why? IIUC there was some
>>> recent legal progress that might help here. What would be the best way
>>> to measure the expected increase in activity?
>>> 
>>> b) How do you expect to get more people involved in the project? What
>>> concrete actions will be taken to increase the chances of new
>>> contributors showing up? Why do you believe these things will work
>>> better than the mentioned earlier attempts at growing the community?
>>> Good ideas of concrete actions are for example cutting new releases,
>>> improving project documentation, presenting the project at various
>>> venues, simplifying the project build and initial setup, and giving
>>> more timely answers and feedback to new users and contributors (see
>>> also my observation from October [1]). How can we best tell whether
>>> such efforts are working?
>>> 
>>> Coming up with good answers to such questions is not necessarily easy
>>> (and it's fine if not all of them can yet be answered), but going
>>> through that effort should give us a good reason to continue the
>>> incubation of Chukwa at least for a few more months until we should
>>> start seeing some concrete and sustainable improvements in community
>>> activity and diversity.
>> 
>> This is exactly what we did for the last months (years, actually).
>> Give it yet more time.
>> Honestly, I don't understand why we should continue in this mode "for
>> another few months" when it failed for the past years.
>> Is this the extra-bonus IPMC time?
>> T

Re: [VOTE] Graduate Apache Flex podling from Apache Incubator

[Suresh Marru]

+ 1 (binding).

All the best as TLP,
Suresh

On Nov 22, 2012, at 5:25 AM, Bertrand Delacretaz  wrote:

> On Thu, Nov 22, 2012 at 8:03 AM, Alex Harui  wrote:
>> ...This is a call for vote to graduate the Apache Flex podling from Apache
>> Incubator...
> 
> We need to see the proposed resolution here, I've copied it from
> https://cwiki.apache.org/confluence/display/FLEX/Graduation+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 development of expressive web
> applications that deploy to all major browsers, desktops and
> devices (including smartphones, tablets and tv).
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Flex Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that the Apache Flex Project be and hereby is
> responsible for the creation and maintenance of software
> related to development of expressive web applications that
> deploy to all major browsers, desktops and devices (including
> smartphones, tablets and tv); and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Flex" 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 Flex Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Flex 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 Flex Project:
> 
> Alex Harui 
> Carol Frampton 
> Christophe Herreman 
> Chuck Mastrandrea 
> Dave Fisher 
> Erik de Bruin 
> Espen Skogen 
> Gordon Smith 
> Greg Reddin 
> Igor Costa 
> Iwo Banas 
> Jeff Tapper 
> Jeffry Houser 
> Jeremy Tellier 
> Jonathon Campos 
> Jun Heider 
> Justin Mclean 
> Kevin Korngut 
> Leif Wells 
> Martin Heidegger 
> Michael Jordan 
> Michael Labriola 
> Michael Schmalle 
> Michelle Yaiser 
> Nicholas Kwaitkowski 
> Omar Gonzalez 
> OmPrakash Muppirala 
> Peter Elst 
> Peter Ent 
> Rui Silva 
> Ryan Frishberg 
> Sebastian Mohr 
> Scott Delamater 
> Tink 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alex Harui
> be appointed to the office of Vice President, Apache Flex, 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 Flex 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 Flex Project; and be it further
> 
> RESOLVED, that the Apache Flex Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Flex podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Flex 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] Graduate Apache Wink from Incubator

[Suresh Marru]

+ 1 (binding).

Looking forward for the project to gain more momentum and community as a TLP.

Suresh
 
On Nov 25, 2012, at 6:49 PM, Luciano Resende  wrote:

> The Apache Wink project entered incubator in May of 2009. Since then
> it has grown the community in users, committers and PPMC members,
> made significant improvements to the project codebase and completed
> many releases following ASF policies and guidelines.
> 
> The Apache Wink community has voted to proceed with graduation [1]
> and the result can be found at [2]. Discussion about the proposed
> resolution
> is also available at [3].
> 
> Please cast your votes:
> 
> [  ] +1 Graduate Wink podling from Incubator
> [  ] +0 Indifferent to graduation status of Wink
> [  ] -1 Reject graduation of Wink podling from Incubator because ...
> 
> Please find the proposed board resolution below.
> 
> [1] http://s.apache.org/wink-graduation-vote
> [2] http://s.apache.org/wink-graduation-result
> [3] http://s.apache.org/wink-graduation-resolution
> 
> 
> Resolution:
> 
> X.Establish the Apache Wink 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 enabling development and
>   consumption of REST style web services.
> 
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "The Apache Wink Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
> 
>   RESOLVED, that The Apache Wink Project be and hereby is
>   responsible for the creation and maintenance of a software
>   project related to enabling development and consumption of
>   REST style web services; and be it further
> 
>   RESOLVED, that the office of "Vice President, Apache Wink" 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
>   Wink Project, and to have primary responsibility for
>   management of the projects within the scope of responsibility of
>   The Apache Wink 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 Wink Project:
> 
> * Bryant Luk (bluk)
> * Christopher James Blythe (cjblythe)
> * Dustin Amrhein (damrhei)
> * Davanum Srinivas (dims)
> * Eli Baram (elib)
> * Michael Elman (elman)
> * Jesse A. Ramos (jramos)
> * Kevan Lee Miller (kevan)
> * Luciano Resende (lresende)
> * Martin Snitkovsky (martins)
> * Nadav Fischer (nfischer)
> * Nicholas L. Gallardo (ngallardo)
> * Zhaohui Feng (rfeng)
> * Michael Rheinheimer (rott)
> * Tomer Shadi (tomershadi)
> 
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Luciano
>   Resende, be and hereby is appointed to the office of Vice
>   President, Wink, 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 Wink Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator Wink podling; and be it further
> 
>   RESOLVED, that all responsibility pertaining to the Apache
>   Incubator Wink podling encumbered upon the Apache Incubator
>   PMC are hereafter discharged.
> 
> 
> Regards
> 
> -- 
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/


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

Re: Sub-projects - when are they acceptable? (was Re: [VOTE] Graduate Nuvem as a sub-project under Apache Tuscany)

[Suresh Marru]

On Nov 21, 2012, at 12:19 PM, Greg Stein  wrote:

> On Wed, Nov 21, 2012 at 9:07 AM, Franklin, Matthew B.
>  wrote:
>> On 11/21/12 7:26 AM, "Benson Margulies"  wrote:
>> ...
>>> So, permit me to ask another, related, question. It seems to me that
>>> the IPMC is concerned with the fact that a project is ready to leave,
>>> but not so much which where it is going. A proposal to form a new TLP
>>> is, I think, a straightforward question to the board, and the IPMC's
>>> action is to make a recommendation to the board.
>>> 
>>> A proposal to be integrated into an existing project is, I think,
>>> within the authority of the existing product's PMC. If Project A
>>> wishes to invite the members of Podling B to join and integrate their
>>> code, then this looks to me like it could just happen without any
>>> approval in advance from the board or even the IPMC. Voting in
>>> committers is a PMC task, voting in PMC members is a PMC task with
>>> board lazy approval, and copying (ip-cleared) code from one place in
>>> ASF source control to another is a PMC task.
>>> 
>>> I think that IPMC graduation votes in this case are a nice thing, but
>>> it seems by this logic that they are not necessary.
>>> 
>>> Does this make sense?
>> 
>> I think your statement makes sense, but I see the votes as a way for IPMC
>> members to assert that they believe all due diligence in IP clearance has
>> been performed and that a sanity check has been done as to whether or not
>> the podling is to be fully integrated into the PMC of the target project.
>> From this perspective the Incubator serves to provide a convenience to the
>> target PMC in regards to releasability of code they are assuming and as a
>> foundation preventative measure for ensuring we don't end up with massive,
>> disconnected umbrellas comprised of former incubator podlings.
> 
> I'm with Matt: the vote is still needed to state "this community/code
> can be moved into the ASF".

Since incubation is more about learning the apache way in practice, I also 
think IPMC will be a better position to gauge it then the target PMC, so 
community readiness vote by IPMC might be good to continue irrespective of the 
podling ends up being a TLP or a sub-project. 

Cheers,
Suresh
 


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

Re: [VOTE] Accept Apache Streams as an Incubator Project

[Suresh Marru]

+ 1 (binding)

All the best,
Suresh

On Nov 14, 2012, at 7:37 AM, "Franklin, Matthew B."  wrote:

> Given the feedback received so far I think the Streams proposal is in good 
> shape so I am calling for a vote to accept Streams into the Incubator.
> 
> The proposal is at: http://wiki.apache.org/incubator/StreamsProposal and also 
> copied as text below.
> 
> Please vote.
> 
> [ ] +1 Accept Streams into the incubator
> [ ] +0 Don't care'
> [ ] -1 Reject for the following reason:
> 
> I'll close the vote at Monday morning on November 19th EST. 
> 
> - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/StreamsProposal 
> -
> 
> Apache Streams Proposal
> 
> == Abstract ==
> 
> Apache Streams will be a lightweight server for ActivityStreams. The role
> of Apache Streams is to provide a central point of aggregation, filtering
> and querying for Activities that have been submitted by disparate systems.
> Apache Streams also intends to include a mechanism for intelligent
> filtering and recommendation to reduce the noise to end users.
> 
> == Proposal ==
> 
> Apache Streams will bring together individuals who are or are looking to
> increase and centralize the production, consumption and federation of
> ActivityStreams throughout enterprise organizations and the Internet as a
> whole.  The target features include:
> 
> * Publication of Activities from multiple systems via HTTP
> * Aggregation and syndication of streams
> * Support for security trimming of streams by social graph
> * Noise reduction and intelligent filtering
> * Federation of streams across disparate systems
> * Provide libraries for easy integration in source systems
> 
> == Background ==
> 
> The ActivityStreams specification standardizes a generic format for
> describing event-based data.  Many social web companies have adopted the
> format and it has been included in the OpenSocial specification as the
> preferred method for delivery of activity data.  During discussions of
> ActivityStreams at OpenSocial events earlier in the year, it became clear
> that multiple organizations are facing similar issues as to the
> publication and filtering of their activities and would benefit from a
> commonly-developed, open-source ActivityStreams server.
> 
> == Rationale ==
> 
> In deployment, activities are generated from multiple sources.  This is
> particularly true within the enterprise where disparate systems create and
> manage activities in stove pipes.  What is needed is a central point for
> consumption, aggregation and exposure of activities generated within these
> systems.
> 
> == Initial Goals ==
> 
> The initial goal of the project is to survey donated code and develop a
> common, high-level architecture for an initial release.  The project will
> then work toward that release in a new code base, pulling in pieces of
> donated code as necessary.
> 
> == Current Status ==
> 
> The MITRE Corporation will donate its prototype code to the project.
> Aside from this, the project is new and will need bootstrap time to
> develop an initial architecture and roadmap.
> 
>  Meritocracy 
> 
> As a new project with many team members who are seasoned Apache veterans,
> Apache Streams is prepared to build the project under the Apache Way.
> 
>  Community 
> 
> The Apache Streams community combines multiple individuals from different
> organizations, many of which have collaborated before in an open
> environment.  Apache Streams is committed to expanding this community and
> adhering to Apache principles of openness and collaboration.
> 
> == Known Risks ==
> 
> An exercise in self-knowledge. Risks don't mean that a project is
> unacceptable. If they are recognized and noted then they can be addressed
> during incubation.
> 
>  Inexperience with Open Source 
> 
> Most of the initial committers have worked in open source and many are
> familiar with the ASF and the Apache Way; but, not all.  Additionally,
> many of the committers have not worked on a software project together and
> will need time to familiarize themselves with each other.
> 
>  Speed of Development 
> 
> This project is dependent upon contributions made on company time. For
> this approach to succeed, the project must deliver a workable system in a
> timeframe acceptable to those companies. The initial parties have the
> intention of releasing a first version within 6 months after starting the
> Incubator. Failure to do so could prevent the project reaching critical
> mass, and could prevent the project from being in a position to attract
> new developers.
> 
>  Reliance on Salaried Developers 
> 
> At present, the vast majority of contributors will be doing so as a part
> of their day jobs. Therefore, as already alluded to, there is a risk that
> the project won't gain enough traction to be of use to their employers.
> However, given the centrality of these codebases to the participating
> companies, it is clearly in their best interests

Re: [VOTE][PROPOSAL] Hadoop Development Tools

[Suresh Marru]

+ 1 (binding)

Suresh

On Nov 6, 2012, at 10:57 AM, Adam Berry  wrote:

> Hello,
> 
> This proposal has been open for discussion for a a few weeks, so now 
> submitting for a vote for this project to be accepted into the incubator.
> 
> Cheers,
> Adam Berry
> 
> = HDT (Hadoop Development Tools) =
> 
> == Abstract ==
> Tools to support developing applications that use Apache Hadoop from within 
> Eclipse.
> 
> == Proposal ==
> Hadoop Development Tools are a set of extensions to Eclipse providing support 
> for creating, launching and debugging distributed applications, as well as 
> interacting with HDFS filesystems. This work will build on the existing Map 
> Reduce Tools present in the Apache Hadoop project.
> 
> == Background ==
> Map Reduce Tools have existed as part of contrib for Apache Hadoop. 
> Unfortunately they are source tied to a single version of Hadoop, and 
> development has stalled, with little movement past the Hadoop 0.20 line.
> 
> == Rationale ==
> Support for newer versions of Hadoop from within Eclipse is regularly raised 
> on the Hadoop mailing lists, so there is a clear need to drive these tools 
> forward. Development tools generally are worked on separate from the target 
> tools/platform, separating the tools out will allow for supporting multiple 
> versions, so a developer could work with a heterogeneous environment. 
> 
> == Initial Goals ==
> * Give the tools project a home of its own.
> * Port current MapReduce tools feature set to all current release lines of 
> Hadoop in a single Eclipse install.
> * Documentation and tutorials for all features.
> * Publish Eclipse update site, and join Eclipse marketplace listing.
> * Establish release cycle that combines support for Hadoop and Eclipse 
> release cycles.
> * Look to build support for YARN, MRUnit and possibly other Hadoop-related 
> projects.
> 
> == Current Status ==
> The source for the current MapReduceTools lives in the contrib section of the 
> Hadoop source. In its current implementation it is tied to the version of 
> Hadoop against which it is compiled. The layout and API that it was developed 
> with means that it can only be used with the 0.20 or 1.0 Hadoop releases, the 
> new layout and YARN api introduced with the 0.23 and 2.0 lines are not 
> supported.
> 
> 
> === Meritocracy ===
> Several people and companies have already expressed an interest in 
> contributing to this project, and we hope to attract additional interest 
> during the proposal discussion. We plan to invest and support a meritocracy 
> that attracts, invites, and supports newcomers to build a vibrant and  
> diverse community. 
> 
> === Community ===
> The target community is developers who are working developing Map/Reduce 
> applications against Hadoop. Given the success of Hadoop the target group is 
> likely to be quite large. Separation from the Hadoop community would make it 
> easier to support multiple versions of hadoop, as well as merging the release 
> cycles of Hadoop and Eclipse to provide predictable iteration and improvement 
> in the toolset. 
> 
> === Core Developers ===
> The initial list of developers includes people experienced with Hadoop and 
> developing against the Eclipse platform.
> * Adam Berry (amberry at yahoo-inc dot com)
> * Jeffrey Zemerick (jeffrrey at mtnfog dot com)
> * Evert Lammerts (Evert dot Lammerts at sara dot nl)
> * Simone Gianni (simoneg at apache dot org)
> 
> === Alignment ===
> Hadoop Development Tools aligns with both Hadoop and Eclipse. Hadoop as the 
> platform for the development target, and Eclipse as the IDE platform used as 
> the base for the tools.
> 
> == Known Risks ==
> 
> === Orphaned Products ===
> 
> === Inexperience with Open Source ===
> The committers have experience with Apache and Eclipse open source 
> development.
> 
> === Reliance on Salaried Developers ===
> Hadoop Development Tools will be developed with a mix of salaried and 
> volunteer time.
> 
> === Relationships with Other Apache Projects ===
> Hadoop Development Tools is closely related to Apache Hadoop.
> 
> === An Excessive Fascination with the Apache Brand ===
> Given the success of Hadoop and associated projects, Apache is the natural 
> place for the Hadoop Development Tools. Chris Mattman suggested the Apache 
> Incubator as appropriate on the Hadoop general mailing list following the 
> success that MRUnit had taking the path from Hadoop contrib to an Apache top 
> level project.
> 
> == Documentation ==
> Documentation for the current tools can be found at 
> http://wiki.apache.org/hadoop/EclipsePlugIn 
> 
> == Initial Source ==
> http://svn.apache.org/repos/asf/hadoop/common/trunk/hadoop-mapreduce-project/src/contrib/eclipse-plugin/
> 
> ==  Source and Intellectual Property Submission Plan ==
> The source, and any suggested initial patches, are already hosted either in 
> Apache’s Subversion or JIRA.
> 
> ==  External Dependencies ==
> Eclipse Platform
> Eclipse Java Development Tools
> 
> ==  Cryptograp