#4259 closed enhancement (worksforme)
add timeline support to trac
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.10.2 |
| Severity: | normal | Keywords: | plugin |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
This project would be friggen great to integrate into trac…
Attachments (0)
Change History (6)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
| Keywords: | plugin added |
|---|
follow-up: 5 comment:4 by , 17 years ago
Replying to cboos:
wontfix or worksforme, that is the question ;)
BTW, this is something that should be addressed in TracTicketTriage: what about tickets for features that won't be part of the Trac core? Should they be closed, which status to set, …?
follow-up: 6 comment:5 by , 17 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Replying to eblot:
TracTicketTriage: what about tickets for features that won't be part of the Trac core? Should they be closed, which status to set, …?
I'd suggest doing it this way:
- when it's clearly in the scope of a plugin:
- wontfix if we don't know about an already existing plugin
- worksforme: when there's a plugin addressing the need
- when it's borderline between plugin/core functionality → milestone 2.0
Now, I also like to keep open the tickets that are clearly candidates for plugins if the interfaces they would need are not yet in place. Once the necessary interfaces are implemented, the ticket can be closed as a normal ticket would (milestone set and fixed).
Typical example is #1947 (see also this mail on trac-dev).
So in the specific case of this ticket, a worksforme seems appropriate.
comment:6 by , 17 years ago
Replying to cboos:
Replying to eblot:
TracTicketTriage: what about tickets for features that won't be part of the Trac core? Should they be closed, which status to set, …?
I'd suggest doing it this way:
- when it's clearly in the scope of a plugin:
- wontfix if we don't know about an already existing plugin
- worksforme: when there's a plugin addressing the need
- when it's borderline between plugin/core functionality → milestone 2.0
…
So in the specific case of this ticket, a worksforme seems appropriate.
"worksforme" should refere to repository contained functionality (as wontfix does).
A separate 'plugin' resolution would help-out: #4260
This is already done in the SimileTimeline plugin.