On 11/15/2015 12:51 PM, charles profitt wrote:
Thanks for linking these - they will make useful references for later, I
hadn't found all of these pages.
On 11/15/2015 12:51 PM, charles profitt wrote:
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.
On
11/15/2015 06:27 PM, Ryan Lerch wrote:
Trac usage in the Fedora Project is a bit of a weird thing IMHO.
Fedora
hosted as set up as a way to host projects -- but with the rise of
Github, and now we also have pagure in Fedora, not sure how many
projects still actively use Fedora Hosted.
The other thing we mainly use trac for in the Project is for tickets of
things like the council and FESCO -- things that aren't tied
specifically to packages (i.e. cant be tracked in Bugzilla)
Some teams, like the Design team also use fedora hosted for this use.
Hmmm. So with these in mind, is a Trac guide still justified? I know
it's used in some teams across the Project, e.g. Design, Ambassadors,
and it's looking like CommOps, but I'm wondering now if this is as high
of a priority? Or perhaps the focus should just be slightly readjusted
towards these specific subgroups?
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com