Wikipedia talk:Requests for comment/Education Program extension: Difference between revisions

Revision as of 14:36, 24 August 2012

Revision as of 08:03, 31 August 2012

Line 18:

It should use wiki pages for textual content (e.g. Commons has 'Institution' pages like [[commons:Institution:New York Public Library]]), categorisation of users ([[:Category:Wikipedians]]), and provide new special pages that are transcludable tools. e.g. I should be able to use the new dynamic user-article-reviewer table should work on [[:Category:Wikipedians by WEP institution: New York University]], [[:Category:Wikipedians by alma mater: New York University]], [[:Category:Wikipedians in New York ]], [[:Category:Candidates for speedy deletion as copyright violations]], [[:Category:Candidates for speedy deletion as attack pages]], [[:Category:Good article nominees]], or [[:Category:Pending DYK nominations]]. <span style="font-variant:small-caps">[[User:John Vandenberg|John Vandenberg]] ^{'''([[User talk:John Vandenberg|chat]])'''}</span> 00:34, 24 August 2012 (UTC)

:This is useful feedback. I'd also like to see future development of the extension include ways of accessing and using the user-article-reviewer data elsewhere such as through categories. I'd also like to see more wikitext-level control of how all course and institution pages, or individual pages, get displayed. I'm not sure what the best way to achieve that is, but maybe something like MediaWiki: namespace pages that determine the layout, so that the community can design and redesign the course pages without forcing the people using the course pages to dealing with (and potentially break) the layout markup themselves.--[[User:Sage Ross (WMF)|Sage Ross (WMF)]] ([[User talk:Sage Ross (WMF)|talk]]) 14:36, 24 August 2012 (UTC)

::Document the [[use cases]], write [[user requirements]], build, test and deploy. If you must deploy an half-baked solution in the interim, please put it in the "Special" namespace. As far as I can see that wont limit the webapp at all, except the URLs wont be as pretty. If you don't, expect all sorts of things to break, and a different segment of the community will be annoyed. Pages in all other namespaces are expected to be readable and editable using the API, e.g. gadgets and the bots, using wikitext. Is there a design doc for how this namespace will work in the API?

::This current webapp design replaces wikitext with a very limited UI, thereby taking the design, automation and general ingenuity capabilities away from the community and restricting it to the developers, who will lack time to keep up. The WEP should use [[Eating your own dog food | the existing infrastructure]]. ;-) Why should WEP get special tools when other review workflows are managed by the community using bots etc.? Of course doing it by bots would need to be resourced, and a non-bitey bot will need to have exception handling reports that users (..possibly staff..) need to monitor and action in order to keep everything working smoothly. But that is part of life doing projects on a wiki. <span style="font-variant:small-caps">[[User:John Vandenberg|John Vandenberg]] ^{'''([[User talk:John Vandenberg|chat]])'''}</span> 08:03, 31 August 2012 (UTC)