On 06/24/2010 04:43 PM, Sebastian Benthall wrote:
Thanks for stepping up on this!
To make this happen, I'd ask everyone with a task that requires
JavaScript coding to check in with me. By doing so, it should be
much easier to avoid duplicate efforts and share resources.
David and I have been talking a lot about team process and how we can
make DVCS work for us.
One topic that came up was the idea of having topical repositories
which are maintained by domain experts. So, for example, Andreas
could maintain the GeoNode repository or branch that all major JS
changes had to go through. Then we would pull from that repo/branch
to the development or release branches.
Mostly so that everyone can see what this would look like, I have used a
forked repository instead of publishing a patch for the template
refactoring suggested by Andreas earlier. Basically: It's easy to add a
public repo with an arbitrary alias (so like, you can add my github repo
as 'dwins' and pull from it with "git pull dwins branchname" instead of
"git pull origin branchname".) This allows really simple branching for
stuff that isn't ready for primetime yet, without ever requiring us to
duplicate those branches in the "central" repository at all if the work
doesn't pan out.
Perhaps playing with this a bit would help folks to figure out what kind
of git usage we are comfortable with. I put some specific instructions
on the other thread along with some notes about the changes I made.
--
David Winslow
OpenGeo - http://opengeo.org/
