Starting Development

Threads related to Google Summer of Code
Post Reply
User avatar
sinbad
OGRE Retired Team Member
OGRE Retired Team Member
Posts: 19265
Joined: Sun Oct 06, 2002 11:19 pm
Location: Guernsey, Channel Islands
x 66
Contact:

Starting Development

Post by sinbad »

Ok, I've added all students to the developers list on Sourceforge, so you should all now be able to connect to CVS using a full developer account, ie via SSH. Please see the Sourceforge documentation on this.

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.

User avatar
Hudson
Halfling
Posts: 60
Joined: Thu Sep 14, 2006 2:46 pm
Location: NY
Contact:

Post by Hudson »

I talked it over briefly with CaseyB, I think ogrenew/Tools/MaterialEditor makes the most sense.

juozasg
Kobold
Posts: 35
Joined: Sun May 07, 2006 7:13 am

Post by juozasg »

I wrote to haffax about this in more detail, but I think because I'll be making many changes in OgreMain and RenderSystems folders as well as in Media, Tests and adding a new folder to Tools it makes the best sense for me to work in a new branch. We could call it ogre-emulategpu.

User avatar
sinbad
OGRE Retired Team Member
OGRE Retired Team Member
Posts: 19265
Joined: Sun Oct 06, 2002 11:19 pm
Location: Guernsey, Channel Islands
x 66
Contact:

Post by sinbad »

@Hudson: ok, you have access to ogrenew/Tools/MaterialEditor on HEAD now.

@juozasg: I've given you blanket permission and created a new branch called 'soc07-emulation' (renamed for consistency with other tags). Please make sure you checkout this branch to work on using the -rsoc07-emulation option.

Post Reply