On Tuesday, September 16, 2014, Jon Robson <jdlrobson(a)gmail.com> wrote:
In the past when I've needed changes merged in this codebase I've had
to actively search out people who feel comfortable reviewing it and
+2ing it.
(snip)
I personally think the idea of a code maintainer is
outdated,
Then let's call them 'people who feel comfortable reviewing and +2ing'
patches in a repository. :) Or first points of contact that can help you
adding reviewers. Knowing who might be good reviewers for a patch is not
simple even for those developers working full time at the Foundation.
Imagine the situation of the rest of contributors.
we should all be maintaining the code in the MediaWiki
world.
Nice thought, but still not helpful for someone like Florian wondering who
should review his patch.
Looking at
https://www.mediawiki.org/wiki/Developers/Maintainers and
looking at
http://phabricator.wikimedia.org/T340 (
Start the process of expanding the arch committee), one idea could be to
organize all those components in areas, nominating "meta-maintainers" for
each area. This way, if a specific component doesn't have any maintainers
assigned, at least someone like Florian could check with the related
meta-maintainer.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil