Re: git: GitHub, Forgejo (was – in quotation marks – "Why I am retiring from contributing to FreeBSD")

On Fri, 2 Jan 2026 17:42:45 -0700
Warner Losh <imp@bsdimp.com> wrote:

> On Fri, Jan 2, 2026, 5:32 PM Graham Perrin <grahamperrin@gmail.com> wrote:
> 
> > On 02/01/2026 15:09, Warner Losh wrote:
> >
> > >     …
> > >
> > >
> > > Bugzilla is a bad place to submit. It's a terrible code review tool. …
> >
> > …
> >
> > > … We're working on … getting a forgejo instance up.
> >
> >
> > 👍
> >
> > So (Warner, please correct me if I'm wrong) a Forgejo working group has
> > superseded the github automation working group …
> >
> 
> No. They are parallel efforts due to uncertain timelines. We need to get
> more out of github in the interim. We always knew our tennancy there would
> only be supplamental. The nature of the supplement will change when we move
> to forgejo.
> 
> If nothing else, i think we need to change ports to better align with
> what's working. So some changes are needed there. And we need to quickly
> tighten up the src side too.
> 
> Warner

Glad to know that!

Once Forgejo instance hosted / managed by FreeBSD project (member) or
FreeBSD Foundation becomes in use, I'll be happy to register and use it,
in parallel with current Bugzilla and Phabricator to see how it goes.

IMHO, why Bugzilla is needed is to report bugs / wants without
patches / codes that there's nothing to "review".

Regards.

> <https://lists.freebsd.org/archives/freebsd-git/>
> >
> > <https://wiki.freebsd.org/WorkingGroup/>
> >
> > <https://lists.freebsd.org/archives/freebsd-git/2024-June/000241.html>,
> > <https://wiki.freebsd.org/WorkingGroup/Github> (2024)
> >
> > ----
> >
> > <
> > https://lists.freebsd.org/archives/freebsd-hackers/2026-January/005440.html>
> >
> > Mark, I think the answer is freebsd-git@


-- 
Tomoaki AOKI    <junchoon@dec.sakura.ne.jp>