leave Document Management System

[artmotion@…]

I think trac needs a bookmark and document management system.

Maybe you know "the personal brain" - a windows based software where you can store your bookmarks and link them together. Over the last years I've build a "brain" with about 1650 bookmarks, many of them are at least in some hierarchive, some of them a linked to other bookmarks.

This should be implemented in a way, that it is possible to link also to normal documents (pdfs, graphics, ...) and maybe also to sourcecode in the subversion repository (including either no release number, or a specific release of the sourcecode file).

[cboos@…]

And what exactly prevents you from using Trac for that?

I'm curious, since:

• you already have plenty of ways (using the WikiFormatting) to refer to URLs, files in your repository, and personal notes (in the form of Wiki pages)
• for files not in the repository, you can still attach them to Wiki pages

(cross-referencing could be one of the missing thing, but it being worked on, see #1242)

[cboos]

Unless I'm mistaken, there's nothing really new/pertinent asked for in this ticket.

[anonymous]

I think the idea is amaizing, document management is a task very important in project management area. Define workflow for document revision, aproval, indexing, text search.

[eblot]

Replying to anonymous:

I think the idea is amaizing, document management is a task very important in project management area.

... but Trac does not aim at being such a tool. It is not (yet?) a universal swiss knife.

[cboos]

Replying to anonymous:

... document management is a task very important in project management area. Define workflow for document revision, aproval, indexing, text search.

Well, without aiming at being a swiss army knife, Trac could definitely gain in usefulness and flexibility if it would be able to do for all its resources what it can do currently only for some, when appropriate of course.

So far, only technical issues are preventing this to happen. In 0.11, there's been some progress on that point (e.g. ticket description history and diffs), but this was made unnecessarily hard by the lack of a convenient and unified data model; improving on this is the whole point of the GenericTrac approach.

In line with the quoted comment above, I can see that what we're doing now with the ticket workflow could be one day transposed to a workflow for Wiki pages (e.g. new -> reviewed <-> modified -> closed).