[GRASS5] GRASS Project Steering Committee and more

[Michael Barton]

At the moment, GRASS seems somewhere between Apache and GDAL in its
organization--and possible contributor/user base.

We might think of something that can start out somewhat less formal, like
MapServer, but be able to scale up to something more formal, like Apache, if
needed in the future. I haven't thought what that might be yet, of course
;-)

Michael


On 4/5/06 3:29 PM, "Markus Neteler" <neteler at itc.it> wrote:

> Dear all,
> 
> since the earlier proposed Contributor Agreement of the OSGeo
> Foundation is a non-issue now (no longer a requirement),
> I would like to push the idea again of forming a Project
> Steering Committee. In any case we should have such a
> structure to make GRASS more independent from individuals
> (in particular, if they aren't available) to take decisions.
> 
> The list of nominations which we got so far is here:
>  
> http://grass.gdf-hannover.de/twiki/bin/view/GRASS/ProjectSteeringCommitee#Nomi
> nations
> 
> Please take a look how the other projects handle this.
> With a growing GRASS project I would really like to
> see some more formal approach of deciding things, at least,
> to have it as backup (in history, decisions worked out smooth in
> the majority of the cases).
> 
> I also feel that OSGeo could become a (second) home to ensure
> that the software and its infrastructure remains available long
> term. If you look at the member lists of the foundation, you
> will find many active people there who push for a better integration
> between GFOSS projects and other projects like Educational Outreach
> or public geodata.
> 
> Thanks
> 
>  Markus
> 
> 
> On Sat, Feb 11, 2006 at 12:16:29AM +0100, Markus Neteler wrote:
>> Dear all,
>> 
>> while I already received two suggestions for a GRASS
>> Project Steering Committee (PSC), I suggest to post the
>> nominations in public, if there are no objections.
>> I would like to have that transparent to everyone.
>> 
>> Nominations should contain the name and a short paragraph
>> why it is a good candidate. We also have to decide,
>> how many members the PSC should have.
>> 
>> It is worth reading
>> - http://www.apache.org/foundation/how-it-works.html
>>    (they are very successful, and the document applies much
>>     to the GRASS project culture)
>> 
>> - http://mapserver.gis.umn.edu/development/rfc/ms-rfc-1/
>>    (MS RFC 1: Technical Steering Committee Guidelines)
>>     apparently 7 members there.
>> 
>> - http://lists.maptools.org/pipermail/gdal-dev/2006-February/thread.html#7881
>>     (GDAL PSC to be formed)
>> 
>> - http://mapserver.gis.umn.edu/development/rfc/ms-rfc-10/
>>    (MS RFC 10: Joining the Open Source Geospatial Foundation)
>> 
>> Related:
>> - 
>> https://sourceforge.net/mailarchive/forum.php?thread_id=9682788&forum_id=475
>>   (Community MapBuilder PMC membership nomination)
>> - 
>> https://sourceforge.net/mailarchive/forum.php?thread_id=9673493&forum_id=475
>>   (MapBuilder & Mapbender and the OSGeo Foundation)
>> 
>> In fact, there is lot of material to digest in these days..
>> 
>> Markus
>> -- 
>> Markus Neteler     <neteler itc it>       http://mpa.itc.it
>> ITC-irst -  Centro per la Ricerca Scientifica e Tecnologica
>> MPBA - Predictive Models for Biol. & Environ. Data Analysis
>> Via Sommarive, 18        -       38050 Povo (Trento), Italy
>> 
>> _______________________________________________
>> grass5 mailing list
>> grass5 at grass.itc.it
>> http://grass.itc.it/mailman/listinfo/grass5
> 

___________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

WWW - http://www.public.asu.edu/~cmbarton
Phone: 480-965-6262
Fax: 480-965-7671