[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipse.org-architecture-council] Bylaws Change on AC (was: 10-Mar AC meeting notes)
|
Am 11.03.2011 16:18, schrieb Oberhuber, Martin:
> Exactly by what we've been doing so far: By the tools we provide to
> the community (git, Hudson + plugins, release-tracker, Forums,
> bugzilla, ...) as well as the guidelines and advice we give (EDP,
> Developer_Resources,
> http://wiki.eclipse.org/Architecture_Council/Top_Ten_Recommendations,
> even individual AC member's blogs), networking between Community and
> Board members (Boris, Wayne, Mike will tell the Board about AC
> ideas)...
Don't those things primarily apply to projects and the community (of
people) working with Eclipse projects directly?
By "ecosystem" I count in all Eclipse members as well. I do have some
doubts that we can "influence" the large corporations in any of their
strategic decisions. That's why I don't think that a statement like this
should be written into the bylaws.
The things we do and the resources (guidelines/practices/tools) we
provide may have an (hopefully positive) influence on developers working
with Eclipse projects within those corporations. That's a very positive
aspect of what we do. But IMHO it doesn't classify to be written into
the bylaws.
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/