git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Antoine Beaupré" <anarcat@debian.org>
To: git@vger.kernel.org
Subject: future of the mediawiki extension?
Date: Sun, 29 Oct 2017 23:00:44 -0400	[thread overview]
Message-ID: <87vaix731f.fsf@curie.anarc.at> (raw)

Hi,

First thanks for the excellent feedback regarding the mediawiki
extension, it's great that obscure extensions like this see such
excellent reviews.

I think, however, it would be good to have a discussion about the future
of that extension in Git. The extension has a bit of a hybrid presence -
it is partly in git core (as a contrib, but still) and partly on GitHub
here:

https://github.com/Git-Mediawiki/Git-Mediawiki/

This leads to some confusion as to where the changes should be
made. Some people make changes straight on GitHub by forking the above
repo, others fork the Git repo, and very few actually send the patches
here, on this mailing list.

There was a discussion last year about moving the module out of git core
and onto its own repository again:

https://github.com/Git-Mediawiki/Git-Mediawiki/issues/34

There is also a discussion on releasing the code to CPAN:

https://github.com/Git-Mediawiki/Git-Mediawiki/issues/18

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). There's an issue on GitHub about this as well:

https://github.com/Git-Mediawiki/Git-Mediawiki/issues/33

So, what should be done about this contrib? Should it stay in Git core?
Or should it be punted back to the community and managed on GitHub?

Please avoid "mailing list vs GitHub" flamewars and keep to the topic of
this specific contrib's future. :)

Thanks!

A.

PS: personally, I don't care much either way. It certainly seem that I
get way better feedback here than I previously got on GitHub, but that
could be because of the hybrid way things are setup in the first
place...
-- 
To punish me for my contempt for authority, fate made me an authority myself.
                       - Albert Einstein

             reply	other threads:[~2017-10-30  3:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30  3:00 Antoine Beaupré [this message]
2017-10-30 10:29 ` future of the mediawiki extension? 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
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=87vaix731f.fsf@curie.anarc.at \
    --to=anarcat@debian.org \
    --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).