Dear all,

I would agree with Bo that having different sites is not bad as long as they are linked to each other in an intuitive and consistent way. I still had concerns about how to organize the development docs on the different websites but after some thinking I came up with the following scheme:

http://www.calitko.org/source-talk/ – General development discussions in Source Talk.
http://doc.calitko.org/ – Calitko Architecture and Design Documentation generated from the source code.
http://trac.calitko.org/wiki/Manuals - Developer Manuals (e.g. Installing Prerequisites, Building Calitko, Coding Conventions, Managing the Calitko Project Files, etc.)
http://trac.calitko.org/wiki/Proposals - Design Proposals and Discussions to be referred to by tickets. A proposal would provide background information to a topic and would outline important concepts and development goals. After a proposal is implemented, the final version of the resulting design should be fully documented in the source code.
https://sourceforge.net/project/showfiles.php?group_id=167356 Calitko source and documentation file downloads at SourceForge.

Although I haven’t tried it yet, there exist a plugin for Trac (PageToLatexPlugin) to create a LaTeX version of the Wiki pages, which is really great as we could provide also the developer manuals for download in pdf or html format.

I’m still not really sure how exactly to manage the Proposals wiki (e.g what exactly happens with the wiki page after a proposal is implemented), I guess we’ll just have to experiment.

Ideas are, as always, welcome!

Best regards,

Peter