Sometimes a module is renamed, and its distribution is renamed accordingly. It would be useful to be able to mark that a pair of distributions with different base names are in fact versions of the same project, and so a module's history is followed through all the names it had. Separately, but probably more difficult, is following when distributions have been split up or combined, in that sometimes a particular module is bundled with others and other times it is released on its own. Both of these cases have happened with my projects.
I agree about following renames. Its easy to do... if we knew what the renames were. It will have to be handled on a case-by-case basis as people spot the renames. Report them as issues as you spot them.
Tracking project splits and merges is more complicated. One example is Net-FTP vs libnet. I don't know how to make sense of that in terms of github.
I agree about the case-by-case, and expected this is probably how it would need to work. I was raising the issue more to say it needed doing, not how.
So to start off here are connections between my most recent projects, simpler version:
More complicated version as a delta:
Another issue with this. Let's say Foo-Bar becomes Bar-Baz. What happens to the existing github repository? Do we rename it and leave the existing users (not to mention historical searches) in the lurch? Maybe one can be a mirror of the other?
Speaking for myself with my original repositories, if I rename the project I rename the repository, which Github supports. Its still the same project, and arguably people should be able to find it most easily using its current name. This is contrasted with a fork, where you'd want both, since a fork didn't occur. As for historical searches, if a search can be done on content and not just the name, then presumably the content will mention the old name a lot and it would be found that way. Speaking for myself, when a rename occurs, my "Changes" file still has a record of prior names, though generally no other files mention the old name.
In other words, I suggest just rename the repository and be done with it. No complication of mirroring. A search on the old name should still be able to find it under the new name.
This can be accomplished using backpan_normalize_dist_names and backpan_normalize_releases in .gitpan. I'll leave untangling the Muldis history for someone to tackle.