From: "Mads Martin Jørgensen" <mmj@mmj.dk>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] distribution "dead upstream" discussion
Date: Fri, 22 Jan 2021 06:03:35 +0000 [thread overview]
Message-ID: <743E0865-72BD-4485-9F25-FDA1B7A49A4F@mmj.dk> (raw)
In-Reply-To: <b6763fd2-a7ca-1c16-b304-43d1ce0b09da@coredump.us>
Hello all,
> On 22 Jan 2021, at 04.50, Chris Knadle <Chris.Knadle@coredump.us> wrote:
>
> I've already explained my concerns in the email I sent to the list. What about what I said wasn't clear? All MLMMJ development has stopped, the mailing list archives stopped working in 2017, there's a repo fork that isn't listed anywhere on the site, and I wanted to know how to report bugs upstream because that was up in the air. Are you saying you consider all of that as being "just fine"?
I also haven't heard from Ben since 2018, so maybe it's time to move the website somewhere else and find a fresh maintainer. Would really hope the transition could be with Bens blessing, but as the original developer I do have access to the people who own the mlmmj.org domain.
Best wishes,
Mads Martin
--
"Why make things difficult, when it is possible to make them cryptic and
totally illogical, with just a little bit more effort?" - A. P. J
next prev parent reply other threads:[~2021-01-22 6:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 10:35 [mlmmj] distribution "dead upstream" discussion Chris Knadle
2021-01-21 17:43 ` webmaster
2021-01-21 21:59 ` Geert Stappers
2021-01-21 22:09 ` Eric Wong
2021-01-21 22:40 ` Christof Thalhofer
2021-01-22 3:50 ` Chris Knadle
2021-01-22 3:57 ` Chris Knadle
2021-01-22 6:03 ` Mads Martin Jørgensen [this message]
2021-01-25 17:20 ` Thomas Goirand
2021-01-26 0:14 ` Mads Martin Jørgensen
2021-01-27 15:58 ` Chris Knadle
2021-02-02 17:14 ` Thomas Goirand
2021-02-03 21:02 ` Chris Knadle
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=743E0865-72BD-4485-9F25-FDA1B7A49A4F@mmj.dk \
--to=mmj@mmj.dk \
--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 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.