> So, say that Rails is to get an official documentation team. Whose > decision would that be? DHH? Anyone in the core team? It would be nice > with an opinion from the person/people that can actually decide wether > or not to get an official team running.
I think the best way around this is just to do something cool and once you've done something, you seek to get that elevated to official status. Say you do an online book that's really great. That'd be wonderful and could well live under the rubyonrails.org site if it's awesome. The same with any other type of documentation, really. That way we don't bestow "official" status to a group of people with good intentions who then never get around to actually doing the work (and at the same time discourage anyone else gunning for the same slot from getting to work). This is especially prudent if this is to be a comparison to Rails Core. That group has its members picked from people who actually did something. Not from people who said they would do something. I think that's a good model to follow. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
