Thanks for the additional details :-)
Perhaps this isn't important right now, but have you given any thought to the naming of the version? I kind of like the clarity and goals of the semver system [1]. The reason why I bring this up is that fixing existing bugs with the API sounds like minor change in the version number, whereas a major change from (v1 -> v2) implies a break with backwards compatibility to create a new API. Perhaps framing the work in terms of semver will help organize the work?
By the way, I quite like the sound of a modern looking (aka RESTful) API for MediaWiki. Does that fit how you are thinking about v2 of the API?
//Ed
On Fri, Dec 28, 2012 at 6:10 AM, Yuri Astrakhan yuriastrakhan@gmail.com wrote:
Bugzilla, mailing list archives, our heads. Now that versionning is per-module, we can start revising them one at a time to support new capabilities. Bugzilla has 150+ open API bugs.
There is an API v2 tracking bug at https://bugzilla.wikimedia.org/show_bug.cgi?id=38891 Make sure bug 38891 depends on any v2 requests you add.
All open API bugs: https://bugzilla.wikimedia.org/buglist.cgi?order=Importance&query_format...
Or we could create an RFC at http://www.mediawiki.org/wiki/RFC
On Fri, Dec 28, 2012 at 5:54 AM, Ed Summers ehs@pobox.com wrote:
On Fri, Dec 28, 2012 at 5:45 AM, Yuri Astrakhan yuriastrakhan@gmail.com wrote:
Let the rotten egg throwing commence!
Sorry to be dense, but where is a good place to learn about what changes are in being planned for v2 of the API?
//Ed
Mediawiki-api mailing list Mediawiki-api@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-api
Mediawiki-api mailing list Mediawiki-api@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-api