On Wed, May 12, 2010 at 12:16 PM, Craig L Russell
<craig.russ...@oracle.com> wrote:
> For me, not so much.
>
> A TLP owns a code base and is responsible for it. While I appreciate the
> sentiment, I don't think it's wise to require that different communities
> with nothing else in common except "cloud" in their name have to be managed
> by the same PMC.
>
> How is "cloud" different from "xml" or "java" or "web" or "database"? We
> have many communities in Apache that share buzzwords yet have different
> approaches.
Right, I think the 3 projects we are talking about can be broken down
into simple lines:
- deltacloud: portable cloud library (with a http interface)
- libcloud: portable cloud library (with a python interface)
- whirr: scripts & tools built on top of the previous two (or other tools)
But my point is not so much about the buzz-wordyness of 'cloud', it
was more about overlapping:
- committers
- community concerns:
- cloud portability
- access to APIs and documentation
To me, the set of the community interested in these things will be
similar, and one TLP to wrap them up in that sense makes sense to me,
we have dozens of examples of TLPs with multipe products, and not all
of them are *bad* TLPs.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
