incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cory Johns <>
Subject Re: what goes in the core Allura repo (was Re: Presentation and Metrics work in Allura)
Date Wed, 31 Oct 2012 15:48:40 GMT
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.

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 <> 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?
> --
> Rich Bowen
> Shosholoza

This e- mail message is intended only for the named recipient(s) above. It 
may contain confidential and privileged information. If you are not the 
intended recipient you are hereby notified that any dissemination, 
distribution or copying of this e-mail and any attachment(s) is strictly 
prohibited. If you have received this e-mail in error, please immediately 
notify the sender by replying to this e-mail and delete the message and any 
attachment(s) from your system. Thank you.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message