[Soc-2010-dev] SVN welcome mail

Ton Roosendaal ton at blender.org
Sun May 2 13:26:15 CEST 2010


Hi Students,

You've been added as bf-blender project member with svn write access,  
welcome! You can use this access now for working on your own branches  
only. Note that for any other commit you'll have to discuss changes  
with the exisiting owners of code. Consult the bf-committers email  
list or IRC if in doubt.

Here's the standard checklist & guidelines for new devs:

- When you get added as Member of the bf-blender project, you can only  
commit on sources when you've checked out logged-in in SVN, not  
anonymous.

- The *main* rules for committing are:
1) Always ensure that what you commit is either on your "own code", or  
you've verified the patch with the owner of the module. If you want to  
change things in other parts of the code, check with one of the  
developers who owns/maintains that.

2) Always do a 'svn update' and 'svn status' before committing. Check  
carefully if the files marked "Modified" are actually what you want to  
commit. Do a 'svn diff' on files if in doubt.

3) Always contribute code in the style as used in the code you've  
worked on. We just have a long history of software development, and  
can't restyle all code to a unified standard. Keeping style per file  
consistant at least keeps things readable.
Make sure you use real TABs, and unix LFs (end of lines).
For new code, check on the style guidelines on blender.org.

4) Blender is strictly cross-platform, and we only accept code that  
compiles for all current platforms correctly. Keep in mind that's for  
the float library still (no sinf or sqrtf), for OpenGL (nothing newer  
than 1.2, or correctly wrapped), Python (3.0), gcc (3.4 should work),  
msvc (6.0 should work), etc. If in doubt, send a patch to the bf- 
committers list.

5) If you add new C files, check if those get included in SConstruct  
files. Makefiles go fine, but MSVC files need patches too. If you  
don't have MSVC, note this in your commit log, or better: notify the  
bf-committers mailing list or go to the irc.freenode.net  
#blendercoders channel.

6) Subscribe to both mailing lists below:
http://lists.blender.org/mailman/listinfo/bf-committers/
http://lists.blender.org/mailman/listinfo/bf-blender-cvs/

Ok. That's it. Thanks! :)

-Ton-

------------------------------------------------------------------------
Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands



More information about the Soc-2010-dev mailing list