Hi, I can think of at least one non public Jira whose links will break. Archiving probably wont work as most links point to a line number, commit, or something specific.
I guess we could just say tough, its too much effort to fix, anyone really interested will find the information for themselves. I see tomcat may have had the same issue. They just started a new repo for each major version and left the old one as is. Annother solution is to put a readme Also, when you delete the apache/sling repo IIRC someone who forked it will take over and all forks will point to them, or at least, thats what happend when I deleted one of my repos. From memory it was the repo at the top of the forks list [1] which seems to be [2], but it could be the first person to fork, if you have the patience to go back through githubs record of the network. Best Regards Ian 1 https://github.com/apache/sling/network/members 2 https://github.com/447327642/sling On 20 October 2017 at 12:11, Robert Munteanu <romb...@apache.org> wrote: > Hi Ian, > > On Fri, 2017-10-20 at 11:04 +0100, Ian Boston wrote: > > BTW, > > Deleting github:apache/sling will 404 every reference to code there > > from > > JIRA in many places. Probably not a good idea to delete it, but it > > should > > be made readonly. > > That's a good point, I did not consider this. > > The problematic part of keeping the old sling repository around is that > it is probably the entry point to many people. > > So the way I see it we have: > > 1. Keep the old 'sling' mirror on Github > > + links are not broken > - content is duplicated and out of date > - no good entry point for users when they visit github.com/apache/sling > > 2. Remove the old sling-mirror > > + good entry point for Sling source code ( can contains e.g. repo > script to pull down all Sling modules ) > + no duplicate or out-of-date content > - links are broken > > Additionally, we already have a gitbox 'sling' repository that is not > mirrored to GitHub - https://gitbox.apache.org/repos/asf?p=sling.git;a= > summary , which can add to the confusion. Yes, we can rename it so it's > not a con per se, but wanted to point that out. > > As usual, my proposal is scripting :-) I would write a Jira script that > inspects all the Sling tickets, and when finding a link to the > github.com/apache/sling repo, I would edit the comment and add a note > that the link is outdated. > > Another alternative is to move the repo to github.com/apache/sling- > archive and tweak the links to point to that. What I don't really like > about that is that we will have outdated content, which is confusing. > Maybe we can talk to infra to move it _and_ change the default branch > to something like 'archived'? This way we'll only get a README.md which > says this repo is archived for historical purposes and we'll also get > proper links if we edit the Jira comments. > > My proposal would be to remove the 'old' sling repository, with > tweaking the Jira comments if we think it's worthwhile. Alternatively, > we can consider archiving it, but that's going to take a bit longer due > to the need to write a script and also asking infra for help with the > move. > > Thanks, > > Robert >
