From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: simon.marchi@polymtl.ca, tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: Gerrit
Date: Tue, 15 Oct 2019 17:09:00 -0000 [thread overview]
Message-ID: <874l0aszoe.fsf@redhat.com> (raw)
In-Reply-To: <83sgnuezpo.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 15 Oct 2019 19:32:51 +0300")
On Tuesday, October 15 2019, Eli Zaretskii wrote:
>> From: Sergio Durigan Junior <sergiodj@redhat.com>
>> Cc: Simon Marchi <simon.marchi@polymtl.ca>, tom@tromey.com, gdb-patches@sourceware.org
>> Date: Tue, 15 Oct 2019 11:57:54 -0400
>>
>> > What is the nature of the affiliation of the site where we use Gerrit
>> > with the GDB project? If the affiliation is lose enough, maybe this
>> > is not a problem for us.
>>
>> There is no official affiliation, I think. The instance was set up by
>> Simon and I, with the help of the OSCI folks, who provides the
>> infrastructure.
>
> Who are the OSCI folks, and why do they provide the infrastructure you
> needed for setting up this service?
https://osci.io/
They provide the infrastructure because I asked them if they could.
My initial plan was to host gerrit on sourceware, but after a bit of
discussion on #overseers, I realized that it would be hard to run the
latest version of gerrit on the machine. Moreover, unfortunately gerrit
doesn't handle user registration by itself, so that meant that I'd have
to set up something for that as well (we all have users on sourceware,
but they don't have passwords associated with them).
The current plan is to run gerrit on the OSCI infrastructure for a
while, and see if the GDB community likes it. If we do, and if we
decide we want to make gerrit our official patch review system, then we
will eventually migrate our instance to sourceware. When that time
comes, we should probably resurrect this conversation, because then the
repository will be hosted in an "official" resource.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2019-10-15 17:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 4:54 [PATCH] gdb: remove unused includes from dwarf2read.c Simon Marchi
2019-10-14 14:22 ` Simon Marchi
2019-10-14 14:39 ` Eli Zaretskii
2019-10-14 15:18 ` Simon Marchi
2019-10-14 17:12 ` Gerrit (was: [PATCH] gdb: remove unused includes from dwarf2read.c) Eli Zaretskii
2019-10-14 17:31 ` Gerrit Simon Marchi
2019-10-14 17:56 ` Gerrit Eli Zaretskii
2019-10-14 18:03 ` Gerrit Tom Tromey
2019-10-14 18:32 ` Gerrit Eli Zaretskii
2019-10-15 1:33 ` Gerrit Simon Marchi
2019-10-15 8:51 ` Gerrit Eli Zaretskii
2019-10-15 15:57 ` Gerrit Sergio Durigan Junior
2019-10-15 16:33 ` Gerrit Eli Zaretskii
2019-10-15 17:09 ` Sergio Durigan Junior [this message]
2019-10-15 17:31 ` Gerrit Eli Zaretskii
2019-10-15 17:49 ` Gerrit Sergio Durigan Junior
2019-10-14 23:51 ` Gerrit Simon Marchi
2019-10-14 18:02 ` [PATCH] gdb: remove unused includes from dwarf2read.c Luis Machado
2019-10-14 20:58 ` Simon Marchi
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=874l0aszoe.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tom@tromey.com \
/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