From: "Antoine Beaupré" <anarcat@debian.org>
To: Matthieu Moy <git@matthieu-moy.fr>
Cc: git@vger.kernel.org
Subject: Re: future of the mediawiki extension?
Date: Mon, 30 Oct 2017 08:28:09 -0400 [thread overview]
Message-ID: <87mv487rc6.fsf@curie.anarc.at> (raw)
In-Reply-To: <q7h9o9opyllo.fsf@orange.lip.ens-lyon.fr>
On 2017-10-30 11:29:55, Matthieu Moy wrote:
>> It should also be mentioned that this contrib isn't very active: I'm not
>> part of the GitHub organization, yet I'm probably the one that's been
>> the most active with patches in the last year (and I wasn't very active
>> at all).
>
> FYI, I'm no longer using Mediawiki as much as I did, and I don't really
> use Git-Mediawiki anymore.
>
> The main blocking point to revive Git-Mediawiki is to find a new
> maintainer (https://github.com/Git-Mediawiki/Git-Mediawiki/issues/33). I
> believe I just found one ;-).
Eh. I assume you mean me here. As I hinted at in another thread, I am
not sure I can commit to leading the project - just scratching an
itch. But I may be able to review pull requests and make some releases
from time to time... I probably won't work on code or features I don't
need unless someone funds my work or something. ;)
We'll see where the community takes us, I guess... Always better to have
more than one maintainer, anyways, just for the bus factor... Worst
case, I'll delegate to a worthy successor. :)
A.
--
Votre silence ne vous protégera pas.
- Audrey Lorde
next prev parent reply other threads:[~2017-10-30 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 3:00 future of the mediawiki extension? Antoine Beaupré
2017-10-30 10:29 ` Matthieu Moy
2017-10-30 12:28 ` Antoine Beaupré [this message]
2017-10-31 5:23 ` Junio C Hamano
2017-10-31 1:37 ` Junio C Hamano
2017-10-31 2:10 ` Antoine Beaupré
2017-11-07 0:44 ` Junio C Hamano
2017-11-07 2:33 ` Antoine Beaupré
2017-11-07 7:46 ` Matthieu Moy
2017-11-07 15:12 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv487rc6.fsf@curie.anarc.at \
--to=anarcat@debian.org \
--cc=git@matthieu-moy.fr \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).