Shawn / Tyler,
I'd be interested in having login access to the osgeo.org server, and sudo
access. I am ok with deferring this if you would prefer it to be in the
context of a SAC policy on administrative access, but we need to get to the
point where more people learn the system, and can fix things.
(note cc: to sac in case you are tempted to reply with a userid and password!)
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | President OSGeo, http://osgeo.org
I guess we want to have a reasonably small number of users with shell and sudo access and continue to rely on Shawn for low-level system changes.
Shawn is doing up some system notes over the next week or so to help orient you to the system.
My main concern is making sure responsibilities are clear so that two of us don't go and try to fix a request or problem. Or go in to 'clean up' something and end up removing something someone else was working on, etc. For this reason I agree that we should use Trac when it is ready (next week) to handle requests/issues in a structured way.
Tyler
On 5-Jan-07, at 10:25 AM, Frank Warmerdam wrote:
Shawn / Tyler,
I'd be interested in having login access to the osgeo.org server, and sudo
access. I am ok with deferring this if you would prefer it to be in the
context of a SAC policy on administrative access, but we need to get to the
point where more people learn the system, and can fix things.
(note cc: to sac in case you are tempted to reply with a userid and password!)
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | President OSGeo, http://osgeo.org