Actions like [1] cannot possibly be considered a good thing, but I certainly understand the sentiment behind it. Attracting new contributors is probably the most vital task of any collaborative volunteer project; without them, any such program is doomed to failure. This is an issue that affects Wikimedia as a whole, but MW development is arguably one of the least successful subprojects at this activity.
Who is responsible for commit access requests now that Brion has left? That applies both in the long-term, once the new CTO is hired, and in the short term, for those requests that are in the queue Right Now. Whoever is responsible, needs as a matter of urgency to both clear the current queue, and to establish an ongoing procedure to clear it more regularly in future. Brion's last review was on 4th August, and left several requests unresolved. One of those requests is now over four months old. This is not an acceptable or sustainable gauntlet to put eager new contributors through.
--HM
[1] http://www.mediawiki.org/w/index.php?title=Commit_access_requests&curid=...
Happy-melon wrote:
Actions like [1] cannot possibly be considered a good thing, but I certainly understand the sentiment behind it. Attracting new contributors is probably the most vital task of any collaborative volunteer project; without them, any such program is doomed to failure. This is an issue that affects Wikimedia as a whole, but MW development is arguably one of the least successful subprojects at this activity.
Who is responsible for commit access requests now that Brion has left? That applies both in the long-term, once the new CTO is hired, and in the short term, for those requests that are in the queue Right Now. Whoever is responsible, needs as a matter of urgency to both clear the current queue, and to establish an ongoing procedure to clear it more regularly in future. Brion's last review was on 4th August, and left several requests unresolved. One of those requests is now over four months old. This is not an acceptable or sustainable gauntlet to put eager new contributors through.
--HM
[1] http://www.mediawiki.org/w/index.php?title=Commit_access_requests&curid=...
I didn't know that page existed. Maybe we can replace it with something more functional, like a web form frontend to an OTRS queue. Limited access with no code review requirement for new extensions would also be a time-saver.
-- Tim Starling
On Wed, Oct 14, 2009 at 11:37 AM, Tim Starling tstarling@wikimedia.org wrote:
I didn't know that page existed. Maybe we can replace it with something more functional, like a web form frontend to an OTRS queue. Limited access with no code review requirement for new extensions would also be a time-saver.
Commit access isn't a huge deal, is it? Can't some paid developer or other just be asked to check the page every day and be given the right to hand out commit access? I don't think the format of the page matters much.
Hoi, Checking something every day IS expensive. Thanks, GerardM
2009/10/14 Aryeh Gregor <Simetrical+wikilist@gmail.comSimetrical%2Bwikilist@gmail.com
On Wed, Oct 14, 2009 at 11:37 AM, Tim Starling tstarling@wikimedia.org wrote:
I didn't know that page existed. Maybe we can replace it with something more functional, like a web form frontend to an OTRS queue. Limited access with no code review requirement for new extensions would also be a time-saver.
Commit access isn't a huge deal, is it? Can't some paid developer or other just be asked to check the page every day and be given the right to hand out commit access? I don't think the format of the page matters much.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, Oct 14, 2009 at 11:42 AM, Gerard Meijssen gerard.meijssen@gmail.com wrote:
Checking something every day IS expensive.
Not if it doesn't change on most days . . . load it up with all the sites you check every day and take ten seconds to see if there are any new requests. Or subscribe to the RSS feed, or whatever you want.
wikitech-l@lists.wikimedia.org