Ferris McCormick posted <[EMAIL PROTECTED]>, excerpted below, on Thu, 12 Jan 2006 13:59:43 +0000:
> This list is not necessarily complete, nor is everything on the list > necessarily appropriate for reporting to devrel. But it should give some > idea of the sorts of things that are helpful for briefly explaining why > devrel has jurisdiction and to give a clue how the reporter wants the bug > to be processed. Thanks. That list at least provides a decent set of examples. When I read "jurisdiction", I thought the usual US/legal sense, as in courts ruling whether they have jurisdiction over a case or not, and my mind was boggling... I couldn't quite figure out how to boil such a concept down into the itemized list you were describing. The examples definitely help me get my mind around the concept you intended! I'd suggest putting at least one or two examples in whatever bug template or HOWTO might result from this, if the thing isn't made an itemized list as you suggested, anyway. I know I had a /terrible/ time figuring out Gentoo's bug system for regular bugs, and can easily envision myself having the same issues trying to fit square pegs into crescent-moon-shaped <g> holes here, so some sort of guide is SURE to prove beneficial. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
