It has always seemed to me that graduation votes are just
recommendations from the incubator to the board. Only the board can
establish a TLP.
In this case, the vote is even less important. The HCatalog gang
proposed to merge into Hive. Hive proposes to give them a less than
warm welcome by some standards. The Hive and HCatalog communities can
cooperate to put the code in the HCatalog tree, and them the Hive
people had best plan to report to the board, promptly. And if the
board is not happy with this not-first-class-citizenship plan, the
board will communicate that to Hive and work out the next steps in the
context of Hive.

If the Hive PMC wants to ask the board in advance if their scheme is
OK, I suppose they can.

All in all, there's not much for the IPMC to say here. There's no
board resolution needed for a podling to contribute itself into an
existing TLP. So long as HCatalog's IP is in good shape, we don't have
much to do with this outcome.

In short, HCatalog is a podling until it isn't. The vote gives
information to the two communities and the board, and we'll wind up
the podling when and if we hear that it's in fact merged into Hive or
has become a TLP.



On Tue, Feb 12, 2013 at 8:14 PM, Alan Gates <ga...@hortonworks.com> wrote:
> So I'm not clear what the next step is here.  The 72 hours have passed, we 
> have 5 +1 votes, 2 -1 votes, and a -0.
>
> Based on this page http://www.apache.org/foundation/voting.html this appears 
> to be a procedural vote so it just requires a majority.
>
> Are we done or is it traditional to allow more time for the vote when the 
> issue is contentious?
>
> Alan.
>
>
> ---------------------------------------------------------------------
> 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

Reply via email to