<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
<title>
Google Code - Summer of Code
-
Organization Application
</title>
<link href="/css/base-200612.css" type="text/css" rel="stylesheet"/>
<link href="/css/soc.css" type="text/css" rel="stylesheet"/>
</head>
<body>
<div id="gaia">
<b>asouzaleite@gmx.de</b> |
<a href="http://code.google.com/p/google-summer-of-code/issues/list">Report bugs</a> |
<a href="http://www.google.com/accounts/Logout?continue=http://code.google.com/soc/">Sign out</a>
</div>
<div id="header">
<div id="logo"><a href="/"><img src="/images/code_sm.png" alt="Google"/></a></div>
<div id="title">
Organization Application
</div>
<div id="breadcrumbs">
<span class="item"><a href="/">Google Code Home</a></span> >
<span class="item"><a href="/soc/2008/">Google Summer of Code</a></span> >
<span class="selected"><a href="/soc/2008/org_signup.html">Organization Application</a></span>
</div>
</div>
<div id="side" dir="ltr">
<div id="menu">
<h4><a href="/">Google Code Home</a></h4>
<ul>
<li><a href="/apis/">Google APIs</a></li>
</ul>
<ul>
<li><a href="/eventcalendar.html">Event Calendar</a></li>
</ul>
<ul>
<li><a href="/oss.html">Open Source</a>
<ul>
<li><a href="/soc/2008/">Google Summer of Code</a>
<ul>
<li><a href="/soc/2008/faqs.html">Program FAQs</a></li>
</ul>
</li>
<li><a href="http://code.google.com/opensource/ghop/">GHOP Contest</a>
</li>
<li><a href="/organizations.html">Organizations</a></li>
<li><a href="/projects.html">Projects</a></li>
<li><a href="/gadgets.html">Gadgets</a></li>
<li><a href="/patches.html">Patches</a></li>
<li><a href="/mirrored.html">Mirrored Code</a></li>
<li><a href="/hosting/">Project Hosting</a></li>
</ul>
</li>
</ul>
<ul>
<li><a href="http://www.google.com/codesearch">Google Code Search</a></li>
</ul>
<ul>
<li><a href="/support/">Knowledge Base</a></li>
</ul>
</div>
<div id="search">
<form id="searchbox_015986126177484454297:pfmwlvdl42y" action="http://www.google.com/cse">
<input type="hidden" name="cx" value="015986126177484454297:pfmwlvdl42y" />
<input type="hidden" name="cof" value="FORID:0" />
<div class="header">Search Google Code:</div>
<input name="q" type="text" size="20" />
<input type="submit" name="sa" value="Search" /><br/>
</form>
<script type="text/javascript" src="http://google.com/coop/cse/brand?form=searchbox_015986126177484454297:pfmwlvdl42y"></script>
</div>
</form>
</div>
</div>
<script type="text/javascript">
//<![CDATA[
function walk(element, condition, operation) {
if (!element) return;
if (condition(element)) {
operation(element);
return;
}
for (var e = element.firstChild; e != null; e = e.nextSibling) {
walk(e, condition, operation);
}
}
function isCurrentLink(e) {
return e.tagName == "A" && e.href == window.location.href;
}
function makeSelected(e) {
e.className = "selected";
}
walk(document.getElementById("breadcrumbs"), isCurrentLink, makeSelected);
walk(document.getElementById("menu"), isCurrentLink, makeSelected);
//]]>
</script>
<div id="body">
<div id="pageTitle">
<h2>Google Summer of Code™ Organization Application</h2>
<h3>
Thank you for signing up your organization with the Google Summer of
Code.
</h3>
</div>
<a name="__top"></a>
<div
style
="padding: 5px; line-height: 145%; font-size: small; margin-left: 3px;"
>
<p style="font-size: large;">
</p>
<form
>
<input type=hidden name=token value='9f3f0c67a3331357c62afe2601979c95'>
<table
class=
"tB"
cellpadding="0"
cellspacing="0"
width="100%">
<tbody>
<tr>
<td>
About Your Organization
</td>
<td style="text-align: right;">
<a href="#__top">^ back to top </a>
</td>
</tr>
</tbody>
</table>
<ol>
<li>
<dl>
<dt>
What is your Organization's Name?
</dt>
<dd>
<input
readonly
disabled=disabled
style="color:#000000"
name="name"
type="text" size="64"
value="Zope Foundation, Inc">
</dd>
</dl>
</li>
<li>
<dl>
<dt>
What is your Organization's Homepage?
</dt>
<dd>
<input
readonly
disabled=disabled
style="color:#000000"
name="homepage"
type="text" size="64"
value="http://foundation.zope.org">
</dd>
</dl>
</li>
<li>
<dl>
<dt>
Describe your organization.
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="descript"
rows="5"
cols="100">The Zope Foundation has the goal to promote, maintain, and develop the Zope (http://zope.org) platform. It does this by supporting the Zope community. Our community includes the open source community of contributors to the Zope software, contributors to the documentation and web infrastructure, as well as the community of businesses and organizations that use Zope.
The Zope Foundation is the copyright holder of the Zope software and many extensions and associated software. The Zope Foundation also manages the zope.org website, and manages the infrastructure for open source collaboration.</textarea>
</dd>
</dl>
</li>
<li>
<dl>
<dt>
Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="whyJoin"
rows="5"
cols="100">We hope to gain useful contributions to our software, and more importantly, more long-term contributors to the Zope project. Last year's four summer of code students all continued to contribute to our project after the summer of code project.
The Zope Foundation hopes to promote interest in participating in the Zope development process as an open source project, and participating in the Zope community in general. We already learned much about the new developer process in last year's participation, and would like to take this GSoC? as an opportunity to implement some of our observations.</textarea>
</dd>
</dl>
</li>
<li>
<dl>
<dt>
Did your organization participate in previous GSoC years? If so,
please summarize your involvement and the successes and failures of your student projects. (optional)
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="oldSocInfo"
rows="5"
cols="100">The Zope Foundation participated in the 2007 GSoC? for the first time with 4 projects, all of them successful. As mentioned above, the students in all four projects continued to participate in our community after the SoC? period.
Last year our main problems involved communication: it took us a while to set up good communication channels between mentors and students, and different mentors and students approached this differently. For this year, the roles of the ZF SoC? general administration and that of the ZF mentor leader are being better defined and differentiated. The mentor leader will provide both mentors and students with guidelines and quality standards to follow, and will require reporting to track progress throughout the project. The most important goal of these guidelines is ensure good communication between all parties involved, with the aim to prevent a student from getting "stuck" on a project.
The ZF expects a larger number of mentors and student applications this year, so we need to get more formal to ensure continued SoC project success in 2008. We hope to also start applying this parts of our mentoring infrastructure for the adoption of new developers outside of the GSoC infrastructure.</textarea>
</dd>
</dl>
</li>
<li>
<dl>
<dt>
If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)? (optional)
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="rejectedYears"
rows="5"
cols="100">We did not apply before 2007. (see previous question)</textarea>
</dd>
</dl>
</li>
<li>
<dl>
<dt>
What license does your project use?
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="license"
rows="5"
cols="100">Zope Public License (ZPL)
http://www.zope.org/Resources/License/ZPL-2.1</textarea>
</dd>
</dl>
</li>
<li>
<dl>
<dt>
URL for your ideas page
</dt>
<dd>
<input
readonly
disabled=disabled
style="color:#000000"
name="ideas"
type="text" size="64"
value="http://wiki.zope.org/gsoc/SummerOfCode2008">
</dd>
</dl>
</li>
<li>
<dl>
<dt>
What is the main development mailing list for your organization?
</dt>
<dd>
<input
readonly
disabled=disabled
style="color:#000000"
name="mailinglist"
type="text" size="64"
value="zope-dev@zope.org">
</dd>
</dl>
</li>
<li>
<dl>
<dt>
Where is the main IRC channel for your organization?
</dt>
<dd>
<input
readonly
disabled=disabled
style="color:#000000"
name="irc"
type="text" size="64"
value="irc://irc.freenode.net/#zope">
</dd>
</dl>
</li>
<li>
<dl>
<dt>
Does your organization have an application template you would like to see students use? If so, please provide it now. (optional)
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="appTemplate"
rows="5"
cols="100">Not yet. The ZF mentor leader is currently working on a set of ZF specific GSoC student application guidelines that will be published in in the ZF GSoC ideas page before the start of the GSoC student application period.</textarea>
</dd>
</dl>
</li>
<li>
<dl>
<dt>
Who will be your backup organization administrator? Please enter their Google Account address. We will email them to confirm, your organization will not become active until they respond. (optional)
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="backupAdmin"
rows="5"
cols="100">martijn.faassen@gmail.com</textarea>
</dd>
</dl>
</li>
</ol>
<table
class=
"tB"
cellpadding="0"
cellspacing="0"
width="100%">
<tbody>
<tr>
<td>
About Your Mentors
</td>
<td style="text-align: right;">
<a href="#__top">^ back to top </a>
</td>
</tr>
</tbody>
</table>
<ol>
<li>
<dl>
<dt>
What criteria did you use to select these individuals as mentors? Please be as specific as possible.
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="mentorCriteria"
rows="5"
cols="100">For an updated mentor list see: http://wiki.zope.org/gsoc/SummerOfCode2008#Mentors
We have asked core Zope committers whether they are interested to mentor students in an open call to the relevant mailing lists. The people who volunteered are all strongly involved into the Zope project as well as very familiar with the Zope codebase and Zope's goal for the upcoming releases.</textarea>
</dd>
</dl>
</li>
<li>
<dl>
<dt>
Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional)
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="mentors"
rows="5"
cols="100">fritigern@gmx.net, martijn.faassen@gmail.com</textarea>
</dd>
</dl>
</li>
</ol>
<table
class=
"tB"
cellpadding="0"
cellspacing="0"
width="100%">
<tbody>
<tr>
<td>
About The Program
</td>
<td style="text-align: right;">
<a href="#__top">^ back to top </a>
</td>
</tr>
</tbody>
</table>
<ol>
<li>
<dl>
<dt>
What is your plan for dealing with disappearing students?
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="disappearingStudents"
rows="5"
cols="100">We hope that the mentors will be able to encourage the students enough not to leave their project in the first place. In particular, we want our mentors to guide the student through the initial project phase of defining the exact goals, non-goals and specifications of the project. By having clear guidelines and communication channels for students to mentors, we hope to increase the student commitment. The student should have a clear way to indicate they are feeling lost or feel stuck, so that the mentor can help.
If a student actually decides to leave, the project will likely be taken on by somebody from the Zope community in the future (depending on the priority) or be saved for the next season.</textarea>
</dd>
</dl>
</li>
<li>
<dl>
<dt>
What is your plan for dealing with disappearing mentors?
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="disappearingMentors"
rows="5"
cols="100">Last year's experience shows that the ZF tends to have a surplus of potential mentors. There is no problem in finding backup mentors among the Zope community. This year, the mentor leader will have a much better defined strategy of keeping in touch with mentors and students weekly in order to follow each project closely and provide for continuity in case something is in danger of getting stuck. (see also (3)). We will assign a backup mentor for each project and let the students know about them, so that if a mentor is absent the student can contact the backup mentor.
We will also require regular reporting by both students and mentors so that the overal coordination can take action when reports fail to come in.</textarea>
</dd>
</dl>
</li>
<li>
<dl>
<dt>
What steps will you take to encourage students to interact with your project's community before, during and after the program?
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="interactionDuring"
rows="5"
cols="100">We constantly encourage people to get involved in the Zope community and are trying to keep the bar for that low. We will certainly send out a call to all people who are using Zope in education to get students interested in this project. No matter whether they are funded by GSoC? or not, they and their contributions are always welcome. For particular guidance, students are welcome to contact any of the mentors, no matter whether they're funded or not.
We expect mentors to encourage students to get involved with the community from the beginning. We will require regular contact either through voice or irc. We also expect mentors to "show the students around", explain to them how our community works, who the key people are and how things work "around here". We also encourage local user groups to invite the students in that area for face-to-face meet ups.
Last year, two of our four students participated in the EuroPython conference in Lithuania during the summer. Two of the students (those working on a Grok-related task) also participated in a Grok development sprint in Germany in october.</textarea>
</dd>
</dl>
</li>
<li>
<dl>
<dt>
What will you do to ensure that your accepted students stick with the project after GSoC concludes?
</dt>
<dd>
<textarea
readonly
disabled=disabled
style="color:#000000"
name="interactionAfter"
rows="5"
cols="100">Regular contact and real life meetings help. As mentioned , students were involved with real-life meetings, which encourages participation. One of the two students that was in our week-long development sprint in Germany in October lives in Brazil, and the community funded his participation in Germany. Last year's four students are now all active and known in the Zope community.
We encourage students to participate in email and irc discussions on their projects. During the tasks, we point out important tasks and topics so that there is a ready set of potential tasks to work on after the conclusion of GSoC.
Students that use the projects in their own work are also encouraged to continue. We therefore want to encourage students to use Zope to solve their own problems both at school and in their workplace.</textarea>
</dd>
</dl>
</li>
</ol>
<table
class=
"tB"
cellpadding="0"
cellspacing="0"
width="100%">
<tbody>
<tr>
<td>
Thanks!
</td>
<td style="text-align: right;">
<a href="#__top">^ back to top </a>
</td>
</tr>
</tbody>
</table>
</form>
</div>
</div>
</div>
<div id="footer" dir="ltr">
<div class="text">
©2007 Google -
<a href="http://www.google.com/">Google Home</a> -
<a href="http://www.google.com/jobs/">We're Hiring</a> -
<a href="http://code.google.com/tos.html">Terms of Service</a> -
<a href="http://www.google.com/privacy.html">Privacy Policy</a> -
<a href="http://groups.google.com/group/codesite-discuss">Discussion Group</a>
</div>
</div>
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct="UA-18071-1"; // code.google.com site-wide tracking
_uanchor=1;
_uff=0;
urchinTracker();
</script>
</body>
</html>