Hello Rodolfo, > I suggest the creation of a "docs" branch to start to write > documentation, and convert the old docs to the new format. I also > suggest we use sphinx to generate both user and dev documentation, to > make a format standard.
That sounds a good idea, but perhaps, it is better not to be a branch. Otherwise, people doing a checkout from our trunk won't have the docs. Also, if we put the docs inside the trunk it is easier to generate packages with documentation bundled. I enjoy your proposal, and I think it is a good start. Does sphinx generates html and pdf formats of these documentations? Thanks for your entusiasm, and the help you have being giving to Umit. Cheers! -- Adriano Monteiro Marques http://adriano-marques.blogspot.com http://www.umitproject.org http://www.pythonbenelux.org "Don't stay in bed, unless you can make money in bed." - George Burns ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Umit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/umit-devel
