[tei-council] Fwd: Re: TEI Project at SourceForge; Subversion Repository; Issue trackers

[Kevin Hawkins]

I have added these questions to the end of:

https://docs.google.com/document/d/1E0aV-E75VOLE_TCrEXVVqaez-9zlyDcpCTeF5QP2BPI/edit

Above that, I have listed documents I have found on www.tei-c.org that 
need to be updated following the migration.  I've also started making a 
table showing old and new URLs.  I sense this is overkill, but right now 
I'm not sure I would correctly update all of the URLs.  Frankly, I would 
prefer if someone closer to them migration went through to update these 
pages since I'm afraid of getting some pieces wrong.  (Maybe James or 
Martin since they have access to the TEI website?)

K.

On 3/14/13 8:51 PM, Kevin Hawkins wrote:
> James (and others),
>
> Given that the IDs of tracker items were unfortunately not maintained in
> the upgrade, I guess we will need to keep the PURL system resolving only
> to tracker rather than repurposing it for the new syntax.  Are we going
> to create a new PURL syntax that resolves to the new SF system or not
> bother, instead using the fairly human-friendly URLs of the new system
> without bothering with any sort of PURL?
>
> Did any part of the upgrade process say how long the redirects would be
> maintained by SourceForge?  Based on that answer, do we have a sense of
> how much value there is in updating URLs in old TCM documents etc. to
> point to the new tracker URLs?  That is, at some point these links will
> break, but it can be helpful to reconstruct a discussion to look at the
> ticket.  On the other hand, the longer ago something was, the less
> likely it is that we will need to (or bother to) dig so deep.
>
> Kevin
>
>> -------- Original Message --------
>> Subject: Re: TEI Project at SourceForge; Subversion Repository; Issue
>> trackers
>> Date: Wed, 13 Mar 2013 11:36:34 +0000
>> From: James Cummings <James.Cummings at IT.OX.AC.UK>
>>
>> Dear TEI Community,
>>
>> The TEI Project upgrade on SourceForge is now successfully
>> complete.  The following URLs have changed:
>>
>> The summary page is now:
>> https://sourceforge.net/projects/tei/
>>
>> The SVN repository is now browsable at:
>> https://sourceforge.net/p/tei/code/
>>
>> Feature requests are now read, created, and managed at:
>> https://sourceforge.net/p/tei/feature-requests/
>>
>> and bugs at:
>> https://sourceforge.net/p/tei/bugs/
>>
>> There are *certainly* going to be some places on websites which
>> point to the wrong URLs and these will be corrected soon. Many of
>> the old URLs will continue to forward for some time. The ID
>> numbers of old tracker items are not preserved, however those
>> pages forward through to the new ones.
>>
>> If you have a copy of the SVN repository checked out then you can
>> 'switch' its location by doing:
>>
>> svn relocate <new-repo-url>
>> svn switch --relocate <old-repo-url> <new-repo-url>
>>
>> e.g.
>> svn relocate svn://svn.code.sf.net/p/tei/code/trunk
>> or
>> svn relocate https://svn.code.sf.net/p/tei/code/trunk
>>
>> or
>> svn switch --relocate
>> https://tei.svn.sourceforge.net/svnroot/tei/trunk
>> svn://svn.code.sf.net/p/tei/code/trunk
>>
>> Or of course simply use the svn checkout code presented to you
>> when you go to  https://sourceforge.net/p/tei/code/
>>
>> If you also commit to the TEI svn repository the urls and
>> protocol is slightly different (svn+ssh).  For more details on
>> repository migration please see
>> https://sourceforge.net/p/forge/community-docs/Repository%20Upgrade%20FAQ/
>>
>>
>> If you have significant problems or questions please direct them
>> here to the mailing list so we can answer them for everyone.
>>
>> Thanks,
>>
>> James Cummings
>> TEI Technical Council Chair
>>