As a sort of compromise, maybe we could write up a list of new features MediaWiki administrators would find useful a month before the release is planned. By that time, we've got a very good idea of what is going to be in it.
This seems like a good idea. Even if we never follow through with every plan, the primary reason I think we need something like this is so administrators can see what we're thinking about doing, and (possibly) provide feedback on that. For example, if a sysadmin sees that OAuth is on the list, they may come and say "This is awesome. You guys should totally do OAuth." or something along those lines.
*--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerromeo@gmail.com
On Tue, Oct 16, 2012 at 12:18 PM, Mark A. Hershberger mah@everybody.orgwrote:
On 10/16/2012 11:45 AM, Tyler Romeo wrote:
There should be some general idea of at least what is planned for a release before the code is
actually
written.
This would mean getting any non-WMF contributors (the volunteers) to spec out what they planned to work on before hand and be committed to actually delivering it.
I'm not sure that is realistic.
It is realistic is getting a schedule for WMF-sponsored work, but a good deal of that is not going to interest the average MW admin since it is focused on Wikipedia.
As a sort of compromise, maybe we could write up a list of new features MediaWiki administrators would find useful a month before the release is planned. By that time, we've got a very good idea of what is going to be in it.
It could be that I'm just too pessimistic, but I think that comes from my introduction to the term "Cookie-Licking".
Mark.
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l