devel:gsoc_organization
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| devel:gsoc_organization [2012-02-10 20:24] – Adapted a bit for 2012 and began adapting the actual application to this year Michitux | devel:gsoc_organization [2012-03-05 20:55] (current) – [Application] andi | ||
|---|---|---|---|
| Line 43: | Line 43: | ||
| Some examples of how to (not) do it [[http:// | Some examples of how to (not) do it [[http:// | ||
| - | Application for mentoring organizations starts at February 27 and goes till March 9 2012. Project administrator for Google Summer of Code will be FIXME (candidate is [[user> | + | Application for mentoring organizations starts at February 27 and goes till March 9 2012. Project administrator for Google Summer of Code will be [[user> |
| * For a list of possible projects, see [[devel: | * For a list of possible projects, see [[devel: | ||
| Line 50: | Line 50: | ||
| - Describe your organization. | - Describe your organization. | ||
| * DokuWiki is a standards compliant, simple to use Wiki, mainly aimed at creating documentation of any kind. It is targeted at developer teams, workgroups and small companies. It has a simple but powerful syntax which makes sure the datafiles remain readable outside the Wiki and eases the creation of structured texts. All data is stored in plain text files – no database is required. A powerful plugin system makes the implementation of additional features like blogging possible while the core code still follows the KISS principle. DokuWiki is used by many individuals, | * DokuWiki is a standards compliant, simple to use Wiki, mainly aimed at creating documentation of any kind. It is targeted at developer teams, workgroups and small companies. It has a simple but powerful syntax which makes sure the datafiles remain readable outside the Wiki and eases the creation of structured texts. All data is stored in plain text files – no database is required. A powerful plugin system makes the implementation of additional features like blogging possible while the core code still follows the KISS principle. DokuWiki is used by many individuals, | ||
| - | - Why is your organization applying to participate in Google Summer of Code 2011? What do you hope to gain by participating? | + | - Why is your organization applying to participate in Google Summer of Code 2012? What do you hope to gain by participating? |
| - | * We have a couple of larger features | + | * Lessons learned from our participation in 2011 showed |
| - Did your organization participate in past Google Summer of Codes? If so, please summarize your involvement and the successes and challenges of your participation. | - Did your organization participate in past Google Summer of Codes? If so, please summarize your involvement and the successes and challenges of your participation. | ||
| - | * Yes, we participated in 2011 for the first time. We mentored two students we selected out of 50 applications, | + | * Yes, we participated in 2011 for the first time. We mentored two students we selected out of 50 applications, |
| - If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)? | - If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)? | ||
| * - | * - | ||
| Line 69: | Line 69: | ||
| * [[user> | * [[user> | ||
| - What criteria did you use to select these individuals as mentors? Please be as specific as possible. | - What criteria did you use to select these individuals as mentors? Please be as specific as possible. | ||
| - | * Our mentors are active contributors and know the DokuWiki code. All of them have direct commit access to our main repository and are also active members of the DokuWiki community. We have met each other in person at Hackfests. We've currently only three mentors not because there aren't any other developers but because the other developers don't have the time for mentoring students and we want to make sure that mentors really have the time that is needed for GSoC. | + | * Our mentors are active contributors and know the DokuWiki code. All of them have direct commit access to our main repository and are also active members of the DokuWiki community. We have met each other in person at Hackfests. |
| - What is your plan for dealing with disappearing students? | - What is your plan for dealing with disappearing students? | ||
| * Try to contact them (and collect contact information like the phone number at the latest when they are accepted) | * Try to contact them (and collect contact information like the phone number at the latest when they are accepted) | ||
| Line 82: | Line 82: | ||
| * Encourage them to ask questions on the mailinglist and in the IRC channel rather than via private chat/mail - of course mentors will be present there and will make sure the questions are answered | * Encourage them to ask questions on the mailinglist and in the IRC channel rather than via private chat/mail - of course mentors will be present there and will make sure the questions are answered | ||
| * Require students to present their concept and intermediate stages of their work on the mailinglist | * Require students to present their concept and intermediate stages of their work on the mailinglist | ||
| + | * Encourage them to fix and commit a least one minor bug from our bugtracker | ||
| - What will you do to ensure that your accepted students stick with the project after Google Summer of Code concludes? (This question hasn't been part of the actual application) | - What will you do to ensure that your accepted students stick with the project after Google Summer of Code concludes? (This question hasn't been part of the actual application) | ||
| * Encourage them to do so | * Encourage them to do so | ||
| Line 88: | Line 89: | ||
| * Depending on the nature of the changes and how much review/ | * Depending on the nature of the changes and how much review/ | ||
| * Give students commit access to the main repository so they can easily contribute changes if the changes they submit show that they are able to work directly in the main repository | * Give students commit access to the main repository so they can easily contribute changes if the changes they submit show that they are able to work directly in the main repository | ||
| + | * Actively invite them to join a bug hunting weekend or any other project event directly after GSoC | ||
devel/gsoc_organization.1328901861.txt.gz · Last modified: 2012-02-10 20:24 by Michitux