Extension talk:Wikibase Repository/Mobilize Wikidata

Hello world!
I'm in the process of sharing my GSoC 2013 application with the Wikimedia community for discussion and feedback. If you've noticed something in the application that I could improve upon, have any queries or maybe just say 'hello', please drop in a word.

Alternatively, I can found on the IRC on freenode (#mediawiki, #wikimedia-dev, #wikimedia-mobile and #wikimedia-wikidata) and the mailing lists (Wikitech-I and Wikidata-I).

Cheers!

GSoC 2013 - Mobilize Wikidata - Feedback
Please add your feedback below :


 * 1) Numbered list item

Feedback
On "User Interface" I'd suggest mentioning that some tweaks might be needed - for instance the Uploads feature on MobileFrontend - I'm not 100% sure that will be useful on a mobile WikiData.
 * I've updated the synopsis section to include specifics of what needs to be worked on now. For the scope of this project, I would be focusing more on Wikibase than MobileFrontend but I like the suggestion anyway! I'll keep it in mind and run it by my mentors to see how they feel about it. -Pragun

I'd hope that 3 weeks is more than enough time for "Community Bonding Period" - hopefully you'll be up and coding during week 1! Also rather than having 1-2 weeks "Testing on mobile devices with different screen sizes." I'd suggest a community feedback period. Testing across devices should be occurring as you go along, especially now Chrome browser allows you to override the display! If you force yourself to work on a tiny browser window for the duration of the project I'm confident you won't need this 2 week period!
 * Completely agree with these points. Shall edit proposal accordingly. 3 weeks will definitely be more than enough! I've begun working on bug fixes here and there already. I've just included this period because I might like to try a few soft experiments before moving on to the actual thing. -Pragun

It's not clear if you plan to but it would also be great if you could commit code as you go along (e.g. Github/Gerrit) rather than submitting to Gerrit at the end - this way your code will benefit more from review and be of better quality. It also will help you with documentation :)
 * Agreed again. It wasn't a good idea to explicitly state 'Submit code to Gerrit' at the end. Will make sure that my proposal conveys that I'll be committing as I go. -Pragun

It would be great if during your last 4-5 weeks you could collect feedback and suggest future enhancements. It would be great if your project outlives GSoC and creates an interested community (including yourself hopefully) that wants to continue working on it.
 * I had intended for this as well, actually but I think that it's a good idea to state so explicitly on my timeline. -Pragun

Otherwise looks great! Good luck!
 * Thanks for all your suggestions! I really appreciate it. :) -Pragun