Changes between Version 1 and Version 2 of PSC


Ignore:
Timestamp:
Jun 11, 2014, 8:29:03 AM (10 years ago)
Author:
martinl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PSC

    v1 v2  
    11= GRASS Project Steering Committee =
     2
     3== Historical Notes ==
     4
     5===1st Letter to GRASS mailing lists===
     6
     7{{{
     8                                     02/10/2006 06:15 PM
     9Dear GRASS community,
     10
     11in the Chicago meeting the GRASS project was suggested to
     12as one of the initial OSGeo foundation projects.
     13
     14So far I only received positive feedback on the idea of
     15moving GRASS more formally to the foundation (while the
     16individual authors are keeping their copyright which is
     17a major difference to the Apache Foundation.)
     18
     19A couple of things will have to be sorted out in the
     20coming months to make GRASS's membership possible (below
     21list is inspired by Frank's mail to the GRASS project):
     22
     23o We will need to form a "GRASS Project Steering Committee"
     24  (PSC). Foundation projects need a formalized management
     25  which may be desired in any case. I would be glad to
     26  receive suggestions of names for this committee. For
     27  inspiration, please look at the MapServer Technical
     28  Steering Committee as described here:
     29
     30    http://mapserver.gis.umn.edu/development/rfc/ms-rfc-1
     31
     32o One benefit of the foundation is some degree of legal
     33   support and protection for the project. The flip side of that
     34   is that the foundation needs to ensure some degree of
     35   rigor and process in how code comes into the project. One
     36   part of that is getting committers to sign a legal agreement
     37   indicating that they agree that changes they commit will
     38   be under the license of GRASS (GPL) and that they have
     39   the right to submit the code (they wrote it, it is not
     40   patented, have permission from their employer, etc).
     41
     42o We will have to review the existing code base (which is
     43   huge - more than 500000 lines of source code in GRASS 6).
     44   Luckily a major code review was already done for GRASS 5.
     45   Also the "Debianization" process was performed for GRASS
     46   5 and GRASS 6.
     47
     48o It is suggested to move the support infrastructure for GRASS
     49   to new foundation systems. Stuff like CVS (maybe SVN then),
     50   and bugtracker and mailing lists. The web site will also
     51   likely appear under a foundation subdomain (ie. grass.osgeo.org)
     52   with hopefully the known mirror site structure as before
     53   with grass.itc.it, grass.ibiblio.org etc as principal mirror
     54   sites. If so, the web site will be migrated into a contents
     55   management system (CMS) in a harmonized "foundation style".
     56   A CMS will hopefully solve the problem to get more people
     57   involved in the Web site contents management.
     58
     59o We hope to establish options to enable sponorship for the
     60   foundation - be as direct funding or for selected foundation
     61   projects. Details have to be worked out. My suggestion is to
     62   create national tax-exempt organizations (such as the
     63   German GRASS Anwender-Vereinigung e.V. which already exists)
     64   which may offer to receive donations.
     65
     66o For now we should think about nominating people with
     67   recognized contribution to the GRASS project, to
     68   free data, to whatever deems significant. A small paragraph
     69   describing why the candidate is proposed as member to
     70   the foundation is needed as well. This will be announced
     71   more formally soon. Please see ongoing discussions here:
     72   http://lists.osgeo.org/mailman/listinfo/discuss
     73
     74(Nearly) nothing is set in stone yet.
     75More details will follow, a couple of official documents
     76are being currently prepared
     77
     78Your feedback is welcome.
     79
     80Markus
     81}}}
     82
     83
     84===2nd Letter to GRASS mailing lists===
     85
     86{{{
     87                                        02/11/2006 12:16 AM
     88Dear all,
     89
     90while I already received two suggestions for a GRASS
     91Project Steering Committee (PSC), I suggest to post the
     92nominations in public, if there are no objections.
     93I would like to have that transparent to everyone.
     94
     95Nominations should contain the name and a short paragraph
     96why it is a good candidate. We also have to decide,
     97how many members the PSC should have.
     98
     99It is worth reading
     100- http://www.apache.org/foundation/how-it-works.html
     101   (they are very successful, and the document applies much
     102    to the GRASS project culture)
     103
     104- http://mapserver.gis.umn.edu/development/rfc/ms-rfc-1/
     105   (MS RFC 1: Technical Steering Committee Guidelines) 
     106    apparently 7 members there.
     107
     108- http://lists.maptools.org/pipermail/gdal-dev/2006-February/thread.html#7881
     109    (GDAL PSC to be formed)
     110
     111- http://mapserver.gis.umn.edu/development/rfc/ms-rfc-10/
     112   (MS RFC 10: Joining the Open Source Geospatial Foundation)
     113
     114Related:
     115- https://sourceforge.net/mailarchive/forum.php?thread_id=9682788&forum_id=475
     116  (Community MapBuilder PMC membership nomination)
     117- https://sourceforge.net/mailarchive/forum.php?thread_id=9673493&forum_id=475
     118  (MapBuilder & Mapbender and the OSGeo Foundation)
     119
     120In fact, there is lot of material to digest in these days..
     121
     122Markus
     123}}}
     124
     125===3rd Letter to GRASS Dev mailing list===
     126
     127{{{
     128Markus Neteler  neteler at itc.it Sun, 23 Apr 2006 18:10:25 +0200
     129
     130On Sat, Apr 22, 2006 at 01:00:01PM +0100, Glynn Clements wrote:
     131...
     132> Alpha support in the current display architecture isn't going to
     133> happen (I reverted the last attempt to add it, and will do likewise in
     134> future).
     135
     136... this is why I really suggest to get interested in a project
     137steering committee [1], [2].
     138
     139Instead of recursively reverted changes of other developers,
     140we should come up with a design discussion and then *vote* on it.
     141At least for such crucidal pieces of the code I would like to
     142see less anarchy and a more formal approach. This will render
     143development more transparent to everybody. The scope cannot be to
     144have two display management systems in parallel, one without
     145and one with alpha support.
     146
     147Existing steering committees, to get inspired from:
     148 Mapserver: http://mapserver.gis.umn.edu/development/rfc/ms-rfc-1
     149 GDAL:      http://www.gdal.org/rfc1_pmc.html
     150 Mapbender: http://www.mapbender.org/index.php/Mapbender_PSC
     151 ...
     152
     153Please think about it!
     154
     155Thanks
     156
     157 Markus
     158
     159[1] http://grass.itc.it/pipermail/grass5/2006-February/021178.html
     160[2] http://grass.itc.it/pipermail/grass5/2006-April/022185.html
     161}}}
     162
     163Answers:
     164
     165 * http://lists.osgeo.org/pipermail/grass-dev/2006-April/thread.html#22556
     166
     167=== Nominations 2006 ===
     168
     169''The comments were copied from the [http://www.nabble.com/forum/Search.jtp?userPosts=y&user=449164&query=psc&sort=date related emails].''
     170
     171 * Brad Douglas (nominated by 11): for clone removal and code refactoring
     172 * Cedric Shock (nominated by 11): various code contributions
     173 * Dylan Beaudette (nominated by 4): deep commitment to community, publishes useful tips
     174 * Glynn Clements (nominated by 1): for his vast knowledge of standards, practices and compatibility
     175 * Hamish Bowman (nominated by 11): for documentation, integration, and various modules
     176 * Helena Mitasova (nominated by 1): for the obvious
     177 * Maciej Sieczka (nominated by 5):
     178 * Markus Neteler (nominated by 14): for the obvious.  :-)
     179 * Michael Barton (nominated by 12): very responsive to comments and questions; various code contributions
     180 * Paolo Zatelli (nominated by 1 ): no reason given
     181 * Paul Kelly (nominated by 11): for PROJ and platform support
     182 * Radim Blazek (nominated by 1): for his extensive GRASS work including vector and DBMS support
     183 * Roger Bivand (nominated by 7): no reason given
     184 * Venkatesh Raghavan (nominated by 9):
     185 * Massimiliano Cannata (nominated by 1):
     186
     187Declined (please reconsider =])
     188
     189 * Radim Blazek (nominated by 1): for his extensive GRASS work including vector and DBMS support
     190
     191=== Status September 2006 ===
     192
     193'''The GRASS Project Steering Committee ([[PSC]])''' - officially formed 11th Sept. 2006.
     194
     195 * '''Michael Barton''' (michael barton * asu edu)
     196 * '''Dylan Baudette''' (debeaudette * ucdavis edu)
     197 * '''Hamish Bowman''' (hamish_nospam * yahoo com)
     198 * '''Massimiliano Cannata''' (massimiliano cannata * supsi ch)
     199 * '''Brad Douglas''' (rez * touchofmadness com)
     200 * '''Paul Kelly''' (paul-grass stjohnspoint co uk)
     201 * '''Helena Mitasova''' (hmitaso * unity ncsu edu)
     202 * '''Scott Mitchell''' (smitch * mac com)
     203 * '''Markus Neteler''' (neteler * osgeo org) (chair)
     204 * '''Maciej Sieczka''' (tutey * o2 pl)
     205
     206(see also [http://grasswiki.osgeo.org/wiki/Team GRASS Team page])
     207
     208Next step: Revise [wiki:RFC/1_ProjectSteeringCommitteeGuidelines RFC1] (Request For Comment) for the GRASS community to consider
     209
     210=== Status November 2006 ===
     211
     212A [http://lists.osgeo.org/mailman/listinfo/grass-psc/ dedicated GRASS-PSC mailing list] has been created. It is open to the public.
     213
     214=== Status December 2006 ===
     215
     216The [[PSC]] has an Agenda (more there).