Re: Sourceware forge experiment

On Thu, 24 Oct 2024 at 20:44, Eric Gallager <[email protected]> wrote:

> On Sun, Oct 20, 2024 at 9:27 PM Mark Wielaard <[email protected]> wrote:
> >
> > As an experiment Sourceware is now running an forgejo v9 instance at
> > https://forge.sourceware.org
> >
> > Everybody with an @sourceware.org, @cygwin.com or @gcc.gnu.org address
> > can register an account (please use the same user name as your account
> > name).
> >
> > The setup has disabled most "extras" (no badges, stars, issues, wikis,
> > packages, timetracking, milestones, etc.). And users can only fork
> > existing repos (it has mirrors of various sourceware projects).
>
> Is the intent to get mirrors of all of them on there at some point?
>

It's an experiment for people who want to try it out, I don't really see
why every project needs to be mirrored there. If nobody from project xyz is
interested in experimenting with forgejo, why bother mirroring that
project's repo?

I'm only seeing a few at the moment...
>
> > Some things haven't been setup yet (external trackers/bugzilla, incoming
> > email, ci, etc.)
>
> I was able to get the link to an external tracker (the gcc bugzilla)
> set up in my "gcc-mirror" fork:
> https://forge.sourceware.org/egallager/gcc-mirror
>
> >
> > The full setup can be found in this git repository:
> > https://sourceware.org/cgit/forge/
> >
> > For now it is only open for existing maintainers/developers for
> > experimentating with a pull-request model.
>
> So, I tested this out: I forked the gcc-mirror and gcc-wwwdocs-mirror
> repos, but it looks like the mirror ones aren't accepting PRs at the
> moment, so I tried forking their "-TEST" variants, but it looks like
> it won't let me make a fork of the "-TEST" copy since I already have a
> fork of the "-mirror" one? When I click the "fork" button on one of
> the "-TEST" repos, it just redirects me back to my existing "-mirror"
> fork of the corresponding "-mirror" one...
>

Go to the -mirror project's settings and delete the repo. You'll be able to
fork the -TEST one after that.


>
> > We can add others as long as they understand this is an experiment
> > and does not mean projects are accepting patches through it.
> > Contributions should still be sent through the mailinglists.
> >
> > There is also a new mailinglist for discussion about the setup and the
> > best way to create a pull-request workflow. Please subscribe if you
> > create an account and mention which project/organization you would
> > like do some experiments for. We can then add you to that organization.
> >
>
> ...is subscribing necessary? I'm trying to limit my subscriptions...
>

> > https://sourceware.org/mailman/listinfo/forge
>