[postgis-devel] Re: PostGIS infrastructure

[Paul Ramsey]

I ran the idea past osgeo, and they'll have us, though they would
prefer if we signalled an intent to enter incubation as an osgeo
project at the same time. Becoming an osgeo project is basically in
line with our thoughts about having some actual procedures for project
management, and adds an extra task around reviewing our intellectual
property and copyright situation (which would be healthy (since we
have some license conflicts in our code base)).

See the principles of incubation for an idea of what we'd be signing
up for: http://www.osgeo.org/incubator/process/principles.html

If we go that way, we can move as much or as little as we want. SVN is
on the table now. To that I'd add the bug tracker. I even volunteer to
figure out how to extract our data from Goog to import into trac.
Having a real trac/svn instance would be awsome. Moving mailing lists
is also possible if you want to do that too (and should be pretty
trivial, since osgeo uses mailman too).

P.

On Thu, Mar 12, 2009 at 9:38 AM, Kevin Neufeld <kneufeld at refractions.net> wrote:
> It's back up again.
>
> Yeah, Mark, I hear you.  And having more than a couple of people with root
> access to such an environment (esp. in different time zones) would indeed be
> welcome.
>
> I was just talking with a few folks here and we would be OK with the postgis
> repository moving elsewhere.  We realize that the hosting box is incredibly
> old and in *desperate* need of TLC.  We are also extremely busy and find it
> tough to give the box the attention it needs.
>
> So, we're open the idea.  Come up with a strategy and specifics, and we'll
> try to work out the details.
>
> Cheers,
> Kevin
>
> Mark Cave-Ayland wrote:
>>
>> Kevin Neufeld wrote:
>>
>>> Hi all, I just noticed that the svn repository is out of commission.
>>>  We're working to get this back online asap.  Thanx for bearing with us.
>>>
>>> Cheers,
>>> Kevin
>>
>>
>> Hi Kevin,
>>
>> One of the conversations we had at the code-sprint was a discussion of
>> infrastructure issues, in particular related to bug tracking/SVN/wiki
>> integration.
>>
>> AIUI the issue here is that the postgis web/SVN server runs an old version
>> of BSD which has the following issues:
>>
>>
>> i) it suffers from a file handle leak which often causes outages like this
>>
>> ii) we can't run Trac or newer versions of SVN
>>
>>
>> The lack of integration between bug tracking/SVN and the inability to view
>> changesets on the web is something that developers do notice and struggle
>> with on a regular basis. As I see it, the potential solutions are:
>>
>>
>> i) bug Refractions until they upgrade the server :)
>>
>> ii) move SVN hosting to an external server (e.g. postgresql.org/osgeo.org)
>> and change svn.refractions.net to point to it.
>>
>>
>> As a potential solution, I'm leaning slightly towards ii) since there is
>> potential for other non-Refractions people to have root access to the
>> server, and hence someone in another timezone can restart things if they
>> break (i.e. if you're on holiday we don't have to ring you up and bug you
>> all the time!).
>>
>> Thoughts?
>>
>>
>> ATB,
>>
>> Mark.
>>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>