I’ve been waiting for this for some time, as I’ll get an idea but not have it detailed enough to post to the forums. It has also been needed for the past suggestions and for future suggestions. The forums are great for discussion as tracker comments are just like blog comments, which are difficult to follow and see if there is a new comment on.
As a whole, I would like to add some of my own, but spending a week or so going through the old discussions might be fun! Some of the new people (Tirellco and Cyberlot) had some great comments that would be worth tracking. That said, there also has to be a formal written proposal to go along with the feature ticket, unless dependency ticket tracking is a feature of the tracker.
The ticket would have a summary and have a link to the wiki page with the full proposal which had thus far been agreed on or discussed to conclusion. It would be nice to have some sort of roadmap for which to show people (and myself) with both QGL and Astrum Futura.
I should Admit That…
I do create tickets for the sake of saying that I’ve completed that task and record that I completed that task. That might not always be the best method when you are working with other people and probably will have a lot more users submitting tickets for defects or features.
So, that is why most of the ticket proposal would be at the wiki and just have a summary at the tracker. If needed and the task is something important and would take more than several hours, it might also be good to mark that ticket in the wiki and as an dependency in the comments (or use the feature if supported).
The Fun Stuff
Mostly, it would be worth going through the old discussions and sort of “close” them and redirect to the tracker and wiki. The discussions wouldn’t be closed, as in forum moderation speak, but really to head it off into a new direction based on what is in the wiki and tracker.
Not quite sure if the update should be posted to a single sticky thread or to each individual thread.
Possibly Related Posts:
- Calibre Improvements
- DragonU Bug Tracker Dev – Milestone 1
- Dragon MVC
- Why I Contributed to WordPress
- DragonU DB Component
Comments are closed.