21–30 of 212 posts
Was Github ruled out because it's not free enough in spirit or are the Gnome folks just wanting to run things on-prem?
… and closed about a bazillion bugs I filed over the years in the process without (apparently) migrating them, too. … though I am pretty sure they left the bugs in the source intact.
Are your bazillion bugs not in the ~14k issues that are on their gnome project page? https://gitlab.gnome.org/groups/GNOME/-/issues
> There are no issues to show.
With the sole exception of one e-mail from legacy Bugzilla:
> This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.
That one that HAS been migrated appears as follows:
> You can subscribe and participate further through the new bug through this link to our GitLab instance: …
… and closed about a bazillion bugs I filed over the years in the process without (apparently) migrating them, too. … though I am pretty sure they left the bugs in the source intact.
Are your bazillion bugs not in the ~14k issues that are on their gnome project page? https://gitlab.gnome.org/groups/GNOME/-/issues
Was Github ruled out because it's not free enough in spirit or are the Gnome folks just wanting to run things on-prem?
Probably because Github is a closed-source company that can remove you, your repo, or your group at any time, for any reason. Committing to a hosted service is a bad idea (see: Sourceforge). That sort of thing isn't acceptable to a project like Gnome.
Earlier quoted context omitted.
It's a fundamental problem of open source projects hosting on GitHub. I don't think the the Fossil colocation model is necessarily right, but some open protocol is needed so that issues can be easily migrated between these services.
Is it really that hard to write a little script to copy the issues over? Github has an exceptional API.
Back then, I managed to get approval from all our contributors/issue authors so that their individual bugs and comments would show up as their individual bugs and comments, as well as retaining issue numbers.
This is the code for it, if anyone is interested, but as I said the whole thing is unsupported now: https://github.com/jleclanche/bugzilla-to-github
Earlier quoted context omitted.
It's a fundamental problem of open source projects hosting on GitHub. I don't think the the Fossil colocation model is necessarily right, but some open protocol is needed so that issues can be easily migrated between these services.
Is it really that hard to write a little script to copy the issues over? Github has an exceptional API.
Earlier quoted context omitted.
Probably because Github is a closed-source company that can remove you, your repo, or your group at any time, for any reason. Committing to a hosted service is a bad idea (see: Sourceforge). That sort of thing isn't acceptable to a project like Gnome.
By committing to use GitHub, you’re only really committing to git. git supports multiple remotes for the purposes of mirroring — use that feature .
You don't use github just for git.
You use it for issue tracking, pull requests and code review, CI hooks, wiki, github pages, kanban boards, bot integration, and so on.
That's all stuff that locks you in to Github, and is non-trivial to migrate to another provider.
… and closed about a bazillion bugs I filed over the years in the process without (apparently) migrating them, too. … though I am pretty sure they left the bugs in the source intact.
… and closed about a bazillion bugs I filed over the years in the process without (apparently) migrating them, too. … though I am pretty sure they left the bugs in the source intact.