community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Upayavira" ...@odoko.co.uk>
Subject Re: Apache project guidelines docs += independence?
Date Mon, 16 May 2011 19:11:35 GMT
+! reads well and clarifies some useful points we often take for
granted.

Upayavira

On Mon, 16 May 2011 12:58 -0400, "Michael McCandless"
<lucene@mikemccandless.com> wrote:
> +1 this is an important topic and you explain it well.
> 
> I'm not sure where it should go but I agree it should be somewhere
> "permanent" and visible.
> 
> Mike
> 
> http://blog.mikemccandless.com
> 
> On Mon, May 16, 2011 at 12:36 PM, Shane Curcuru <asf@shanecurcuru.org>
> wrote:
> > A number of different issues recently about commercial influence in our
> > projects have had me thinking about the importance that Apache projects
> > are managed independently.  Since this isn't explicitly stated in the
> > obvious places, I wrote a little essay for my personal blog:
> >
> > http://communityovercode.com/2011/05/apache-projects-are-independent/
> >
> > Comments?  I think as the ASF grows up, and as some of our projects are
> > on the way to scoring mega stardom, it's important to ensure both that
> > our projects can continue to manage themselves independently, but also
> > to *explain* to the world that this is important to us, and why.
> >
> > Do people like this?  Where would be a good place to put it in /dev or
> > the community site as a requirement for Apache projects?  I think it's
> > clear that the board (past, present, and future) will expect projects to
> > be managed independently, but it's not clear that we've done a good
> > enough job of explaining this yet.
> >
> > - Shane
> >
> >
> 

Mime
View raw message