From: Juliana Sims <juli@incana.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
MSavoritias <email@msavoritias.me>,
ian@retrospec.tv
Cc: guix-devel@gnu.org
Subject: Re: Next Steps For the Software Heritage Problem
Date: Fri, 28 Jun 2024 14:01:52 -0400 [thread overview]
Message-ID: <43YSFS.1AUYM0TVIQQA2@incana.org> (raw)
Hey y'all,
I've avoided weighing in on this topic because I'm of two minds about
it. Still, when members of the community raise concerns, it's important
to take those concerns seriously. We must be careful how we address
them because the opinions and concerns of any community member are as
legitimate as those of any other.
This conversation has at times been contentious. People have not always
used the most diplomatic language. And yet, there has been a thorough
discussion of this topic. The conclusion appears to be that Guix cannot
make changes in relation to SWH. It's clear there is no more room for
productive conversation. I therefore echo Ludo's request to let this
topic drop.
I want to express my gratitude for a community where people are able to
express their concerns and have them taken seriously, regardless of who
they are. Let's not lose that. Let's not forget that, even when
passions are high, we all want Guix to succeed and have a healthy
community, and we all work to that end as best as we can with the
information and resources available to us.
Best,
Juli
next reply other threads:[~2024-06-28 18:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 18:01 Juliana Sims [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-19 7:52 Next Steps For the Software Heritage Problem Simon Tournier
2024-06-19 9:13 ` MSavoritias
2024-06-19 9:54 ` Efraim Flashner
2024-06-19 10:25 ` raingloom
2024-06-19 15:46 ` Ekaitz Zarraga
2024-06-20 6:36 ` MSavoritias
2024-06-20 14:35 ` Ekaitz Zarraga
2024-06-21 8:51 ` MSavoritias
2024-06-19 10:34 ` MSavoritias
2024-06-19 14:41 ` Simon Tournier
2024-06-20 6:51 ` MSavoritias
2024-06-20 14:40 ` Simon Tournier
2024-06-21 9:08 ` MSavoritias
2024-06-18 17:12 Andy Tai
2024-06-18 18:08 ` Ian Eure
2024-06-19 10:31 ` raingloom
2024-06-27 12:27 ` Ludovic Courtès
2024-06-27 15:30 ` Ian Eure
2024-06-27 16:48 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-27 16:58 ` Ludovic Courtès
2024-06-18 8:37 MSavoritias
2024-06-18 14:19 ` Ian Eure
2024-06-19 8:36 ` Dale Mellor
2024-06-20 17:00 ` Andreas Enge
2024-06-20 18:42 ` Dale Mellor
2024-06-20 20:54 ` Andreas Enge
2024-06-20 20:59 ` Ekaitz Zarraga
2024-06-20 21:12 ` Andreas Enge
2024-06-21 8:41 ` Dale Mellor
2024-06-21 9:19 ` MSavoritias
2024-06-21 13:33 ` Luis Felipe
2024-06-20 21:27 ` Simon Tournier
2024-06-18 16:21 ` Greg Hogan
2024-06-18 16:33 ` MSavoritias
2024-06-18 17:31 ` Greg Hogan
2024-06-18 17:57 ` Ian Eure
2024-06-19 7:01 ` MSavoritias
2024-06-19 9:57 ` Efraim Flashner
2024-06-20 2:56 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-20 5:18 ` MSavoritias
2024-06-19 10:10 ` Efraim Flashner
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=43YSFS.1AUYM0TVIQQA2@incana.org \
--to=juli@incana.org \
--cc=email@msavoritias.me \
--cc=guix-devel@gnu.org \
--cc=ian@retrospec.tv \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.