git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <git@matthieu-moy.fr>
Cc: "Antoine Beaupré" <anarcat@debian.org>, git@vger.kernel.org
Subject: Re: future of the mediawiki extension?
Date: Tue, 31 Oct 2017 10:37:29 +0900	[thread overview]
Message-ID: <xmqqh8ug3xnq.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <q7h9o9opyllo.fsf@orange.lip.ens-lyon.fr> (Matthieu Moy's message of "Mon, 30 Oct 2017 11:29:55 +0100")

Matthieu Moy <git@matthieu-moy.fr> writes:

> So, my conclusion is that a simpler submission mechanism (GitHub's
> pull-requests) and a less picky code review would help Git-Mediawiki.
>
> From previous discussions, I think Junio will agree with that: he's
> reluctant to keeping too much stuff in contrib/ and usally prefers
> external projects.
>
> Note that being a separate project doesn't mean there can't be any
> interaction with this list. Requests for reviews for separate projects
> are usually welcome even though they don't happen often here.

I would say that Git and its ecosystem has become mature enough that
any add-on project that aims to make life more pleasant for those
who use Git and $X together for any value of $X can now stand on its
own, without being under Git umbrella like back in the days when the
number of people who know and/or use Git were small.  The world is
no longer constrained by small number of people with Git expertise,
and it has become practical to discuss their project among those who
are familiar with (and motivated to learn) *both* Git and $X without
necessarily involving Git 'core' people.

Participants of this list will continue to strive to keep this list
the place for people to come for Git expertise.  But this list may
no longer be the best place to find those who are experts on *both*
Git and $X.  And that is why I think an external project standing on
its own would be more preferrable these days.

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

  parent reply	other threads:[~2017-10-31  1:37 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 [this message]
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=xmqqh8ug3xnq.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).