Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hive >> mail # user >> [DISCUSS] Proposed Changes to the Apache Hive Project Bylaws

Copy link to this message
Re: [DISCUSS] Proposed Changes to the Apache Hive Project Bylaws
Okay, I'm convinced that one-year terms for the chair are reasonable.
 Thanks for the reassurance, Edward and Thejas.

Is 24h rule is needed at all? In other projects, I've seen patches simply
> reverted by author (or someone else). It's a rare occurrence, and it should
> be possible to revert a patch if someone -1s it after commit, esp. within
> the same 24 hours when not many other changes are in.

Sergey makes a good point, but the 24h rule seems helpful in prioritizing
tasks.  We're all deadline-driven, right?

I'm the chief culprit of seeing "patch available" and ignoring it until it
has been committed.  Then if I find some minor typo or doc issue, I'm
embarrassed at posting a comment after the commit because nobody wants to
revert a patch just for documentation.

-- Lefty
On Sun, Dec 29, 2013 at 12:06 PM, Thejas Nair <[EMAIL PROTECTED]>wrote:

> On Sun, Dec 29, 2013 at 12:06 AM, Lefty Leverenz
> <[EMAIL PROTECTED]> wrote:
> > Let's discuss annual rotation of the PMC chair a bit more.  Although I
> > agree with the points made in favor, I wonder about frequent loss of
> > expertise and needing to establish new relationships.  What's the ramp-up
> > time?
> The ramp up time is not significant, as you can see from the list of
> responsibilities mentioned here -
> http://www.apache.org/dev/pmc.html#chair .
> We have enough people in PMC who have been involved with Apache
> project for long time and are familiar with apache bylaws and way of
> doing things. Also, the former PMC chairs are likely to be around to
> help as needed.
> > Could a current chair be chosen for another consecutive term?  Could two
> > chairs alternate years indefinitely?
> I would take the meaning of rotation to mean that we have a new chair
> for the next term. I think it should be OK to have same chair in
> alternative year. 2 years is a long time and it sounds reasonable
> given the size of the community ! :)
> >  Do many other projects have annual rotations?
> Yes, at least hadoop and pig project have that.  I could not find
> by-laws pages easily for other projects.
> >
> > Would it be inconvenient to change chairs in the middle of a release?
> No. The PMC Chair position does not have any special role in a release.
> > And now to trivialize my comments:  while making other changes, let's fix
> > this typo:  "Membership of the PMC can be revoked by an unanimous vote
> > ..." *(should
> > be "a unanimous ..." just like "a university" because the rule is based
> on
> > sound, not spelling)*.
> I think you should feel free to fix such a typos in this wiki without
> a vote on it ! :)
> --
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.