From faassen at startifact.com  Thu May  8 11:16:38 2008
From: faassen at startifact.com (Martijn Faassen)
Date: Thu May  8 11:16:40 2008
Subject: [Gsoc] Attention mentors and students: communication rules for the
	google summer of code
Message-ID: <8928d4e90805080816k581a6e2eve1fbe849b4b5c668@mail.gmail.com>

Hi there,

I just posted the following to arrange some communication rules:

http://wiki.zope.org/gsoc/SummerOfCodeCommunication

Quick summary of the rules:

* weekly communication between mentor and student (beyond email, set time aside)

* weekly reports by mentor and student individually to the mentor
coordinator (that's me), by email.

* each project needs a backup-mentor assigned.

* mentors, update
http://wiki.zope.org/gsoc/SummerOfCode2008AcceptedProjects with your
project's information

I will be checking the accepted projects page in a few days and hunt
down those mentors who haven't updated it yet, or don't have a backup
mentor yet. :)

Regards,

Martijn
From faassen at startifact.com  Thu May  8 11:26:55 2008
From: faassen at startifact.com (Martijn Faassen)
Date: Thu May  8 11:26:54 2008
Subject: [Gsoc] students: where to checkin code
Message-ID: <8928d4e90805080826q156edcf7yf6b0516581087dab@mail.gmail.com>

Hi there,

During the actual development, the Zope Foundation students are
required to check in their code in svn.zope.org. This is something the
mentors already have access to, and for the students it is a good idea
to have write access to svn.zope.org in any case. Your mentor can help
get you write access if you don't have it already.

If after the project you want to take your project further and you do
not want to use svn.zope.org anymore for some reason, this is open to
you, even though we encourage all students to continue contributing
there. During the project we should see your work being done in
svn.zope.org, however.

Note that I recall the summer of code itself wants all code produced
to also be in code.google.com at the end. This we see as a final
delivery step, and not as the main working environment.

Regards,

Martijn
From faassen at startifact.com  Thu May  8 14:23:36 2008
From: faassen at startifact.com (Martijn Faassen)
Date: Thu May  8 14:23:35 2008
Subject: [Gsoc] Re: students: where to checkin code
In-Reply-To: <8928d4e90805080826q156edcf7yf6b0516581087dab@mail.gmail.com>
References: <8928d4e90805080826q156edcf7yf6b0516581087dab@mail.gmail.com>
Message-ID: <8928d4e90805081123x74f81770n90c6d0bf9a5fd877@mail.gmail.com>

Mentors,

Getting checkin access for your students, is detailed here:

http://wiki.zope.org/gsoc/UsingSvnZopeOrg

Regards,

Martijn
From luciano at ramalho.org  Tue May 27 11:46:57 2008
From: luciano at ramalho.org (Luciano Ramalho)
Date: Tue May 27 11:46:56 2008
Subject: [Gsoc] Flint: bonding period report
Message-ID: <4331ad810805270846m15300dc8v8d59b15eada87e83@mail.gmail.com>

My mentor, Leo, requested a report about our activities during the
GSoC "bonding period", so here it is.

I am fortunate to have a close friend as a mentor this year, so we did
not feel much further "bonding" was required or appropriate :-).

However, we did take advantage of the fact that we live in the same
city to meet a few times (I think it was three times, about 9h total)
to discuss the design of Flint, and take a good look at Drupal, which
is probably the most important non-Zope Open Source CMS out there. We
also spent some time outside of those meetings writing about Flint. I
also took some time to reread parts of Philkon's Zope 3 book,
particularly those concerning the implementation of the idea of
"content" within Zope-3, an area that we have not explored so much in
Grok, IMHO.

Some of what we discussed is posted here:

http://flint-cms.blogspot.com/

And we also wrote some specs and ideas in the project Wiki here:

http://code.google.com/p/flint-cms/w/list

I will import some of the texts in that wiki to the Zope SVN repo as
part of the documentation of Flint.

Cheers,

Luciano