User:Clancer

This is the template for candidates who want to apply to mentorship programs such as Google Summer of Code or Outreach Program for Women.

The sooner we know about your project proposal the better. We can save you a lot of time by bringing more eyes to your draft and pointing you to the right direction. You are encouraged to start drafting your application as a subpage of your mediawiki.org userpage as soon as possible. Once you feel the basic idea is framed, the next steps will be to find or file an enhancement request at Bugzilla and send an email to the wikitech-l mailing list including the links to your wiki page and your bug report.

If you have any question the best place to ask is the Discussion page related to the program you are applying to.

Check also some real examples of good GSoC project proposals.

Name and contact information
Name: Rohan Verma Email: rohan.j.verma@gmail.com IRC or IM networks/handle(s): clancer Location: ACT, Australia TimeZone: GMT +10:00 Typical working hours: 3pm-1am

Synopsis
Short summary describing your project: what it means to accomplish, and how it will benefit MediaWiki or Wikimedia projects such as Wikipedia.

My project will allow users of mediawiki to display course information from a moodle instance. This will benefit MediaWiki by extending the wikitext parser to handle a new type of tag for moodle integration. This project will also benefit Wikimedia projects that also use a moodle instance. Educational instutions will be able to display updated course information easily in their wiki.

Deliverables
Required
 * Extension adds tag to wikitext
 * This tag gathers information about a moodle course
 * Gathers information using moodle webservices
 * Displays information in a well formatted node

Optional
 * Extension can gather other information from moodle
 * tag takes different parameters


 * Extension allows user to specify which moodle instance to gather information from
 * prefix system for identifing moodle instances
 * moodle instance url stored in mediawiki database

Schedule
Investation - April 30
 * Continue reading through MW source code and extension sourcecode
 * Continue contact with mentor and other interested person about the design of the extension
 * Explore capabilities of gathering information from moodle through a MW extension
 * Finish Investigation deadline - May 27

Community Bonding - May 28
 * Keep in contact
 * Use/Lurk IRC all day every day
 * Use/Read mailing list to help with design
 * Fix bugs and contribute to MediaWiki community


 * Try to find out more about culture
 * Review other successful people in mediawiki
 * Try to get advice from past GSoC participants
 * Have fun

Milestone 1 Design finished - June 16
 * Design will include a high level diagram of extension
 * Design will specify functionality of the extension
 * What the parameters of the tag will be
 * What information will be gathered from the webservices


 * Design will include a class diagram of implementation

Coding start! - June 17
 * 2 Week - Implement moodle tag with parameters
 * 3 Weeks - Gather information from moodle webservices
 * 1 Weeks - Displays information correctly

Milestone 2 Coding deadline and passes unit tests - August 11
 * Tests will include:
 * Calls to moodle webserives
 * Parameters passed to tag
 * Functions defined in each class

Finish Code Review deadline - August 25
 * Some (hopefully all) files reviewed by mentor/community
 * Conduct own code review according to MW standards
 * better not to bother others will small things

Cleaning up, Reworking, Other awesome stuff - August 26
 * Testing everything
 * Integration Testing
 * System Testing


 * Applying feedback from code reviews
 * Documentation
 * Finish basic documentation of extension
 * Continue documentation of changes

Milestone 3 Ready for deployment, testing and documentation finished - September 8
 * Yay!!
 * Start Deployment

Finish Deploying deadline - September 16
 * Merged with trunk
 * Left one week to quick fix anything that goes wrong

Milestone 4 Glory - Eternal
 * Will include cake

About you
We don't just care about your project -- you are a person, and that matters to us! What drives you? What makes you want to make this the most awesomest wiki enhancement ever?

You don't need to write out your life story (we can read your blog if we want that), but we want to know a little about what makes you tick. Are you a Wikipedia addict wanting to make your own experience better? Did a wiki with usability problems run over your dog, and you're seeking revenge? :-) What does making this project happen mean to you?

Participation
We don't just want to know what you plan to accomplish; we want to know how. Briefly describe your work style: how you plan to communicate progress, where you plan to publish your source code while you're working, how and where you plan to ask for help. (We will tend to favor applicants that demonstrate a clear vision for what it means to be an active participant in our development community.)

Past open source experience
Thoughout last year I worked with a small team from my university to develop a set of plugins for Moodle. Learning Outcome Wizard This project allows Education Developers share ways to design courses in moodle more effectively. It did this by allowing them to create flowcharts in a tree structure containing a series of questions. A user who used this model would go through the series of questions and at the end be linked to a moodle activity such as a forum that would be appropriate for their course.

Any other info
Please add any other relevant information -- UI mockups, references to related projects, a link to your proof of concept code, whatever. There are no specific requirements, but we love to see people who love what they're doing. Show us you're excited about this project and have an interest in the background and are considering how best to make your idea work.