date:20110617

Re: Request ASF assistance to reform XALAN PMC

2011-06-17 Thread Bertrand Delacretaz

Hi,

On Thu, Jun 16, 2011 at 12:27 AM, Steven J Hathaway
steven.j.hatha...@state.or.us wrote:
 ...Bertrand Delacretaz has indicated that XALAN_C is a candidate for
 moving to the attic.

 I would like to see XALAN moved to the Incubator instead of
 the attic.  I will help reinstate the XALAN PMC but need some
 ASF assistance

We are actively looking for a solution, and might be able to reboot
Xalan without having to go through the incubator, see
http://s.apache.org/reboot_xalan - I'm hoping to have more news early
next week.

-Bertrand

-
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

2011-06-17 Thread Konstantin Boudnik

Tom,

Looking through the proposal with a bit more attention I've noticed
that initial source code linked in here
https://github.com/cloudera/bigtop
refers to iTest framework as the foundation of BigTop testing.

However, iTest repository at github.com/cloudera/iTest isn't
available? Will it be available along with the rest of the code or it
isn't opened to the public? What's the deal there? I believe it'd be
beneficial for the community to be able to see the source code of the
testing engine. Please correct me if I'm wrong though ;)
--
  Thanks,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622

Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.



On Tue, Jun 14, 2011 at 11:43, 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.

 Cos

 -
 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] Bigtop for the Apache Incubator

2011-06-17 Thread Alan Gates


Tom,

I'd like to join as a committer and mentor as well.

Alan.

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 minimal risk of
this work becoming non-strategic and the contributors are confident
that a larger

Re: process for going Dormant/Retired

2011-06-17 Thread Henri Yandell

On Wed, Jun 15, 2011 at 7:11 PM, David Crossley cross...@apache.org wrote:
 David Crossley wrote:
 Christian Grobmeier wrote:
 
  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.

 I suggest search the mail lists for past similar situations.

 We did have a recent discussion too about the process.
 IIRC, the Leo Simons was very helpful.

 Clutch provides some links:
 http://incubator.apache.org/clutch.html#h-Retire
 However there is more involved. When we find/create/enhance
 some docs, we can add to those pointers.

 Ah yes, one of those links goes to INCUBATOR-100

 Giving this discussion a new name and linking from JIRA.

Also, is there a retired-podlings url that the Attic can link to?

Hen

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

Re: process for going Dormant/Retired

2011-06-17 Thread Henri Yandell

On Fri, Jun 17, 2011 at 2:04 AM, Henri Yandell flame...@gmail.com wrote:
 On Wed, Jun 15, 2011 at 7:11 PM, David Crossley cross...@apache.org wrote:
 David Crossley wrote:
 Christian Grobmeier wrote:
 
  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.

 I suggest search the mail lists for past similar situations.

 We did have a recent discussion too about the process.
 IIRC, the Leo Simons was very helpful.

 Clutch provides some links:
 http://incubator.apache.org/clutch.html#h-Retire
 However there is more involved. When we find/create/enhance
 some docs, we can add to those pointers.

 Ah yes, one of those links goes to INCUBATOR-100

 Giving this discussion a new name and linking from JIRA.

 Also, is there a retired-podlings url that the Attic can link to?

Some additional thoughts after reviewing the Bluesky thread. Generally
the Attic process should be followed for retired podlings; things like
making svn, JIRA etc read-only, updating the podling website with a
bold notice that the podling is retired and making the announcement.

Also a FAQ item from the bluesky thread:

 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.

We really want to be strong on that 'not vouched for' point. I think
we also should think about the question of whether we keep source that
wasn't able to check off its IP checklist items. We've got strong
podlings (JSPWiki springs to mind) where these haven't been checked
off yet - I think the Incubator PMC should push very strongly on
podlings to sort out their copyright early instead of letting it
linger. Perhaps even put in place some timelines 'sort it out in 3
months' etc.

Hen

-
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)

2011-06-17 Thread Henri Yandell

On Tue, Jun 14, 2011 at 4:16 PM, Upayavira u...@odoko.co.uk wrote:


 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.

Agreed - the Verify distribution rights section of the incubation process.

However, Bluesky haven't managed to check off the two copyright items.
I think we should remove the source in svn rather than continuing to
assume that we have a license to the code.

Hen

-
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

2011-06-17 Thread Konstantin Boudnik

Oh, I see. Looks like a dangling links indeed... Thanks for pointing out.

On Thu, Jun 16, 2011 at 05:32PM, Roman Shaposhnik wrote:
 Hi Cos,
 
 On Thu, Jun 16, 2011 at 5:21 PM, Konstantin Boudnik c...@apache.org wrote:
  However, iTest repository at github.com/cloudera/iTest isn't
  available? Will it be available along with the rest of the code or it
  isn't opened to the public? A error in the document? What's the deal there? 
  I
  believe it'd be beneficial for the community to be able to see the source 
  code
  of the testing engine. Please correct me if I'm wrong though ;)
 
 iTest is now part of bigtop and resides under test/src/itest-common:
 https://github.com/cloudera/bigtop/tree/master/test/src/itest-common
 
 So in that sense it is there, but not as a separate project. The original
 documentation for iTest is available under this link:
http://cloudera.github.com/bigtop/iTest/
 
 And it looks like there are could be a couple of dangling links there still
 pointing to where iTest used to be on GitHub as a separate repository.
 
 Thanks,
 Roman.
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

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

Re: process for going Dormant/Retired

2011-06-17 Thread Donald Whytock

Should there be a way to comment on the dormant podling?  Perhaps
analysis on what (over and above community, the core problem) would be
required to make the project viable, in case anyone who has the time
and interest and expertise (i.e. someone other than, say, me) wanted
to try to revive it?

Don

On Fri, Jun 17, 2011 at 5:09 AM, Henri Yandell flame...@gmail.com wrote:
 On Fri, Jun 17, 2011 at 2:04 AM, Henri Yandell flame...@gmail.com wrote:
 On Wed, Jun 15, 2011 at 7:11 PM, David Crossley cross...@apache.org wrote:
 David Crossley wrote:
 Christian Grobmeier wrote:
 
  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.

 I suggest search the mail lists for past similar situations.

 We did have a recent discussion too about the process.
 IIRC, the Leo Simons was very helpful.

 Clutch provides some links:
 http://incubator.apache.org/clutch.html#h-Retire
 However there is more involved. When we find/create/enhance
 some docs, we can add to those pointers.

 Ah yes, one of those links goes to INCUBATOR-100

 Giving this discussion a new name and linking from JIRA.

 Also, is there a retired-podlings url that the Attic can link to?

 Some additional thoughts after reviewing the Bluesky thread. Generally
 the Attic process should be followed for retired podlings; things like
 making svn, JIRA etc read-only, updating the podling website with a
 bold notice that the podling is retired and making the announcement.

 Also a FAQ item from the bluesky thread:

  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.

 We really want to be strong on that 'not vouched for' point. I think
 we also should think about the question of whether we keep source that
 wasn't able to check off its IP checklist items. We've got strong
 podlings (JSPWiki springs to mind) where these haven't been checked
 off yet - I think the Incubator PMC should push very strongly on
 podlings to sort out their copyright early instead of letting it
 linger. Perhaps even put in place some timelines 'sort it out in 3
 months' etc.

 Hen

 -
 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

[VOTE] Accept Bigtop for incubation

2011-06-17 Thread Tom White

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
Hadoop or related Apache projects (Alejandro Abdelnur, Konstantin
Boudnik, Eli Collins, Alan Gates, Patrick Hunt, Steve Loughran, Owen
O'Malley, John Sichi, Michael Stack, Tom White)

Re: [VOTE] Accept Bigtop for incubation

2011-06-17 Thread Mattmann, Chris A (388J)

+1 from me (binding).

Good work guys.

Cheers,
Chris

On Jun 17, 2011, at 10:15 AM, Tom White 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 ==

== 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.
}}}

The intent of this project is to build a community where the projects
are brought together, packaged, and tested for interoperability.

== Initial Goals ==

Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.

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 ==

== Core Developers ==

Many of the committers

Re: [VOTE] Accept Bigtop for incubation

2011-06-17 Thread Leif Hedstrom


On 06/17/2011 11:15 AM, Tom White wrote:

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



+1 (binding).

Cheers,

-- leif

-
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

2011-06-17 Thread Ashish

+1 (non-binding)

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 ==

== 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.
}}}

The intent of this project is to build a community where the projects
are brought together, packaged, and tested for interoperability.

== Initial Goals ==

Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.

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 ==

== Core Developers ==

Many of the committers to the Bigtop project have contributed

Re: [VOTE] Accept Bigtop for incubation

2011-06-17 Thread Patrick Hunt

+1 (binding)

On Fri, Jun 17, 2011 at 10:31 AM, Ashish paliwalash...@gmail.com wrote:
+1 (non-binding)

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 ==

== 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.
}}}

The intent of this project is to build a community where the projects
are brought together, packaged, and tested for interoperability.

== Initial Goals ==

Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.

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 ==

== Core Developers ==

Re: [VOTE] Accept Bigtop for incubation

2011-06-17 Thread Eli Collins

+1 (non-binding)

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 ==

== 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.
}}}

The intent of this project is to build a community where the projects
are brought together, packaged, and tested for interoperability.

== Initial Goals ==

Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.

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 ==

== Core Developers ==

Many of the committers to the Bigtop project have contributed

Re: [VOTE] Accept Bigtop for incubation

2011-06-17 Thread arv...@cloudera.com

+1 (non-binding)

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 ==

== 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.
}}}

The intent of this project is to build a community where the projects
are brought together, packaged, and tested for interoperability.

== Initial Goals ==

Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.

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 ==

== Core Developers ==

Many of the committers to the Bigtop project have contributed

Re: [VOTE] Release Droids 0.1-incubating RC2

2011-06-17 Thread sebb

On 16 June 2011 17:29, Richard Frovarp rfrov...@apache.org wrote:
On 06/15/2011 08:47 PM, sebb wrote:

On 12 June 2011 04:43, Richard Frovarprfrov...@apache.org 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

Source files:
http://people.apache.org/~rfrovarp/droids/

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachedroids-011/

SVN source tag (r1127762):
https://svn.apache.org/repos/asf/incubator/droids/tags/0.1-incubating/

PGP release keys (signed using 3698A2B1):
https://svn.apache.org/repos/asf/incubator/droids/KEYS

[ ] +1
[ ] +0
[ ] -1

There must be a disclaimer saying that the project is undergoing
Incubation.
This is normally in a DISCLAIMER file, which should be in SVN, source
and binary archives.

Added.

The website should also carry a prominent disclaimer, nromally at the
start of the index page.

Will have someone work on that.

The NOTICE file must only contain required notices, and only for items
that are actually included in the release, not run-time dependencies
that are downloaded by Maven.

E.g. is JUnit included in the release? If not, remove the reference.

Do not add any extraneous text to the Notice file - e.g explanations
and headings - it should be as short as possible (but no shorter).

Done.

The project name should be shown as Apache Droids in the Notice file(s).

Fixed as well.

I think the above all need to be fixed before release.

The source archive contents agree with SVN (apart from extra files
generated by Maven).
Sigs and hashes are OK; key is in public PGP repo.
Contents of jar files look good; there are NL files in the META-INF dir.

The source and javadoc jar manifests could include the Specification
entries.

I don't know that I completely understand this. I'm not too familiar with
the manifest files, and adding specification into a search returns back the
specs on the file format.

I meant the Specification entries which are already in the binary jar
manifests, for example:

Specification-Title: Apache Droids Core
Specification-Vendor: The Apache Software Foundation
Specification-Version: 0.1-incubating

These would also be useful in the source and javadoc jar manifests.

[The Implementation entries really only apply to binary jars.]

It would be useful to include the Java source and target versions in
the binary jar manifests.

Will do.

The SVN properties don't appear to have been set on many of the source
files, which suggests that some committers have not set up their SVN
defaults correctly.
(I'll raise a JIRA for correcting the properties)

Applied / fixed. Thanks.

-
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

2011-06-17 Thread Eric Sammer

+1 (non-binding).

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 ==

== 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.
}}}

The intent of this project is to build a community where the projects
are brought together, packaged, and tested for interoperability.

== Initial Goals ==

Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.

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 ==

== Core Developers ==

Many of the committers to the Bigtop project have contributed

Re: [VOTE] Accept Bigtop for incubation

2011-06-17 Thread Zimdars, Paul A (3880-Affiliate)

+1 (non-binding)

Paul

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 ==

== 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.
}}}

The intent of this project is to build a community where the projects
are brought together, packaged, and tested for interoperability.

== Initial Goals ==

Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.

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 ==

== Core Developers ==

Many of the committers to the Bigtop

Suggestions for transferring folks from pre-existing mailing lists.

2011-06-17 Thread 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 ?

- Just add everyone from the old list to the new @incubator list?
(possible?)

- Just should we just send a message and have people subscribe to the new
list (which may lose some people in transition)?

Thanks,
Jon.

-- 
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// j...@cloudera.com

RE: Suggestions for transferring folks from pre-existing mailing lists.

2011-06-17 Thread Gavin McDonald



 -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

Re: Suggestions for transferring folks from pre-existing mailing lists.

2011-06-17 Thread David Crossley

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

-David

-
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

2011-06-17 Thread Edward J. Yoon

+1 (non-binding)

Sent from my iPhone

On 2011. 6. 18., at 오전 4:20, Zimdars, Paul A (3880-Affiliate)
paul.a.zimd...@jpl.nasa.gov wrote:

+1 (non-binding)

Paul

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 ==

== 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.
}}}

The intent of this project is to build a community where the projects
are brought together, packaged, and tested for interoperability.

== Initial Goals ==

Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.

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 ==

== Core Developers ==

Re: [VOTE] Accept Bigtop for incubation

2011-06-17 Thread Ralph Goers

+1 (binding)

Ralph

On Jun 17, 2011, at 10:15 AM, Tom White 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 ==

== 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.
}}}

The intent of this project is to build a community where the projects
are brought together, packaged, and tested for interoperability.

== Initial Goals ==

Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.

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 ==

== Core Developers ==

Many of the committers to the Bigtop project have

Re: Request ASF assistance to reform XALAN PMC

Re: [PROPOSAL] Bigtop for the Apache Incubator

Re: [PROPOSAL] Bigtop for the Apache Incubator

Re: process for going Dormant/Retired

Re: process for going Dormant/Retired

Re: Bluesky status and plans (was: Monthly reports missing)

Re: [PROPOSAL] Bigtop for the Apache Incubator

Re: process for going Dormant/Retired

[VOTE] Accept Bigtop for incubation

Re: [VOTE] Accept Bigtop for incubation

Re: [VOTE] Accept Bigtop for incubation

Re: [VOTE] Accept Bigtop for incubation

Re: [VOTE] Accept Bigtop for incubation

Re: [VOTE] Accept Bigtop for incubation

Re: [VOTE] Accept Bigtop for incubation

Re: [VOTE] Release Droids 0.1-incubating RC2

Re: [VOTE] Accept Bigtop for incubation

Re: [VOTE] Accept Bigtop for incubation

Suggestions for transferring folks from pre-existing mailing lists.

RE: Suggestions for transferring folks from pre-existing mailing lists.

Re: Suggestions for transferring folks from pre-existing mailing lists.

Re: [VOTE] Accept Bigtop for incubation

Re: [VOTE] Accept Bigtop for incubation

23 matches

Site Navigation

Mail list logo

Footer information