Committing permissions are based on a separate file though, so we'll need to establish where each of your projects is going to 'live' in the repository. Options are:
1. Directly on the HEAD
This is appropriate if your work is core, and it's possible to isolate any potential side effects from other students and developers fairly easily, e.g. through a #define.
2. In a separate branch
This is to be used if your work is core, but it's disruptive and not easy to isolate. To prevent it getting in the way of anyone else's work, you'll have your own branch to work in which, if all goes well, will eventually be merged back into the HEAD. This is how most of the SoC 2006 projects functioned and we do this periodically for our own work if there's something long-running that will cause significant temporary instability.
3. In an isolated subtree
If your project is a tool and won't affect anything in the core, you can have a separate folder area to work in on the HEAD. For example ogreaddons/ or ogrenew/Tools are possibilities.
Students, as part of your preparation before coding starts, please plan out where you think your work should go, in collaboration with your mentor, and I'll organise access. We'll update the Wiki to reflect that too so that community members know where to get the latest work in progress.
2 students have decided on this already, Brian Johnstone (Praetor, scripting) will be working on the HEAD since the scripting classes should be fairly easily pluggable, and Tim Kelsey (c4llidus) will be working in the soc07-memory branch since his changes are likely to be quite disruptive. Your access is granted so you can start committing whenever you like.
There's no pressure to start yet though, this is still the familiarisation and planning phase
Just be ready by 28th May at the latest.