Re: [PROPOSAL] Bigtop for the Apache Incubator
+1. Looking forward to the vote.
On Jun 13, 2011, at 9:26 PM, Tom White wrote:
Hi,
I would like to propose Bigtop to be an Apache Incubator project.
Bigtop is a project for the development of packaging and tests of the
Hadoop ecosystem. The goal is to do testing at various levels
(packaging, platform, runtime, upgrade, etc...) developed by a
community with a focus on the system as a whole, rather than
individual projects.
Here's a link to the proposal on the wiki
http://wiki.apache.org/incubator/BigtopProposal
I've also included the initial contents below.
Cheers,
Tom
= Bigtop - Apache Hadoop Ecosystem Packaging and Test =
== Abstract ==
Bigtop - a project for the development of packaging and tests of the
Hadoop ecosystem.
== Proposal ==
The primary goal of Bigtop is to build a community around the
packaging and interoperability testing of Hadoop-related projects.
This includes testing at various levels (packaging, platform, runtime,
upgrade, etc...) developed by a community with a focus on the system
as a whole, rather than individual projects.
Build, packaging and integration test code that depends upon official
releases of the Apache Hadoop-related projects (HDFS, MapReduce,
HBase, Hive, Pig, ZooKeeper, etc...) will be developed and released by
this project. As bugs and other issues are found we expect these to be
fixed upstream.
== Background ==
The initial packaging and test code for Bigtop was developed by
Cloudera to package projects from the Apache Hadoop ecosystem and
provide a consistent, inter-operable framework.
== Rationale ==
Hadoop defines itself as:
{{{
The Apache Hadoop project develops open-source software for reliable,
scalable, distributed computing. Hadoop includes these subprojects:
* Hadoop Common: The common utilities that support the other Hadoop
subprojects.
* HDFS: A distributed file system that provides high throughput access
to application data.
* MapReduce: A software framework for distributed processing of large
data sets on compute clusters.
}}}
There are also several other Hadoop-related projects at Apache. Some
TLP examples include HBase, Hive, Mahout, ZooKeeper, and Pig. There
are also several new projects in the Incubator such as HCatalog and
Sqoop.
There is limited interoperability testing done the projects
themselves. The intent of this project is to build a community where
the projects are brought together, packaged, and tested for
interoperability.
Projects such as Apache Whirr (incubating), which deploy and use a
collection of Hadoop-related projects, would benefit from the
interoperability testing done by Bigtop, rather than picking and
testing project combinations themselves.
== Initial Goals ==
Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.
Some current goals include:
* create a set of packages for the Hadoop ecosystem, over a wide
range of platforms
* interoperability test these projects
* document project sets that are known to work well together
Bigtop’s release artifact would consist of a single tarball of
packaging and test code that, when built, would produce source and
binary Linux packages for the upstream projects.
= Current Status =
== Meritocracy ==
Bigtop was originally developed and released as an open source
packaging infrastructure, CDH, by Cloudera.
== Community ==
The community is primarily the original developers at Cloudera,
however a number of contributions to the packaging specifications have
been accepted from outside contributors. Growing a diverse community
is the main reason to bring Bigtop to the Apache Incubator.
== Core Developers ==
The core developers for Bigtop project are:
* Andrew Bayer has extensive expertise with build tools, specifically
Jenkins continuous integration and Maven.
* Peter Linnell has contributed to the RPM packaging.
* Bruno Mahé has overseen much of the development of the RPM and
Debian packaging system.
* Roman Shaposhnik designed and implemented the system testing framework.
Many of the committers to the Bigtop project have contributed towards
Hadoop or related Apache projects (Alejandro Abdelnur, Eli Collins,
Patrick Hunt, John Sichi, Michael Stack, Tom White) and are familiar
with Apache principals and philosophy for community driven software
development.
== Alignment ==
We expect projects in Bigtop to be drawn from Hadoop and related
projects at Apache. Bigtop will complement these projects (Hadoop,
Pig, Hive, HBase, etc...) by providing an environment for contributors
interested in building more complex data processing pipelines to work
together integrating more than a single project into a well tested
whole.
= Known Risks =
== Orphaned Products ==
The contributors are leading vendors of Hadoop-based technologies and
have a long standing in the Hadoop community. There is
Re: *** Monthly reports missing ...
will do this today for Isis. sorry and LieGrue, strub --- On Tue, 6/14/11, Noel J. Bergman n...@devtech.com wrote: From: Noel J. Bergman n...@devtech.com Subject: *** Monthly reports missing ... To: general@incubator.apache.org Date: Tuesday, June 14, 2011, 4:58 AM I know that it is early (as in the earliest that the meeting could possibly happen), but we're late. BeanValidation, Bluesky, Isis, and Wave are all missing from the Wiki. --- Noel - 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
[alois] Incubation failed?
Hi all, shortly after the last report in March one of the Alois-Devs contacted me and told me, that there will be no further development on the project because of some personal trouble and changes to the company IMSEC (inventor of alois). Even prior march there were only slow steps to observe - website has been established, code has been made accessible via svn (but no more commits) and a few talks has been given. We waited for three more months and there is still no interest in the project: no mailinglist activity, no commits, no new issues. I do not expect any changes to the current situation. I would like to propose Dormant or Retired status for the alois project - not sure what is more matching or what the difference between these two is. Unfortunately I have not found any docs about this process. Any comments to this? Thanks, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Bluesky status and plans (was: Monthly reports missing)
On Tue, Jun 14, 2011 at 12:58 AM, Noel J. Bergman n...@devtech.com wrote: I know that it is early (as in the earliest that the meeting could possibly happen), but we're late. BeanValidation, Bluesky, Isis, and Wave are all missing from the Wiki. Bluesky entered incubation nearly three and half years ago. It is time to decide that incubation is not going to succeed for this podling? --- Noel - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request: Can proposed committers introduce themselves?
Hi, let me introduce myself a little bit more as promised in my voting email ;-) My name is Juergen Schmidt (jsc) and i work on the project since 1997, started at StarDivision - Sun - Oracle where i am still employed today. But i am here as individual and everything i will do and say here is based on my very own opinion and motivation. I will also do not speak for Oracle in any way and i am here only to help and to bring OpenOffice.org forward. At the beginning i was deeply involved in the development of UNO the underlying component middleware technology and focused later more and more on the general programmability features. As the API and Extensions project lead i always tried to bring these features forward. I always had the vision of a component based architecture where you have well defined functional blocks (components) that build altogether a complete product. In an ideally world you would be able to define a feature set, let's say you need a writer component only, and some kind of tooling would package all necessary fine grained components that builds all together a full featured writer editor. Ok i know that is very highlevel but i hope the idea becomes a little bit more clear. Anyway in the existing code base we are of course far away of such an architecture because it's more complex and the modularization that would be necessary is not in place yet. But maybe we can achieve it in the future or can at least move forward in this direction. Make things easier reusable and also easier exchangeable for example if a better implementation becomes available ... I worked also on tooling and documentation that helps to develop with and for OpenOffice.org (SDK, DevGuide, NetBeans Extension plugin, ...). Compared to another proprietary office suite we have a lot of space for improvements here to make it easier for end users and developers to develop their own automation workflows, solutions or to develop connectors in other business critical applications. Yes the success of OpenOffice.org should be in the business world and not only in the private sector. A successful future of the OpenOffice.org project needs sponsors and they come probably not from the private sector only. As some kind of OOo Evangelist i have spread and shared my knowledge around the API and Extensions development on many conferences all over the world (e.g. JavaOne, FISL, FOSS.IN, FOSDEM, LinuxTag,...) . Community work was one part of my daily work and also of my private spare time.The split of the community last year was a dark moment in the history of OOo and i hope that over time we will have again one community working all together on the same goal. I am also a member of the OOo community council and besides the general work there i focused on the organization of an internship program (2010) which is comparable to the well known GSOC. We hadn't the same budget as Google but we were able to run at least 6 projects with success. That should be enough for the moment and if you have any further question that is related to my person or to my work as a OOo community member feel free to ask me. I hope this can be the beginning of a new great project where political issues becomes more and more unimportant in the future. Kind regards Juergen
Re: [PROPOSAL] Bigtop for the Apache Incubator
On 14/06/11 05:26, Tom White wrote: Hi, I would like to propose Bigtop to be an Apache Incubator project. Bigtop is a project for the development of packaging and tests of the Hadoop ecosystem. The goal is to do testing at various levels (packaging, platform, runtime, upgrade, etc...) developed by a community with a focus on the system as a whole, rather than individual projects. Here's a link to the proposal on the wiki http://wiki.apache.org/incubator/BigtopProposal I've also included the initial contents below. Cheers, Tom I've added my name to the committer list, I won't be working on this in much/any of work time, and am fairly overcommitted, so don't expect that much. I can contribute some of my experience in VM setup/teardown for testing RPM installations, and how to do functional testing of dynamically created Hadoop clusters. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Bigtop for the Apache Incubator
I've added more on the limitations of the current process (not synchronised releases, not enough automated testing on multiple-host clusters), and on a risk of the project: the upstream projects need to care about and work on more synchronized releases. Cloudera managed to address that problem by patching their forks of the apache projects, then push back the patches by way of JIRA patches. Bigtop should not get into the game of having its own branches of any of the ASF projects, instead it should focus on getting its changes into trunk of the various projects SVN trees, and on having near-synchronized releases of the various projects That requires -engagement from the committer teams to get patches in. Having committers from the relevant projects in the BigTop project would address this. -support from the PMCs to do releases on a regular schedule. That's hard, but something like a six-monthly schedule for the big projects with the up and coming projects releasing in a proper factor of that timescale (3, 2, 1 month), could help. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [alois] Incubation failed?
If that is the recommendation, check with the community to see if there is any pushback, and depending on result we'll vote on it. Thanks for taking the time to get this going. :-) --- Noel -Original Message- From: Christian Grobmeier [mailto:grobme...@gmail.com] Sent: Tuesday, June 14, 2011 4:18 To: general@incubator.apache.org Subject: [alois] Incubation failed? Hi all, shortly after the last report in March one of the Alois-Devs contacted me and told me, that there will be no further development on the project because of some personal trouble and changes to the company IMSEC (inventor of alois). Even prior march there were only slow steps to observe - website has been established, code has been made accessible via svn (but no more commits) and a few talks has been given. We waited for three more months and there is still no interest in the project: no mailinglist activity, no commits, no new issues. I do not expect any changes to the current situation. I would like to propose Dormant or Retired status for the alois project - not sure what is more matching or what the difference between these two is. Unfortunately I have not found any docs about this process. Any comments to this? Thanks, Christian - 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: Bluesky status and plans (was: Monthly reports missing)
We can take that up with the community. They've certainly had their struggles, but seem to come back sporadically. --- Noel -Original Message- From: sa3r...@gmail.com [mailto:sa3r...@gmail.com]On Behalf Of Sam Ruby Sent: Tuesday, June 14, 2011 6:49 To: general@incubator.apache.org Subject: Bluesky status and plans (was: Monthly reports missing) On Tue, Jun 14, 2011 at 12:58 AM, Noel J. Bergman n...@devtech.com wrote: I know that it is early (as in the earliest that the meeting could possibly happen), but we're late. BeanValidation, Bluesky, Isis, and Wave are all missing from the Wiki. Bluesky entered incubation nearly three and half years ago. It is time to decide that incubation is not going to succeed for this podling? --- Noel - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Bluesky status and plans (was: Monthly reports missing)
On Tue, Jun 14, 2011 at 16:15, Noel J. Bergman n...@devtech.com wrote: We can take that up with the community. They've certainly had their struggles, but seem to come back sporadically. --- Noel -Original Message- From: sa3r...@gmail.com [mailto:sa3r...@gmail.com]On Behalf Of Sam Ruby Sent: Tuesday, June 14, 2011 6:49 To: general@incubator.apache.org Subject: Bluesky status and plans (was: Monthly reports missing) On Tue, Jun 14, 2011 at 12:58 AM, Noel J. Bergman n...@devtech.com wrote: I know that it is early (as in the earliest that the meeting could possibly happen), but we're late. BeanValidation, Bluesky, Isis, and Wave are all missing from the Wiki. Bluesky entered incubation nearly three and half years ago. It is time to decide that incubation is not going to succeed for this podling? I've been following the mailing list for a while now and I don't see any progress towards what could become an Apache project eventually. Bernd - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Bluesky status and plans (was: Monthly reports missing)
On Tue, Jun 14, 2011 at 10:38 AM, Bernd Fondermann bernd.fonderm...@googlemail.com wrote: On Tue, Jun 14, 2011 at 16:15, Noel J. Bergman n...@devtech.com wrote: We can take that up with the community. They've certainly had their struggles, but seem to come back sporadically. I've been following the mailing list for a while now and I don't see any progress towards what could become an Apache project eventually. All past struggles aside, if there are no credible plans to produce an ASF project after 2.5 years, then IMHO it is time to begin the process of terminating the incubation of this podling. - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Bigtop for the Apache Incubator
Steve, Thanks for signing up. Bigtop should not maintain branches or patchsets on top of upstream projects. Any bugs or compatibility problems that are found will need to be resolved in the upstream projects and then released in those projects. This makes things harder for Bigtop, but, like you, I hope having committers from the upstream projects involved in Bigtop will give projects further impetus to make releases in a timely manner. Cheers, Tom On Tue, Jun 14, 2011 at 4:51 AM, Steve Loughran ste...@apache.org wrote: I've added more on the limitations of the current process (not synchronised releases, not enough automated testing on multiple-host clusters), and on a risk of the project: the upstream projects need to care about and work on more synchronized releases. Cloudera managed to address that problem by patching their forks of the apache projects, then push back the patches by way of JIRA patches. Bigtop should not get into the game of having its own branches of any of the ASF projects, instead it should focus on getting its changes into trunk of the various projects SVN trees, and on having near-synchronized releases of the various projects That requires -engagement from the committer teams to get patches in. Having committers from the relevant projects in the BigTop project would address this. -support from the PMCs to do releases on a regular schedule. That's hard, but something like a six-monthly schedule for the big projects with the up and coming projects releasing in a proper factor of that timescale (3, 2, 1 month), could help. - 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: Bluesky status and plans (was: Monthly reports missing)
Sam Ruby wrote: All past struggles aside, if there are no credible plans to produce an ASF project after 2.5 years, then IMHO it is time to begin the process of terminating the incubation of this podling. I'm not arguing that point. As I had replied, we can start the dormancy discussion with them. Do you wish to do that, or ask Bill? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Etch Status?
What is preventing Etch from graduating? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
June 2011 Incubator Board Report
The Incubator PMC now totals 143 members, with some additional requests (joining and a resignation) pending. Recent changes include Peter Royal and Phil Steitz (pending) dropping off; and Shane Curcuru, Srinath Perera, Nicolas Lalevee, Marvin Humphrey, Michael McCandless, Nigel Daley, Tommaso Teofili, Yegor Kozlov, Leif Hedstrom and Steve Loughran joining the PMC. Certainly the biggest thing in the Incubator this month is the arrival of OpenOffice.org for Incubation. OpenOffice.org is going to need significant help and guidance, with an emphasis on liasoning with other, external, projects such as LibreOffice. There is very significant concern regarding how this project will relate to the rest of the Openoffice.org ecosystem, and those will need to be carefully addressed. One of the first challenges for the project will be deciding its scope. If it is going to try to be the old OpenOffice.org, essentially an Apache Licensed coopetitor to the downstream forks; or if it is going to focus on common technologies, release vanilla binaries for key platforms, and let the downstreams take the primary role in delivering end-user binaries. Other issues with respect to OpenOffice.org may challenge our infrastructure. There may also be IP (patent and trademark) issues to address. But the lengthy and diverse list of Mentors should be aware of and preparing to address all of the issues. Despite OpenOffice.org's arrival, and its well than 1000 messages swamping the mailing list, there was more activity than just that one topic. BigTop, a project for the development of packaging and tests of the Hadoop ecosystem, is proposed for Incubation. Flume -- a distributed, reliable, and available system for efficiently collecting, aggregating, and moving large amounts of log data to scalable data storage systems such as Apache Hadoop's HDFS -- was voted to enter Incubation. Sqoop -- a tool designed for efficiently transferring bulk data between Apache Hadoop and structured datastores such as relational databases -- was voted to enter Incubation. There is nascent discussion regarding moving Alois and BlueSky to dormant status. Airavata Airavata is a software toolkit currently used to build science gateways but that has a much wider potential use. It provides features to compose, manage, execute, and monitor large scale applications and workflows on computational resources ranging from local clusters to national grids and computing clouds. A list of the three most important issues to address in the move towards graduation 1. Finish the security paper work needed to import donated code with cryptographic dependencies. 2. Engage the community by document existing design, drafting detailed JIRA tasks defining smaller goals. 3. Remove incompatible license dependencies and implement over ALV2 compatible libraries. 4. Simplify the build process and provide simple to use cases. 5. At least one Apache Incubator release. 6. Develop a strong community with organizational diversity and well aligned with existing ASF projects as outlined here: http://wiki.apache.org/incubator/AiravataProposal#Alignment Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No, not at this time. How has the community developed since the last report? The interactions to date have been focused on development, and getting the project started. How has the project developed since the last report? Airavata was voted into the Incubator by the IPMC on May 7, 2011. Suresh Marru is pushing forward on the Airavata website. There is also work going on related to this to define a new Apache Airavata logo. In addition, Suresh led a development roadmap discussion. ALOIS The ALOIS project team wrote an private e-mail to it's mentors shortly after the last report. They have told us that due to personal reasons they cannot keep this project alive and there will be no project activity in near future. We have agreed to wait until the June 2011 comes up. So far there is no change in project activity or interest, no e-mails and even no more private messages. After this report the Incubator-PMC needs to discuss about moving this podling to attic. (Christian Grobmeier) In addition to Christian's report, I'd like to mention that we didn't find any interest in the project outside of our small group, although we did quite a lot requests off list. If there would be someone to take over the project, we would be happy to give a helping hand at the start. (Urs Lerch) BeanValidation Apache Bean Validation will deliver an implementation of the JSR303 Bean Validation 1.0 specification. BVAL entered incubation on March 1, 2010. A list of the three most important issues to address in the move towards graduation. * Perform successful Releases - Done * Grow the community and committer base - stale at a medium level * Decide on graduation target of TLP or
Re: Bluesky status and plans (was: Monthly reports missing)
On Tue, Jun 14, 2011 at 11:20 AM, Noel J. Bergman n...@devtech.com wrote: Sam Ruby wrote: All past struggles aside, if there are no credible plans to produce an ASF project after 2.5 years, then IMHO it is time to begin the process of terminating the incubation of this podling. I'm not arguing that point. As I had replied, we can start the dormancy discussion with them. Do you wish to do that, or ask Bill? Not clear who Bill is in the context, but in any case, I encourage everybody and anybody who believes that it is possible to create a credible plan that they personally endorse for graduation for BlueSky to do so and submit a report for BlueSky in time for inclusion in the July board report. If that can't be done, then, yes Noel, I would appreciate it if you would start a discussion about dormancy at that time. --- Noel - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Hadoop related Incubator projects
There are some which indicate that their sole impediment to graduation is community size. Has there been any consideration of the Hadoop TLP picking them up as sub-projects? --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Etch Status?
On Tue, Jun 14, 2011 at 5:31 PM, Noel J. Bergman n...@devtech.com wrote: What is preventing Etch from graduating? A diverse, active, growing community and building releases. Martijn - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Hadoop related Incubator projects
On Tue, Jun 14, 2011 at 8:35 AM, Noel J. Bergman n...@devtech.com wrote: There are some which indicate that their sole impediment to graduation is community size. Has there been any consideration of the Hadoop TLP picking them up as sub-projects? Wow, the wheels turn. The Hadoop PMC was strongly encouraged by the board to divest itself of the Hadoop-podlings, because it had become an umbrella project. I think that over all, most of the projects are doing better are doing as TLP and incubator projects. -- Owen
Re: Bluesky status and plans (was: Monthly reports missing)
On Tue, Jun 14, 2011 at 7:38 AM, Bernd Fondermann bernd.fonderm...@googlemail.com wrote: On Tue, Jun 14, 2011 at 16:15, Noel J. Bergman n...@devtech.com wrote: We can take that up with the community. They've certainly had their struggles, but seem to come back sporadically. --- Noel -Original Message- From: sa3r...@gmail.com [mailto:sa3r...@gmail.com]On Behalf Of Sam Ruby Sent: Tuesday, June 14, 2011 6:49 To: general@incubator.apache.org Subject: Bluesky status and plans (was: Monthly reports missing) On Tue, Jun 14, 2011 at 12:58 AM, Noel J. Bergman n...@devtech.com wrote: I know that it is early (as in the earliest that the meeting could possibly happen), but we're late. BeanValidation, Bluesky, Isis, and Wave are all missing from the Wiki. Bluesky entered incubation nearly three and half years ago. It is time to decide that incubation is not going to succeed for this podling? I've been following the mailing list for a while now and I don't see any progress towards what could become an Apache project eventually. Bernd +1, At the beginning I was really trying to help and be a non-official mentor for the Bluesky podling and I now tend to agree with Bernd that no really progress has been made and I don't see that changing in the near/medium future. -- 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: [VOTE] Release Droids 0.1-incubating RC2
On Sat, Jun 11, 2011 at 10:43:21PM -0500, Richard Frovarp wrote: Please vote on the release cndidate for Apache Droids Incubating, version 0.1-incubating. I've received one binding IPMC +1 votes and 2 non-binding +1 votes. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-droids-dev/201106.mbox/%3c4de7d6cc.8080...@apache.org%3E Hi, Looks like this is the inaugural ASF release for Droids, right? First, congratulations on getting this far! It can take a long time and a lot of effort to get to the point where a podling's contributors feel comfortable proposing an ASF release. That said, I have some questions about the PPMC vote thread. Droids has the following roster, according to the status page: Mentors Ross Gardler Paul Fremantle Grant Ingersoll Committers Thorsten Scherler Ryan McKinley Grant Ingersoll Oleg Kalnichevski This is the tally for the PPMC vote: +1 Torsten Scherler +1 Richard Frovarp +1 Bertil Chapuis The Droids status page has apparently not been kept up to date, since there are numerous authors listed at... http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fincubator%2Fdroids ... and both Richard Frovarp and Bertil Chapuis seem to have commit rights. Can you please confirm that the three +1 votes all belong to people who are official members of the Droids PPMC? Then there's the IMPC vote, which looks like it comes from Thorsten Scherler. According to this... http://people.apache.org/committers-by-project.html#incubator-pmc ... Thorsten is not on the IPMC right now, though as an ASF Member he can simply request to join. Once that happens, you'll have 1 IPMC vote. However, none of the Droids Mentors appear to have participated in the vote. I know one of them is camping and one took a new job recently, but still, it's troubling. In principle, I'd like to freelance and contribute some oversight towards your release by performing a surface review and voting. I can check license headers, sigs and sums, etc, and help with an audit of LICENSE and NOTICE, especially if we can work together to produce an authoritative list of the project's dependencies. Unfortunately, my Java expertise is almost all theoretical, so code review will be limited to fumbling around until I figure out how to run the test suite and verify that it passes. However, I won't personally feel comfortable contributing a +1 without at least one of your Mentors signing off, particularly for a first release which endorses the IP clearance process. I've only been on the IPMC a few weeks. Can any of our more experienced hands offer recommendations about the best way to proceed? Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Bluesky status and plans (was: Monthly reports missing)
What happens to a dormant podling? Are its files still accessible, and does its licensing still apply? Don On Tue, Jun 14, 2011 at 12:21 PM, Luciano Resende luckbr1...@gmail.com wrote: On Tue, Jun 14, 2011 at 7:38 AM, Bernd Fondermann bernd.fonderm...@googlemail.com wrote: On Tue, Jun 14, 2011 at 16:15, Noel J. Bergman n...@devtech.com wrote: We can take that up with the community. They've certainly had their struggles, but seem to come back sporadically. --- Noel -Original Message- From: sa3r...@gmail.com [mailto:sa3r...@gmail.com]On Behalf Of Sam Ruby Sent: Tuesday, June 14, 2011 6:49 To: general@incubator.apache.org Subject: Bluesky status and plans (was: Monthly reports missing) On Tue, Jun 14, 2011 at 12:58 AM, Noel J. Bergman n...@devtech.com wrote: I know that it is early (as in the earliest that the meeting could possibly happen), but we're late. BeanValidation, Bluesky, Isis, and Wave are all missing from the Wiki. Bluesky entered incubation nearly three and half years ago. It is time to decide that incubation is not going to succeed for this podling? I've been following the mailing list for a while now and I don't see any progress towards what could become an Apache project eventually. Bernd +1, At the beginning I was really trying to help and be a non-official mentor for the Bluesky podling and I now tend to agree with Bernd that no really progress has been made and I don't see that changing in the near/medium future. -- 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Droids 0.1-incubating RC2
On 06/14/2011 12:31 PM, Marvin Humphrey wrote: On Sat, Jun 11, 2011 at 10:43:21PM -0500, Richard Frovarp wrote: Please vote on the release cndidate for Apache Droids Incubating, version 0.1-incubating. I've received one binding IPMC +1 votes and 2 non-binding +1 votes. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-droids-dev/201106.mbox/%3c4de7d6cc.8080...@apache.org%3E Hi, Looks like this is the inaugural ASF release for Droids, right? Thank you for looking at this. Yes, it will be. First, congratulations on getting this far! It can take a long time and a lot of effort to get to the point where a podling's contributors feel comfortable proposing an ASF release. That said, I have some questions about the PPMC vote thread. Droids has the following roster, according to the status page: Mentors Ross Gardler Paul Fremantle Grant Ingersoll Committers Thorsten Scherler Ryan McKinley Grant Ingersoll Oleg Kalnichevski This is the tally for the PPMC vote: +1 Torsten Scherler +1 Richard Frovarp +1 Bertil Chapuis The Droids status page has apparently not been kept up to date, since there are numerous authors listed at... http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fincubator%2Fdroids ... and both Richard Frovarp and Bertil Chapuis seem to have commit rights. Can you please confirm that the three +1 votes all belong to people who are official members of the Droids PPMC? Yes, the page needs to be updated. Ross has provided us with a link to the page on how to update that information. I personally haven't had time to do it. I think I'm on the PPMC, but for the Incubator, I'm not quite sure the distinction between a PPMC member and a committer. Then there's the IMPC vote, which looks like it comes from Thorsten Scherler. According to this... http://people.apache.org/committers-by-project.html#incubator-pmc ... Thorsten is not on the IPMC right now, though as an ASF Member he can simply request to join. Once that happens, you'll have 1 IPMC vote. But he is. Several months ago the board acked his request, but it would appear that the IPCM membership roster hasn't been updated. However, none of the Droids Mentors appear to have participated in the vote. I know one of them is camping and one took a new job recently, but still, it's troubling. Ross participated in a previous vote that didn't pass as we found things we need to clean up. It would seem he didn't have the time to participate this time. In principle, I'd like to freelance and contribute some oversight towards your release by performing a surface review and voting. I can check license headers, sigs and sums, etc, and help with an audit of LICENSE and NOTICE, especially if we can work together to produce an authoritative list of the project's dependencies. Unfortunately, my Java expertise is almost all theoretical, so code review will be limited to fumbling around until I figure out how to run the test suite and verify that it passes. I can put together a list. Maven should give it to me easily and I can post. I've gone through it quite carefully and everything I can see indicates that we are good. I've been doing some of this as PMC Chair for Apache Lenya, so I do have some experience with it. Further help and guidance of course is always welcome. However, I won't personally feel comfortable contributing a +1 without at least one of your Mentors signing off, particularly for a first release which endorses the IP clearance process. Fair enough. I've only been on the IPMC a few weeks. Can any of our more experienced hands offer recommendations about the best way to proceed? Thanks once again. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Bigtop for the Apache Incubator
On 14/06/11 05:26, Tom White wrote: Hi, I would like to propose Bigtop to be an Apache Incubator project. Bigtop is a project for the development of packaging and tests of the Hadoop ecosystem. The goal is to do testing at various levels (packaging, platform, runtime, upgrade, etc...) developed by a community with a focus on the system as a whole, rather than individual projects. Here's a link to the proposal on the wiki http://wiki.apache.org/incubator/BigtopProposal I've also included the initial contents below. Cheers, Tom I've added my name to the committer list, I won't be working on this in much/any of work time, and am fairly overcommitted, so don't expect that much. I can contribute some of my experience in VM setup/teardown for testing RPM installations, and how to do functional testing of dynamically created Hadoop clusters. I am going to add my name to the list of the committers too. Considering my other commitments I might not be able to work much on this project, but I guess the fact that I have wrote like 50% of the underlying system framework might count for something. Cos - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Bigtop for the Apache Incubator
On Tue, Jun 14, 2011 at 11:43 AM, Konstantin Boudnik c...@apache.org wrote: On 14/06/11 05:26, Tom White wrote: Hi, I would like to propose Bigtop to be an Apache Incubator project. Bigtop is a project for the development of packaging and tests of the Hadoop ecosystem. The goal is to do testing at various levels (packaging, platform, runtime, upgrade, etc...) developed by a community with a focus on the system as a whole, rather than individual projects. Here's a link to the proposal on the wiki http://wiki.apache.org/incubator/BigtopProposal I've also included the initial contents below. Cheers, Tom I've added my name to the committer list, I won't be working on this in much/any of work time, and am fairly overcommitted, so don't expect that much. I can contribute some of my experience in VM setup/teardown for testing RPM installations, and how to do functional testing of dynamically created Hadoop clusters. I am going to add my name to the list of the committers too. Considering my other commitments I might not be able to work much on this project, but I guess the fact that I have wrote like 50% of the underlying system framework might count for something. Welcome aboard Cos! Glad to have you on. Cos has made a ton of contributions to the test frameworks in Bigtop. Looking forward to your contributions! Thanks, Eli - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Etch Status?
We are close to the next release and will do it as soon as the latest open technical points are resolved. Concerning the diverse growing community, we still have to invest into more public relations and heighten the profile of the project. We got some useful tips at the Apache Retreat in Knockree. regards Michael 2011/6/14 Martijn Dashorst martijn.dasho...@gmail.com: On Tue, Jun 14, 2011 at 5:31 PM, Noel J. Bergman n...@devtech.com wrote: What is preventing Etch from graduating? A diverse, active, growing community and building releases. Martijn - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Droids 0.1-incubating RC2
On 14 June 2011 19:39, Richard Frovarp rfrov...@apache.org wrote: On 06/14/2011 12:31 PM, Marvin Humphrey wrote: On Sat, Jun 11, 2011 at 10:43:21PM -0500, Richard Frovarp wrote: Please vote on the release cndidate for Apache Droids Incubating, version 0.1-incubating. I've received one binding IPMC +1 votes and 2 non-binding +1 votes. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-droids-dev/201106.mbox/%3c4de7d6cc.8080...@apache.org%3E Hi, Looks like this is the inaugural ASF release for Droids, right? Thank you for looking at this. Yes, it will be. First, congratulations on getting this far! It can take a long time and a lot of effort to get to the point where a podling's contributors feel comfortable proposing an ASF release. That said, I have some questions about the PPMC vote thread. Droids has the following roster, according to the status page: Mentors Ross Gardler Paul Fremantle Grant Ingersoll Committers Thorsten Scherler Ryan McKinley Grant Ingersoll Oleg Kalnichevski This is the tally for the PPMC vote: +1 Torsten Scherler +1 Richard Frovarp +1 Bertil Chapuis The Droids status page has apparently not been kept up to date, since there are numerous authors listed at... http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fincubator%2Fdroids ... and both Richard Frovarp and Bertil Chapuis seem to have commit rights. Can you please confirm that the three +1 votes all belong to people who are official members of the Droids PPMC? Yes, the page needs to be updated. Ross has provided us with a link to the page on how to update that information. I personally haven't had time to do it. I think I'm on the PPMC, but for the Incubator, I'm not quite sure the distinction between a PPMC member and a committer. Then there's the IMPC vote, which looks like it comes from Thorsten Scherler. According to this... http://people.apache.org/committers-by-project.html#incubator-pmc ... Thorsten is not on the IPMC right now, though as an ASF Member he can simply request to join. Once that happens, you'll have 1 IPMC vote. But he is. Several months ago the board acked his request, but it would appear that the IPCM membership roster hasn't been updated. Indeed. The request was sent to the board on Dec 4th 2010, and it was acked by Bertrand Delecretaz the same day. Committee-info.txt and the LDAP group need to be updated. However, none of the Droids Mentors appear to have participated in the vote. I know one of them is camping and one took a new job recently, but still, it's troubling. Ross participated in a previous vote that didn't pass as we found things we need to clean up. It would seem he didn't have the time to participate this time. In principle, I'd like to freelance and contribute some oversight towards your release by performing a surface review and voting. I can check license headers, sigs and sums, etc, and help with an audit of LICENSE and NOTICE, especially if we can work together to produce an authoritative list of the project's dependencies. Unfortunately, my Java expertise is almost all theoretical, so code review will be limited to fumbling around until I figure out how to run the test suite and verify that it passes. I can put together a list. Maven should give it to me easily and I can post. I've gone through it quite carefully and everything I can see indicates that we are good. I've been doing some of this as PMC Chair for Apache Lenya, so I do have some experience with it. Further help and guidance of course is always welcome. However, I won't personally feel comfortable contributing a +1 without at least one of your Mentors signing off, particularly for a first release which endorses the IP clearance process. Fair enough. I've only been on the IPMC a few weeks. Can any of our more experienced hands offer recommendations about the best way to proceed? Thanks once again. - 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: Bluesky status and plans (was: Monthly reports missing)
On Wed, 15 Jun 2011 00:34 +0200, Bernd Fondermann bernd.fonderm...@googlemail.com wrote: On Tue, Jun 14, 2011 at 20:00, Donald Whytock dwhyt...@gmail.com wrote: What happens to a dormant podling? Are its files still accessible, and does its licensing still apply? I'd guess that the files remain accessible. However... Please use unreleased code, especially from the Incubator, with extreme care. Nobody, especially not the ASF, will grant for it. Specifically, it is during the process of releasing that an ASF project reviews the licenses included within a codebase. Taking code direct from ASF subversion (and more particularly unreleased code), the ASF will give no guarantees over licenses used. It would be legitimate to have incompatibly licensed code in SVN, so long as it is removed before the product is released. So yes, the code will be there, but no, the ASF will not be making any statements about the licensing credentials of that code. Do with it as you wish. Upayavira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Droids 0.1-incubating RC2
On Tue, Jun 14, 2011 at 01:39:20PM -0500, Richard Frovarp wrote: Looks like this is the inaugural ASF release for Droids, right? Thank you for looking at this. Yes, it will be. w00t! Yes, the page needs to be updated. Ross has provided us with a link to the page on how to update that information. I personally haven't had time to do it. I think I'm on the PPMC, but for the Incubator, I'm not quite sure the distinction between a PPMC member and a committer. The roles are just as distinct as they are between a Committer and a PMC member for a top-level project, and there are separate voting procedures. Some projects add both roles at once: http://incubator.apache.org/guides/ppmc.html#Voting+in+a+new+committer http://incubator.apache.org/guides/ppmc.html#Voting+in+a+new+PPMC+member For projects which wish to have all committers also be PPMC members, the Voting in a new PPMC member guide below should then be followed, noting that if desired it is possible to run a joint committership and PPMC vote, providing that the guidance for both is followed. There should be archived VOTE threads on the droids-private list, which were cc'd to private@incubator.a.o. Hopefully they were for PPMC membership. If not, there will be some cleanup work to do. ... Thorsten is not on the IPMC right now, though as an ASF Member he can simply request to join. Once that happens, you'll have 1 IPMC vote. But he is. Several months ago the board acked his request, but it would appear that the IPCM membership roster hasn't been updated. OK, great! That's resolved. Ross participated in a previous vote that didn't pass as we found things we need to clean up. It would seem he didn't have the time to participate this time. OK, that's reassuring. :) (Looks like OOo is already starting to impact our volunteer resources.) FYI, at this point I still plan to gate my vote on a +1 vote from a Droids Mentor. IMO, it would be less than ideal to have an inaugural release approved by one interested party (Thorsten) augmented by freelancers, even if one or more Mentors has expressed some measure of support in the past. In principle, I'd like to freelance and contribute some oversight towards your release by performing a surface review and voting. I can check license headers, sigs and sums, etc, and help with an audit of LICENSE and NOTICE, especially if we can work together to produce an authoritative list of the project's dependencies. Unfortunately, my Java expertise is almost all theoretical, so code review will be limited to fumbling around until I figure out how to run the test suite and verify that it passes. I can put together a list. Maven should give it to me easily and I can post. That would be most helpful. I intend to rely on this list as authoritative, as assessing a Java code base for dependencies is outside my area of expertise. I've gone through it quite carefully and everything I can see indicates that we are good. I've been doing some of this as PMC Chair for Apache Lenya, so I do have some experience with it. Excellent. Was your work documented anywhere? Ideally, there would be a JIRA issue I can read over explaining why each dependency with a non-category-A license is OK. http://www.apache.org/legal/resolved.html Further help and guidance of course is always welcome. You are gracious. I'll defer to others on guidance; I see my role as more that of a QC engineer. And to start off my QC, I'll note that there are some oddities in the top level directory of the archive. Here's the file list: DEPENDENCIES LICENSE LICENSE.txt NOTICE NOTICE.txt README.TXT droids-core droids-norobots droids-solr droids-spring droids-tika droids-wicket pom.xml The LICENSE and LICENSE.txt files are essentially duplicates of each other, having only whitespace differences. However, the NOTICE and NOTICE.txt files are quite distinct (diff below my sig). I think this is a blocker. I'm not sure what the DEPENDENCIES file is supposed to tell us, but it contains minimal information. Presumably it's some Maven thing I just don't grok. Lastly, I think it's worth commenting on the contents of README.TXT, which starts off like so: A p a c h eD r o i d s -- by Thorsten Scherler thorsten at apache.org That credit is obviously inaccurate and seems quite unusual for an Apache project. I know that other projects have gone out of their way to delete all @author tags. Perhaps Droids might consider doing likewise. I also intend to run a RAT report, and to pore over LICENSE and NOTICE more thoroughly, but I'm out of time for today and wanted to get you this feedback sooner rather than later. Best, Marvin Humphrey marvin@smokey:~/Desktop/droids/droids-0.1-incubating $ diff -u NOTICE NOTICE.txt --- NOTICE 2011-05-25
Re: [PROPOSAL] Bigtop for the Apache Incubator
Cool project. I'd also like to join as a committer so that I can contribute Hama package and continuous improvements to the community. May I join in? On Wed, Jun 15, 2011 at 3:48 AM, Eli Collins e...@cloudera.com wrote: On Tue, Jun 14, 2011 at 11:43 AM, Konstantin Boudnik c...@apache.org wrote: On 14/06/11 05:26, Tom White wrote: Hi, I would like to propose Bigtop to be an Apache Incubator project. Bigtop is a project for the development of packaging and tests of the Hadoop ecosystem. The goal is to do testing at various levels (packaging, platform, runtime, upgrade, etc...) developed by a community with a focus on the system as a whole, rather than individual projects. Here's a link to the proposal on the wiki http://wiki.apache.org/incubator/BigtopProposal I've also included the initial contents below. Cheers, Tom I've added my name to the committer list, I won't be working on this in much/any of work time, and am fairly overcommitted, so don't expect that much. I can contribute some of my experience in VM setup/teardown for testing RPM installations, and how to do functional testing of dynamically created Hadoop clusters. I am going to add my name to the list of the committers too. Considering my other commitments I might not be able to work much on this project, but I guess the fact that I have wrote like 50% of the underlying system framework might count for something. Welcome aboard Cos! Glad to have you on. Cos has made a ton of contributions to the test frameworks in Bigtop. Looking forward to your contributions! Thanks, Eli - 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
