Oh, nice.
I'll send my future patches on the forgejo instance, then.
Le 2024-11-20 à 17 h 35, Mark Wielaard a écrit :
Hi Antoni,
On Wed, Nov 20, 2024 at 11:11:01AM -0500, Antoni Boucher wrote:
From what I understand, pull requests on forge.sourceware.org can be
removed at any time, so I could lose track of the status of my
patches.
It is an experiment, and the experiment could fail for various
reasons. At that point we could decide to just throw everything
away. But we wouldn't do that randomly and I think people are willing
to let the experiment run for at least a year before deciding it does
or doesn't work. And we would of course give people the chance to
migrate the work they want to preserve somewhere else (forgejo has
good import/export to various other forges).
We could also decide the current setup is not good (and admittedly the
-mirror/-test thing is a little odd) and change those names and/or
resetup those repos.
But interestingly it seems that wouldn't impact your workflow. Which I
hadn't even thought was possible. But I just tried on our forgejo
setup and of course it works. You can do pull request to your own fork
from one branch to another.
Seeing this already thought me something I didn't know was possible or
useful. But I can totally see now how these "self pull requests" help
someone keep track of their work.
I really like forgejo and use it for some of my personal projects.
If you still think there would be benefit in me sending patches to
forge.sourceware.org, please tell me and I'll try.
If another developer/maintainer like David is happy to try what you
already have been doing through github I think it would be
useful. Even if it doesn't work out for you that would be very
valuable feedback.
I do have to note that there are people a little nervous about reviews
completely "bypassing" the mailinglists. But that would be even more a
concern with using github for this.
Cheers,
Mark
