Folks, The latest cool tool to hit the streets, Eric''s Production Log Analyser, prompts me to ask: is anybody maintaining a simple informative list of these tools? If I were starting a Rails app today and hadn''t been lurking on this list, how would I know about the PLA? I don''t have faith in Wikis to do this job. It requires the effort (and most importantly judgement) of a single person or small group. A single HTML page (on planetrubyonrails.org, for instance) should briefly describe all the _good_ tools, so someone can easily view the status of the RoR ecosystem. Another page could describe the runners up, if you like. A similar idea would be good for tutorials etc. Cheers, Gavin
> The latest cool tool to hit the streets, Eric''s Production Log > Analyser, prompts me to ask: is anybody maintaining a simple > informative list of these tools? If I were starting a Rails app today > and hadn''t been lurking on this list, how would I know about the PLA?I try to cover any new releases on www.theexciter.com every week(-ish), but it''s by no means total coverage, since I only pick out the stuff I like and/or can remember whenever I write the Rails Weekly...> I don''t have faith in Wikis to do this job. It requires the effort > (and most importantly judgement) of a single person or small group.Here''s a little secret I want to share with you; almost everything requires a little effort. ;) I think you''ve just volunteered to maintain that wiki page! -j
* Gavin Sinclair <gsinclair-81uBx+iSpXA0n/F98K4Iww@public.gmane.org> [0441 02:41]:> I don''t have faith in Wikis to do this job. It requires the effort > (and most importantly judgement) of a single person or small group. > > A single HTML page (on planetrubyonrails.org, for instance) should > briefly describe all the _good_ tools, so someone can easily view the > status of the RoR ecosystem. Another page could describe the runners > up, if you like.That sounds a bit back-asswards. Surely maintaining a webpage needs the effort of a single person or small group, whereas anyone could edit the wiki? -- ''Yeah, well I''m gonna build my own themepark! With blackjack aaand Hookers! Actually, forget the park. And the blackjack.'' -- Bender Rasputin :: Jack of All Trades - Master of Nuns
On Friday, April 1, 2005, 5:40:03 PM, Dick wrote:> * Gavin Sinclair <gsinclair-81uBx+iSpXA0n/F98K4Iww@public.gmane.org> [0441 02:41]:>> I don''t have faith in Wikis to do this job. It requires the effort >> (and most importantly judgement) of a single person or small group. >> >> A single HTML page (on planetrubyonrails.org, for instance) should >> briefly describe all the _good_ tools, so someone can easily view the >> status of the RoR ecosystem. Another page could describe the runners >> up, if you like.> That sounds a bit back-asswards. Surely maintaining a webpage needs > the effort of a single person or small group, whereas anyone could edit the > wiki?Nice in theory. I don''t believe it works in practice. Compare the Rails tutorial on the wiki to the ones done by a single person. Look at Ruby Weekly News [1] and ask yourself "If this is so useful, which it is, why hasn''t it grown organically on a Wiki?" It''s the (gargantuan) effort of an individual. Anyway, sooner or later we''re going to have a review capability on RubyForge, so excellent projects can be given a chance to shine. Hopefully that will solve this problem. Cheers, Gavin [1] http://www.google.com :)