At 17:49 -0800 3/6/09, Matt Aimonetti wrote:
> Documentation is important but we are far from having a
> Rails 3 alpha release, let's focus on the code (Merb 1.1
> and Rails 3) and when we will have something to document,
> we'll use all the great stuff you put together.

This is a false dichotomy.  There is no conflict between
some folks working on (including generating criteria for)
documentation tools and others working on defining the new
code base, writing detailed comments in the code, etc.

Indeed, the better idea we have of the tools we want R3 to
have, the better the comments are likely to be.  Also, if
core developers are thinking about doc tools as they code,
they may come up with ideas for metadata extraction, etc.


I don't expect to be a contributor to the R3 code base; I
don't have the necessary chops or interest.  However, I'm
expecting to use the R3 docs in my work and I'm hoping to
make a real contribution to the R3 documentation tools.

In particular, I'd like to create an Ontiki-based wiki for
R3/Ruby/... API information, etc.  Knowing what folks want
the docs to look and act like is critical to this effort.

I'm hoping that you're not asking folks to avoid work (or
even speculation) on parts of the ecosystem that interest
them.  Tell me it isn't so...


> Matthew Ford is going to add a LOT of documentation to the
> Merb Book really soon. We will need help reviewing his work.

I'll be there, as before, with my eye-shade firmly in place...

-r
-- 
http://www.cfcl.com/rdm            Rich Morin
http://www.cfcl.com/rdm/resume     [email protected]
http://www.cfcl.com/rdm/weblog     +1 650-873-7841

Technical editing and writing, programming, and web development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" 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/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to