Thinking about a date-matching algorithm

Seriously, since it is a learning project, we are not looking
for independent, remote developers.

No sweat.

I will populate the RubyForge CVS tree soon (before the next
XP-Cincy meeting for sure).

That would be great; I’ve found working with temporal patterns to be
tricky and I’d be interested in seeing how other people are thinking.

BTW, folks might be interested in noting that the group is made up of
mostly Java programmers. At any given meeting there will be between 4
to 6 pairs of Java programmers and 1 pair of Ruby programmers. Yet, the
Ruby version of ECal is keeping pace with the Java version. Part of
that is due to the nature of Ruby, and part is the fact that with fewer
programmers, we don’t thrash between alternatives as much as the larger
Java group.

Definitely. I first implemented Runt in Java ( http://chronicJ.org ),
a language with which I’m much more experienced. Working on both projects
with a similar frequency to what you mentioned, the Java version took/takes
way more time. Especially considering that I wrote my first Ruby script
in December '03.

BTW, thanks for Rake! I’m using it for Runt, and am going to begin using it
alongside and/or in place of Ant and Maven at work.

Cheers,

Matt