On Jan 31, 2011, at 10:19 PM, Konstantin Boudnik wrote:
On Sun, Jan 30, 2011 at 23:19, Owen O'Malley omal...@apache.org
wrote:
On Jan 30, 2011, at 7:42 PM, Nigel Daley wrote:
Now that http://apache-extras.org is launched
-1.
Move it away from TRUNK so it doesn't affect builds is a much better
(and simpler) solution. If someone wants to revive it, he can within
the bounds of Apache Hadoop and will become a part of the Hadoop
community, which would be good.
If you'd move it off-site, if the code ever gets new
For contrib components that we elect not to remove, I suggest that we
remove them from the main build, so that failures in a contrib
component don't hinder the main build and release. This is what
ZooKeeper does, for example.
Tom
On Fri, Feb 11, 2011 at 2:03 AM, Bernd Fondermann
Tom,
How do these contrib components get released then? If the intent of having
the code is to eventually produce release artifacts that people can use,
then allowing them to further degrade in releasability seems antithetical to
the point of keeping the source around. I think users who download
On Fri, Feb 11, 2011 at 1:03 PM, Aaron Kimball akimbal...@gmail.com wrote:
Tom,
How do these contrib components get released then?
In source form - this is what ZooKeeper does.
If the intent of having
the code is to eventually produce release artifacts that people can use,
then allowing
+1. And only include them as source in releases.
Nige
On Feb 11, 2011, at 10:12 AM, Tom White wrote:
For contrib components that we elect not to remove, I suggest that we
remove them from the main build, so that failures in a contrib
component don't hinder the main build and release. This
After considering the feedback, I will move forward with calling a separate
vote for each contrib (or small groups of contribs). The vote will ask the PMC
to abandon the given contrib or move it to core. For those we agree to
abandon, I will setup an Attic wiki that will point to the last SVN
Hi Chris,
You use the word 'project' over and over. These contrib modules are not Apache
projects. They are source code directories within the various Hadoop
subprojects. Reading thru attic.apache.org, I don't see how it directly
relates. Surely not every 'svn remove dir' should be replaced
+1 for the reasons already cited: independent release cycles,
testing/build problems, lack of maintenance, etc. I think we should
strongly discourage new contrib components in favour of Apache Extras
or github, remove inactive contrib components, and also allow
maintainers to move components out
On Tue, Feb 1, 2011 at 1:02 AM, Allen Wittenauer
awittena...@linkedin.comwrote:
So is the expectation that users would have to follow bread crumbs
to the github dumping ground, then try to figure out which repo is the
'better' choice for their usage? Using LZO as an example, it
On Tue, Feb 1, 2011 at 9:37 AM, Tom White t...@cloudera.com wrote:
HBase moved all its contrib components out of the main tree a few
months back - can anyone comment how that worked out?
Sure. For each contrib:
ec2: no longer exists, and now has been integrated into Whirr and much
improved.
I agree with Owen. If we move code out of the contrib project, then it is
more likely to create confusion among users, especially when multiple
versions of the code base float around.
But I agree that we should purge contrib code that is not being used or not
being actively developed.
thanks,
On 31/01/11 05:24, Konstantin Boudnik wrote:
Shall we not dictate a location of contrib projects once they are
moved of Hadoop? If ppl feel like they are better be served by GitHub
perhaps they should have an option to get hosted there?
-I see discussions about Git at the ASF infra mailing
On 31/01/11 03:42, Nigel Daley wrote:
Folks,
Now that http://apache-extras.org is launched
(https://blogs.apache.org/foundation/entry/the_apache_software_foundation_launches)
I'd like to start a discussion on moving contrib components out of common,
mapreduce, and hdfs.
These contrib
On Sun, Jan 30, 2011 at 23:19, Owen O'Malley omal...@apache.org wrote:
On Jan 30, 2011, at 7:42 PM, Nigel Daley wrote:
Now that http://apache-extras.org is launched
(https://blogs.apache.org/foundation/entry/the_apache_software_foundation_launches)
I'd like to start a discussion on moving
Owen,
I am surprised to not see jute (aka hadoop recordio) on this list.
- milind
On Jan 30, 2011, at 11:19 PM, Owen O'Malley wrote:
On Jan 30, 2011, at 7:42 PM, Nigel Daley wrote:
Now that http://apache-extras.org is launched
On Sun, Jan 30, 2011 at 11:19 PM, Owen O'Malley omal...@apache.org wrote:
Also note that pushing code out of Hadoop has a high cost. There are at
least 3 forks of the hadoop-gpl-compression code. That creates a lot of
confusion for the users. A lot of users never go to the work to figure out
Folks,
Now that http://apache-extras.org is launched
(https://blogs.apache.org/foundation/entry/the_apache_software_foundation_launches)
I'd like to start a discussion on moving contrib components out of common,
mapreduce, and hdfs.
These contrib components complicate the builds, cause test
Huge +1.
Sqoop has continued development at https://github.com/cloudera/sqoop
MRUnit is at https://github.com/esammer/mrunit
I think the former can be easily removed. The latter, per my previous email,
I think could be removed as well.
On Sun, Jan 30, 2011 at 10:42 PM, Nigel Daley
While this seems to be a very good and long awaited advancement (btw
thanks to Eric Sammer for making a first project on the move out of
MRUnit!) I have a concern about lack of Git support on
http://apache-extras.org. I am sure that hosting decision was deeply
considered by Apache board (or the
+1 - A really good idea to clean up the builds and ownership issues.
I think it is good to have a default location for related projects and
apache-extras.org does seem like a logical place.
We should also probably add a prominent wiki section to support use of
apache-extras.org and to provide
+1
Agree w Eric's comments around defaults and documenting them.
How about setting a date where the projects are created on apache
extras and removed from contrib unless someone volunteers to maintain
them? I agree apache extras should be the default unless the person
volunteering to maintain
On Jan 30, 2011, at 7:42 PM, Nigel Daley wrote:
Now that http://apache-extras.org is launched (https://blogs.apache.org/foundation/entry/the_apache_software_foundation_launches
) I'd like to start a discussion on moving contrib components out of
common, mapreduce, and hdfs.
The PMC can't
23 matches
Mail list logo
