From: Alex Combas <alex.combas@...>
Date: 2006-02-17T07:51:42+09:00
Subject: Re: Don't let this happen to Ruby, pleeeeease?

On 2/16/06, Glenn Smith <glenn.ruby@gmail.com> wrote:> Sorry, bit of a late night rant from somebody who cares...>
I agree, road maps are nice. Are they necessary? I dont think so.
I would prefer developers working on code and bug fixes as opposed towriting documentation and to my way of thinking a road map fallsunder documentation.
As long as the system is working, and the senior developers have mattersin hand then it doesn't matter to me if they write status reports and road maps.
Road maps tend to happen in very large and very well organized projects, I thinkof ones such as FireFox, Openoffice and Eclipse (all of which havegoverning bodys) orwith very small projects where goals are easily defined and reached.
However  road maps are not always nessisary, I believe the LinuxKernel does not have any road map and afaik no opensource programminglanguage has a published road map.Except maybe perl, but lets not talk about broken promises.
What ruby really needs is better documentation! (imo).I believe we currently have tones of docs, and more should always be welcome,but I think we need to work on the quality of our existing docs a lot more.
Something I would like to see is an easy way to give back to ruby highlightedin our docs and websites and more unification among all Rubys access pointson the web.
The only thing I've been able to think of so far for someone suchas myself to do is to contribute to the rubygarden.org wiki and helpkeep it cleanand up to date, that's my personal goal :) ...as well as perhapsjoining a projectand contributing code, of course.
MY PERSONAL GRIPE!Please turn this into a wiki so that we can clean it up:http://www.rubygarden.org/faq/main/The ruby FAQ really really needs some love.Yes, I'm talking to you dblack :)
--Alex Combashttp://noodlejunkie.blogspot.com/