On 04/29/2013 05:27 PM, Quim Gil wrote:
On 04/29/2013 02:18 PM, Aayush Sharma wrote:
Hi Aayush, please write more specific emails in a mailing list. It will
help getting more people looking at your proposal.
You could also have pasted the summary here, so people can have a look
and decide whether they want to check more or not.
For instance, in your proposal you say
GSoC Project Idea: MediaWiki API 2.0
I will be working and modifying MediaWiki API to solve the following
problems:
* Avoiding client to update every time API changes
* Developers will develop extensions from the single default API
(recommended).
* Reduce the cost of making a change in MediaWiki.
* Organize feature changes - if the client asks for ver X, API
guarantees the capabilities of X and result in format X.
* Avoid cluttering of parameters.
* All API capabilities should return only the data requested to
minimize bandwidth and improve speed.
Good luck!
Hi, Aayush. I'm cc'ing the mediawiki-api mailing list.
Some questions:
* Do you plan on working in a branch for a few weeks or months and then
merging it into master on September 10th? It seems to me that it would
be better to write improvements one by one and have a lot of smaller merges.
* What kind of documentation will you be writing? A walkthrough of the
code so future developers can understand it? Some kind of user-facing
manual? Other things?
* Have you already reviewed
https://www.mediawiki.org/wiki/API/REST_proposal , read the last few
months of the mediawiki-api mailing list
https://lists.wikimedia.org/mailman/listinfo/mediawiki-api , and looked
at the recent changes to the API code
https://gerrit.wikimedia.org/r/#/q/message:api+status:merged,n,z to see
what the current trends are?
* Can you tell us how long it has taken you to do similar projects in
the past?
* Who are your mentors?
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation