docrails gives way to docmerb
Rails user’s are aware that with the latest 2.2 release, docrails has been merged into the source. This project started to improve documentation coverage and clarity by establishing rules. After my last post, I figure this is something we should do for merb. Not only does this help the community, but it also lets the lead Merb developers focus on more important improvements. If you would like to contribute, feel free to request access to the github repository.
December 11th, 2008 at 12:50 am
[...] Update – Due to user comments, I have spawned a new github community project called docmerb. For details, see my follow-up post. [...]
December 11th, 2008 at 2:48 pm
I’m a bit confused by what’s pushing you to start an entire separate project when the core team is working on a Merb book:
http://book.merbist.com http://github.com/mattetti/merb-book
The link to your github repo isn’t right and is pointing to lifo’s repo so I can’t check on you did. However I’d like to encourage you to work with us on the merb book instead of having two parallel projects.
- Matt
December 11th, 2008 at 4:30 pm
This isn’t a separate project. It was never specified that the merb-book would have code documentation attached. It seems like its more towards translations (according to your post) and written in a more tutorial fashion than anything else. This is going to be strictly rdoc related material. If the scope has now changed, than I would gladly contribute to the same project.
December 11th, 2008 at 5:46 pm
@justin ohh I misunderstood you. I didn’t realize you wanted to add better inline code documentation, could you please update the link to your repo.
Thanks for your support.
- Matt
December 11th, 2008 at 7:25 pm
@matt it has been updated. We may want to consider merging the projects or making them sister projects so as Merb Book is written people also update the documentation, since if they wrote the chapter they should understand the code that makes it work