SoC2007 application: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
No | No | ||
== | ==If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?== | ||
== | |||
==Who will your organization administrator be? Please include Google Account information.== | |||
Oleksandr Moskalenko <moskalenko@gmail.com> | Oleksandr Moskalenko <moskalenko@gmail.com> | ||
==What license does your project use?== | |||
GPL | |||
==What is the URL for your ideas page?== | |||
http://wiki.scribus.net/index.php/SoC2007_ideas | |||
==What is the main development mailing list for your organization?== | |||
http://nashi.altmuehlnet.de/pipermail/scribus/ | |||
==What is the main IRC channel for your organization?== | |||
#scribus on Freenode | |||
==Does your organization have an application template you would like to see students use? If so, please provide it now.== | |||
* Name / University / current enrollment information. | |||
* Biographical sketch. | |||
* Did you ever code in C, C++ or Python? Please provide examples of code. | |||
* Do you use Scribus? Please provide examples if you do. | |||
* Do you make other use of Scribus than for laying out articles? please describe and show examples. | |||
* Were you involved in Scribus development in the past? What were your contributions? | |||
* Were you involved in other OpenSource development projects in the past? If yes, please tell us project, when and in what role were you involved? | |||
* Why have you chosen your development idea and what do you expect from your implementation? | |||
==Who will be your backup organization administrator? Please include Google Account information. == | |||
Alexandre Prokoudine <alexandre.prokoudine@gmail.com> | Alexandre Prokoudine <alexandre.prokoudine@gmail.com> | ||
== | == Who will your mentors be? Please include Google Account Information. == | ||
Andreas Vox <???@gmail.com> | |||
Andreas Vox < | |||
Peter Linnell <mrdocs@gmail.com> | Peter Linnell <mrdocs@gmail.com> | ||
Riku Leino <tsoots@gmail.com> | Riku Leino <tsoots@gmail.com> | ||
Oleksandr Moskalenko <moskalenko@gmail.com> | Oleksandr Moskalenko <moskalenko@gmail.com> | ||
Jean Ghali <darth.scribius@gmail.com> | Jean Ghali <darth.scribius@gmail.com> | ||
=== | ==What criteria did you use to select these individuals as mentors? Please be as specific as possible.== | ||
==What is your plan for dealing with disappearing students?== | |||
==What is | |||
==What is your plan for dealing with disappearing mentors?== | |||
==What steps will you take to encourage students to interact with your project's community before, during and after the program?== | |||
==What will you do to ensure that your accepted students stick with the project after GSoC concludes?== | |||
==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== | ||
Revision as of 19:22, 8 March 2007
Google Summer of Code 2007 application
Describe your organization.
We are used to collaborate across timezones and cultures. For the Google Summer of Code we gave ourself a more formal project organization structure in addition to the two software project organizations hugin and panotools .
Why is your organization applying to participate in GSoC 2007? What do you hope to gain by participating?
Did your organization participate in GSoC 2005 or 2006? If so, please summarize your involvement and the successes and failures of your student projects.
No
If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
Who will your organization administrator be? Please include Google Account information.
Oleksandr Moskalenko <moskalenko@gmail.com>
What license does your project use?
GPL
What is the URL for your ideas page?
http://wiki.scribus.net/index.php/SoC2007_ideas
What is the main development mailing list for your organization?
http://nashi.altmuehlnet.de/pipermail/scribus/
What is the main IRC channel for your organization?
- scribus on Freenode
Does your organization have an application template you would like to see students use? If so, please provide it now.
- Name / University / current enrollment information.
- Biographical sketch.
- Did you ever code in C, C++ or Python? Please provide examples of code.
- Do you use Scribus? Please provide examples if you do.
- Do you make other use of Scribus than for laying out articles? please describe and show examples.
- Were you involved in Scribus development in the past? What were your contributions?
- Were you involved in other OpenSource development projects in the past? If yes, please tell us project, when and in what role were you involved?
- Why have you chosen your development idea and what do you expect from your implementation?
Who will be your backup organization administrator? Please include Google Account information.
Alexandre Prokoudine <alexandre.prokoudine@gmail.com>
Who will your mentors be? Please include Google Account Information.
Andreas Vox <???@gmail.com>
Peter Linnell <mrdocs@gmail.com>
Riku Leino <tsoots@gmail.com>
Oleksandr Moskalenko <moskalenko@gmail.com>
Jean Ghali <darth.scribius@gmail.com>
What criteria did you use to select these individuals as mentors? Please be as specific as possible.
What is your plan for dealing with disappearing students?
What is your plan for dealing with disappearing mentors?
What steps will you take to encourage students to interact with your project's community before, during and after the program?
What will you do to ensure that your accepted students stick with the project after GSoC concludes?
What criteria did you use to select these individuals as mentors? Please be as specific as possible
- familiarity and experience with the prepress technologies
- knowledge of the existing open source technologies applied to desktop publishing
- experience in mentoring junior coders, possibly from an academic environment
- in depth knowledge of user requirements
- ...