To follow-up on this, perhaps it would be better to release the updated code base and dub it a 4.0 as you suggested and then simply stub out all the new features and sections for documentation that are needed. My take is that if we just outline these at a high-level and then as the community for support it's more likely to get completed. Otherwise, if you were to visit the website now it appears that it's a stalled project with that last revision and blog post almost a year old. For a model on how to do this, I have really liked the approach that http://refinerycms.com/ has taken. They pull in the documentation directly from github, which allows for two benefits - easy to accept new documentation from the community and builds the documentation into the application (ex: http://refinerycms.com/guides/contributing-to-refinery and https://github.com/resolve/refinerycms/blob/2-0-stable/doc/guides/8%20-%20Contributing/2%20-%20Writing%20a%20guide%20for%20this%20website.textile ). Perhaps we can also use this launch as an opportunity to shift the core code base to github and then use this model for documentation?
Cheers, Roy -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en
