From: "Antoine Beaupré" <anarcat@debian.org>
To: Junio C Hamano <gitster@pobox.com>, Matthieu Moy <git@matthieu-moy.fr>
Cc: git@vger.kernel.org
Subject: Re: future of the mediawiki extension?
Date: Mon, 30 Oct 2017 22:10:22 -0400 [thread overview]
Message-ID: <874lqg83u9.fsf@curie.anarc.at> (raw)
In-Reply-To: <xmqqh8ug3xnq.fsf@gitster.mtv.corp.google.com>
On 2017-10-31 10:37:29, Junio C Hamano wrote:
>> There's also a hybrid solution used by git-multimail: have a copy of the
>> code in git.git, but do the development separately. I'm not sure it'd be
>> a good idea for Git-Mediawiki, but I'm mentionning it for completeness.
>
> I think the plan was to make code drop from time to time at major
> release points of git-multimail, but I do not think we've seen many
> updates recently.
I'd be okay with a hybrid as well. It would require minimal work on
Git's side at this stage: things can just stay as is until there's a new
"release" of the mediawiki extension and at that point you can decide if
you merge it all in or if you drop it in favor of the contrib.
I think it's also fine to punt it completely out to the community.
Either way, I may have time to do some of that work in the coming month,
so let me know what you prefer, I guess you two have the last word
here. The community, on Mediawiki's side, seem to mostly favor GitHub.
A.
--
Never attribute to malice that which can be adequately explained by
stupidity, but don't rule out malice.
- Albert Einstein
next prev parent reply other threads:[~2017-10-31 2:10 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é
2017-10-31 5:23 ` Junio C Hamano
2017-10-31 1:37 ` Junio C Hamano
2017-10-31 2:10 ` Antoine Beaupré [this message]
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=874lqg83u9.fsf@curie.anarc.at \
--to=anarcat@debian.org \
--cc=git@matthieu-moy.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).