On Dec 12, 2007, at 6:45, Trond Norbye wrote:
My first question is about SCM.
We are a team of developers here that are going to be working on the
code, and want to share our work with the team while we're working.
I am not a big fan of sending "diff-files" within the team and
applying them, since tracking the changes will become difficult
(until we're done so we can push a patch back out to the community
to get it integrated into the Subversion repository).
I'm a giant subversion anti-fan for the very reason that it makes
efforts like yours (and mine) a lot more difficult. If you're not
part of the core group with access to the (hopefully available)
central repo, then it quickly becomes increasingly difficult for
people to review your changes and for you to keep them up-to-date as
other changes make it into the subversion trunk.
That said, distributing patches is currently the only means of making
changes available as someone who doesn't have commit access.
I managed this by using mercurial queues to maintain my changes atop
a tree I replicated from subversion. Other developers do the same by
using git-svn or similar.
Perhaps it'd be appropriate to have community repositories upon which
we can build and review features and then have the svn maintainers
pull interesting changes from these.
--
Dustin Sallings
