News entry for the survey

Done

Details

3 participants

Efraim Flashner
John Kehayias
Maxim Cournoyer

Owner: unassigned

Submitted by: John Kehayias

Severity: normal

John Kehayias wrote on 26 Nov 2024 21:22

Recipients:(name . guix-patches@gnu.org)(address . guix-patches@gnu.org)(address . guix-maintainers@gnu.org)

Message-ID:87wmgpzqw1.fsf_-_@protonmail.com

Hi Guix,

Here's a quick patch to add a news entry about the survey before it closes on Sunday. I plan to push this later today in the interest of giving more time for people to see it, but wanted to send it for quick review if there is anything.

1. For the commit I just took a recent one as there is no associated commit. Is there something better?

2. The survey is "closing" at the end of Sunday Dec. 1st. We could specify end of that day local time perhaps? futurile said they won't open it until the following morning (UK) time, so I think that lines up with the end of Sunday everywhere. But not sure what is clearer.

Thanks!

John

From 43fc838ccb8c9ba9ada9f8c27ad3723eb7785b32 Mon Sep 17 00:00:00 2001
Message-ID: <43fc838ccb8c9ba9ada9f8c27ad3723eb7785b32.1732651474.git.john.kehayias@protonmail.com>
From: John Kehayias <john.kehayias@protonmail.com>
Date: Tue, 26 Nov 2024 15:02:35 -0500
Subject: [PATCH] news: Add entry for the guix survey.

Note: no associated commit, so took a recent one at the time of this writing.

* etc/news.scm: Add entry.

Co-authored-by: Steve George <steve@futurile.net>
Change-Id: Ia770d3e24bcdd167bf05d84b60151756ffa88f1c
---
 etc/news.scm | 8 ++++++++
 1 file changed, 8 insertions(+)

Toggle diff (23 lines)diff --git a/etc/news.scm b/etc/news.scm
index 0628b0fdb4..36b45ae936 100644
--- a/etc/news.scm
+++ b/etc/news.scm
@@ -34,6 +34,14 @@
 
 (channel-news
  (version 0)
+ (entry (commit "335f07eb47f7f900a6f11576ea6156c70b562208")
+        (title
+         (en "Please take the first Guix user and contributor survey!"))
+        (body
+         (en "We're running our first user and contributor survey to gather
+views across the community.  If you'd like to take part, please go to
+@url{https://guix.limesurvey.net/}.  Submissions close at the end of Sunday,
+December 1st (11:59pm UTC).")))
  (entry (commit "ccf72d5074b0c5ba793e686cbb1d6eaad39824bf")
         (title
          (de "Neues Format @samp{appimage} für den Befehl @command{guix pack}")

base-commit: a2a3264bb38568e892e69e64dcfd12829a9975ce
-- 
2.46.0

John Kehayias wrote on 27 Nov 2024 07:14

Recipients:(address . 74549-done@debbugs.gnu.org)(address . guix-maintainers@gnu.org)

Message-ID:87iks919uo.fsf@protonmail.com

On Tue, Nov 26, 2024 at 08:22 PM, John Kehayias wrote:

Toggle quote (17 lines)> Hi Guix,
>
> Here's a quick patch to add a news entry about the survey before it
> closes on Sunday. I plan to push this later today in the interest of
> giving more time for people to see it, but wanted to send it for quick
> review if there is anything.
>
> 1. For the commit I just took a recent one as there is no associated commit. Is there something better?
>
> 2. The survey is "closing" at the end of Sunday Dec. 1st. We could
> specify end of that day local time perhaps? futurile said they won't
> open it until the following morning (UK) time, so I think that lines
> up with the end of Sunday everywhere. But not sure what is clearer.
>
> Thanks!
> John

Pushed as cd26d76fedb7ab13ad91bd5dcfce119892b8e62e with minor update to

add year (as suggested by rekado on #guix).

I hope this isn't an inappropriate use of news, though I think this is a

good way to get the best coverage for the survey. I meant to bring this

up earlier but forgot.

Do we have any policy or precedent for removing a news entry? Might make

sense for this one as it doesn't directly apply to Guix (as code).

Anyway, hope my taking initiative didn't ruffle any feathers! Happy to

revert later as well.

John

Closed

Maxim Cournoyer wrote on 28 Nov 2024 05:41

Re: News entry for the survey

Recipients:(name . John Kehayias)(address . john.kehayias@protonmail.com)

Message-ID:87zflkj7gz.fsf@gmail.com

Hi John,

John Kehayias <john.kehayias@protonmail.com> writes:

Toggle quote (14 lines)> Hi Guix,
>
> Here's a quick patch to add a news entry about the survey before it
> closes on Sunday. I plan to push this later today in the interest of
> giving more time for people to see it, but wanted to send it for quick
> review if there is anything.
>
> 1. For the commit I just took a recent one as there is no associated commit. Is there something better?
>
> 2. The survey is "closing" at the end of Sunday Dec. 1st. We could
> specify end of that day local time perhaps? futurile said they won't
> open it until the following morning (UK) time, so I think that lines
> up with the end of Sunday everywhere. But not sure what is clearer.

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!

Thanks,

Maxim

John Kehayias wrote on 28 Nov 2024 06:11

Recipients:(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)

Message-ID:87sercrlhv.fsf@protonmail.com

Hi Maxim,

On Thu, Nov 28, 2024 at 01:41 PM, Maxim Cournoyer wrote:

Toggle quote (11 lines)> 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.

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.

Thanks for chiming in Maxim!
John

Maxim Cournoyer wrote on 28 Nov 2024 08:41

Recipients:(name . John Kehayias)(address . john.kehayias@protonmail.com)

Message-ID:87cyifkdpf.fsf@gmail.com

Hi John,

John Kehayias <john.kehayias@protonmail.com> writes:

Toggle quote (21 lines)> 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.

Toggle quote (5 lines)

> 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!

Thanks,

Maxim

Efraim Flashner wrote on 28 Nov 2024 12:46

Recipients:(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)

Message-ID:Z0hYL5cCjm4mdcKG@3900XT

On Thu, Nov 28, 2024 at 04:41:16PM +0900, Maxim Cournoyer wrote:

Toggle quote (40 lines)> 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

John Kehayias wrote on 28 Nov 2024 16:26

Recipients:(name . Efraim Flashner)(address . efraim@flashner.co.il)

Message-ID:8734jbcrcg.fsf@protonmail.com

Hi,

On Thu, Nov 28, 2024 at 01:46 PM, Efraim Flashner wrote:

Toggle quote (30 lines)> 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.
>>

No worries. As do I, which is why I hadn't raised earlier, as I should

have.

Toggle quote (15 lines)>> > 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.

Sounds good. I'll revert by Monday, noting in the commit message why

and as notice for what news.scm should be used for.

Thanks for the understanding!

John

John Kehayias wrote on 4 Dec 2024 06:55

Recipients:(name . Efraim Flashner)(address . efraim@flashner.co.il)

Message-ID:87ldww800x.fsf@protonmail.com

Toggle quote (22 lines)>>> > 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.
>
> Sounds good. I'll revert by Monday, noting in the commit message why
> and as notice for what news.scm should be used for.
>
> Thanks for the understanding!
>
> John

Reverted with aa8d8d6634ccd443d7375a0bdbb120674b40178d.

Thanks for the input and understanding.

Your comment

This issue is archived.

To comment on this conversation send an email to 74549@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it

mumi current 74549

Then, you may apply the latest patchset in this issue (with sign off)

mumi am -- -s

Or, compose a reply to this issue

mumi compose

Or, send patches to this issue

mumi send-email *.patch

is:open	open issues
is:done	closed issues
submitter:<who>	search issue submitter
author:<who>	search by message author
date:yesterday..now	search by issue date
mdate:3m..2d	search by message date