Opened 18 years ago
Closed 18 years ago
#4385 closed enhancement (invalid)
make trac a groupware
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | 0.10.2 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
- calendar to set meetings (incl. occurences, alerts, conflict detection)
- forums
- document server
or, how difficult will it be to add these as plugins? (are there any such components that can be easily wrapped as trac plugins?)
Attachments (0)
Change History (3)
comment:1 by , 18 years ago
Description: | modified (diff) |
---|
comment:2 by , 18 years ago
its a request to make trac a full fledged groupware solution. this means having the above integrated (forums based on wiki format, being able to refer to wiki pages, wiki pages referring to items in the document server etc.)
as an intermediate solution, maybe use 3rd party components wrapped thinly. this will probably not get the integration level required.
sorry, accidentally deleted that comment, readding it.
—cboos
comment:3 by , 18 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Well, if the 3rd party components are TracPlugins, the integration level you ask for can be reached, thanks to the ubiquitous use of the TracLinks in the content:
- for forums, there's already the TracHacks:DiscussionPlugin
- for the file server, there are many options:
- use a Subversion repository for that; adequately setup I think you can even access it through web folders (?)
- there's an open ticket for allowing file uploads to the repository through the Trac web interface (#2956)
- if you don't want to / can't use SVN for file sharing, then wiki pages can have attachments, so you could manually create a few FileArea/… pages and use those for file server, as an interim solution;
- the main missing part in your 'groupware' shopping list is probably the calendar part; but I see no reason such a beast couldn't be implemented as a plugin (well, admittedly it would be a lot of work, but doable)
In any case, this is outside the scope of the Trac core. Of course, we're open to support whatever missing extension point would be needed to implement the above plugin; that could be filed as a separate, more precise, tickets when needed.
I think this kind of questions should be asked in one of the mailing lists.
→ close as invalid ?