while the above post is still relevant, i wanted to clarify something
to my knowledge, we have not had any issues with collisions thus far
as you guessed, it is probably still a bit early for that :)
as we are in the 'svn add' phase of things for the most part, these breakages should be more easily avoided
2.0.1 file X has class foo, then a gsoc developer adds file Y and redeclares class foo
that is the gist of the type of problems occurring, along with that, ive seen include path issues in other files
hopefully this clears some things up
my original message for archival purposes:
As of late there have been a good number of breakages in the gsoc branches of
the subversion repository. I had some of my own ideas for resolving simple
things like class redeclarations (commenting), and Elijah seemed on the same
page. What would be ideal though, is if we could avoid issues like this all
together. As an example, again, a class redeclaration: the developer working
on the code in question could comment it his/herself before committing the code.
Or, even better, name the class something else for the time being, then, if
need be, the class name can be refactored later on. There have also been some
more serious issues that many of us have probably had to deal with, so
resolutions may be more involved in those cases.
I encourage others to send their thoughts on this, as I am surely no authority
on the issue."