Benson Margulies wrote:
There are some minor English language issues, like agreement in
number. Sean, do you want edits?
I'm not sure if Sean wants edits, since I don't know which Sean you
mean. [1]
But I'm happy if people want to copy or adapt this blog posting to use
on any apache.org website, preferably under /dev or on the community site.
I think it could definitely use some cleanup, and it especially could
use some expanded explanations, both of the reasons for this rule, and
for some of the specific ways that PMCs need to act or be seen to act.
In a perfect world, we'd actually have a series of essays. Something
like my posting as the header on the /dev site as official
documentation. Then get several people to write personal blog posts
about the same topic, giving their perspective on what this means.
Especially for a concept like "independence", I find it really helps to
have several different people explain it in their own words - along with
whatever official policy we post on apache.org somewhere.
- Shane
[1] Sorry to point out the obvious and presumably unintentional typo,
but that's a name that I do not respond to. 8-P
On Mon, May 16, 2011 at 3:11 PM, Upayavira <u...@odoko.co.uk> wrote:
+! reads well and clarifies some useful points we often take for
granted.
Upayavira
On Mon, 16 May 2011 12:58 -0400, "Michael McCandless"
<luc...@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 <a...@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
>
>
