* Betr.: " Re: [tryton] Administrator and user documentation" (Sat, 6 Aug 2011 09:08:38 +0200):
Hi Albert, > A Divendres, 5 d'agost de 2011 23:28:36, Telesight va escriure: > > @Albert > > > > Hola, > > Thanks for pointing me to your efforts. It looks great. If we could reach > > that! > > But first we have to write the documentation ;-) > > Well, the idea behind this development (which would be great to port to > Tryton if the community is interested on it), is that documentation can be > inherited the same way views are. So this means that documentation should be > written with that in mind. Would that be something that the Tryton community > would like to have? Of course any step to create a maintainable documentation is highly appreciated. We tried that in the German community a little bit the way you are describing [1]. We tried to focus on some primary use cases and described the first steps to get into the application from down to top. Each use case can be the continuation of a former. The challenge will always be: - There must be someone taking care of the actualization. We get many requests for documentation, a lot of announces to step in, very few at the end to do it;). So continuous man power is a problem. - Documentation will/can rarely be a comprehensive way to rollout Tryton for a specific business. This should be clear for writers and readers from the beginning. That said I am really appreciating each effort, that will take away some load on the IRC etc. in explaining repeatedly the basic steps to newcomers. So as for me: Just do it! [1] http://tryton.origo.ethz.ch/wiki/doc -- Mathias Behrle MBSolutions Gilgenmatten 10 A D-79114 Freiburg Tel: +49(761)471023 Fax: +49(761)4770816 http://m9s.biz UStIdNr: DE 142009020 PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6
signature.asc
Description: PGP signature
