From: Chris Knadle <Chris.Knadle@coredump.us>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Candidate for an 1.4.0.a1, glad for the work
Date: Wed, 08 Feb 2023 07:44:00 +0000 [thread overview]
Message-ID: <572dfe82-87b0-f959-f174-0944c5658199@coredump.us> (raw)
Greetings.
I want to give anyone working on the 1.4.0.a1 mlmmj candidate my thanks, it's
good to see that this work is going on, and I'm looking forward to packaging it
and other pieces for it for Debian when it's in a semi-stable/usable state.
I'm personally interested in an mlmmj-archiver web indexing program, because
I've had difficulties with other mailing list archivers. Lurker works but seemed
relatively inflexible, and Mhonarc required a fair bit of configuration and I
never did figure out its configuration language. Debian mailing lists are
archived in Mhonarc but I don't currently have access to the configuration used
for those.
Re: using the mlmmj name, my only thought is perhaps a minor addition to the
name to distinguish the fork, such as mlmmj-ng (next-generation) or mlmmj2. It's
not a requirement, it's just mentioning what I typically see other projects do.
I think the idea is to cover the possibility of upstream picking up their old
project again and/or avoiding old/new naming clashes. If the old/same name is
stuck with I don't have any objection.
Just in case I don't check the mailing list often enough: when you think the
program is in a buildable/usable enough state for being packaged and uploaded to
Debian, please ping me via email.
Thanks
-- Chris
--
Chris Knadle
Chris.Knadle@coredump.us
Baptiste Daroussin:
> Hello everyone,
>
> A 1.5 years ago, I migrated FreeBSD's mailing list to mlmmj. So far so good we
> are very happy with it.
>
> Since that date I have been working on modernizing mlmmj codebase, integrate our
> patches etc. While the work is clearly not done, I think it is advanced enough
> for it to be shared.
next reply other threads:[~2023-02-08 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 7:44 Chris Knadle [this message]
2023-02-08 9:03 ` [mlmmj] Candidate for an 1.4.0.a1, glad for the work Baptiste Daroussin
2023-02-08 9:18 ` Mads Martin Jørgensen
2023-02-08 9:22 ` Zhang Huangbin
2023-02-08 10:01 ` Baptiste Daroussin
2023-02-08 10:04 ` Mads Martin Jørgensen
2023-02-08 11:03 ` Franky Van Liedekerke
2023-02-08 11:20 ` Baptiste Daroussin
2023-02-08 22:00 ` Christian Stærk
2023-02-11 19:15 ` Wolf Bergenheim
2023-02-11 20:15 ` Wolf Bergenheim
2023-02-17 16:00 ` Franky Van Liedekerke
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=572dfe82-87b0-f959-f174-0944c5658199@coredump.us \
--to=chris.knadle@coredump.us \
--cc=mlmmj@mlmmj.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 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).