Andrus Adamchik wrote:
No firefight - there is simply no other way to build karma on an open
source project. And the fact that one of our projects was done with no
community involvement simply sucks.
My point was that if some sort of distributed SCM was used rather than
SVN, then it wouldn't matter that much at all. Non-committers (in this
case, the students) would still be able to pull and update from the main
codebase while committing locally. They'd get the benefits of having
some sort of endorsed code management system that they could easily
generate patches from. The idea of SVK was batted around on the mentor
list, but didn't get very far. Cayenne tried two different SVN
installations, which made it rather difficult to keep on top of
patches. Others used no SCM at all.
Anyway, to get back where this started. Did we give the students
everything they needed to work most effectively and productively? If
so, then JIRA patches are the way to go for next year. If not, what
could be done differently?
--
Kevin Menard
Servprise International, Inc.
"Remote reboot without pulling the plug" -- http://www.servprise.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
