Matthieu Moy <git@xxxxxxxxxxxxxxx> 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.
