> Hello Martin, > > Monday, January 3, 2005, 12:41:54 AM, you wrote: > >>> [CB] I think we should place them in CVS in the documentation section >>> with >>> everything else, do them in the consistent xdoc format. Of course new >>> features should be added to JIRA as well. > MW> Proverbial problem this. First have to agree what the consistent > format > MW> is and a process to manage the changes. Yes to cvs. Personally I would > MW> prefer using docbook/xml since this has tags to support documentation > MW> and has maven support ... > MW> http://maven-plugins.sourceforge.net/maven-sdocbook-plugin/ > > the design docs I have in mind are of temporary nature - they are more > or less a discussion between us about how to break a large feature > into smaller parts, assign the responsibilities to components and > build a work breakdown structure for implementation. I want to keep > the amount of time that we spend on these documents as low as > possible. They will contain text, a few diagrams and some sample code. > And they will have a chapter structure. That's it. Just sparkling > water, not champagne! >
guys, for this kind of stuff we would need Confluence. We already have a license for it because I requested it some time ago (Matthias, it has been attached to your Atlassian account if I am not mistaken), just need to get it properly up and running without those classloader hassles -- Wouter ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Andromda-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-devel
