Per this thread [1] should we have a single set of committers for the
entire Hadoop project, ie all subprojects?
If the vote passes, current and future committers will gain commit
rights in all current (Common, HDFS, MapReduce, YARN) and future
Hadoop subprojects. The specific change to the bylaws
+1 (binding).
On Thu, Aug 23, 2012 at 9:20 PM, Eli Collins wrote:
> Per this thread [1] should we have a single set of committers for the
> entire Hadoop project, ie all subprojects?
>
> If the vote passes, current and future committers will gain commit
> rights in all current (Common, HDFS, Map
+1
Doug
On Fri, Aug 24, 2012 at 10:55 AM, Jakob Homan wrote:
> +1 (binding).
>
> On Thu, Aug 23, 2012 at 9:20 PM, Eli Collins wrote:
>
>> Per this thread [1] should we have a single set of committers for the
>> entire Hadoop project, ie all subprojects?
>>
>> If the vote passes, current and fut
On Thu, Aug 23, 2012 at 9:20 PM, Eli Collins wrote:
> Per this thread [1] should we have a single set of committers for the
> entire Hadoop project, ie all subprojects?
>
> If the vote passes, current and future committers will gain commit
> rights in all current (Common, HDFS, MapReduce, YARN) an
+1 -C
On Thu, Aug 23, 2012 at 9:20 PM, Eli Collins wrote:
> Per this thread [1] should we have a single set of committers for the
> entire Hadoop project, ie all subprojects?
>
> If the vote passes, current and future committers will gain commit
> rights in all current (Common, HDFS, MapReduce, Y
+1 (non binding)
On Sat, Aug 25, 2012 at 6:33 AM, Chris Douglas wrote:
> +1 -C
>
> On Thu, Aug 23, 2012 at 9:20 PM, Eli Collins wrote:
>> Per this thread [1] should we have a single set of committers for the
>> entire Hadoop project, ie all subprojects?
>>
>> If the vote passes, current and futu
+1
On Fri, Aug 24, 2012 at 7:25 PM, Harsh J wrote:
> +1 (non binding)
>
> On Sat, Aug 25, 2012 at 6:33 AM, Chris Douglas wrote:
>> +1 -C
>>
>> On Thu, Aug 23, 2012 at 9:20 PM, Eli Collins wrote:
>>> Per this thread [1] should we have a single set of committers for the
>>> entire Hadoop project,
+1
+1.
Tom Graves
On 8/23/12 11:20 PM, "Eli Collins" wrote:
> Per this thread [1] should we have a single set of committers for the
> entire Hadoop project, ie all subprojects?
>
> If the vote passes, current and future committers will gain commit
> rights in all current (Common, HDFS, MapReduce
+1
Makes sense.
My rational is that since "Any committer may serve as the manager of a release"
http://www.apache.org/dev/release-publishing.html#release_manager
then any committer needs access to the whole tree.
Thanks,
--Konstantin
On Thu, Aug 23, 2012 at 9:20 PM, Eli Collins wrote:
> Per thi
,
Uma
From: Eli Collins [e...@cloudera.com]
Sent: Saturday, August 25, 2012 4:23 AM
To: general@hadoop.apache.org
Subject: Re: [VOTE] Maintain a single committer list for the Hadoop project
On Thu, Aug 23, 2012 at 9:20 PM, Eli Collins wrote:
> Per t
+1
Tom
On Fri, Aug 24, 2012 at 5:20 AM, Eli Collins wrote:
> Per this thread [1] should we have a single set of committers for the
> entire Hadoop project, ie all subprojects?
>
> If the vote passes, current and future committers will gain commit
> rights in all current (Common, HDFS, MapReduce,
I feel this proposal is taking us in the wrong direction.
Apache Board has encouraged us to move to TLPs. We did follow through partially
with Pig, Hive, HBase. Chris M, in the other thread, has made good arguments,
drawing from the larger apache experience, on why the remaining hadoop sub
pro
It has been clear for a long time that HDFS & MapReduce were largely
disjoint developer communities. We set up the sub-projects to recognize
that fact and allow each community to focus on its own issues. I think
merging the committer lists is moving the project the wrong direction.
-1 to merging t
On Aug 23, 2012, at 9:20 PM, Eli Collins wrote:
> Per this thread [1] should we have a single set of committers for the
> entire Hadoop project, ie all subprojects?
I feel like we need to have a wider discussion here.
This discussion started when a diverse set of folks working on YARN for a year
On Tue, Aug 28, 2012 at 4:12 PM, Arun C Murthy wrote:
> On Aug 23, 2012, at 9:20 PM, Eli Collins wrote:
>
>> Per this thread [1] should we have a single set of committers for the
>> entire Hadoop project, ie all subprojects?
>
> I feel like we need to have a wider discussion here.
>
> This discuss
Hi Eli,
On Aug 28, 2012, at 4:57 PM, Eli Collins wrote:
>> [...snip...]
>>
>> Thoughts?
>
> I'd start a separate discussion thread or vote about moving some or
> all of the sub-projects to TLPs. IMO we should resolve this issue
> independently - there's no reason to block this decision on a pos
BTW, one amendment to my proposed process below:
On Aug 28, 2012, at 6:37 PM, Mattmann, Chris A (388J) wrote:
> [...snip...]
>
> 4. paste resolution from #0 to board@.
An alternative to #4 is to go through the Incubator, which might be good to get
other
Foundation members on the PMC that are
Sorry just being complete here:
On Aug 28, 2012, at 6:37 PM, Mattmann, Chris A (388J) wrote:
>
>
>> For example if YARN spins out as a
>> TLP this issue still remains for the rest of the sub-projects, so I
>> don't want to stall progress on this on the larger more complex
>> discussion of whethe
On Tue, Aug 28, 2012 at 6:37 PM, Mattmann, Chris A (388J)
wrote:
> Hi Eli,
>
> On Aug 28, 2012, at 4:57 PM, Eli Collins wrote:
>
>>> [...snip...]
>>>
>>> Thoughts?
>>
>> I'd start a separate discussion thread or vote about moving some or
>> all of the sub-projects to TLPs. IMO we should resolve th
Hey Eli,
Correct, VOTE thread isn't the right thread for discussing this.
I'll handle future discussion of these issues in 3 separate DISCUSS
threads for each TLP.
Thanks!
Cheers,
Chris
On Aug 28, 2012, at 7:09 PM, Eli Collins wrote:
> On Tue, Aug 28, 2012 at 6:37 PM, Mattmann, Chris A (388J)
-1
Given the other discussion related to TLP and the proposal here is
essentially going in the opposite direction.
On Tue, Aug 28, 2012 at 7:09 PM, Eli Collins wrote:
> On Tue, Aug 28, 2012 at 6:37 PM, Mattmann, Chris A (388J)
> wrote:
> > Hi Eli,
> >
> > On Aug 28, 2012, at 4:57 PM, Eli Colli
+1
--
Aaron T. Myers
Software Engineer, Cloudera
On Thu, Aug 23, 2012 at 9:20 PM, Eli Collins wrote:
> Per this thread [1] should we have a single set of committers for the
> entire Hadoop project, ie all subprojects?
>
> If the vote passes, current and future committers will gain commit
> ri
Given that a discussion of a TLP proposal is happening in parallel, and that
there seems to be a positive response there, is this vote still happening?
At any rate, here's my opinion: The earlier project split, however painful it
was, has done a lot of good, both in terms of project management
On Thu, Aug 30, 2012 at 9:20 AM, Vinod Kumar Vavilapalli
wrote:
>
> Given that a discussion of a TLP proposal is happening in parallel, and that
> there seems to be a positive response there, is this vote still happening?
>
Yes, related discussions don't stop votes. Plenty of people don't
want
With 12 +1s (9 binding) and 3 -1s (binding) the vote passes.
I'll update the bylaws to reflect the merged committer lists
(http://s.apache.org/Owx).
Thanks,
Eli
On Thu, Aug 23, 2012 at 9:20 PM, Eli Collins wrote:
> Per this thread [1] should we have a single set of committers for the
> entire H
I've updated asf-authorization-template to reflect this:
$ svn log -r 830654
r830654 | acmurthy | 2012-08-31 09:02:23 -0700 (Fri, 31 Aug 2012) | 1 line
Merge hadoop-hdfs & hadoop-mapreduce lists per http://s.apache.org/pn
--
On Aug 30, 2012, at 9:30 PM, Eli Collins wrote:
> With 12 +1s (9 binding) and 3 -1s (binding) the vote passes.
>
> I'll update the bylaws to reflect the merged committer lists
> (http://s.apache.org/Owx).
>
Also, could you please update the site to reflect this?
thanks,
Arun
> Thanks,
> Eli
On Fri, Aug 31, 2012 at 9:04 AM, Arun C Murthy wrote:
> On Aug 30, 2012, at 9:30 PM, Eli Collins wrote:
>
>> With 12 +1s (9 binding) and 3 -1s (binding) the vote passes.
>>
>> I'll update the bylaws to reflect the merged committer lists
>> (http://s.apache.org/Owx).
>>
>
> Also, could you please u
29 matches
Mail list logo
