Changes between Initial Version and Version 1 of PSC/Creation2006


Ignore:
Timestamp:
May 14, 2016, 8:26:59 AM (8 years ago)
Author:
neteler
Comment:

moved 2006 notes here

Legend:

Unmodified
Added
Removed
Modified
  • PSC/Creation2006

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