User talk:Rtdwivedi

Hello everyone! Please feel free to start a discussion here.

Comments
Somme comments on the proposal:


 * 1) Please remove discussion on this talk page that aren't related to this proposal.

Tpt (talk) 09:39, 26 April 2013 (UTC)
 * 1) For the planing (some comments)
 * 2) May 27- June 17: Ok. Needed time but, if you have no other work at the same time, I believe you can learn the codebase in a week.
 * 3) June 17- June 30: I think that unit tests goes at the same time as the refactoring: you refactor something and you write unit tests.
 * 4) July 1- July 5: I don't think that "use less of global variables" is a goal in itself. It'll be done as the same time as the move to PHP of some parts of code and refactor of the JS part.
 * 5) July 5- July 20: Ok.
 * 6) July 21- July 31: Should be done before the JS refactoring as the JS refactored code will be based on the new PHP components.
 * 7) August 1 - August 12: Should maybe be mixed with the refactoring. Write only unit test during a week is awful.
 * 8) August 12- August 25: Mixed with the refactoring.
 * 9) August 25- September 10: Should be done at the beginning of the JS refactoring as you'll use it for the refactoring.
 * 10) September 10- September 16: Ok
 * 11) September 16- September 23: Ok

Are you already in the Indian Wikimedia community?
Please join the Wikimedia India mailing list so you can keep up with what's happening in the Indian Wikimedia community! Sharihareswara (WMF) (talk) 15:11, 8 May 2013 (UTC)

--Hi! I have joined the mailing list. Thanks a lot! Rtdwivedi

Thanks for your wikisource project
Hi Rtdwivedi, Aubrey told us into it.wikisource that you are working about VisualEditor + proofread extension. It's simply GREAT! I'm not a programmer, even if I love DIY (do-it-yourself ;-) ) programming (python-js-templates and now Lua), just as I can. I'd like to help you as I can with a decent "normal" source user and with some experience about main troubles of source automation. I explored too the edit interface/philosophy of Distributed Proofreaders; my suggestion for you is, to explore it using a programmer point of view (if you never did), there are excellent tools and ideas IMHO, most of them inspiring for a new proofreading user interface.

I don't want to waste your time any more; tell me if I can help you, and how. In the meantime I'm exploring Lua and it's excellent mw.loadData. --Alex brollo (talk) 10:05, 30 May 2013 (UTC)


 * Hi Alex,
 * Thanks a lot! The simplest way in which you can help me is by filing relevant bugs on Bugzilla and assigning it to me. If you want a feature to be added then also put it on Bugzilla. Currently, I am exploring the codebase. Thanks a lot! -- Aarti Dwivedi 12:55, 30 May 2013 (UTC)
 * Perhaps you can't imagine how much a poor and aged "DIY programmer" hates bugzilla; but your work deserves such a heroic effort by me. ;-)
 * Some it.source users did very bold and effective tries to "rebuild proofread environment" by javascript manipulation, clues being "remove anything useless from edit environment to gain any possible pixel to edit space" and "move any needed tool into fixed boxes". I'll encourage them to follow your work. --Alex brollo (talk) 21:29, 30 May 2013 (UTC)
 * If you find it convenient, you can mail me about the features and bugs or ping me on IRC about the same. My nick on IRC is Rtdwivedi. -- Aarti Dwivedi 21:36, 30 May 2013 (UTC)