All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kelling <iank@fsf.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-devel archive search was missing some messages but it's fixed now
Date: Mon, 04 Dec 2017 15:45:59 -0500	[thread overview]
Message-ID: <87a7yyql14.fsf@fsf.org> (raw)
In-Reply-To: <fbff6cd8-e3b8-3baa-b54d-87ce385061d6@redhat.com>

Laszlo Ersek <lersek@redhat.com> writes:

> Hello Ian,
>
> On 12/04/17 21:02, Ian Kelling wrote:
>
>> General thoughts about the archive: I'm looking forward to us upgrading
>> to mailman 3 at some point which will bring an improved archive
>> interface.
>
> Do you mean HyperKitty?

Yes.

>
> Will you seek out community feedback on it first?

Yes, of course. And I expect the old interface to continue to exist
alongside it indefinitely.

>
>> Of course, you can always download the archive and search it
>> on your local computer.
>
> The one HyperKitty instance that I can readily look at is:
>
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/
>
> It only offers the following download options:
>
> - "Past 30 days (mbox)"
> - "This month (mbox)"
> - "Entire archive (mbox)"
>
> Maybe it's configurable site by site, but I find this lacking compared
> to: "download whichever month you want, in isolation", which is offered
> by mailman2:
>
> ftp://lists.gnu.org/qemu-devel/
>
> If someone needs it all, the latter remains easy to script with wget,
> for example.
>
> (Back to my original point -- judged similarly from the fedora devel
> archive, I find HyperKitty hardly usable for normal reading, and I think
> it will completely fail for patch series threads and the discussions
> under them. HyperKitty is a step towards social media in my opinion, and
> as such inappropriate for development lists (again, IMO). I'm happy to
> learn otherwise, of course -- are there good counter-examples where
> HyperKitty has worked out fine, for archiving email-based patch traffic
> and development discussion?)
>
> NB: my opinion on this likely doesn't matter, as I'm not a heavy
> qemu-devel contributor.

And you've given some reasons why :)

-- 
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7  DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org

  reply	other threads:[~2017-12-04 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 20:02 [Qemu-devel] qemu-devel archive search was missing some messages but it's fixed now Ian Kelling
2017-12-04 20:37 ` Laszlo Ersek
2017-12-04 20:45   ` Ian Kelling [this message]
2017-12-04 20:49 ` Ian Kelling

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=87a7yyql14.fsf@fsf.org \
    --to=iank@fsf.org \
    --cc=lersek@redhat.com \
    --cc=qemu-devel@nongnu.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.
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.