Changes between Initial Version and Version 7 of Ticket #1835
- Timestamp:
- Feb 1, 2007, 9:57:37 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1835
- Property Status new → reopened
- Property Severity normal → major
- Property Summary Is it possible to integrate a thread-based "view" (something like a phpbb) with trac? → Add a discussion tab for Trac resources
- Property Priority low → normal
- Property Milestone → 1.0
- Property Keywords tracobject added
-
Ticket #1835 – Description
initial v7 1 Was originally: ''Is it possible to integrate a thread-based "view" (something like a phpbb) with trac?'' 2 1 3 I'm in a development team which consists of many people from different departments of our company. For now, we're using a forum for "informal" discussion of feature-proposals (where everyone can contribute), an issuetracking system as a "formal" way to categorize and track our development progress (which is managed by a few "head developers) and a wiki for documentation purposes (which again is open for all users). 2 4 So the "life cycle" of a feature looks like this: proposal > discussion between all developers > creating of an "ticket" with formal specs (deliverables etc.) in bugtracker which may be commented on by everyone but responsibility for the ticket is held by a "head developer" > actual coding > documentation in wiki. 3 5 4 Trac really looks great for combining the "formal" project-management with documentation and source-code-management but the wiki-based "view" is (IMHO) to complicated for the init al, informal discussion. The ticket-view is better suited for that, but doing informal discussions there would weaken (again IMHO) the formal "progress-tracking" approach as there will be many tickets which won't make it to a "real" issue.6 Trac really looks great for combining the "formal" project-management with documentation and source-code-management but the wiki-based "view" is (IMHO) to complicated for the initial, informal discussion. The ticket-view is better suited for that, but doing informal discussions there would weaken (again IMHO) the formal "progress-tracking" approach as there will be many tickets which won't make it to a "real" issue. 5 7 6 So to keep all the rel avant development information in one place/system it would be great, if one could have some "forum"-like functionality with a threaded view.8 So to keep all the relevant development information in one place/system it would be great, if one could have some "forum"-like functionality with a threaded view. 7 9 8 10
