Goal: everyone is able to find what they are looking for with minimal confusion.
@PROPOSAL: when the history page is written on the new Apache site, we archive the previous 2.X releases here on Apache. The SF pages would then redirect (http 302) or simply a banner "cTAKES is now an officially hosted Apache project. Click here " Same goes for the NCI website that can give the impression that the NCI is the home for cTAKES. my 2 cents, --Andy On Mar 7, 2013, at 1:32 PM, "Masanz, James J." <[email protected]> wrote: > As I recall, once something is on sourceforge, you can't just delete it. > > Plus as Britt pointed out there are people still using an older version and > we shouldn't want to totally delete information about previous releases. > > If there are any pages that need stronger wording and you don't have access > to update the page, if you send me your suggestions, I can update them. > > -- James > >> -----Original Message----- >> From: ctakes-dev-return-1345-Masanz.James=mayo....@incubator.apache.org >> [mailto:ctakes-dev-return-1345- >> [email protected]] On Behalf Of Britt Fitch >> Sent: Thursday, March 07, 2013 10:29 AM >> To: [email protected] >> Subject: Re: SourceForge Project Upgrade - Code Repo Complete >> >> Can we update the pages that point to the old version to strongly >> suggest that they visit the new Apache pages, rather than remove the old >> version? >> Or can we move the artifacts for the old version to an archive in >> Apache? >> Andy McMurry and I still maintain the Scrubber tool which depends on an >> older version of cTAKES. It is our plan to update it, but we have not >> done so yet. >> >> >> On Thu, Mar 7, 2013 at 11:07 AM, Dligach, Dmitriy < >> [email protected]> wrote: >> >>> Should we consider getting rid of the sourceforge version of cTAKES >>> completely to avoid confusing people who want to download cTAKES for >>> the first time? Depending on how you google it, the sourceforge >>> version might come up first. >>> >>> Dima >>> >>> Begin forwarded message: >>> >>> From: SourceForge.net<http://SourceForge.net> < >>> [email protected]<mailto:[email protected] >>> noreply+.net >>>>> >>> Date: March 6, 2013 9:35:41 PM EST >>> To: <[email protected]<mailto:[email protected]>> >>> Subject: SourceForge Project Upgrade - Code Repo Complete >>> Reply-To: <[email protected]<mailto:[email protected]>> >>> >>> Your code repository in upgraded project ohnlp is now ready for use. >>> >>> Old repository url: http://ohnlp.svn.sourceforge.net/svnroot/ohnlp >>> >>> New repository checkout command: svn checkout --username=dimdym >>> svn+ssh:// [email protected]/p/ohnlp/code/trunk ohnlp-code >>> >>> You should do a checkout using the new repository location. The old >>> repository is read-only now. >>> >>> For more detailed instructions on migrating to your new repo, please >>> see >>> https://sourceforge.net/p/forge/community-docs/Repository%20Upgrade%20 >>> FAQ/ >>> >>> -- >>> SourceForge.net<http://SourceForge.net> has sent this mailing to you >>> as a registered user of the SourceForge.net<http://SourceForge.net> >>> site to convey important information regarding your >>> SourceForge.net<http://SourceForge.net> account or your use of >>> SourceForge.net<http://SourceForge.net> services. >>> If you have concerns about this mailing please contact our Support >>> team per: http://sourceforge.net/support >>> >>>
