XWiki Projects

This page hosts project ideas for the Google Summer of Code 2008. Students can come up with their own ideas, and propose them on the mailing list or the IRC channel.

#warning("The GSoC 2008 project is now closed.")

#info("XWiki GSoc 2007 projects are over here")

Topics: #toc("" "2" "")

#set ($sql = ", BaseObject obj, StringProperty year where obj.name=doc.fullName and obj.className='GoogleSummerOfCode.ProjectClass' and doc.name<>'ProjectClassTemplate' and year.id.id = obj.id and year.id.name = 'year' and year.value = '2008' order by doc.name") #set ($projects= $xwiki.searchDocuments($sql))

#macro (displayProject $project $item $student)

#if ($student != "")

$project.display("name")? by $student

#else

$project.display("name")?

#end

$project.details
Coordinated by $project.leader. #if("$!project.workload" != "")Estimated workload: $project.workload.#end Read more...?
#end

Suggested way of working for SOC students

#error("Important Dates (timeline): http://code.google.com/soc/2008/faqs.html#0.1_timeline")

First and foremost, working on XWiki needs to be fun and a good learning process! However the XWiki project is already following some development rules that we're asking SOC students to follow too. This is for the good of the XWiki project but more importantly it's a good way to learn how an open source community works and if these practices are followed then it'll be much easier to integrate the SOC student work into XWiki's official releases.

So here are some practices we'd like SOC students to follow (please comment on the list if you'd like to change some of them or propose other things):

  • SOC students should be considered like any XWiki contributor which means they should respect the same rules and which means they are not committers on XWiki core. Note that a SOC student can become a Committer in the same manner a contributor can become one.
  • SOC students will be given commit access to the sandbox only where they'll create their project (one top level directory for each project). For projects which need to modify some existing code, JIRA issues will need to be created and patches attached. It's important that patches be of good quality and small in order to be applied quickly. Once sandbox projects reach a good level of maturity (meaning they work and the code is of code quality, documented, etc) then we'd like to migrate them to the main release tree.
  • SOC students should obey all Community rules. For example this means:
    • using the XWiki coding conventions
    • using the defined communication channels: IRC and mailing list
    • etc
  • SOC students have time allocated to familiarize with XWiki development process. As such we'd like each SOC student to pick one or several existing issues in JIRA and send a patch that fixes it/them before that period ends (from April 14th to May 26th) This is a critical integration step to ensure all SOC students understand how XWiki works and it's a chance to start asking questions and get to know each other.
  • SOC student should post a quick introduction on the xwiki dev mailing list to explain who they are and what they're going to work on.
  • SOC student should always go to the list when communicating about their project. They should not talk directly to their mentors. They should use the XWiki IRC channel if they need to talk to them. The goal is that everyone in the XWiki community help them, answer their questions but also know what they are doing. This will make patch applications and integration of their work back into XWiki trunk easier later on. This is very important and a criteria of success for the student. This is about learning how open source works… Note that student can also CC their mentor's email address if they want but the mails have to go to the XWiki dev list.
  • SOC students should not block on anything for a long period of time. They should ask plenty of questions on the list (but they should also be autonomous!)
  • SOC students should be as much as possible in contact with the community, following the mailing lists (and answering mails, when they know what to say), stay on the IRC channel, give regular status updates on their project. This does not mean that a SOC student is not allowed to take a break, of course, but that while working a student should be integrated as much as possible with the community.
  • When taking a vacation/break, notify the mentor; a mysterious disappearance could lead to a negative feedback afterwards.
Remember that this is not a summer job, or a Rent-a-coder like project, but a rewarded successful integration in an free software/open source community. If all you are interested in is the money, then better look for a real job, as Free Software requires passionate people; an ideal candidate is more interested in the t-shirt.

Conditions for success

Students will need to meet these criteria for sucess:

  • 1) Must have something that works and is in some finished state.
  • 2) Must be integrated or close to be integrated in xwiki without too much effort
  • 3) Must have interacted correctly and continuously with the community
  • 4) The work must have been enough (it's supposed to be a 2 men/month effort)
Note that the real important part is 3) since this is a criteria for success for 1), 2) and 4).

Student Application template

Please use this template as the basis for you student application which must be submitted to google.

Selected Projects for GSOC 2008

#foreach ($item in $projects) #set($project = $xwiki.getDocument($item)) $project.use("GoogleSummerOfCode.ProjectClass") #if ($project.active == "Yes") #displayProject($project $item "") #end #end

Proposed Projects

#*

*#

$projects.size() projects proposed in total.

#foreach ($item in $projects) #set($project = $xwiki.getDocument($item)) $project.use("GoogleSummerOfCode.ProjectClass") #displayProject($project $item "") #end

Tags:
Created by Sergiu Dumitriu on 2009/03/07 12:30
   

Get Connected