public inbox for [email protected]  

help / color / mirror / Atom feed

From: Robert Treat <[email protected]>
To: [email protected]
Cc: Dave Page <[email protected]>
Cc: Magnus Hagander <[email protected]>
Subject: Re: Moving the website project from GBorg
Date: Tue, 12 Jun 2007 10:30:28 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

On Tuesday 12 June 2007 04:39, Dave Page wrote:
> Magnus Hagander wrote:
> > On Tue, Jun 12, 2007 at 09:06:58AM +0100, Dave Page wrote:
> >> I've created a pgweb project on pgFoundry to migrate from GBorg to. The
> >> original idea was to migrate the CVS and just lose the bugs etc. as
> >> they're largely out of date at the moment anyway. We can make an effort
> >> to be more organised with the more usable pgFoundry trackers in the
> >> future.
> >
> > They're only slightly more usable, but still ;-)
> > Agreed (again) on the fact that we just drop whatever's tehre now. It's
> > all insanely out of date.
> >
> >> Magnus has since come up with an idea though, that instead of using CVS
> >> on pgFoundry, we move the website CVS to an SVN repository actually on
> >> wwwmaster to remove the dependency on pgFoundry for the operation of the
> >> website. This seems like a fine idea to me - any other thoughts or
> >> ideas?
> >
> > Can we set up some way to replicate that repository *back* into
> > pgfoundry? Might be nice for "outsiders" to be able to use the cvs
> > viewer... Or we just add a simplistic cvs viewer on wwwmaster for them?
>
> We could probably rsync it back in, *when* we have a SVN-supporting
> GForge, assuming that it remains 1 repo per project.
>

If we're going to go through this trouble, is there some reason not to put up 
a public trac site some place and make use of it? 

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

view thread (14+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Moving the website project from GBorg
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox