Aaron Bannert wrote:
On Tuesday, September 16, 2003, at 08:52 AM, Stephen McConnell wrote:
As soon as you let a PMC make decisions behind closed doors - then your asking for trouble. A PMC is there to handle either (a) dull, boring, mindless administrata, or (b) nasty stuff that you really don't want to know about. Anything in between should be for the community to decide and if that causes some flack - so be it.
Again, this is incorrect and very misleading.
:-)
Aaron - it's only my opinion.
While you may think it is wrong relative to you interpritation of the roles and responsibilities of a PMC, the comments are not incorrect - they are simply an opinion.
As to misleading - that comes down to your objective. If your objective is community engineering within an open source project then yes, my observations would clearly be misleading as thay imply problems related to a club mentality which would naturally be counter-productive. On the otherhand, if your aiming for a structure within which decisions are transparent and function is oriented to facilitating[1] and representing[2] a community[3] - then perhaps you could consider the same observations as engaging, embrassing, even ... enabling[4].
Cheers, Steve.
[1] http://dictionary.reference.com/search?q=facilitating [2] http://dictionary.reference.com/search?q=representing [3] http://dictionary.reference.com/search?q=community [4] http://dictionary.reference.com/search?q=enabling
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
