From: Eric Gallager via Gdb <gdb@sourceware.org>
To: Mark Wielaard <mark@klomp.org>
Cc: binutils@sourceware.org, gcc@gcc.gnu.org, gdb@sourceware.org,
newlib@sourceware.org, libc-alpha@sourceware.org,
forge@sourceware.org
Subject: Re: Sourceware forge experiment
Date: Thu, 24 Oct 2024 15:44:10 -0400 [thread overview]
Message-ID: <CAMfHzOu83FihjWQ0bkFVN8QxQnbUi=BwmKdo8npCXQWnYSLZAw@mail.gmail.com> (raw)
In-Reply-To: <20241021012256.GE20500@gnu.wildebeest.org>
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
next prev parent reply other threads:[~2024-10-24 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 1:22 Mark Wielaard
2024-10-24 15:29 ` Automatic URLs in forgejo? (was Re: Sourceware forge experiment) David Malcolm via Gdb
2024-10-24 15:36 ` Richard Earnshaw (lists) via Gdb
2024-10-24 15:42 ` Jonathan Wakely via Gdb
2024-10-24 15:43 ` Jonathan Wakely via Gdb
2024-10-24 19:44 ` Eric Gallager via Gdb [this message]
2024-10-24 20:02 ` Sourceware forge experiment Jonathan Wakely via Gdb
2024-11-08 13:07 ` Mark Wielaard
2024-10-24 20:25 ` Andrew Pinski via Gdb
2024-10-24 20:29 ` Andrew Pinski via Gdb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMfHzOu83FihjWQ0bkFVN8QxQnbUi=BwmKdo8npCXQWnYSLZAw@mail.gmail.com' \
--to=gdb@sourceware.org \
--cc=binutils@sourceware.org \
--cc=egall@gwmail.gwu.edu \
--cc=forge@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=newlib@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox