Sourceware forge experiment

Sourceware forge experiment

[Mark Wielaard]

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). Some
things haven't been setup yet (external trackers/bugzilla, incoming
email, ci, etc.)

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. 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.

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

Automatic URLs in forgejo? (was Re: Sourceware forge experiment)

[David Malcolm via Gdb]

On Mon, 2024-10-21 at 03:22 +0200, Mark Wielaard 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). Some
> things haven't been setup yet (external trackers/bugzilla, incoming
> email, ci, etc.)
> 
> 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. 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.
> 
> https://sourceware.org/mailman/listinfo/forge

Thanks for setting this up.

How easy would it be to set up automatic URL generation in the web UI
from regexes on the text of commit subjects/message? 

GCC has its own short notation for referring to commits, see e.g. 

https://forge.sourceware.org/gcc/gcc-mirror/commit/83abdb041426b7490e93c3f77be93148bcd94de3
where I wrote:
"I believe this hasn't been necessary since r15-1413-gd3878c85f331c7."
It would be nice if the "r15-1413-gd3878c85f331c7" were to get auto-
urlified in the web UI to
https://forge.sourceware.org/gcc/gcc-mirror/commit/d3878c85f331c7

Similarly, in GCC we use the notation PRnnnnnn or PR component/nnnnnn
to refer to "problem reports" in bugzilla.  Looking at e.g.
https://forge.sourceware.org/gcc/gcc-mirror/commit/65c5bbe1c92f9c08e99d3a37c136f2ef9804a37f
it would be nice if the "PR114423" in the subject line and the 
"PR preprocessor/114423" in the ChangeLog fragments in the commit log
got auto-urlified in the web UI to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114423

Other projects sharing the forgejo instance have other notations,
policies, and bug tracker instances, of course.

FWIW I seem to recall seeing something like this working in the
instance that was recently demoed at Cauldron.

Hope this is constructive; thanks again
Dave

Re: Automatic URLs in forgejo? (was Re: Sourceware forge experiment)

[Richard Earnshaw (lists) via Gdb]

On 24/10/2024 16:29, David Malcolm wrote:
> On Mon, 2024-10-21 at 03:22 +0200, Mark Wielaard 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). Some
>> things haven't been setup yet (external trackers/bugzilla, incoming
>> email, ci, etc.)
>>
>> 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. 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.
>>
>> https://sourceware.org/mailman/listinfo/forge
> 
> Thanks for setting this up.
> 
> How easy would it be to set up automatic URL generation in the web UI
> from regexes on the text of commit subjects/message? 
> 
> GCC has its own short notation for referring to commits, see e.g. 
> 
> https://forge.sourceware.org/gcc/gcc-mirror/commit/83abdb041426b7490e93c3f77be93148bcd94de3
> where I wrote:
> "I believe this hasn't been necessary since r15-1413-gd3878c85f331c7."
> It would be nice if the "r15-1413-gd3878c85f331c7" were to get auto-
> urlified in the web UI to
> https://forge.sourceware.org/gcc/gcc-mirror/commit/d3878c85f331c7
> 
> Similarly, in GCC we use the notation PRnnnnnn or PR component/nnnnnn
> to refer to "problem reports" in bugzilla.  Looking at e.g.
> https://forge.sourceware.org/gcc/gcc-mirror/commit/65c5bbe1c92f9c08e99d3a37c136f2ef9804a37f
> it would be nice if the "PR114423" in the subject line and the 
> "PR preprocessor/114423" in the ChangeLog fragments in the commit log
> got auto-urlified in the web UI to:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114423
> 

See the wiki page I added today for setting up bugzilla (gcc.gnu.org/wiki/ForgeExperiment).  It only works for the <component>/<id> style due to limitations in the way forgejo uses the regex groups.


> Other projects sharing the forgejo instance have other notations,
> policies, and bug tracker instances, of course.
> 
> FWIW I seem to recall seeing something like this working in the
> instance that was recently demoed at Cauldron.
> 
> Hope this is constructive; thanks again
> Dave
> 

Re: Automatic URLs in forgejo? (was Re: Sourceware forge experiment)

[Jonathan Wakely via Gdb]

On Thu, 24 Oct 2024 at 16:29, David Malcolm <dmalcolm@redhat.com> wrote:

> On Mon, 2024-10-21 at 03:22 +0200, Mark Wielaard 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). Some
> > things haven't been setup yet (external trackers/bugzilla, incoming
> > email, ci, etc.)
> >
> > 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. 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.
> >
> > https://sourceware.org/mailman/listinfo/forge
>
> Thanks for setting this up.
>
> How easy would it be to set up automatic URL generation in the web UI
> from regexes on the text of commit subjects/message?
>

Currently not possible, but there's an upstream feature request to support
it:
https://codeberg.org/forgejo/forgejo/issues/3274

Re: Automatic URLs in forgejo? (was Re: Sourceware forge experiment)

[Jonathan Wakely via Gdb]

On Thu, 24 Oct 2024 at 16:42, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:

>
>
> On Thu, 24 Oct 2024 at 16:29, David Malcolm <dmalcolm@redhat.com> wrote:
>
>> On Mon, 2024-10-21 at 03:22 +0200, Mark Wielaard 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). Some
>> > things haven't been setup yet (external trackers/bugzilla, incoming
>> > email, ci, etc.)
>> >
>> > 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. 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.
>> >
>> > https://sourceware.org/mailman/listinfo/forge
>>
>> Thanks for setting this up.
>>
>> How easy would it be to set up automatic URL generation in the web UI
>> from regexes on the text of commit subjects/message?
>>
>
> Currently not possible, but there's an upstream feature request to support
> it:
> https://codeberg.org/forgejo/forgejo/issues/3274
>

(which is also noted on the wiki page)

Re: Sourceware forge experiment

[Eric Gallager via Gdb]

On Sun, Oct 20, 2024 at 9:27 PM Mark Wielaard <mark@klomp.org> 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?
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...

> 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

Re: Sourceware forge experiment

[Jonathan Wakely via Gdb]

On Thu, 24 Oct 2024 at 20:44, Eric Gallager <egall@gwmail.gwu.edu> wrote:

> On Sun, Oct 20, 2024 at 9:27 PM Mark Wielaard <mark@klomp.org> 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
>

Re: Sourceware forge experiment

[Mark Wielaard]

Hi Eric,

On Thu, 2024-10-24 at 15:44 -0400, Eric Gallager wrote:
> On Sun, Oct 20, 2024 at 9:27 PM Mark Wielaard <mark@klomp.org> 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?
> I'm only seeing a few at the moment...

To see how well it scales a couple more sourceware projects now have a
mirror on the forge: https://forge.sourceware.org/explore/organizations
gcc, binutils-gdb, glibc, elfutils, newlib, valgrind, debugedit,
bunsen, annobin, bzip2, cgen, dwz, insight, libabigail and systemtap.

If you are interested in others, please just ask.
https://sourceware.org/projects.html

> > 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

It isn't necessary, but it is a good place to discuss the forge
experiment. You don't have to be subscribed to post and you can read
the archives through https://inbox.sourceware.org/forge (also through
nntp, imap, atom or git cloning the whole thing).

Cheers,

Mark

Re: Sourceware forge experiment

[Andrew Pinski via Gdb]

On Sun, Oct 20, 2024 at 6:26 PM Mark Wielaard <mark@klomp.org> 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). Some
> things haven't been setup yet (external trackers/bugzilla, incoming
> email, ci, etc.)
>
> 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. 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.

Is the pull request to the gcc:gcc-test repo limited? Do you need
extra permissions added to do it?
This was not mentioned so I thought I could register with my
@gcc.gnu.org account as the email and it would work.

Thanks,
Andrew Pinski

>
> 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.
>
> https://sourceware.org/mailman/listinfo/forge

Re: Sourceware forge experiment

[Andrew Pinski via Gdb]

On Thu, Oct 24, 2024 at 1:25 PM Andrew Pinski <pinskia@gmail.com> wrote:
>
> On Sun, Oct 20, 2024 at 6:26 PM Mark Wielaard <mark@klomp.org> 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). Some
> > things haven't been setup yet (external trackers/bugzilla, incoming
> > email, ci, etc.)
> >
> > 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. 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.
>
> Is the pull request to the gcc:gcc-test repo limited? Do you need
> extra permissions added to do it?
> This was not mentioned so I thought I could register with my
> @gcc.gnu.org account as the email and it would work.

Never mind, it is just brokeness of the way of the test repos work.
The problem will not show up in the final thing so I am less worried.

>
> Thanks,
> Andrew Pinski
>
> >
> > 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.
> >
> > https://sourceware.org/mailman/listinfo/forge