I think it would be a good thing if, if we have an ongoing project, we
try to make it easy to follow its evolution. If part of the point of
OCS (is it coincidence it shares an acronym with Officer Candidate
School? :-P ) is to educate people to show them how good techniques/
tech/tools/libraries are applied, I think it would be more accessible
if the trunk were kept as clean as possible. By that, I mean not
interleaving commits between different threads of work, where
possible.
So for example, if one group is working on refactoring a feature to
separate concerns more, and another group is working on replacing XML
mappings with Fluent NHibernate ones, both of those should occur
within separate branches, and only merge to trunk when a commit can be
made that is complete enough not just to demonstrate progress, but
also educate someone who might be reading the commit log. Perhaps
there are many people reading the commit log, than able to attend the
sessions. Those who are only present in spirit should be catered to,
and it seems like a good way is to pay attention to team-working /
source-control good-practises. Those that only want to catch the
highlights can then just read the trunk log, whereas those that want
more detail can zip off to the branches if they like for the more
stream-of-conciousness logs (commit early and often, right? ;-) ).
Dare I suggest
github.com might be a better place for the repository?
I'm late to that bandwagon, but it seems like a social network for
programmers. I'm _really_ enjoying git compared to svn, too; it's
kinda like coming from VSS to svn. Perhaps a session on DVCSs...?
Pete
On Apr 8, 8:20 pm, Jeremy Skinner <
jer...@jeremyskinner.co.uk> wrote:
> How about something along similiar lines to the CaveatEmptor auction app? (
http://www.hibernate.org/400.html) The model is fairly simple to understand
> and there's quite a bit of scope for illustrating different techniques &
> technologies.
>
> Jeremy
>
> 2009/4/6 Alan Dean <
alan.d...@gmail.com>