Thanks for your feedback! I have removed these from both reporting-issues.html and the community guide.
Since I had some time, I also looked at the rest of the website. Regarding the link to cvs2svn I tried to find if it was rehosted somewhere else but couldn't find someone who actually had the code. We _could_ probably get the code from Debian (or FreeBSD) and host it ourselves but I don't know if that is worth the effort. For now I'm pointing at the Linux/BSD distributions. As far as I can see, the only remaining links to tirgis.org are in the following pages: * Old release notes. I'm reluctant to change history. Possibly we could add a note that the link is now defunct (like I did in the news page). * Old CVE advisories (.txt files). I believe these to be historic evidence which should not be changed at all. (And it affects version 1.4 and 1.6). * Translations (Japanese and Chinese) of faq.html. This seems to be related to the cvs2svn but I dare not to touch it. I hope someone else in dev@ master these languages. [[[ Remove even more references of tigris.org from the website. * docs/community-guide/l10n.html Removed reference to old l10n-??@subversion.tigris.org mailing lists. Referred translation discussions to dev@. * faq.html Remove dead cvs2svn links. * mailing-lists.html Adjusted a comment to contain the right address for dev@ Remove reference to Tigris Discussion page. * news.html Make a note that subversion.tigris.org is no longer available but keep old link for historic reference. * reporting-issues.html Remove the section Issuezilla. ]]] Kind regards Daniel Sahlberg
Index: docs/community-guide/l10n.part.html =================================================================== --- docs/community-guide/l10n.part.html (revision 1879655) +++ docs/community-guide/l10n.part.html (arbetskopia) @@ -70,10 +70,7 @@ href="https://svn.apache.org/repos/asf/subversion/trunk/subversion/po/"; >the po section of the repository</a>. Please contact dev@subversion.apache.org when you want to start a translation not -available yet. Translation discussion takes place both on that list -and on dedicated native language mailing lists (<a -href="http://subversion.tigris.org/servlets/ProjectMailingListList"; -><em>l10n-??@subversion.tigris.org</em></a>).</p> +available yet. Translation discussion takes place on that list.</p> </div> <!-- l10n-overview --> Index: faq.html =================================================================== --- faq.html (revision 1879655) +++ faq.html (arbetskopia) @@ -861,27 +861,14 @@ title="Link to this section">¶</a> </h3> -<p>Try the cvs2svn conversion tool, from <a -href="http://cvs2svn.tigris.org/";>http://cvs2svn.tigris.org/</a> (see -also its <a href="http://cvs2svn.tigris.org/features.html"; >feature -list</a> and <a href="http://cvs2svn.tigris.org/cvs2svn.html"; ->documentation</a>). cvs2svn seems to be what most people use, but if -for some reason it doesn't meet your needs, there are at least two -other tools you could try:</p> - -<ul> - -<li>One based on <a -href="http://public.perforce.com/public/revml/index.html";>VCP</a> -written by Chia-liang Kao can be found on <a -href="http://search.cpan.org/perldoc?VCP::Dest::svk";>CPAN</a>.</li> - -<li>refinecvs written by Lev Serebryakov is at <a +<p>The cvs2svn conversion tool seems to be what most people use. It was +previously hosted on http://cvs2svn.tigris.org/, however this site was +shut down July 1, 2020. If you are running Linux or a BSD-based system +your distribution might still have a package for you. If not you might try +refinecvs written by Lev Serebryakov at <a href="http://lev.serebryakov.spb.ru/refinecvs/"; ->http://lev.serebryakov.spb.ru/refinecvs/</a>.</li> +>http://lev.serebryakov.spb.ru/refinecvs/</a>.</p> -</ul> - </div> Index: mailing-lists.html =================================================================== --- mailing-lists.html (revision 1879655) +++ mailing-lists.html (arbetskopia) @@ -318,7 +318,7 @@ ...)" where N is a revision number, and the information in parens is a platform string, see the PLATFORMS file for more examples. Substitute FAIL for PASS if the test fails. (Also, please set the - Reply-to header on such mails to d...@subversion.tigris.org, so + Reply-to header on such mails to dev@subversion.apache.org, so any problems are followed up on the main list.) --> </tr> @@ -467,20 +467,6 @@ </div> <!-- #announcements --> - -<div class="h2" id="other-lists"> -<h2>Other Mailing Lists - <a class="sectionlink" href="#other-lists" - title="Link to this section">¶</a> -</h2> - -<p>We have a variety of additional mailing lists for other aspects of - the project management. You can find these lists on - our <a href="http://subversion.tigris.org/ds/viewForums.do"; >old - Tigris.org Discussions page</a>.</p> - -</div> <!-- #other-lists --> - </div> <!-- #site-content --> </body> </html> Index: news.html =================================================================== --- news.html (revision 1879655) +++ news.html (arbetskopia) @@ -2130,7 +2130,8 @@ you can't find what you're looking for here at this website, chances are good that we've not yet migrated that information yet from our <a href="http://subversion.tigris.org/"; >old - website</a>.</p> + website</a>. [As of July 1, 2020 the old website is no longer + available.]</p> </div> <!-- #news-20091107 --> Index: reporting-issues.html =================================================================== --- reporting-issues.html (revision 1879655) +++ reporting-issues.html (arbetskopia) @@ -96,16 +96,6 @@ </div> <!-- #queries --> -<div class="h2" id="issuezilla"> -<h2>Issuezilla, the Old Bug Tracker - <a class="sectionlink" href="#issuezilla" - title="Link to this section">¶</a> -</h2> - -<p>Subversion's previous issue tracker can be accessed at <a href="http://subversion.tigris.org/servlets/ProjectIssues";>http://subversion.tigris.org/servlets/ProjectIssues</a>. Its content was transferred to the new tracker in September 2015. Since then, it is available for read-only access, until we decide to turn it off.</p> - -</div> <!-- #issuezilla --> - </div> <!-- #site-content --> </body> </html>
