(no subject)

[jgart]

Tobias Geerinckx-Rice <me@tobias.gr>,
Leo Famulari <leo@famulari.name>,
Ryan Prior <ryanprior@hey.com>,
BonfaceKilz <me@bonfacemunyoki.com>,
Pjotr Prins <pjotr2021@thebird.nl>,
Yasuaki Kudo <yasu@yasuaki.com>,
Raghav Gururajan <rg@raghavgururajan.name>,
Guillaume Le Vaillant <glv@posteo.net>,
Pierre Neidhardt <mail@ambrevar.xyz>,
Arun Isaac <arunisaac@systemreboot.net>,
Kevin Herald Reierskog <regen@anche.no>
Subject: Guix Packaging Meetup Saturday Nov 27 2PM ET (19:00 UTC)
Reply-To:
In-Reply-To:

Hi Guixers!

I'd like to invite you to another Guix packaging meetup this Saturday, November 27 at 2PM ET (19:00 UTC).

Let's try Big Blue Button provided by nixnet.services this time. It has a fancy whiteboard!

https://meet.nixnet.services/b/jga-rtw-ahw-yky

Hope to see you there!

jgart

(no subject)

[jgart]

On Thu, 25 Nov 2021 06:11:50 -0500 jgart <jgart@dismail.de> wrote:
> Hi Guixers!
> 
> I'd like to invite you to another Guix packaging meetup this Saturday, November 27 at 2PM ET (19:00 UTC).
> 
> Let's try Big Blue Button provided by nixnet.services this time. It has a fancy whiteboard!
> 
> https://meet.nixnet.services/b/jga-rtw-ahw-yky
> 
> Hope to see you there!
> 
> jgart
> 

Oops, I forgot to add a subject to this email.

Didn't add it now in the hopes that my thread is the only one without a subject.

Not sure what to do at this point.

Is there a manual I can consult for what to do in this particular situation?

Some edge cases of email lists/threads escape me.

all best,

jgart

Re: Guix packaging meetup: Saturday 27 November

[Tobias Geerinckx-Rice]

[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]

Hi jgart,

Thank you for the invitation!

jgart 写道：
> Not sure what to do at this point.

At this point, not much: you might reply to the mail with a 
non-empty subject, and hope that people will reply to that one, or 
that they will manually copy it when replying to your original 
post.  Others might add a meaningful subject of their own, as I 
have tried to do.

Still, expect some untitled ‘Re:’ messages.  It's not the end of 
the world :-)

Mailing list archives are just that: snapshots of each message 
sent to members.  They do not generally offer a way to modify 
recorded history[0].  They do not really track mutable state such 
as ‘topics’.

Threading is (or should be) based on message IDs, although some 
archivers will use the subject as an additional heuristic.

bug-guix/guix-patches are simple bug trackers built on top of 
mailing lists that add such mutable state (‘bug title’, priority, 
openness, etc.) but this is a separate database.

Kind regards,

T G-R

[0]: Exceptions like GDPR and ‘asking nicely to remove 
embarrassing info’ exist, but are by definition exceptional and 
often involve human administrator action.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

Re: Guix packaging meetup: Saturday 27 November

[jgart]

On Thu, 25 Nov 2021 22:01:32 +0100 Tobias Geerinckx-Rice <me@tobias.gr> wrote:
> Hi jgart,
> 
> Thank you for the invitation!
> 
> jgart 写道：
> > Not sure what to do at this point.
> 
> At this point, not much: you might reply to the mail with a 
> non-empty subject, and hope that people will reply to that one, or 
> that they will manually copy it when replying to your original 
> post.  Others might add a meaningful subject of their own, as I 
> have tried to do.
> 
> Still, expect some untitled ‘Re:’ messages.  It's not the end of 
> the world :-)
> 
> Mailing list archives are just that: snapshots of each message 
> sent to members.  They do not generally offer a way to modify 
> recorded history[0].  They do not really track mutable state such 
> as ‘topics’.
> 
> Threading is (or should be) based on message IDs, although some 
> archivers will use the subject as an additional heuristic.
> 
> bug-guix/guix-patches are simple bug trackers built on top of 
> mailing lists that add such mutable state (‘bug title’, priority, 
> openness, etc.) but this is a separate database.
> 
> Kind regards,
> 
> T G-R
> 
> [0]: Exceptions like GDPR and ‘asking nicely to remove 
> embarrassing info’ exist, but are by definition exceptional and 
> often involve human administrator action.

Thanks Tobias for the info. Sorry for the mixup with the email.

I'll send an email now to help-debbugs at gnu org

all best,

jgart

Re: Guix packaging meetup: Saturday 27 November

[zimoun]

Hi,

On Thu, 25 Nov 2021 at 22:01, Tobias Geerinckx-Rice <me@tobias.gr> wrote:

> Thank you for the invitation!

Cool!  I say each time to my self: next I will attend… and life happens.
Anyway, next time I will be there. :-)


(Off-topic ramblings…

> Threading is (or should be) based on message IDs, although some 
> archivers will use the subject as an additional heuristic.

That’s why GNU web front-end use numbering instead of Message IDs. :-p

For instance the message I am replying is the 184th sent to guix-devel
for Nov. 2021.  Since it is easy to know this information (extrinsic),
it is obvious to link the archive:

    https://lists.gnu.org/archive/html/guix-devel/2021-11/msg00184.html

Sigh.  Why am I sarcastic here? ;-)

When using Notmuch (or any descent email client), it is trivial to get
the Message ID (press just ’cI’ with emacs-notmuch):

    87bl28q6h7.fsf@nckx

Knowing this information, other tools use that for indexing, for
instance ’public-inbox’:

    https://yhetil.org/guix/87bl28q6h7.fsf@nckx

(emacs-notmuch: ’cl’ correctly configured add the URL in the kill ring,
ready for pasting wherever)

I do not know if GNU Mailman with HyperKitty is serving URLs archive
containing Message-ID (intrinsic).  On a side note, I find interesting
that the GNU project does not deploy a recent release of a GNU tool for
friendly collaboration; because the version of GNU Mailman behind
<https://lists.gnu.org/> is more than outdated.

What depends on Guix project is the numbering of the front-end Mumi
(really nice and friendly front-end for Debbugs), as with:

    https://issues.guix.gnu.org/17150#3

the 4th message about bug 17150.  Where it could nice to have in
addition:

    https://issues.guix.gnu.org/87lhvqm179.fsf@yeeloong.lan

(I found the message ID using this: M-x debbugs-gnu-bugs 17150 then pick
the message then M-x gnus-summary-show-raw-article and grep Message-ID
which can be automated and maybe included by Emacs Gnus, dunno.)

For instance, ’public-inbox’:

    https://yhetil.org/guix/87lhvqm179.fsf@yeeloong.lan/

…end)


Cheers,
simon

Re: Guix packaging meetup: Saturday 27 November

[Tobias Platen]

I'm interested in joining that packaging meetup, since I have been
using Guix for some years, and want to package some software that I
have written and already packaged for Debian.

Tobias Alexandra

On Thu, 2021-11-25 at 22:01 +0100, Tobias Geerinckx-Rice wrote:
> Hi jgart,
> 
> Thank you for the invitation!
> 
> jgart 写道：
> > Not sure what to do at this point.
> 
> At this point, not much: you might reply to the mail with a 
> non-empty subject, and hope that people will reply to that one, or 
> that they will manually copy it when replying to your original 
> post.  Others might add a meaningful subject of their own, as I 
> have tried to do.
> 
> Still, expect some untitled ‘Re:’ messages.  It's not the end of 
> the world :-)
> 
> Mailing list archives are just that: snapshots of each message 
> sent to members.  They do not generally offer a way to modify 
> recorded history[0].  They do not really track mutable state such 
> as ‘topics’.
> 
> Threading is (or should be) based on message IDs, although some 
> archivers will use the subject as an additional heuristic.
> 
> bug-guix/guix-patches are simple bug trackers built on top of 
> mailing lists that add such mutable state (‘bug title’, priority, 
> openness, etc.) but this is a separate database.
> 
> Kind regards,
> 
> T G-R
> 
> [0]: Exceptions like GDPR and ‘asking nicely to remove 
> embarrassing info’ exist, but are by definition exceptional and 
> often involve human administrator action.