[OSGeo-Conf] [Board] Conference Committee Guidelines
gcpp.kalxas at gmail.com
Tue Dec 6 04:48:19 PST 2016
The following are my own views, not an official response from the board:
If such policy never existed and things worked well for the conference
committee, then why did the committee tried to apply a new policy? And
why did this new policy got blocked? Perhaps because it was not clear
how the committee should work in the first place?
The board is asking for a document to actually avoid this situation.
Having some (even minimal) document of how things work (and incubation
committee documents are an excellent example, thanks Jody), would avoid
such problems in the future.
I don't believe that the board is trying to lead by directing or
micro-managing the committees. We actually were all against that in the
video conference we had. But in order to get some consensus, a minimal
set of rules has to be somehow be expressed.
Please have in mind that volunteers don't only loose their interest when
formalities/bureaucracy take over, but also when things are not
transparent or when major conflicts happen. I am guessing that Steven
did not step down as a chair just because the new policy didn't go
through, but also by being involved in a conflict with long e-mail
threads etc. The board discussion was towards making things more
transparent and open. It was also clear that the "committee guidelines"
on our wiki are not a formal document but just an example, and that
committees are free to do their own thing.
Regarding your reference to the Eric Raymond document, personally I find
it offensive that you question us being aware of it, or having read it.
In any case, thank you for your input.
On 12/06/2016 12:48 PM, Cameron Shorter wrote:
> OSGeo board,
> I suspect you'll get a minimal response to a call for membership
> The reasons are relatively subtle. Volunteers step up to scratch an
> itch if they feel there is a need. If such policies are not in place
> yet, then communities probably don't feel the need for them.
> Having the board direct communities to produce documents, in a
> command-and-control type request is typically not how open source
> communities work effectively.
> I think you will find OSGeo communities work effectively, whether
> their processes are written down or not.
> If you haven't already read it, I suggest having a look at The
> Cathedral and the Bazaar, by Eric Raymond. In particular, this chapter:
> I suggest that leading by example and amplifying initiatives of others
> will be more effective for you than leading by directing. It will help
> you as a board be more effective during your term in office.
> Warm regards, Cameron
> On 6/12/2016 4:17 AM, Angelos Tzotsos wrote:
>> Dear Conference Committee,
>> Following up on your recent motion to update your membership policies
>> and process, and the issues raised by this motion, the board has held
>> a video meeting to discuss the issue of committee guidelines.
>> As a result, the board is asking everyone to write down "committee
>> guidelines" on how each functions. The idea is to make sure our
>> committees are transparent in their decision making, and open to
>> There is a wiki page here
>> https://wiki.osgeo.org/wiki/Committee_Guidelines that provides more
>> information (and helpfully provides guidance for committee chairs).
>> There are some examples of different committees doing their thing
>> here (https://wiki.osgeo.org/wiki/Committee_Guidelines#Examples).
>> Best regards,
Angelos Tzotsos, PhD
OSGeo Charter Member
More information about the Conference_dev