There will be no drastic changes. We'll keep improving services to
make the (email-based) workflows better and more efficient. But we
will also do an experiment with Forgejo to let people try out a pull
request workflow. We don't know if the experiment will be successful,
nobody will be forced to participate, but volunteers to try it out
(and help with the setup and configuration) are more than welcome. It
might take up to a year to determine whether the experiment is a
success or a failure.

Attached are the Sourceware BoF discussion topics and notes taken by
Elena during the discussions (the notes might note make much sense to
people not there, but feel free to ask questions if something seems
unclear).

Jonathan Wakely posted about editor config, b4 setup and signing your
git commits:
https://inbox.sourceware.org/CACb0b4kOiiwbMuT8BpG30+mg=yq+DSM+1s_gO_5CehSCy5MAmg@mail.gmail.com/
https://inbox.sourceware.org/CACb0b4=uX+P4Wc5VtJGTrh=yMH+OMz9vnXuU5LAVRkz3-ZZzmw@mail.gmail.com/
https://inbox.sourceware.org/gcc/CACb0b4=KewuK-oXhny_ojwgxewFrib3RrUezvow0ZdMJox-LbA@mail.gmail.com/

Nick Alcock posted about hardware-backed git commit and tag signing
https://inbox.sourceware.org/87ttebeokf.fsf@esperi.org.uk/
(This would require an ssh server version update.)

Note that GCC also has a https://gcc.gnu.org/wiki/GitCookbook which
might be interesting not just for GCC hackers, but also for other
Sourceware projects.

Bradley Kuhn posted about a talk at LPC that covered some of the same
issues we discussed at Cauldron "A little GitLab won't hurt you"
https://inbox.sourceware.org/F8FB9E25-F496-4932-B359-930E269F3CB7@sfconservancy.org/

Joseph Myers wrote up his desired features for a system providing pull
request functionality. Which is a good guide to follow when we are
experimenting with Forgejo to see how close we can come to this ideal.
https://inbox.sourceware.org/b440cf28-674b-122a-160b-0fb96bbf989b@redhat.com/

At the Cauldron I tried to suggest we might want to resurrect the
gerrit experiment. But people really didn't seem to be enthousiastic
about it (one could say they were the opposite of enthousiastic). So I
talked to Sergio Durigan Junior who originally setup the gerrit
instance. And we agreed to reuse the VM for the Forgejo experiment.

That VM should have enough resources for the initial experiment. I'll
talk to the Sourceware PLC to discuss what resources are needed if we
want to roll this out for all Sourceware projects. We already made an
estimate for a larger gitolite server as part of the Security Vision
document: https://sourceware.org/sourceware-security-vision.html
Part of the Forgejo experiment will be making sure resource estimates
are correct.

If there are people who have some experience setting up/configuring a
Forgejo service please let us know your experiences.