Wikipedia talk:Requests for comment/Education Program extension: Difference between revisions
Content deleted Content added
→Terrible design: reply |
→Terrible design: on wikitext and structured data |
||
Line 20:
::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]] <sup>'''([[User talk:John Vandenberg|chat]])'''</sup></span> 08:03, 31 August 2012 (UTC)
:::This extension is a tangible step forward for keeping track of what courses are doing. The flexibility and complexity of full wikitext project pages is a double-edged sword; for newcomers, it's often overwhelming, and the first casualty is complete lists of students' usernames for each class. Having that student/class information built into the software in an inflexible way is basically the core purpose for this initial version, so that we, as experienced editors, can then monitor groups of students in a reliable way. Note that the "course description" section actually is wikitext, with a history (which, I believe, is why it doesn't simply use special pages). So it would be possible to have a fair bit of flexibility even with this initial version, if we transclude templates into the course description pages.
:::I'm not sure how this extension works with the API; I'll ask the developer, Jeroen De Dauw, about that.--[[User:Sage Ross (WMF)|Sage Ross (WMF)]] ([[User talk:Sage Ross (WMF)|talk]]) 16:19, 31 August 2012 (UTC)
|