Currently, the Tigris.org machine has an "instance set" (custom code) which causes that site to be published from the /trunk/www directory of our now-read-only svn.collab.net repository via some cron job. Now that we have our CVS data converted to Subversion, there's no reason to keep the live CVS repository at subversion.tigris.org. And now that we aren't using the svn.collab.net repos, the website on subversion.tigris.org is frozen in time.
I'm proposing that we do this:
* Ask CollabNet Ops to convert subversion.tigris.org from a CVS-backed
project to a Subversion-backed one, giving us a clean Subversion
repository on the box to play with.
* Ask CollabNet Ops to remove or disable the instance set that tells
the server to pull www bits from svn.collab.net, and let the default
behavior (of auto-publishing the /trunk/www directory of the on-site
project repository) kick in. Of course, in the process, we'll be
careful *not* to lose our 'downloads'/'tarballs' folder (which isn't
versioned).
* 'svn export' our ASF 'www' directory, and 'svn import' that into
the new subversion.t.o repository's /trunk/www directory, effective
forking the history of those files, but for what I think are obviously
good reasons.
At this point, we've preserved the current state of the subversion.t.o
website, but we can now make changes to it in the same way every other
project makes those changes. And, of course, we're free to rethink,
refactor, reorganize, and re-everything-else our subversion.a.o web presence.
And yes, I'm volunteering to manage this.
Thoughts? (Silence is assent.)
--
C. Michael Pilato <[email protected]>
CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
