Suggestion to move from Sourceforge/Mercurial to a more modern platform
60 views
Skip to first unread message
Kyle Maas
Oct 6, 2026, 12:28:02 PMOct 6
to hugi...@googlegroups.com
There are several new hosted git platforms for open source projects
which support easy forking, issue tracking, and pull requests.
Searching through the mailing list archives, it looks like it's been
brought up before and it looked like there were a lot of people onboard
with it, and then the efforts just kind of fizzled out. I fully
understand an aversion to Github, but is there a reason other than the
work involved to not move to something like GitLab, Codeberg, a Gitea
instance, or any number of other tools?
(For the record, since this was brought up in one of the threads I found
in the archives, I do not work for or have any affiliation with any of
them. It's just that the barrier to entry right now to help out is
fairly high, and frankly nothing else I work on now uses Mercurial. I
come from a Subversion background, and there's still almost nothing I
work on anymore using SVN. I liked SVN better than git, but ultimately
it's a lot easier anymore to find developers (or technical users who can
be converted into developers) who use git than anything else. But even
if everyone wanted to stick with Mercurial, a Mercurial host with patch
management or the equivalent of pull requests would make things a lot
nicer to work on.)
Warm Regards,
Kyle Maas
which support easy forking, issue tracking, and pull requests.
Searching through the mailing list archives, it looks like it's been
brought up before and it looked like there were a lot of people onboard
with it, and then the efforts just kind of fizzled out. I fully
understand an aversion to Github, but is there a reason other than the
work involved to not move to something like GitLab, Codeberg, a Gitea
instance, or any number of other tools?
(For the record, since this was brought up in one of the threads I found
in the archives, I do not work for or have any affiliation with any of
them. It's just that the barrier to entry right now to help out is
fairly high, and frankly nothing else I work on now uses Mercurial. I
come from a Subversion background, and there's still almost nothing I
work on anymore using SVN. I liked SVN better than git, but ultimately
it's a lot easier anymore to find developers (or technical users who can
be converted into developers) who use git than anything else. But even
if everyone wanted to stick with Mercurial, a Mercurial host with patch
management or the equivalent of pull requests would make things a lot
nicer to work on.)
Warm Regards,
Kyle Maas
T. Modes
Oct 6, 2026, 1:31:19 PMOct 6
to hugin and other free panoramic software
kylem...@gmail.com schrieb am Dienstag, 6. Oktober 2026 um 18:28:02 UTC+2:
But even if everyone wanted to stick with Mercurial, a Mercurial host with patch
management or the equivalent of pull requests would make things a lot
nicer to work on.)
Like merge requests https://sourceforge.net/p/hugin/hugin/merge-requests/?status=all ?
Kyle Maas
Oct 6, 2026, 1:41:52 PMOct 6
to hugi...@googlegroups.com
Yep. Exactly like that. Didn't know
SourgeForge had that now. Is there anywhere where issues are
tracked?
Warm Regards,
Kyle Maas
Kyle Maas
--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/hugin-ptx/d641f330-a685-4673-8c63-f04fbe69fd88n%40googlegroups.com.
T. Modes
Oct 6, 2026, 1:49:58 PMOct 6
to hugin and other free panoramic software
kylem...@gmail.com schrieb am Dienstag, 6. Oktober 2026 um 19:41:52 UTC+2:
Yep. Exactly like that. Didn't know SourgeForge had that now. Is there anywhere where issues are tracked?
(mentioned on the website https://hugin.sourceforge.io/ , in the README and the help files on the main page https://wiki.panotools.org/Hugin and https://wiki.panotools.org/Hugin_Trackers just to mention some places)
Kyle Maas
Oct 6, 2026, 3:44:01 PMOct 6
to hugi...@googlegroups.com
Perfect. Thank you! I'll see what I
can do to help.
Warm Regards,
Kyle Maas
Kyle Maas
--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/hugin-ptx/2a032e6d-0401-4575-80a1-3e9d81a1e8c1n%40googlegroups.com.
Bruno Postle
Oct 7, 2026, 6:25:31 PMOct 7
to hugi...@googlegroups.com
At this point the only reason to switch to Github is because that is where all the users are, Sourceforge is otherwise functionally equivalent with git support, pull-requests etc..
I did plan on migrating the panotools repositories from mercurial to git, but staying with Sourceforge for now. As a test I have migrated the Panotools::Script perl module: https://sourceforge.net/p/panotools/panotools-script/
This was quite easy in the end, here are my steps:
# use hg-fast-export to convert a local hg repo to git
git clone https://github.com/frej/fast-export.git
git init Panotools-Script.git
cd Panotools-Script.git/
../fast-export/hg-fast-export.sh -r ../Panotools-Script.hg/
# hg-fast-export creates a master branch, rename this to main
git checkout master
git branch -m master main
# this repo started as CVS, use git-filter-repo and a custom mailmap to fix some missing email addresses
git filter-repo --mailmap mailmap --force
# create a git repo on sourceforge and push (just the main branch needed for this repo)
git remote add origin ssh://bruno...@git.code.sf.net/p/panotools/panotools-script
git push -u origin main
git clone https://github.com/frej/fast-export.git
git init Panotools-Script.git
cd Panotools-Script.git/
../fast-export/hg-fast-export.sh -r ../Panotools-Script.hg/
# hg-fast-export creates a master branch, rename this to main
git checkout master
git branch -m master main
# this repo started as CVS, use git-filter-repo and a custom mailmap to fix some missing email addresses
git filter-repo --mailmap mailmap --force
# create a git repo on sourceforge and push (just the main branch needed for this repo)
git remote add origin ssh://bruno...@git.code.sf.net/p/panotools/panotools-script
git push -u origin main
--
Bruno
Reply all
Reply to author
Forward
0 new messages