Eric Boutilier wrote: > On Mon, 16 Jun 2008, Glynn Foster wrote: > >> Hey, >> >> Just a quick sanity check here - I'm trying to create the recently >> approved 'emancipation' community group. Seemingly the web app doesn't >> like it, because there's an existing 'project or community' that has >> both the same short name, and title. >> >> > > I remember running into that once... I think the problem is that under > the hood of the webapp, community and project names actually use the > same index column in the database or something like that. I think what > I ended up doing was archiving the project's content somewhere and > deleting it to free up the short-name or "moving" (effectively > renaming) the old project to free up the short-name. > > You could just try toggling the type in the database... they're in the same table, and there's a column that sets whether it's a community or project. >> What's the recommended course of >> action for migrating over from a project to a community? I'm just >> worried about possible consequences in the SCM hosting that I haven't >> thought about. >> >> > > I'm not sure about the mechanics of the scm subsystem though. > > I imagine all the project repos will become orphaned, since there is no way to get to the SCM Management link from a community page.
-steve -- stephen lau | [EMAIL PROTECTED] | www.whacked.net _______________________________________________ website-discuss mailing list [email protected]
