On 26/8/25 05:57, wirz wrote:
I do think it is about time Hugin/panotools switched to git. There is
a lot
to like about mercurial, but git won. Also switching to git would make
migration away from sourceforge easier if that needed to happen.
Yes, git would be an improvement, and I'm pretty sure there is no
downside other than the one-time work of switching. I'm not saying
that isn't work of course.
I am not a contributor, but yes I think Git is the clear winner in the
VCS scope.
What would have an even higher benefit to me would be to use a
platform where patches can be contributed through pull requests or
similar, instead of uploading patches as single files / zipped
collections of files. And the notifications on launchpad seem to be
broken -- I'm seeing that in both directions, which makes it less
attractive to contrib patches, etc. I'd probably do more if it were
simpler.
Pull Requests/Merge Requests are a great way to allow new users to
easily contribute, I agree!
But I think github should serve as a cautionary tale: I have perceived
them as beyond any doubt 10 years ago, while now I perceive github
mostly as a tool for Microsoft to collect LLM training material.
GitHub is indeed a rather different place than it was 10 years ago, it
is now an AI training source and has now been handed to Microsoft's AI
team to run, which leaves a sick feeling in my stomach. Self-hosted
platforms are fairly easy to set up and manage, or there are great
alternatives like Codeberg (as well as plenty of others) if you don't
have the time or inclination to self-host.
Regards,
Justin
--
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/hugin-ptx/ac0ed2c5-088e-413b-8aaa-ff04bc1dece5%40gmail.com.
