Sourceforge has been getting some bad press as of late, and tbh, being on Sourceforge gives us very little.
Should we stay or should we go?
The only thing we really use on it is their svn server, but that's incidental. Going to open a bug about moving to Git too for vcs; moving to wmf gerrit/github would hence therefore fix this bug also...
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Request | None | T101051 Migrate AWB away from SourceForge? | ||
| Resolved | Reedy | T102425 Backup AWB SVN repo | |||
| Open | Request | None | T101053 Switch AWB from SVN to Git? |
Is there anything any of us can do to help with this? This doesn't seem like something we can do much to help you with but if I'm wrong let me know and I'll do what I can.
I think the decision just needs to be made that this is something we want to do. And that all current developers are ok with git, see also T101053
I've been mirroring the SVN repo to https://github.com/reedy/autowikibrowser on an adhoc basis. I think I might want to create an AutoWikiBrowser "organization" on github if we went that route, and then move that repo from my ownership, to the global
I'm leaning very much towards this. SFs sketchy behaviour as of late, and also the amount of downtime. I think it's about time
I think we only need to really get @Rjwilmsi to confirm he's ok with git (or ok to learn). If we grant push access, we can use it roughly like SVN, but have PR on github too...
If migrated to GitHub, I would be able to fix quick and dirty typo mistakes in the interface and easy fixes like that. I'm all for that alternative!
As a sidenote: migrating all the eggs of the whole world into one basket of github seem to be a bad long-term strategy. I'd say doing it independently should be preferred.
It is excellent idea. On git i can make changes, on svn i can not. To awb is on git, i would solve several tasks.
No
T101053: Switch AWB from SVN to Git? could be done without moving away from SourceForge.
T102427: Re-migrate AWB svn repo to git? has the repo link https://github.com/reedy/autowikibrowser - The task is about whether I re-do the export from scratch to fix a few little issues
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".)