Hello all. I, like many of you, got very excited when we heard about a Ruby on Rails contest. If you haven''t heard about it yet it is a contest to explore what can be done with ruby on rails in just 24 hours. It’s an event to highlight the development speed and creativity of the rails community. It was supposed to have happened last weekend, but the organizers were understandably busy with their Ruby on Rails day jobs (as am I). However, it will still happen, we just need better planning, more time in advanced, and a registration system (which I am working on). I have started a Typo blog to be a centralized place to find everything about Railsday: http://www.railsday.com/ Please take a look and leave all your feedback there. -Lucas http://www.rufy.com/
This sounds like a great idea, but how is the 24-hour time limit going to be enforced? Couldn''t someone just upload code that was written before the start of the competition? If this is an issue, what about specifying a theme for the contest when it begins? For example, you could specify that something relating to ''photos'' must be built, or something that facilitates person-to-person communications. You could specify anything really, and there would still be a lot of diversity in the entries. But this way you can be relatively sure everyone has been fair. Cheers, Ben On 4/13/05, Lucas Carlson <rails-1eRuzFDw/cg@public.gmane.org> wrote:> Hello all. I, like many of you, got very excited when we heard about a > Ruby on Rails contest. If you haven''t heard about it yet it is a > contest to explore what can be done with ruby on rails in just 24 > hours. It''s an event to highlight the development speed and creativity > of the rails community. It was supposed to have happened last weekend, > but the organizers were understandably busy with their Ruby on Rails > day jobs (as am I). However, it will still happen, we just need better > planning, more time in advanced, and a registration system (which I am > working on). I have started a Typo blog to be a centralized place to > find everything about Railsday: > > http://www.railsday.com/ > > Please take a look and leave all your feedback there. > > -Lucas > http://www.rufy.com/ > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
> This sounds like a great idea, but how is the 24-hour time limit going > to be enforced?A subversion repository will be setup for each project and contenders will be required to commit during the 24 hour period.> Couldn''t someone just upload code that was written > before the start of the competition?Yes, cheating is possible. It is inevitable in many ways.> If this is an issue, what about specifying a theme for the contest > when it begins?This would limit the creativity of the contest, which is exactly not what we intend to do. Maybe in the future we will crack down on cheating in creative ways, but for the mean time, the honor principal applies. -Lucas
On Thursday, April 14, 2005, 2:05:46 PM, Lucas wrote:>> This sounds like a great idea, but how is the 24-hour time limit going >> to be enforced?> A subversion repository will be setup for each project and contenders > will be required to commit during the 24 hour period.This is a great idea, but maybe next time a one-week timeframe would be worth a try. More consideration, more polish and testing, more ability to sleep. Gavin
> This is a great idea, but maybe next time a one-week timeframe would > be worth a try. More consideration, more polish and testing, more > ability to sleep.It is interesting that you say next time since it hasn''t happened yet, but the reason we want 24 hours is to show off the productivity of a single day of focused rails development. -Lucas http://rufy.com/
On 14.4.2005, at 06:11, Ben Myles wrote:> This sounds like a great idea, but how is the 24-hour time limit going > to be enforced? Couldn''t someone just upload code that was written > before the start of the competition?I think it''s pretty hard to explain how you checked in 500 lines of code 30 minutes after the competition started. So using Subversion gives the organizers quite a good way to log how the application is doing. Maybe put into the rules that the progress must be checked in with at least given (time or loc) intervals? This would at least make the cheating a bit more work. //jarkko> > If this is an issue, what about specifying a theme for the contest > when it begins? For example, you could specify that something relating > to ''photos'' must be built, or something that facilitates > person-to-person communications. You could specify anything really, > and there would still be a lot of diversity in the entries. But this > way you can be relatively sure everyone has been fair. > > Cheers, > > Ben > > On 4/13/05, Lucas Carlson <rails-1eRuzFDw/cg@public.gmane.org> wrote: >> Hello all. I, like many of you, got very excited when we heard about a >> Ruby on Rails contest. If you haven''t heard about it yet it is a >> contest to explore what can be done with ruby on rails in just 24 >> hours. It''s an event to highlight the development speed and creativity >> of the rails community. It was supposed to have happened last weekend, >> but the organizers were understandably busy with their Ruby on Rails >> day jobs (as am I). However, it will still happen, we just need better >> planning, more time in advanced, and a registration system (which I am >> working on). I have started a Typo blog to be a centralized place to >> find everything about Railsday: >> >> http://www.railsday.com/ >> >> Please take a look and leave all your feedback there. >> >> -Lucas >> http://www.rufy.com/ >> >> _______________________________________________ >> Rails mailing list >> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >> http://lists.rubyonrails.org/mailman/listinfo/rails >> > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Jarkko Laine http://jlaine.net http://odesign.fi _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails