|Version 5 (modified by 13 years ago) ( diff ),|
A Sea Change for Trac
"Full fathom five thy father lies,
Of his bones are corals made,
Those are pearls that were his eyes,
Nothing of him that doth fade,
But doth suffer a sea change,
into something rich and strange,
Sea-nymphs hourly ring his knell,
Hark! now I hear them, ding-dong, bell."
Ariel, from William Shakespeare's "The Tempest"
The SeaChange/ pages are used for collecting information about problems with the Trac community, in order to fix them. By community we mean Trac administrators/plugin developers, end users and core developers.
- SeaChange/WhatUsersWant lists the most frequent requests for major features (you can vote there!)
- SeaChange/WhatDevelopersWant is used as a blackboard between developers to exchange ideas about future directions
- SeaChange/DocumentationRequests collects requests for topics that should be documented, so that contributors (not necessarily developers) know where to start.
Also, it could be worth looking at other wikis, BugTrackingSystem and repository browsers, and see what the users can expect from other competitor systems. Note that since the success of Trac integration model (well, CvsTrac's model actually), some of the other bug tracking systems are evolving towards more integration as well, most notably by having an integrated wiki and/or source code browser.
High Level Observations
These are observations only, no judgement is implied. We're just trying to collect data.
- Trac core development has stagnated to a certain degree.
- A lot of the current core developers do not or cannot commit a lot of time to the project.
- Frequently requested features do not get implemented. eg. multi-project support.
- Release cycle is way too slow.
- Historically, there's effectively zero chance of a plugin getting into the core.
WebAdmin being the exception confirming the rule? :-) — cboos
- Features that users think should be "core" are not (this is very subjective).