Sid Wiesner wrote: > We've been using Trac at our company since 0.8, and it has been a > tremendous help in keeping project organized and having visibility > into it as it evolves. I'd like to help the Trac project to give bacck > as it has helped us so much. As a first step, I've started digging > through the Active Tickets list. > > I've already started to add keywords, mark dupes, and things along > that track. But I don't want to step on toes so I have not been > closing many of them or assigning to milestones. Are there any rules > of the road here I should follow? Or any advice?
Thanks. I don't think there are any written guidelines at this point, but maybe later this evening I'll write up a "triage guide" on the wiki with some hints about which resolutions to use, keywords to use, etc. I think we should start encouraging more community members to help with the triage and once the workflow changes have been merged I think that we should disallow anonymous users from setting milestones, priorities, probably everything but version and component. -- Matt Good --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev -~----------~----~----~----~------~----~------~--~---
