public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mark Wielaard <mark@klomp.org>
Cc: gdb@sourceware.org
Subject: Re: Sourceware joins Software Freedom Conservancy
Date: Tue, 16 May 2023 19:12:23 +0300	[thread overview]
Message-ID: <83lehoz254.fsf@gnu.org> (raw)
In-Reply-To: <d2a0c5489b28a69e2f4b4923c1ea3ea21fdbfca7.camel@klomp.org> (message from Mark Wielaard on Mon, 15 May 2023 21:00:00 +0200)

> From: Mark Wielaard <mark@klomp.org>
> Cc: gdb@sourceware.org
> Date: Mon, 15 May 2023 21:00:00 +0200
> 
> > Any chance you (or someone else "in the know") could explain what
> > does this mean in practical terms?
> 
> In practical terms it just means that Sourceware is a bit more
> organized/formalized.
> 
> >   E.g., do any of the addresses and URLs
> > we've been using for working on GDB will change in any way?
> 
> They will not.
> 
> >   What about access to the GDB Git repository?
> 
> That will be the same as before.
> We will just have more (redundant) backups, like those on sourcehut:
> https://sr.ht/~sourceware/binutils-gdb/sources
> 
> >   What about development procedures and practices?  Etc. etc.
> 
> This is only about the actual infrastructure services. You as gdb
> community of course still decide how to use those and what policies
> your projects uses.
> 
> > It is a bit strange that such an announcement talks at length about
> > everything except what the GDB developers and contributors need to
> > know.
> 
> Sorry, we were just excited about all the future potential.
> Hopefully the opportunity to protect the confidence in the long term
> future of Sourceware is also of interest to the gdb community.
> 
> See also the newly announced Sourceware Overseers Open Office hours:
> https://inbox.sourceware.org/overseers/20230515183216.GA11203@gnu.wildebeest.org/T/#u

Thanks for the useful info.

      reply	other threads:[~2023-05-16 16:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 18:18 Mark Wielaard
2023-05-15 18:44 ` Eli Zaretskii
2023-05-15 19:00   ` Mark Wielaard
2023-05-16 16:12     ` Eli Zaretskii [this message]

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=83lehoz254.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=mark@klomp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).