[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grass-psc
Subject:    [GRASS-PSC] GRASS SVN migration: authentication procedure
From:       neteler () fbk ! eu (Markus Neteler)
Date:       2007-12-10 17:03:39
Message-ID: 20071210220329.GC14949 () fbk ! eu
[Download RAW message or body]

Here the current state of GRASS OSGeo-SVN account activation
and the concept behind it:

Current members of Group "grass":
  - bdouglas, benducke, cdavilam, cmbarton, dcalvelo, epatton, glynn, 
    helena, jachym, kyngchaos, martinl, mlennert, msieczka, neteler, 
    rantolin, sholl, smitch, wolf
  
Current members of Group "grass_addons":
   - all members of group "grass"
   - ychemin

Current members of Group "translations" (limited access to /grass/trunk/locale/):
   - all members of group "grass"
   - future enabled translators (currently none)

The "translations" requires an acceptance process which might
be easier than RFC2 acceptance (since only translations are
involved). We'll start this procedure soon.

For authentication, the OSGeo LDAP is used (single sign-on).

Remember:
- GRASS developers need to obtain an "osgeo_id" at
  http://www.osgeo.org/osgeo_userid
  Check at http://www.osgeo.org/cgi-bin/ldap_web_search.py 
  if you forgot your "osgeo_id".
  
- GRASS developers have to agree to abide by RFC2
  http://download.osgeo.org/grass/grass6_progman/rfc/rfc2_psc.html
  in an email to M Neteler (PSC chair) or preferably to
  grass-psc mailing list after subscription (subscribe at
  http://lists.osgeo.org/mailman/listinfo/grass-psc ) to
  get their "osgeo_id" activated for SVN write access.
  NOTE: any GRASS-PSC member can add new developers
  who were approved by the GRASS-PSC. 
  
Hopefully more developers complete the procedure over the
next days.

Happy hacking,
Markus

[prev in list] [next in list] [prev in thread] [next in thread]