Edgewall Software

Changes between Initial Version and Version 7 of Ticket #1835


Ignore:
Timestamp:
Feb 1, 2007, 9:57:37 AM (13 years ago)
Author:
Christian Boos
Comment:

The summary has been changed to reflect the new intent of the ticket (comment:6).

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1835

    • Property Status newreopened
    • Property Severity normalmajor
    • 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 lownormal
    • Property Milestone1.0
    • Property Keywords tracobject added
  • Ticket #1835 – Description

    initial v7  
     1Was originally: ''Is it possible to integrate a thread-based "view" (something like a phpbb) with trac?''
     2
    13I'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).
    24So 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.
    35
    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 inital, 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.
     6Trac 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.
    57
    6 So to keep all the relavant development information in one place/system it would be great, if one could have some "forum"-like functionality with a threaded view.
     8So 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.
    79
    810