https://bugzilla.wikimedia.org/show_bug.cgi?id=68054
--- Comment #1 from [email protected] --- > If it was a conscious choice to do this I'm curious why. We want all gerrit repos replicated on github. We could setup replication for each repository in our gerrit separately. That would allow full control of repository names at github. But it is tedious, time-consuming, and has other warts too. So in order to escape such a messy, verbose replication setup, gerrit replicates each and every projects to github under the name that gets used on gerrit [1]. For this replication, we do not prune leading paths, as that would map different names on gerrit to the same names on github [2]. However, some people felt strongly that they needed a better repository name on github, or had a following on github that they would not want to loose. So they had an additional, separate replication target set up. And hence, those repositories get replicated twice to github. Once for the canonical name. And a second time for the custom name of their liking. > Also note that GitHub supports renaming of repositories and > automatically keeps redirects[...] Thanks! That wasn't available when we added custom replication. We could use that to solve most issues. > As an example I've created a redirect from > https://github.com/wikimedia/mediawiki to > https://github.com/wikimedia/mediawiki-core. Eventually this should be > done the other way around [...] Not too sure about this one. Doing it “the other way around” would make it even more confusing for people, because the “canonical” github name would differ from the gerrit name too much to be able to map it clearly. [1] github does not like “/”s in repo names, so we're having them replaced by “-”s. [2] For example we currently have three repositories in gerrit that end in “/data”. Or which of “analytics/kraken” and “analytics/vagrant/kraken” should become github's “kraken”? Same problems for “/Nostalgia”. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
