incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alvaro del Castillo <...@bitergia.com>
Subject Re: what goes in the core Allura repo (was Re: Presentation and Metrics work in Allura)
Date Wed, 31 Oct 2012 16:33:39 GMT
El mié, 31-10-2012 a las 17:08 +0100, Roberto Galoppini escribió:
> On Wed, Oct 31, 2012 at 4:48 PM, Cory Johns <johnsca@geek.net> wrote:
> 
> > I know that licensing was a concern and motivation for splitting things
> > out, such as for the SCM tools which we're currently working on breaking
> > out of core.
> >
> 
> As far as we talk about Bitergia Metrics tools Alvaro has been clear about
> their will to re-license them under the Apache license,

yes!

>  while it's also
> true that there are some dependencies on GPLed code (Bicho and CVSAnaly, if
> I'm not wrong, both used as a batch process crunching reports, guess Alvaro
> and Jesus can add some light on this if needed).

This tools could be run isolated and the communication between Bitergia
Metrics and the tools is using JSON files. So there are no probs with
this GPL tools.

Cheers

> 
> 
> 
> 
> >
> > Not knowing how it might work with the Apache way of doing things, it seems
> > like a Neighborhood for Allura extensions would give a lot of the benefits
> > while allowing for things to be separated for licensing concerns.  Has that
> > been considered as an option?
> >
> > On Wed, Oct 31, 2012 at 11:27 AM, Rich Bowen <rbowen@rcbowen.com> wrote:
> >
> > >
> > > On Oct 25, 2012, at 7:10 AM, Alvaro del Castillo wrote:
> > >
> > > >> We can talk about both this AlluraBitergiaMetrics tool and tools in
> > > general.  I
> > > >> am currently thinking that AlluraBitergiaMetrics might be good to
keep
> > > as a
> > > >> separate tool and not merge it into the core yet, since there is
> > > cleanup to do.
> > > >
> > > > Yes, the point is in which moment a module is mature enough to enter
> > > > into the Allura repo.
> > >
> > >
> > > Personally, I'd love to see immature code in the Allura repo. It gives
> > > people the opportunity to see it develop, and to jump in and help where
> > > possible. As long as stuff is clearly marked as experimental, or
> > immature,
> > > or whatever, then no damage is done when stuff breaks. It's a simple
> > matter
> > > to exclude that stuff from any releases we make, right?
> >
> 
> Talking about "core vs plug-ins", I think it's material to make new
> plug-ins first class citizen, that means being part of the distributed
> platform. This way this podling can really welcome innovation, everyone
> will have the real possibility to influence allura's set of features,
> and end-users decide what they want or not want to run.
> 
> Roberto
> 
> 
> 
> > > --
> > > Rich Bowen
> > > rbowen@rcbowen.com
> > > Shosholoza
> >
> 


-- 
|\_____/| Alvaro del Castillo
 [o] [o]  acs@bitergia.com - CTO, Software Engineer
 |  V  |  http://www.bitergia.com
  |   |
-ooo-ooo-
|\_____/| Alvaro del Castillo
 [o] [o]  acs@bitergia.com - CTO, Software Engineer
 |  V  |  http://www.bitergia.com
  |   |
-ooo-ooo-


Mime
View raw message