Difference between revisions of "GSOC"

Jump to: navigation, search
(removing note about GSOC 2010)
(content copied from 19 wiki)
Line 67: Line 67:
  
 
==2009==
 
==2009==
{{GSOC 09}}
+
 
 
Overview and results: [[GSOC/2009]]
 
Overview and results: [[GSOC/2009]]
  
Line 75: Line 75:
 
# [[Development:Paint tool|What you paint is what you get]]
 
# [[Development:Paint tool|What you paint is what you get]]
 
# [[Development:Google Gears integration|Google Gears integration]]
 
# [[Development:Google Gears integration|Google Gears integration]]
 +
 +
==2011==
 +
 +
Overview: [[GSOC/2011]]
  
 
==See also==
 
==See also==

Revision as of 15:40, 5 July 2011

Overview

Moodle has been involved in Google's Summer of Code program since 2006. This program pays students to work on open source software products for about three months (over the northern hemisphere summer), mentored by existing developers of those products. The work usually adds a new feature or a new module. The intention is that this new code improves the core software, as well as helping new programmers to become familiar with developing in an open source community.

Matching students and mentors

Mentors are regular Moodle developers who volunteer to help guide and support students in the program. The final decision on who can be a mentor is made by Martin Dougiamas. Successful mentoring is quite a commitment so this task should not be taken on lightly.

Students apply to projects via Google and are evaluated and selected by the full group of Moodle mentors.

Development process

Once students and mentors have been matched with projects within Moodle, our process runs something like this:

Create a specification in Moodle Docs
On the wiki page created for them students should start developing a detailed specification with feedback from mentors. The page should outline database table designs, the GUI (eg mock screenshots), the hows and whys etc. The document should be clear and logically organised.
Seek and absorb community feedback
Students should introduce the project in the appropriate forums on Using Moodle to help draw attention to it and to stimulate some discussion around their development. The more feedback we have the better, especially if it includes a wide variety of users (developers, teachers, students etc). Students should keep responding in those forums to build a dialogue with the community.
Evolve the specification
Students and mentors should use the feedback to evolve the specification into something that all users are happy with. Sometimes it's worth doing more research to find the "best" way to do something without adding Yet Another Option.
Set up tasks in the Moodle Tracker
Once the specification has settled down, it's time to start work. The mentor should create a new issue in the Moodle Tracker, and students should add sub-tasks in roughly chronological order for all the different parts of the project. This helps students keep track of where they are, but also allows the community to "watch you" develop and to help you where they can. Before CVS permission is granted, patches and code can be attached to the sub-tasks.
Develop in CVS and link to tracker
Once CVS permission is granted, students can develop their code in Moodle's CVS repository. Every commit will then be attached automatically to the tracker if it includes an issue number (eg MDL-7777). This process works best for contained projects like modules - for complicated patches it is often easier just to attach successive diffs directly to the tracker bugs.
Advertise milestones in the forums
Major milestones should be posted in the forums, to maintain community interest and draw in new testers and more feedback.
Finish off projects
Once the time is up, finished projects need to be assessed and uploaded to Google as per their instructions. Hopefully the code is also good enough to go into the next Moodle release too!

2006

  1. Presets for Database module project notes
  2. Integrated bug tracker project notes
  3. AJAX course format project notes
  4. Admin page cleanup project notes
  5. Global search project notes

2007

Overview and results: GSOC/2007

  1. New question types
  2. Enterprise-level improvements
  3. Chat revamp
  4. Messaging improvements
  5. Automated grading of programs
  6. User Management Improvements
  7. Email interface
  8. Social Networking features
  9. Development:Voice

2008

Overview and results: GSOC/2008

  1. Usability issues
  2. SQLite
  3. Animated grade statistics report
  4. Language editing interface
  5. Feed aggregation library
  6. Customisable theme
  7. Blog improvements
  8. Further messaging improvements
  9. Automatic accessibility checking
  10. Progress tracking
  11. Secure RSS feeds
  12. Moodle IDE

2009

Overview and results: GSOC/2009

  1. Record audio repository plugin
  2. Timeline course format
  3. Improve Moodle user experience consistency
  4. What you paint is what you get
  5. Google Gears integration

2011

Overview: GSOC/2011

See also