[Gsoc] Commiting source to svn

Baiju M mbaiju at zeomega.com
Fri Apr 13 07:00:28 EDT 2007

(I have CC'ed this mail to gsoc list, may be useful to others)

Hi Nikhil,
          I hope you are already started going through Zope
source code, wiki and mailing lists.  Did you send contributor
agreement ?

You can create a branch of Zope 3 trunk to make changes,
Branch can be placed here:

Please ping me before doing your initial commits, also come online
in IRC while doing your commits.  We can merge the changes in
your branch to trunk later.

Here are few things I want to point out about Zope's
svn and committing.

 - This page has more information about how to work
   with Zope Subversion:
   Esapecial Zope SVN FAQ will be really useful:

 - Also go through subpages of this page:

- set svn:eol-style native to new Python and text files

   To set eol-style use this command::

     svn ps svn:eol-style native filename.py

   or a in $HOME/.subversion/config add/replace
   'auto-props' section like this::

     * = svn:eol-style=native

 - Make sure that you are committing to the right URL

   'svn info' will give you the svn URL you are working.

 - If you are using a public machine for working,
   use a passphrase when generating the key.
   You can update your keys from here:

Baiju M

More information about the Gsoc mailing list