incubator-libcloud mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Hogstrom <>
Subject Re: [libcloud] Project needs for TLP.
Date Wed, 08 Dec 2010 19:22:18 GMT
Hash: SHA1

Since the measure of a podling's readiness to graduate is the community and the PPMCs ability
to deal with this kind of situation as an IPMC member I'd like to see this resolved and then
the vote be taken again.  I don't particularly care if Java is accepted or not, I'm more interested
to see if the community handle's itself in a respectful manner.  So far, so good.

On Dec 7, 2010, at 12:04 PM, Jed Smith wrote:

> All valid points.
> Before we graduate, I'd like to see all of this taken care of. I'd almost
> reverse my vote to -1 in the graduation vote based on some of these
> revelations, but that is done. I do not, however, feel that we are ready to
> graduate without more participation and project direction from consensus
> instead of a single person. (That isn't negative to Paul in the slightest,
> as he's gotten us this far: I think we need feet to start running with,
> though.)
> I think this should be our first course of action, vote in the community for
>> yearly rotating positions for things like overall project management, code
>> management, documentation management, etc. This would probably clear up most
>> of Ant's concerns in its self. (also defining set roles for the project that
>> follow the Apache way would be good, ex:
>> ).
> I don't know if we have enough of a committer base to perhaps to go Ant's
> level just yet, but I'm all for a bit more structure in decision making and
> consensus. We need documentation on what our goals are, how Paul does what
> he does, and a light structure for decision-making and voting.
>> Outside of project participation, there is one other topic that I think
>> need further discussion. This is the Java portion of libcloud which is
>> clearly not ready for TLP status. I would move for this to be removed from
>> the libcloud project for its own project.
> I raced you with a message on this very point. I fully support it for the
> reasons given there.
>> I would now move that for future development and needs for graduation, we
>> should discuss redefining libcloud as a python library only
> I agree, but only *for now*. I would like to see Paul's vision (which I
> somewhat share) become more than a wispy dream before 1.0. This is part of
> the roadmap and long-term vision that I'd like to see put in place.
> In short: let's organize before we even think about 0.5.0 and I believe that
> will definitely make us more ready for graduation.
> -- 
> Jed Smith

Version: GnuPG/MacGPG2 v2.0.14 (Darwin)


View raw message