We don't need too much organization, just a way to keep track of the docs. Maybe a documentation specific svn repo? Finalized documentation can be merged into packages when ready...
As I said, working on it.
I have considered various approaches (really many of them).
Anyway, for now the best concept seems to simply keep everything in single svn repo and roll out a system of user rights to allow write access to topic++ folders.
Also, I am afraid we will have to fix T++ format (and handling) to be more svn friendly - now it is zlib compressed ready for #inclusion into C++, we should make this optional IMO and keep it as QTF text.
Members
Pages
Help
Register
Login
Home
