From: Valentin Gagarin <valentin@gagarin.work>
To: Alyssa Ross <hi@alyssa.is>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH] Documentation: reword information on mailing lists
Date: Tue, 18 Aug 2026 22:16:09 +0200 [thread overview]
Message-ID: <e2a7f616-e4dd-4027-a592-e3fb7726067a@gagarin.work> (raw)
In-Reply-To: <anSqkuzoWB3Ihv1S@mbp.qyliss.net>
>> +List archives are served with https://public-inbox.org/README[public-inbox] and only support plain text.
>
> This isn't strictly true. We should be clearer here.
Will fix.
> I consider Hyperkitty a bit legacy,
> since I'd originally hoped people could post through it, but that hasn't
> worked out. If it got much harder to keep running I'd probably drop it,
> so not sure it's worth directing people to at this point? It's pretty
> clunky and doesn't even look that nice…
I only put it in there because it seems to have been discussed on the
mailing list once in a while, and it still seems to be the case that
it's a more conventional reading experience for most people running into
Spectrum. I suggest to either point it out and keep maintaining it, or
to shut it down and post a note on discuss@spectrum-os.org. I have no
opinion on the outcome, I'm just trying to clarify the facts.
>> +NOTE: If you have the capacity to mirror the mailing list archives, please do!
>
> Think this is worth the space?
I just kept that because the previous content appeared deliberate and
made sense to me. Happy to drop it, there's a link on each public-inbox
front page anyway.
prev parent reply other threads:[~2026-08-18 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 8:56 [PATCH] Documentation: reword information on mailing lists Valentin Gagarin
2026-08-07 16:07 ` Alyssa Ross
2026-08-18 20:16 ` Valentin Gagarin [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=e2a7f616-e4dd-4027-a592-e3fb7726067a@gagarin.work \
--to=valentin@gagarin.work \
--cc=devel@spectrum-os.org \
--cc=hi@alyssa.is \
/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://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
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 NNTP newsgroup(s).