devel:gsoc_organization
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| devel:gsoc_organization [2011-02-13 15:05] – created - copied from devel:gsoc (and adapted) Michitux | devel:gsoc_organization [2012-03-05 20:55] (current) – [Application] andi | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Google Summer of Code Organization ====== | ====== Google Summer of Code Organization ====== | ||
| - | This page is for organizing our participation | + | (Students please have a look at [[gsoc]]) |
| - | If you are a student please have a look at [[gsoc]]. | + | This page is for organizing our participation |
| ===== Mentors ===== | ===== Mentors ===== | ||
| Line 10: | Line 10: | ||
| > Mentors are people from the community who volunteer to work with a student. Mentors provide guidance such as pointers to useful documentation, | > Mentors are people from the community who volunteer to work with a student. Mentors provide guidance such as pointers to useful documentation, | ||
| + | |||
| + | The [[http:// | ||
| Mentors should | Mentors should | ||
| Line 19: | Line 21: | ||
| Feel free to add yourself as mentor also for ideas where a mentor is already listed. Then we can balance the load of the different mentors when it is decided which ideas will actually be implemented so not one mentor has 5 students and another mentor has not a single student. There can also be more than one mentor per student. | Feel free to add yourself as mentor also for ideas where a mentor is already listed. Then we can balance the load of the different mentors when it is decided which ideas will actually be implemented so not one mentor has 5 students and another mentor has not a single student. There can also be more than one mentor per student. | ||
| - | Please put yourself also on the [[gsoc# | + | If you don't like being mentor for any existing idea and don't have own ideas you can still be mentor |
| + | After the application period we will have to review and rank all applications in the GSOC system. There we need to assign the final mentors for each task. | ||
| + | |||
| + | |||
| + | ===== Lessons Learned ===== | ||
| + | |||
| + | Some thoughts from 2011 | ||
| + | * Improve the internal selection of applications process, suggested rating system | ||
| + | - Written their name | ||
| + | - Something in the proposal | ||
| + | - Interesting | ||
| + | - I'd give some time to mentor | ||
| + | - I'd be happy to mentor this | ||
| + | * Add 2-3 public demo's during the summer | ||
| + | * Formalize mentors meeting before midterm and final evaluation -> set dates | ||
| + | * Invite (mail) students to __other__ coding/ | ||
| ===== Application ===== | ===== Application ===== | ||
| Line 26: | 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 | + | Application for mentoring organizations starts at February |
| * For a list of possible projects, see [[devel: | * For a list of possible projects, see [[devel: | ||
| Line 32: | Line 49: | ||
| * Write an [[http:// | * Write an [[http:// | ||
| - 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. | + | * 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. |
| - | * FIXME | + | - Why is your organization applying to participate in Google Summer of Code 2012? What do you hope to gain by participating? |
| - | - Why is your organization applying to participate in Google Summer of Code 2011? What do you hope to gain by participating? | + | * Lessons learned from our participation in 2011 showed |
| - | * We have a couple of larger features | + | |
| - | * New features | + | |
| - | * New developers | + | |
| - 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. | ||
| - | * No | + | * 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)? | ||
| - | * No, the idea existed, but we haven' | + | * - |
| - What license(s) does your project use? | - What license(s) does your project use? | ||
| * GPL version 2. | * GPL version 2. | ||
| Line 47: | Line 61: | ||
| * [[gsoc# | * [[gsoc# | ||
| - What is the main development mailing list for your organization? | - What is the main development mailing list for your organization? | ||
| - | * [[http:// | + | * Our general (and development) mailing list is http:// |
| - What is the main IRC channel for your organization? | - What is the main IRC channel for your organization? | ||
| * irc:// | * irc:// | ||
| - Does your organization have an application template you would like to see students use? If so, please provide it now. | - Does your organization have an application template you would like to see students use? If so, please provide it now. | ||
| - | * Yes, every application needs to cover at least the points at [[gsoc#application]]. | + | * Yes, see [[devel:gsoc#the_application]] (full template included in the actual application) |
| - | * FIXME - ideas can be found e.g. at https:// | + | |
| - Who will be your backup organization administrator? | - Who will be your backup organization administrator? | ||
| * [[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. | ||
| - | * Are active DokuWiki | + | * Our mentors are active |
| - | * see above (needs | + | |
| - | * FIXME | + | |
| - 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 postal address and phone number | + | * Try to contact them (and collect contact information like the phone number at the latest when they are accepted) |
| - | * Make sure they provide their code after each (even small) change so at least we won't loose the code | + | * Make sure they provide their code after each (even small) change |
| - | * FIXME | + | * If they don't reappear or reappear and can't catch up let them fail in the next review (and let them know they will fail in the review of course) |
| + | * If this happens already during the community bonding period contact Google directly | ||
| - What is your plan for dealing with disappearing mentors? | - What is your plan for dealing with disappearing mentors? | ||
| - | * Try to contact them, e.g. by phone | + | * Try to contact them, e.g. by phone, and replace |
| - | * Replace | + | |
| - | * FIXME | + | |
| - What steps will you take to encourage students to interact with your project' | - What steps will you take to encourage students to interact with your project' | ||
| * Require students to subscribe to the mailinglist | * Require students to subscribe to the mailinglist | ||
| Line 72: | 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 | ||
| - | * FIXME | + | * 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? | + | - What will you do to ensure that your accepted students stick with the project after Google Summer of Code concludes? |
| * Encourage them to do so | * Encourage them to do so | ||
| * Students of course keep the copyright of their code so they become part of the project rather than just their code | * Students of course keep the copyright of their code so they become part of the project rather than just their code | ||
| Line 79: | 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 | ||
| - | * FIXME | + | * Actively invite them to join a bug hunting weekend or any other project event directly after GSoC |
devel/gsoc_organization.1297605945.txt.gz · Last modified: 2011-02-13 15:05 by Michitux