https://bugzilla.wikimedia.org/show_bug.cgi?id=72907
--- Comment #2 from Jan Zerebecki <[email protected]> --- (In reply to Jeroen De Dauw from comment #1) > First of all, why? Why were they not put on gerrit to begin with? 1) For consistency; it just corrects a mistake. Contributions and review can then be done in one place. 2) Because a build of stuff deployed on the WMF cluster should not need external services. 3) Github is not free software. > Secondly, we cannot do this without forking certain repos. Which ones are you thinking of? For stuff that are external libraries maintained by non-mediawiki communitites that are pulled in during a Wikidata build, a mirror on gerrit is sufficient, but lets only take a stab at that after the rest is done. > Also, we already had this discussion, and esentially decided to have > components that depend on MediaWiki be on Gerrit and those that don't on > GitHub. Which is why I wonder why this bug appears all of a sudden. Can you link to this discussion? > I'd like to so a good justification that holds into account the > disadvantages and costs of a move for each individual component before it's > moved. What are the disadvantages? I'm not aware of any. The cost is: Create gerrit repo; create phabricator project; merge any open pull requests; git push into gerrit; move over any old pull requests that can't be merged yet; move over any open bug reports; update repo URL where it is used; put old repo in deprecated state. Not that big IMHO. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
