Coding conventions

Would be nice if we agreed on some conventions so that we could collaborate effectively.

I’d suggest trying to make code more portable for the development and deployment purposes:

It should be easy to separate customizations from the core code. I’d like to avoid going through my settings.py to remove passwords before I can commit my changes to the public repository. Maybe we should at least group those settings in the end of the settings.py – if possible?

Alternatively – we can have a separate local_settings.py with very simple structure that can be cleaned automatically by some script.

Another annoying part – having to remove site-specific messages from .po file before commit – here I can’t suggest anything yet, but this is a significant barrier for sharing local changes.

Thirdly – should we set up meta discussion group – maybe using the development version of the software? So that we could discuss programming aspects? Wiki is not perfect for discussions… Posted this here because I don’t see other place.

—Evgeny.

Hey Evgeny,
I think the answer to your first question lies in settings_local.py.dist you are suppose to move that to settings_local.py and that is ignored by git. The answer to your second part I think is forking the cnprog. Merging changes every so often from the upstrem to your repo, this is also something i have done. I forked this project so I could develop how I want, and then I merge new changes from upstream in to my fork.