Re: smashing repos

[Adrian Cole]

ps had a good chat with henning on irc about responsibility and modularity.

Going idea is to setup a main jclouds repo in apache's git namespace and also ones per provider, api, driver.  The latter repos would be "lazy-created" by folks who care enough to set it up and have support by one or more committers.

I'll do my best to save further discussion for the incubator mailing lists.. to that end, please help Becca however you can wrt proposal submission!

https://groups.google.com/forum/?fromgroups=#!topic/jclouds-dev/mjRiig6Msqs

-A

On Saturday, April 6, 2013 1:46:57 PM UTC-7, Roman Shaposhnik wrote:

On Fri, Apr 5, 2013 at 3:38 PM, Adrian Cole <adrian...@gmail.com> wrote:
> Hi, team.
>
> It should be relatively unsurprising that the move to ASF incubation will
> result in code transitions :)  On irc today, I had a discussion I'll call
> "pain tolerance" which could be roughly summarized as "few folks are willing
> to work on providers they don't use, and even fewer for providers no-one
> uses".  The jist is that now that jclouds requires no central registration
> of providers, unpopular or incomplete provider code need not weigh down our
> committers work load, and certainly needn't distract us when we transition
> into ASF.  We can't rely on my high tolerance for pain to be the implicit
> champion for unpopular, abandoned, or unfinished code.  This is not the
> apache way, nor is it fair.   This doesn't mean I won't volunteer to
> champion a ton of stuff, just don't expect me to be the fallback for all
> code nobody else wants or wants to touch.  Code in that category should be
> scrapped vs dumped into apache.

This will jive very well with ASF's 'community over code motto'. Kudos to you
guys for proactively tackling the challenge

Thanks,
Roman.