On Tue, Feb 26, 2013 at 9:59 PM, Yuri Astrakhan yuriastrakhan@gmail.comwrote:
Atul, one of the fun projects that has been sitting on my backburner is to implement errors and warnings localization for the Web API. The project would involve some planning, figuring out translation framework, and later
- converting all API modules and extensions to use it. As a result, all
clients, including mobile, will be able to report errors to the users in their native language. I am not sure how GSOC supervision functions, but I will definitely be involved with the implementation.
This is slightly bigger than a bug fix, but should be fairly independent from everything and will give you good exposure into internals as well as javascript and other clients.
I think this is a potential 'good' project itself. There are also small tasks associated that the applicant can learn from, say properly handle the errors and warnings in an extension that doesn't already do it.
On Tue, Feb 26, 2013 at 11:20 AM, Atul Agrawal adi.mdkk2@gmail.com wrote:
@Waldir:working on the link you sent me.I will notify you if I need any help
@Quim:While I will love to work under a project and be guided .It will be great if you can suggest some beginner level project and I can work with someone or by my own. I will like to solve arithmetic bugs,logical bugs,deadlock situation and teamworking bugs. And one more thing as mediaWiki documentation is so vast, how will I know in which specific area I have to develop my skills so that I will able to get the idea as well as solve it which will be proposed for gsoc 2013?Do
I
need to contact the mentors?
Thanks for being so helpful.
Atul
On Tue, Feb 26, 2013 at 9:13 PM, Quim Gil qgil@wikimedia.org wrote:
On 02/26/2013 01:23 AM, Atul Agrawal wrote:
Thanks a lot.Will try to fix bugs.But what knowledge should I have to
fix
bugs?knowing php is sufficient?Till now I have read this page( Developing_Extensions<http://**www.mediawiki.org/wiki/Manual:** Developing_extensions<
http://www.mediawiki.org/wiki/Manual:Developing_extensions%3E
.If
you can share the documents one should read before fixing bugs,I will
be
highly obliged.
We have many different software projects, and what to read depends pon what bugs you want to fix.
Why not choosing first a project or a bug that interests you, and then learn about the pieces involved as you try to fix it?
We can help you find a first bug. What is your area of interest?
-- Quim Gil Technical Contributor Coordinator @ Wikimedia Foundation http://www.mediawiki.org/wiki/**User:Qgil<
http://www.mediawiki.org/wiki/User:Qgil%3E
______________________________**_________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/**mailman/listinfo/wikitech-l<
https://lists.wikimedia.org/mailman/listinfo/wikitech-l%3E
-- Atul Agrawal B.E Mechanical BITS PILANI Goa Campus Mobile:+91-81491-95049 _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l