On 03/06/2015 07:27 PM, Rich Freeman wrote: > On Fri, Mar 6, 2015 at 1:14 PM, Sven Vermeulen <sw...@gentoo.org> wrote: >> >> It doesn't hurt to have a recommendation, and personally I really appreciate >> when people (yes, that includes developers and wranglers ;-) update the line >> to be more informative. There already is a recommendation on the wiki, part >> of the Bug Wranglers project [1]. >> > > Sure, beautiful bug reports are nice, but if people are suffering > burnout over editing the line it this doesn't seem like the biggest > value-add to me. > > By all means have a standard. But, don't discourage but reporters by > asking them to rework reports if they don't conform, and don't > discourage maintainers or bug wranglers by yelling at them if they > don't clean these up. People can of course can still make things as > pretty as they want to. > > The only reason I could see for rigid adherence to a standard is if > we're using the field as input to some kind of program, and if we're > doing that then the data should really be broken down into appropriate > fields like atom, desc, etc. > > So, have a best practice, but let's not get carried away with this > sort of thing to the point where people feel like it is getting in the > way. >
I too feel that whatever gets decided here will soon be forgotten and people will revert back to whatever makes more sense to them. Would it be terribly difficult to set a template in the "Summary" field whenever the "Keywording and Stabilization" component is selected when filing a bug? -- Regards, Markos Chandras
