During the retrospective at the March Coding Day, there was some
opinion expressed that one (or more?) ongoing projects might be a
positive stimulus to the coding sessions, at least for some attendees
(possibly those who are more frequent attendees).
I would like to invite opinions and discussion about this proposal.
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.
> During the retrospective at the March Coding Day, there was some
> opinion expressed that one (or more?) ongoing projects might be a
> positive stimulus to the coding sessions, at least for some attendees
> (possibly those who are more frequent attendees).
> I would like to invite opinions and discussion about this proposal.
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.
> > During the retrospective at the March Coding Day, there was some
> > opinion expressed that one (or more?) ongoing projects might be a
> > positive stimulus to the coding sessions, at least for some attendees
> > (possibly those who are more frequent attendees).
> > I would like to invite opinions and discussion about this proposal.
Peter,
Sounds like we have need of a session on Git ;-)
My concern with Git is that it doesn't (or didn't, last time I checked) have
a Windows client, although I think that I heard a rumour that the Tortoise
folk were working on one.
On Wed, Apr 8, 2009 at 9:20 PM, petemounce <peter.mou...@gmail.com> wrote:
> 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.
> > > During the retrospective at the March Coding Day, there was some
> > > opinion expressed that one (or more?) ongoing projects might be a
> > > positive stimulus to the coding sessions, at least for some attendees
> > > (possibly those who are more frequent attendees).
> > > I would like to invite opinions and discussion about this proposal.
> Sounds like we have need of a session on Git ;-)
> My concern with Git is that it doesn't (or didn't, last time I checked) > have a Windows client, although I think that I heard a rumour that the > Tortoise folk were working on one.
> > Sounds like we have need of a session on Git ;-)
> > My concern with Git is that it doesn't (or didn't, last time I checked)
> > have a Windows client, although I think that I heard a rumour that the
> > Tortoise folk were working on one.
I would like to propose that in May, we give the project a morning and afternoon session. The morning to be an environment preparation session, mostly with a focus on Git I suspect as the knowledge of that is thin in the community. The afternoon to be cutting the first code. Does that make sense, or is there a better approach?
To minimise wheel-spinning, I propose that the functional scope of the project be elaborated in this discussion list beforehand.
In the same vein, I propose that the technology pieces get agreed in this list beforehand as well. For example - what framework to use for unit testing? What database technology to use? What will be the data access approach?
As Lead, Robin will have final say on both of these questions - taking into account the community feedback.
Regards, Alan Dean Sent from Esher, Surrey, United Kingdom
On Mon, Apr 6, 2009 at 9:21 PM, Alan Dean <alan.d...@gmail.com> wrote: > All,
> During the retrospective at the March Coding Day, there was some > opinion expressed that one (or more?) ongoing projects might be a > positive stimulus to the coding sessions, at least for some attendees > (possibly those who are more frequent attendees).
> I would like to invite opinions and discussion about this proposal.
> I would like to propose that in May, we give the project a morning and
> afternoon session. The morning to be an environment preparation session,
> mostly with a focus on Git I suspect as the knowledge of that is thin in the
> community. The afternoon to be cutting the first code. Does that make sense,
> or is there a better approach?
> To minimise wheel-spinning, I propose that the functional scope of the
> project be elaborated in this discussion list beforehand.
> In the same vein, I propose that the technology pieces get agreed in this
> list beforehand as well. For example - what framework to use for unit
> testing? What database technology to use? What will be the data access
> approach?
> As Lead, Robin will have final say on both of these questions - taking into
> account the community feedback.
> Regards,
> Alan Dean
> Sent from Esher, Surrey, United Kingdom
> On Mon, Apr 6, 2009 at 9:21 PM, Alan Dean <alan.d...@gmail.com> wrote:
> > All,
> > During the retrospective at the March Coding Day, there was some
> > opinion expressed that one (or more?) ongoing projects might be a
> > positive stimulus to the coding sessions, at least for some attendees
> > (possibly those who are more frequent attendees).
> > I would like to invite opinions and discussion about this proposal.
> I would like to propose that in May, we give the project a morning and
> afternoon session. The morning to be an environment preparation session,
> mostly with a focus on Git I suspect as the knowledge of that is thin in the
> community. The afternoon to be cutting the first code. Does that make sense,
> or is there a better approach?
> To minimise wheel-spinning, I propose that the functional scope of the
> project be elaborated in this discussion list beforehand.
> In the same vein, I propose that the technology pieces get agreed in this
> list beforehand as well. For example - what framework to use for unit
> testing? What database technology to use? What will be the data access
> approach?
> As Lead, Robin will have final say on both of these questions - taking into
> account the community feedback.
> Regards,
> Alan Dean
> Sent from Esher, Surrey, United Kingdom
> On Mon, Apr 6, 2009 at 9:21 PM, Alan Dean <alan.d...@gmail.com> wrote:
> > All,
> > During the retrospective at the March Coding Day, there was some
> > opinion expressed that one (or more?) ongoing projects might be a
> > positive stimulus to the coding sessions, at least for some attendees
> > (possibly those who are more frequent attendees).
> > I would like to invite opinions and discussion about this proposal.
I'd be interested in following patterns, which are associated with
DDD. (Repositories, Entities, ValueObjects, Factories, Services etc.)
Or even DDD if it's popular.
Last time we discussed creating a developer community website. I would
much prefer to assist in working towards something, which adds value
to the community.
Alan and I spoke about an alternative cookieless authentication form.
Is there scope for more than one project? Is there any interest in
HTTP Auth?
On Apr 14, 9:30 pm, petemounce <peter.mou...@gmail.com> wrote:
> > I would like to propose that in May, we give the project a morning and
> > afternoon session. The morning to be an environment preparation session,
> > mostly with a focus on Git I suspect as the knowledge of that is thin in the
> > community. The afternoon to be cutting the first code. Does that make sense,
> > or is there a better approach?
> > To minimise wheel-spinning, I propose that the functional scope of the
> > project be elaborated in this discussion list beforehand.
> > In the same vein, I propose that the technology pieces get agreed in this
> > list beforehand as well. For example - what framework to use for unit
> > testing? What database technology to use? What will be the data access
> > approach?
> > As Lead, Robin will have final say on both of these questions - taking into
> > account the community feedback.
> > Regards,
> > Alan Dean
> > Sent from Esher, Surrey, United Kingdom
> > On Mon, Apr 6, 2009 at 9:21 PM, Alan Dean <alan.d...@gmail.com> wrote:
> > > All,
> > > During the retrospective at the March Coding Day, there was some
> > > opinion expressed that one (or more?) ongoing projects might be a
> > > positive stimulus to the coding sessions, at least for some attendees
> > > (possibly those who are more frequent attendees).
> > > I would like to invite opinions and discussion about this proposal.
> Last time we discussed creating a developer community website. I would > much prefer to assist in working towards something, which adds value > to the community.
I like this idea...we could always take the OpenSpaceCode website itself and use that as the basis for our project. There'd certainly be scope to play with http auth if we did this.
> Oh; also - we could get it set up on teamcity.codebetter.com ...?
If not, I'd be happy to host it on my TeamCity instance ( build.jeremyskinner.co.uk)
