--- a/doc/v2_planning/coding_style.txt	Fri Sep 03 15:01:23 2010 -0400
+++ b/doc/v2_planning/coding_style.txt	Fri Sep 03 16:20:10 2010 -0400
@@ -8,9 +8,35 @@
 - David
 - Olivier D [leader unless David wants to be]
 
-Existing Python coding style specifications:
---------------------------------------------
+Existing Python coding style specifications and guidelines:
+-----------------------------------------------------------
 
     * http://www.python.org/dev/peps/pep-0008/
     * http://google-styleguide.googlecode.com/svn/trunk/pyguide.html
+    * http://www.voidspace.org.uk/python/articles/python_style_guide.shtml
+    * http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html
+    * http://www.cs.caltech.edu/courses/cs11/material/python/misc/python_style_guide.html
+    * http://barry.warsaw.us/software/STYLEGUIDE.txt
+    * http://self.maluke.com/style
+    * http://chandlerproject.org/Projects/ChandlerCodingStyleGuidelines
+    * http://lists.osafoundation.org/pipermail/dev/2003-March/000479.html
+    * http://learnpython.pbworks.com/PythonTricks
+    * http://eikke.com/how-not-to-write-python-code/
+    * http://jaynes.colorado.edu/PythonGuidelines.html
+    * http://docs.djangoproject.com/en/dev/internals/contributing/#coding-style
 
+We will probably want to take PEP-8 as starting point, and read what other
+people think about it / how other coding guidelines differ from it.
+
+Documentation:
+--------------
+
+How do we write doc?
+
+Python 3:
+---------
+
+Is it reasonable to have coding guidelines that would make the code as
+compatible as possible with Python 3?
+
+