Re: future of the mediawiki extension?

Matthieu Moy [off-list ref] 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.

On 2017-10-31 10:37:29, Junio C Hamano wrote:

quoted

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

"Junio C Hamano" [off-list ref] wrote:

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 realize I didn't answer this point. The reason you didn't see any
update recently is just that there haven't been any release and
actually not much development for a while on git-multimail.

I still have a list of "would be nice to have" features, but it seems
users are essentially happy with git-multimail as it is (or at least,
aren't unhappy enough to send patches or discuss interesting issues),
I haven't received any bug report or pull-requests for a long time.

But I still do maintain git-multimail and I will continue updating it
in git.git.

-- 
Matthieu Moy
https://matthieu-moy.fr/