OSGeo-Board RE: Calibrate our time for working together

[Chris Holmes]

For now I'm just about the same as Frank.  I haven't talked to my job 
yet, and in some scenarios I may be able to get my paid work to overlap 
with foundation activities, so may be able to put in more.  Much needs 
to be figured out on that front.  But I can commit 8 hrs a week for 
sure, will just work longer weeks.  My availability is more like 10am - 
6pm eastern time.  Am not currently planning on having internet at home, 
but I also don't have a place yet, so that may change. And I could make 
weekends for a meeting if need be, but would prefer weekday meetings. 
Also have a slight preference for wed - fri for meetings, as I already 
have geotools and geoserver ircs on monday and tuesday.  If we need to 
do mon/tue then I can figure out the exact times of those.

So in conclusion
a) 8-10 on average, may be a bit more after I figure out my job stuff
b) 10am - 6pm est for sure.
c) yes, but prefer weekdays for regular meeting

Chris

Frank Warmerdam wrote:
> Gary Lang wrote:
> 
>> Board,
>>
>> In order to calibrate the bandwidth we have for working together I'd 
>> like to ask that we each post the following:
>>
>> a) how much time you can devote to board activities in a week
> 
> 
> Gary,
> 
> I am prepared to spend roughly 8hours/week on foundation activity,
> somewhat front loaded at the beginning I would imagine.
> 
>> b) what are the hours in which you'll generally be available for board =
>> discussions
> 
> 
> I am generally available 9:00am to 4:30pm eastern time.  I will
> be intermittently available outside that range.
> 
>> c) can you be available on the weekend for a meeting?
> 
> 
> Yes, most weekends.
> 
> Best regards,

-- 
Chris Holmes
The Open Planning Project
thoughts at: http://cholmes.wordpress.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cholmes.vcf
Type: text/x-vcard
Size: 269 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/board/attachments/20060214/b7848bee/attachment.vcf>