[OSGeo-Board] opening and organizing

[Daniel Brookshier]

Part of Tyler's confusion is perhaps the board compartmentalization.  
You are moving quite fast and most of the conversation has happened  
in the board list. By using the task list and making sure the right  
people have access, the confusion might be reduced. The board might  
consider also opening the board list up and creating a private list  
for specific conversations.

The key to managing this as a community is to move a lot of work into  
committees when possible. The goal over time should be to make the  
board list a quiet place. It will be a while before that happens, but  
that should be the plan.

In terms of a master list verses several. The tasks should be managed  
by the team. Any conflicts or joint work should be handled by the  
chairs or appointees. I'd say this is handled like a business, but is  
not. Most are volunteers and I'm sure that even though this is part  
of your job, dedicating 100% is not possible. Even I'm only supposed  
to work half my time on this community. The fewer things we need to  
focus on the better. The only challenge is ensuring that volunteers  
are keeping up their end.


Daniel Brookshier
Community Manager
214-207-6614

On Mar 6, 2006, at 7:21 PM, Gary Lang wrote:

> " I personally don't feel like we need a coordinated master task  
> list,"
>
> How can a Visibility Committee can do their job, absent of having this
> somewhere? Let's say Tyler wanted to do this. He seems confused about
> what we're doing. What is another solution to help him with his
> confusion?
>
> Gary
>
> -----Original Message-----
> From: Frank Warmerdam [mailto:fwarmerdam at gmail.com] On Behalf Of Frank
> Warmerdam (External)
> Sent: Monday, March 06, 2006 5:15 PM
> To: board at board.osgeo.org
> Subject: Re: [OSGeo-Board] opening and organizing
>
> Chris Holmes wrote:
>> Gary Lang wrote:
>>> So Committees are one sets of projects. Another would be stuff like
>>> "Where 2.0 Approach".
>>>
>>> This last one shows some of the problem - Nat Torkington called me
> this
>>> morning and among other things asked me to speak at the conference,
> and
>>> only by accident through our conversation discovered I was on the
> OSGeo
>>> board. We should coordinate on Where 2.0 as one of the OSGeo
> projects.
>>>
>>> There may be other things.
>> Well, I'd say this is a sub project of the publicity and visibility
>> committee.
>>
>>>
>>> So what I'm looking to do and will do if no one else is, is to  
>>> create
> a
>>> table that shows fields such as:
>>>
>>> "Task/Issue" "Owner" "Date Due" "Description" "Communication needed"
>> Isn't this kind of thing what the integrated task trackers of
> collabnet
>> are for?  So the visibility committee would make a task about where
> 2.0?
>>  And it's up to them to keep the appropriate people in the loop?
>
> Chris / Gary,
>
> I would concur with Chris that "Where 2.0" is a task of VisCom.   We
> create
> committees so that we (the board) don't have to be directly  
> responsible
> for
> everything going on.  If Where 2.0 is an important conference and we
> want
> to make a substantial presence known there, I hope VisCom would  
> indicate
> that in a report to the board (or we would ask).  But generally  
> speaking
> I
> don't think I (as a board member) need to know each conference that
> VisCom
> coordinates someone to attend and speak on OSGeo's behalf.
>
> I personally don't feel like we need a coordinated master task list,
> though
> I am willing to defer to others if they think it is necessary (and are
> willing
> to make it happen).  What we need to ensure, as a board, is that the
> appropriate committees are established, and are operating to our
> expectations.
> Not that we are on top of each action item of the committees.
>
> I expect many of us will want to be observers (ie. subscribed to the
> committee
> mailing lists) for several of these projects as a mechanism to keep
> aware
> of what is going on.
>
> PS. I'm still a bit unclear on this whole "officer" issue.  In my  
> head I
> still distinguish between fairly independent projects (like GDAL) and
> committees created by the board for a specific area of responsibility
> like viscom, webcom, or the incubator committee.  But in all cases  
> I am
> happy to say that the chair needs to be approved (ie. appointed) by  
> the
> board and is the official conduit for reporting.
>
> Best regards,
> -- 
> --------------------------------------- 
> +--------------------------------
> ------
> I set the clouds in motion - turn up   | Frank Warmerdam,
> warmerdam at pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush    | President OSGF,
> http://osgeo.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: board-unsubscribe at board.osgeo.org
> For additional commands, e-mail: board-help at board.osgeo.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: board-unsubscribe at board.osgeo.org
> For additional commands, e-mail: board-help at board.osgeo.org
>