From: Efraim Flashner <efraim@flashner.co.il>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: John Kehayias <john.kehayias@protonmail.com>,
74549@debbugs.gnu.org, guix-maintainers@gnu.org
Subject: [bug#74549] News entry for the survey
Date: Thu, 28 Nov 2024 13:46:55 +0200 [thread overview]
Message-ID: <Z0hYL5cCjm4mdcKG@3900XT> (raw)
In-Reply-To: <87cyifkdpf.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]
On Thu, Nov 28, 2024 at 04:41:16PM +0900, Maxim Cournoyer wrote:
> Hi John,
>
> John Kehayias <john.kehayias@protonmail.com> writes:
>
> > Hi Maxim,
> >
> > On Thu, Nov 28, 2024 at 01:41 PM, Maxim Cournoyer wrote:
> >
> >> I'm a bit surprised by the need of a news entry for this; I'd typically
> >> consider only news that impact users, or at least the software that Guix
> >> constitutes, as news worthy :-). I wouldn't like the news channel to
> >> become some place where more "random" things get advertised, such as
> >> venues and what not.
> >>
> >> I'd prefer if this was kept to other communication channels, suchas the
> >> help-guix mailing list or the #guix IRC channel.
> >>
> >> My 2 cents!
> >
> > Apologies for perhaps rushing this. I should have asked around and
> > gotten some consensus before such a change to how we use news. While I
> > do think it can be useful for such a thing, I do agree that this
> > probably leads to an erosion of the intended purpose of guix pull
> > --news now that I think more about it.
>
> Perhaps I was a bit slow to answer -- I have a steady stream of messages
> to attend to.
>
> > Does it make sense to revert it (how does that end up working for
> > news)? I can revert with a note to keep news more directly
> > software-related, lest it sets a precedent. Though maybe this should
> > be opened up to wider discussion.
>
> I don't foresee a problem with reverting a news entry; people pulling to
> a commit before the reversal will see the news, those to a commit
> including it shouldn't see it.
>
> It's not a big deal, but in order to not set a precedent, I'd rather see
> it reverted. I've answered the survey, by the way!
I think we can wait until after the deadline ends to revert it, as long
as it's already there.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-11-28 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 20:22 [bug#74549] News entry for the survey John Kehayias via Guix-patches via
2024-11-27 6:14 ` bug#74549: " John Kehayias via Guix-patches via
2024-11-28 4:41 ` [bug#74549] " Maxim Cournoyer
2024-11-28 5:11 ` John Kehayias via Guix-patches via
2024-11-28 7:41 ` Maxim Cournoyer
2024-11-28 11:46 ` Efraim Flashner [this message]
2024-11-28 15:26 ` John Kehayias via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z0hYL5cCjm4mdcKG@3900XT \
--to=efraim@flashner.co.il \
--cc=74549@debbugs.gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=maxim.cournoyer@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).