Back in December, Google announced their Sketchup API blog:
A not-so-publicized aspect of it is that there is now a Ruby Doc WIKI over there too:
http://groups.google.com/group/SketchUp-Plugins-Dev
The biggest secret in town is that the doc at the above link is an updated version from the current Ruby Help.
An even BETTER aspect of all this is that I can edit all the doc to include more information, make clarifications, add better examples, fix incorrect information, and so on.
When you get to the Doc page, click on "view all". That brings up the whole list of classes. Then, you can click on "show page details" (upper right in the main panel) and then you can sort on the date to see what's been changed. For example, you can click on the Face class to see the updated doc for classify_point. The 'who updated it last' statistic is bogus, but the date is accurate.
With your help, we can really make this Ruby doc super. I've updated several of the html files already, as have some Google developers.
If you want a change to be made, document your change and post it here in the Ruby forum. Make the subject something identifiable, and prefix it with "[ruby doc]", like this: [ruby doc face.classify_point not documented]. If I don't see it after a reasonable amount of time has expired, send a PM to ping me. Then, I'll review your change and incorporate it into the doc. Sample code, fixed typos, more details - whatever you see fit. If I don't understand your update, we can discuss it here in the forum. We'll uses the posts here to track your changes. Please only request one topic change per thread so they don't get lost. For instance, if you have 5 changes for one method, post them in one thread. If you have updates for 5 different methods, post 5 different threads, one per method. Try to format your change to match the existing format.
If you just ask me to "update the transformation doc" or some such vague or extensive request, that ain't going to happen, and I will ask you to be more specific. As far as formatting, please don't bother to ask me to "change all the examples to have a blue background". I do stuff like this as I can, when I am editing for content, and as I have time.
So remember, make your requests for updates specific and thought out. I can help with the wording, and anybody else can participate in the wordsmithing too, if need be. If you have example code (even whole programs that don't stray too far from the method they describe) then post that too if you want it in the doc. Be sure it's tested and commented where need be. These things I'll be happy to incorporate. 
Finally, before you request a change, to perhaps save yourself some effort, please check the above doc to make sure your change request has not already been made.
I hope this doesn't come across too "do it my way"-ish. The doc needs a lot of work, and it can't be fixed overnight. I'm just one guy, with a life, so I will get to changes as I can.
One comment I do want to make about the doc, and I've shared this directly with Google, is that the SU Ruby API doc, overall, is VERY good. I've been working with several other OO APIs lately, and they REALLY suck. @Last (now Google), organized the Ruby doc in an excellent manner and it should stand as an example for other development organizations to follow.
Todd



