[cvs] [Wiki] changed: GSoC2010Application
Michael Rubinsky
mrubinsk at horde.org
Fri Mar 12 17:26:09 UTC 2010
mrubinsk Fri, 12 Mar 2010 12:26:09 -0500
Modified page: http://wiki.horde.org/GSoC2010Application
New Revision: 1.5
Change log: tweak
@@ -44,18 +44,18 @@
Our mentors are all developers who have been active members of the
project for many years and are still active in current development.
All of them have proven their development skills by contributing
substantial and well written code to the project. They also share a
sense of social skills as they are actively helping users,
administrators and other developers on the mailing lists and on IRC on
a daily basis.
12. What is your plan for dealing with disappearing students?
-First of all we will try hard to not let them disappear at all. From
our experiences in the past we've learned that we need to keep close
contact to the students from the very beginning and demand regular,
active status updates. We won't allow any local development but
require them to use the public SCM repository right from the start and
commit early and often. They have to be available for direct
communication through IRC or IM.
-If they fall off the earth and can't be reached by any means like IM,
direct mail, or phone calls as a last resort, there is not much we can
do though obviously. If we reach them we will try to find out what
kept them from sticking to our rules, and how to improve working
together.
+First of all we will try hard to not let them disappear at all. From
our experiences in the past we've learned that we need to keep close
contact with the students from the very beginning and demand regular,
active status updates. We won't allow any local development but
require them to use the public SCM repository right from the start and
commit early and often. They have to be available for direct
communication through IRC or IM.
+If they fall off the earth and can't be reached by any means like IM,
direct mail, or phone calls as a last resort, there is obviously not
much we can do. If we reach them we will try to find out what kept
them from sticking to our rules, and how to improve working together.
13. What is your plan for dealing with disappearing mentors?
We don't expect any mentors to disappear because we talk to each
other on a daily basis and have known each other for years. If a
mentor has to pass because of illness or similar, there are more
developers on the project that may be able take over mentorship. And
of course the other mentors can jump in too.
14. What steps will you take to encourage students to interact
with your project's community before, during and after the program?
-We will try to give them a warm welcome and introduce them to the
project personally as good as possible. Before the program ends we
will discuss with them how they could imagine to further contribute to
the project, and what roles we as the mentors see for them in the
community. We will also try to keep them attached to their projects by
involving them into the bug reporting and release processes as far as
their work is affected.
+We will try to give them a warm welcome and introduce them to the
project personally as good as possible. Before the program ends we
will discuss with them how they could imagine to further contribute to
the project, and what roles we, as the mentors, see for them in the
community. We will also try to keep them attached to their projects by
involving them in the bug reporting and release processes as far as
their work is affected.
15. What will you do to ensure that your accepted students stick
with the project after !GSoC concludes?
See above? No idea.
More information about the cvs
mailing list