Re: [VOTE] Accept Bigtop for incubation
+1 (binding)
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jun 17, 2011 at 1:15 PM, Tom White tomwh...@apache.org wrote:
As there are no active discussions on the proposal thread, I would
like to initiate a vote to accept Bigtop as an Apache Incubator
project.
The proposal is available at
http://wiki.apache.org/incubator/BigtopProposal?action=recallrev=13
I've also put a copy of the proposal at the end of this email.
The discussion thread is available at
http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3cbanlktimriyvs5g5maklqvinauz9h6s5...@mail.gmail.com%3E
Please cast your votes:
[ ] +1 Accept Bigtop for incubation
[ ] +0 Indifferent to Bigtop incubation
[ ] -1 Reject Bigtop for incubation
This vote will close 72 hours from now.
Thanks,
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, Hama
and Sqoop.
From a packaging and deployment perspective, the current
loosely-coupled nature of the project has limitations:
1. Insufficient building against trunk versions of dependent projects
(in the style of Apache Gump).
1. Insufficient testing against the trunk versions of dependent projects.
1. No consistent packaging for the Linux servers which provide the
main Hadoop datacenter platform.
1. No functional testing against multi-machine clusters as part of
the regular automated build process. This is due to a lack of a
physical or virtual Hadoop cluster for testing, and not enough test
suites designed to run against a live cluster with known datasets.
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 and Konstantin Boudnik designed and implemented
the system testing framework.
Many of the
RE: Suggestions for transferring folks from pre-existing mailing lists.
-Original Message- From: David Crossley [mailto:cross...@apache.org] Sent: Saturday, 18 June 2011 11:18 AM To: general@incubator.apache.org Subject: Re: Suggestions for transferring folks from pre-existing mailing lists. Gavin McDonald wrote: From: Jonathan Hsieh Looking for some advise on a quick question: What have folks generally done to transfer folks from an external mailing list to a new podling mailing list? - Forward mail from old list to new list @incubator.apache.org list ? No - Just add everyone from the old list to the new @incubator list? (possible?) possible but not allowed, we will not auto subscribe people from external mailing lists. - Just should we just send a message and have people subscribe to the new list (which may lose some people in transition)? Yes please. Those that don't make it across don't want to I guess (?) It would be good if someone could enhance the Guide docs as they go. Here is one place where mail lists are mentioned: http://incubator.apache.org/guides/mentor.html#request-mailing-lists Sure, I added a note to that area of the page. Gav... -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: This list is for how not why?
Hi, Are podling and podlet the same? Thanks, khirano - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Bigtop for incubation
On Fri, Jun 17, 2011 at 6:15 PM, Tom White tomwh...@apache.org wrote: Please cast your votes: [X] +1 Accept Bigtop for incubation [ ] +0 Indifferent to Bigtop incubation [ ] -1 Reject Bigtop for incubation (binding) Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: OpenOffice.org next steps
On Mon, Jun 13, 2011 at 10:44 PM, Joe Schaefer joe_schae...@yahoo.com wrote: Correct. 99% of the time the private list is used for voting in new committers/PPMC members. +1 (Some established projects elect committers on public lists but this requires high levels of trust and isn't recommended) The dev list is the all other business list for the project. +1 Communication at Apache should be as public as possible whilst respecting people and the law. Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Bigtop for incubation
+1. (binding)
Cheers,
Nige
Sent from my iPhone4
On Jun 17, 2011, at 10:15 AM, Tom White tomwh...@apache.org wrote:
As there are no active discussions on the proposal thread, I would
like to initiate a vote to accept Bigtop as an Apache Incubator
project.
The proposal is available at
http://wiki.apache.org/incubator/BigtopProposal?action=recallrev=13
I've also put a copy of the proposal at the end of this email.
The discussion thread is available at
http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3cbanlktimriyvs5g5maklqvinauz9h6s5...@mail.gmail.com%3E
Please cast your votes:
[ ] +1 Accept Bigtop for incubation
[ ] +0 Indifferent to Bigtop incubation
[ ] -1 Reject Bigtop for incubation
This vote will close 72 hours from now.
Thanks,
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, Hama
and Sqoop.
From a packaging and deployment perspective, the current
loosely-coupled nature of the project has limitations:
1. Insufficient building against trunk versions of dependent projects
(in the style of Apache Gump).
1. Insufficient testing against the trunk versions of dependent projects.
1. No consistent packaging for the Linux servers which provide the
main Hadoop datacenter platform.
1. No functional testing against multi-machine clusters as part of
the regular automated build process. This is due to a lack of a
physical or virtual Hadoop cluster for testing, and not enough test
suites designed to run against a live cluster with known datasets.
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 and Konstantin Boudnik designed and implemented
the system testing framework.
Many of
Re: Suggestions for transferring folks from pre-existing mailing lists.
Gavin, Thanks for the advice. Will do #3. Jon. On Fri, Jun 17, 2011 at 5:51 PM, Gavin McDonald ga...@16degrees.com.auwrote: -Original Message- From: Jonathan Hsieh [mailto:j...@cloudera.com] Sent: Saturday, 18 June 2011 9:12 AM To: general@incubator.apache.org Subject: Suggestions for transferring folks from pre-existing mailing lists. Looking for some advise on a quick question: What have folks generally done to transfer folks from an external mailing list to a new podling mailing list? - Forward mail from old list to new list @incubator.apache.org list ? No - Just add everyone from the old list to the new @incubator list? (possible?) possible but not allowed, we will not auto subscribe people from external mailing lists. - Just should we just send a message and have people subscribe to the new list (which may lose some people in transition)? Yes please. Those that don't make it across don't want to I guess (?) Gav... Thanks, Jon. -- // Jonathan Hsieh (shay) // Software Engineer, Cloudera // j...@cloudera.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- // Jonathan Hsieh (shay) // Software Engineer, Cloudera // j...@cloudera.com
Re: [VOTE] Accept Bigtop for incubation
+1
Tom
On Fri, Jun 17, 2011 at 10:15 AM, Tom White tomwh...@apache.org wrote:
As there are no active discussions on the proposal thread, I would
like to initiate a vote to accept Bigtop as an Apache Incubator
project.
The proposal is available at
http://wiki.apache.org/incubator/BigtopProposal?action=recallrev=13
I've also put a copy of the proposal at the end of this email.
The discussion thread is available at
http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3cbanlktimriyvs5g5maklqvinauz9h6s5...@mail.gmail.com%3E
Please cast your votes:
[ ] +1 Accept Bigtop for incubation
[ ] +0 Indifferent to Bigtop incubation
[ ] -1 Reject Bigtop for incubation
This vote will close 72 hours from now.
Thanks,
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, Hama
and Sqoop.
From a packaging and deployment perspective, the current
loosely-coupled nature of the project has limitations:
1. Insufficient building against trunk versions of dependent projects
(in the style of Apache Gump).
1. Insufficient testing against the trunk versions of dependent projects.
1. No consistent packaging for the Linux servers which provide the
main Hadoop datacenter platform.
1. No functional testing against multi-machine clusters as part of
the regular automated build process. This is due to a lack of a
physical or virtual Hadoop cluster for testing, and not enough test
suites designed to run against a live cluster with known datasets.
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 and Konstantin Boudnik designed and implemented
the system testing framework.
Many of the committers to the Bigtop project have contributed towards
Re: process for going Dormant/Retired
On 18 June 2011 02:12, David Crossley cross...@apache.org wrote: Henri Yandell wrote: Also, is there a retired-podlings url that the Attic can link to? There is a default link generated from the section title. However i just created explicit links. So after rsync it will be: http://incubator.apache.org/projects/#dormant http://incubator.apache.org/projects/#retired Probably That page is rather long, and it's not immediately obvious that there are 4 sections in it. Might I suggest adding an intro at the start, e.g. something like: This page lists all Incubator projects in the following sections: * Currently in incubation * Graduated from incubation * Dormant Projects * Retired from incubation and link these accordingly? - 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
