Should we? See also T101051
I know @Magioladitis and @Rjwilmsi aren't familiar with git, but we can use it in a similar way to SVN
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Request | None | T102427 Re-migrate AWB svn repo to git? | ||
| Open | Request | None | T101051 Migrate AWB away from SourceForge? | ||
| Open | Request | None | T101053 Switch AWB from SVN to Git? |
Event Timeline
Comment Actions
While Phabricator would be good to have everything at one place, and Gerrit being a WMF-site, GitHub seems to be a place whre more users could help out with (given GitHub's online editing mode), problem with that being that not all of you devs. know how to use it.
Comment Actions
Gerrit, and likely Differential , promote much better code review processes/quality than Github.
Comment Actions
I'm not adversed to Gerrit/Differential. The barrier to entry for Windows (which, most of the developers of AWB are going to), to run git review and such can be a PITA
Comment Actions
In general, please do not add "me too" or "I like green more than yellow" comments to any tasks.
Personal preferences don't add anything substantial to the discussion and create notifications for everybody. Thanks.
Comment Actions
The previous comments don't explain what/who exactly this task is stalled on ("If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on"). Hence resetting task status.
(Smallprint, as general orientation for task management: If work on this task is blocked by another task, then that other task should be added via Edit Related Tasks... → Edit Subtasks. If this task is stalled on an upstream project, then the Upstream tag should be added. If this task requires info from the task reporter, then there should be instructions which info is needed. If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead. If this task is out of scope and nobody should ever work on this, then task status should be "declined".)
Comment Actions
Given how most of the other devs have moved on, and that WMF is moving to Gitlab Soon (maybe this project would be a good one just to establish it works at a minimum), Gitlab might be a good time to move.
Comment Actions
fwiw, importing a github repo (like https://github.com/reedy/autowikibrowser) into gitlab should just be a few mouse clicks away.
While "importing svn repos from Phab" is still yet another open ticket at T308061.
Comment Actions
Yeah, given that we already have a git repo by reedy, it should be easy to migrate to https://gitlab.wikimedia.org or simply closing/archiving the sourceforge repo and deciding to have future development at GitHub. @Reedy: any opinions?
If we would like to migrate to GitLab, it looks like the next step would be submitting a form at https://phabricator.wikimedia.org/maniphest/task/edit/form/105/.
Comment Actions
So my thoughts are, yes it's about time and if nothing else it is probably proper that AWB is hosted on WMF infra (as a volunteer/community project) rather than third party.
However, I'm just doing this as a volunteer, I am not currently familiar with git beyond "git clone", so I would want a switch from SVN to git to be as simple as possible for me and other volunteer contributors. I want to be able to do the git basics - equivalent of SVN checkout, commit, update, revert and ideally have the minimum extra stuff on top. (Adding extra procedures would make this feel like 'work' to me and I already have an day job (unrelated) where I have procedures etc.)
So I'm willing to learn how to do the basics in git. But for now following T385222 I've got a new IDE to familiarize with and Linux testing to do. So I'd suggest @Reedy if you want to give some thought as to how WMF could host AWB in a novice-friendly way, maybe setup a trial instance (if you can readily refresh it from SVN again later), then ask me again say in a couple of weeks, I should be ready to work with you on getting switched over.
Comment Actions
I'm not in a particular rush, but "soon" would be nice.
Why I filed T385296: Unbreak/update my svn to git conversion..., but I'm not against re-doing it from scratch, as per T102427: Re-migrate AWB svn repo to git?.
It's not overly difficult, just some mapping and stuff to do.
I had an ad hoc mirror at https://github.com/reedy/autowikibrowser, that was done on a VM that no longer exists. I need to work out where I may have put the backup (if I kept one)... It's as far back as Sep 21, 2022.
I think I'm definitely tempted to use https://gitlab.wikimedia.org/ rather than https://gerrit.wikimedia.org/ for various reasons. Partly so you don't need to use git review.
To some extent, you can just keep pushing to master (git commit; git push), but we'll see. It would be semi nice to move away from doing that.
We might be able to even end up actually running some sort of CI. Amazing.
I'm obviously happy to sit down at some point and have a call to go through workflow stuff etc.