On Thu, Aug 19, 2010 at 6:45 PM, Craig L Russell
<craig.russ...@oracle.com> wrote:
> I wish we had completed this discussion while subversion was still in
> incubation, while the subversion community could learn the common Apache
> terminology and have no need for translation of the terms.
>
> Instead, a suggestion to that effect was brutally shot down.
>
> And since it's apparently not clear what my point is, I'll repeat it:
>
> Apache has a common set of terms that everyone who participates is expected
> to understand. They are documented in the foundation "How we work" pages.
>
> Projects are free to have their own set of rules and terminology. If they
> differ much from standard Apache governance, there's an opportunity for them
> to have their own bylaws.
>
> When communicating with the wider Apache community, the standard terms are
> all that are needed. Parentheticals in such things as board reports, which
> are widely disseminated, might seem useful early in the project but are
> unnecessary very quickly. If they serve to clarify for the wider community,
> ok. But if parentheticals' only purpose is project communication, I believe
> that they are best avoided, as project members should know the Apache
> terminology (before exiting incubation).

Who cares?  This reeks to me of bureaucracy one might find at a
$dayjob.  I mean, the "apache" terms were used in the report, the
parentheticals were project-specific.  Eventually, they might simply
realize that the apache terminology is cool enough to use directly.
All board members are apparently competent enough to ignore the
parentheticals in their mind's eye - if they had a problem, they would
have mentioned it.  All will be ok, really.  This thread, like Joe's
thread, makes me wonder how such a pioneering group got such an
obeying/mother-may-i culture - it's nearly embarrassing.

--tim

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to