[SAC] Notification proceedures (was Subversion vhost migration underway)

Howard Butler hobu at iastate.edu
Sun Mar 4 02:15:25 EST 2007

On Mar 4, 2007, at 12:48 AM, Jason Birch wrote:

> We may want to think about what caused this problem in the first  
> place.  I have a feeling it was because of the chaos of the initial  
> changeover.  Does SAC need to put a notification procedure in place  
> for projects using the OSGeo infrastructure, or should a post to  
> the SAC mailing list be enough, with a requirement that projects  
> monitor that list?

I think that all projects depending on infrastructure should have at  
least one representative subscribed to the SAC list at the very  
least.  Notification of major changes and meeting minutes with  
upcoming changes are going to come across this list.  I also am in  
the habit of blurbing small changes and additions as I make them to  
#telascience so that I don't step on other people's toes who might be  
doing similar sorts of things (it also provides a nice sanity check).

As far as the chaos of the initial changeover, I think CN's layout is  
mostly to blame.  We were pretty much forced to answer to every URL  
under the sun for all kinds of things.  Replicating enough  
infrastructure to keep the lights on through the CN->self transition  
was pretty tough.  It would have been nice to do things like vhosts  
for trac and svn and layout stuff how we may have ultimately wanted  
them to be at that time but we didn't have all of our ducks in a row  
to do it.  I think we have still come a long ways, and stuff is still  
a little bumpy, but we'll eventually get to something that works well  
for us.  The challenge is not pissing people off too much while we  
try to do it :)


More information about the Sac mailing list