Manuzhai wrote:
But the wiki definition should not limit further functionality.
Yes, it should. Trac modules do one thing, and do it well. A
documentation system such as what you seem to be pursuing has very
different requirements.
Essentially the trac wiki it can be seen as an "Integrated Project
Documentation Tool".
It can be used to build documentation, yes. But it can also used for
other things, such as development discussions. Also, I think the "many
eyes make any bug shallow" or whatever is very applicable to
documentation, and as such having wiki-like documentation is a
feature, not a bug. The document ownership thing is completely opposed
to this approach.
"
Trac uses a minimalistic approach to web-based software project
management. Our mission; to help developers write great software while
staying out of the way. Trac should impose as little as possible on a
team’s established development process and policies.
"
An optional(!) "document ownership" would help to fulfill the above
basic goal of trac, to stay out of an established development process.
Teams which prefere the wiki style can simply ignore the "document
ownership"
As said, those are just suggestions.
.
--
http://lazaridis.com
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
