JeroenDeDauw added a comment. I strongly dislike moving all repositories used by Wikidata to Gerrit. The same goes for any such general policy, such as forcing people to use a particular OS or IDE. If the people that contribute to a repository most want to have it at a given location, than let them. I'm much more happy with the GitHub workflow and flexibility than with Gerrit. However I am not arguing that Wikibase Repository should be moved to GitHub. Neither am I arguing against moving WikimediaBadges to Gerrit, if that is what the people working on it desire.
A lot of the components used by the Wikidata project get significant contributions from people not explicitly inside of the Wikidata team. The opinions of these people should also be held into account. People such as Bene, Lazowik, Addshore, Tpt and indeed myself. The two main authors of Wikibase DataModel Serailization are Tpt and me. The main author of Diff is me. Additional objection comes from me being highly dubious about ideological undertone of this proposal: "Github is not free software". WMDE uses other non-free software. Should we spend our time on addressing that rather than our departments actual goals? And if we should, should it not be done a bit more holistically? While the non free services we use might not be "ideologically pure", they have provided good value for little effort in the past. Unlike several solutions we set up in-house. We have spend way less time on configuring TravisCI than on Jenkins, and less time on Configuring ScrutinizerCI than our own in house code coverage collector, yet the former provided more features and flexibility in both instances. I'm also not happy with how this discussion was held. Very different concerns are put forwards and then argumentation is provided about why this solution addresses them. This comes over to me as trying to find reasons for an approach after deciding it is a good one. (I am not saying that is anyone’s intention, just that it comes over that way.) It also deludes the discussion, making it hard to find agreement on concrete points. For instance, the location of issues/tasks has been brought up. Moving the repositories to gerrit gets rid of the GitHub issue trackers. One can simply close the GitHub issue trackers if them being open is the issue. This also makes us gloss over the real mismatch of concerns about the issues/tickets: we want to be able to track all sprint items in one place. Everyone agrees with that (as far as I know). The contention is about what kind of tasks should be tracked by sprints, which is a question of scrum process, and very far removed from where one puts their git repos. Pulling code from GitHub has been mentioned as a concern by OP. If read-only mirroring on Gerrit is an acceptable approach for this party libraries, then why not do the same for the components who's principal authors prefer GitHub? That is an acceptable compromise for me. TASK DETAIL https://phabricator.wikimedia.org/T74907 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: JeroenDeDauw Cc: Addshore, Liuxinyu970226, Ricordisamoa, chasemp, mmodell, Abraham, Aklapper, thiemowmde, Qgil, Snaterlicious, daniel, adrianheine, Tobi_WMDE_SW, GPHemsley, Legoktm, JeroenDeDauw, JanZerebecki, aude, Glaisher, MZMcBride, Lydia_Pintscher, Dereckson, hoo, Wikidata-bugs, greg _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
