On Sun, 2015-11-15 at 08:00 -0500, Justin W. Flory wrote:
It was mentioned earlier that the Docs Team may have already written
some kind of formal documentation somewhere about using Trac, but
after
doing some searching, all I could find was information about the
actual
package in Fedora and a few short snippets about some of the plugins
available for it. So with that in mind, I think we'll be starting
from
scratch on this.
I found the following:
*
https://fedoraproject.org/wiki/Trac
*
https://fedoraproject.org/wiki/Infrastructure/Tickets
*
https://fedoraproject.org/wiki/Infrastructure/CommonProblems
1.
https://fedoraproject.org/wiki/Infrastructure/ReportProblem
*
http://trac.edgewall.org/wiki/TracGuide
Some of the more important parts:
*
http://trac.edgewall.org/wiki/TracTickets
*
http://trac.edgewall.org/wiki/TracTickets
As a general outline, I feel like this flow would be a good way to
go
about it:
1) What is Trac?
2) What is used for?
3) How do I use it?
3.1) Signing in
3.2) Common tasks
3.3) Writing new tickets
3.4) Handling old tickets
4) Why use it?
I agree with those general items. I am curious, too, if some teams
using Trac will have different 'norms' [1,2,3] for how to handle items.
--
charles profitt <fedora(a)cprofitt.com>
[1] - https://www.berea.edu/brushy-fork-institute/establishing-group-no
rms/
[2] - http://www.businessdictionary.com/definition/group-norms.html
[3] - http://www.transitionputney.net/home/working-group-norms/