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


Somme comments on the proposal:

  1. Please remove discussion on this talk page that aren't related to this proposal.
  1. For the planing (some comments)
    1. 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.
    2. 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.
    3. 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.
    4. July 5- July 20: Ok.
    5. July 21- July 31: Should be done before the JS refactoring as the JS refactored code will be based on the new PHP components.
    6. August 1 - August 12: Should maybe be mixed with the refactoring. Write only unit test during a week is awful.
    7. August 12- August 25: Mixed with the refactoring.
    8. August 25- September 10: Should be done at the beginning of the JS refactoring as you'll use it for the refactoring.
    9. September 10- September 16: Ok
    10. September 16- September 23: Ok

Tpt (talk) 09:39, 26 April 2013 (UTC)Reply[reply]

Are you already in the Indian Wikimedia community?Edit

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)Reply[reply]

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

Thanks for your wikisource projectEdit

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)Reply[reply]

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)Reply[reply]
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)Reply[reply]
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)Reply[reply]

Proofread extensionEdit

Hi! Ciao! Namaste! It's great to hear that you will do this project on the proofread extension! I'm also from Italian Wikisource like Alex above, and being a programmer in real life, and having already fought with the ProofreadPage code in the past years, I particularly appreciate your courage :) You told Alex to put all bugs and features in bugzilla... be ready, we will give you bahut bahut of them! :D Here's my first for now: bug49023 You may also want to take a look at how I customized my vector.css in order to better exploit all the space available, particularly useful when working on a Page. It would be nice to have a similar layout, activated from user preferences. Candalua (talk) 20:03, 31 May 2013 (UTC)Reply[reply]

Hi! Thanks a lot, both for the welcome and bug. I'll be tracking the bugs and use them as pointers during refactoring.--Rtdwivedi(User talk:Rtdwivedi|talk]]) 20:21, 31 May 2013 (UTC)Reply[reply]

Thanks + bugEdit

Hi, and thank you very much for undertaking this badly needed work! I'm looking forward to a terrific new proofreadpage extension. In the meanwhile, I took the liberty of creating a bug report and assigning it to you about the failure of sectional transclusion with composite section names. Best of luck with the project! Teak (talk) 15:33, 10 June 2013 (UTC)Reply[reply]

Hi. Thanks a lot! I will take care of the bug. Happy bug filing! :-) Rtdwivedi 15:43, 10 June 2013 (UTC)Reply[reply]

GSoC / OPW IRC AllHands this weekEdit

Hi, you are invited to the GSoC / OPW IRC AllHands meeting on Wednesday, June 26, 2013 at 15:00 UTC (8:30pm IST, 8am PDT). We have done our best finding a time that works decently in as many timezones as possibles. Please confirm at qgil wikimedia.org so I can add you to the calendar invitation and I have your preferred email for other occasions. If you can't make it's fine, but let me know as well. Thank you!--Qgil (talk) 18:00, 24 June 2013 (UTC)Reply[reply]

Wrapping up GSoCEdit

Congratulations for your PASS! Now please wrap up your GSoC project properly:

  • Update the related Bugzilla report(s) accordingly, filing reports for known bugs when appropriate.
  • Publish your wrap up post at wikitech-l (as en email or a blog post) and then add the URL to Mentorship_programs/status#2013-09-monthly.

Take a break and celebrate. You deserve it! We hope to see you sticking around, extending your project or joining new tasks. If you need advice please check with your mentors or myself. I will be happy to help you in whatever I can!--Qgil (talk) 21:11, 1 October 2013 (UTC)Reply[reply]

Great work at test2Edit

I see the results - I suppose - of your work into test2.wikipedia, I run my tools into the new javascript-almost-indipendent nsPage.... they run! Our itsource edit tools are indipendent from underlying html, the only link being the ids of textareas; ids have not been changed, and they run happily ;-)

I let them active into test2.wikipedia just to test them. I installed there the Template:Rh importing it from en.source, it easily manages ruunning headers and IMHO this template could be considered a standard for this job. One of our tools ( autoRi()) adds the template to header by itself, the trick being to read the code of the two former pages; another comfortable tool (autoPt() ) manages hyphenated words at the end and beginning of pages, and IMHO it's much better that its en.source version, since it's simpler and much more generalized. But.... don't waste your precious time with such minimal details. :-). Go ahead! Alex brollo (talk) 13:28, 29 November 2013 (UTC)Reply[reply]

Hi Alex! Thanks a lot! I am glad your tools are working fine. Aarti 05:47, 2 December 2013