git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Antoine Beaupré" <anarcat@debian.org>
Cc: Matthieu Moy <git@matthieu-moy.fr>, git@vger.kernel.org
Subject: Re: future of the mediawiki extension?
Date: Tue, 07 Nov 2017 09:44:03 +0900	[thread overview]
Message-ID: <xmqq7ev2j4to.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <874lqg83u9.fsf@curie.anarc.at> ("Antoine Beaupré"'s message of "Mon, 30 Oct 2017 22:10:22 -0400")

Antoine Beaupré <anarcat@debian.org> writes:

> 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.

I guess I shouldn't leave this thread hanging.

As contrib/README says, the "owners" of an area in contrib/ has the
ultimate say and control over the area, and for contrib/mw-to-git,
the "owners" have always been Matthieu, at least to me.

As he made it clear earlier in this thread that (1) he sees you as a
steady hand that can help guide the tool forward as its new "owner",
and (2) he thinks Git-Mediawiki will be helped by being an
independent project hosted at GitHub, now you have the say ;-)

A few topics from you that are already on list may want to go
through to 'master' as any other topics, but from there on, I am
fine with the development of Git-Mediawiki primarily done as a
separate project, optionally giving contrib/mw-to-git/ occasional
update dumps.  You could even choose to remove contrib/mw-to-git/*
except for git-remote-mediawiki.txt that says that the tool's main
development effort happens at GitHub to redirect people, if you
think that would reduce potential confusion.

I am also OK to serve as a patch monkey and keep going; I won't be
picking up patches to contrib/mw-to-git/ unless you (and others)
review them, though.

  reply	other threads:[~2017-11-07  0:44 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é
2017-11-07  0:44       ` Junio C Hamano [this message]
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=xmqq7ev2j4to.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=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).