Today is (soft) pencil's down date

[Ingo Schommer]

Hello students and mentors,

Today marks the "soft pencils down date", as Google calls it.

This means feature development should stop,

and your attention should shift to polish.

For your projects, this will mean the following activities:

- Documentation (user and dev)

- Test coverage (mainly unit, maybe some functional)

- Continuous integration (e.g. on http://travis-ci.org/)

Yuki has done this for the content personalization module, which is awesome (see post)

- Documenting remaining highlevel work (e.g. in a github wiki page)

- Documenting remaining bugs (e.g. in github issues)

- Creating a release for the module (if applicable), and registering it on ss.org

I've contacted some of you individually about mergebacks,

please use this week to get some peer review,

and do everything you can to ensure a smooth mergeback.

The firm pencils down date is on the 20th (ical).

Many of you have expressed interest to continue working

on your project after GSOC, which is fantastic!

But we also need to submit a "final code result" to Google.

So on the 20th, please tag a release and send me a download link (github generates those automatically).

If there's any code outside of github (there really shouldn't be), you can upload files 

in the "downloads" section of your repo manually as well.

If your project involved core, please include diff files (created through git format-patch?).

Thanks!

Ingo

[Ingo Schommer]

Hello again,

I've just found some official guidance from Google on the code submissions: 

http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/codeguidelines

Thanks

Ingo

On 13/08/2012, at 1:03 PM, Ingo Schommer <in...@silverstripe.com> wrote:

Hello students and mentors,

Today marks the "soft pencils down date", as Google calls it.

This means feature development should stop,

and your attention should shift to polish.

For most of our GSOC projects, this will mean the following:

- Documentation (user and dev)

- Test coverage (mainly unit, maybe some functional)

- Continuous integration (e.g. on http://travis-ci.org/)

Yuki has done this for the content personalization module, which is awesome (see post)

- Documenting remaining highlevel work (e.g. in a github wiki page)

- Documenting remaining bugs (e.g. in github issues)

- Creating a release for the module (if applicable), and registering it on ss.org