On Tue, 23 Oct 2007, Stephen Hahn wrote:
> * Valerie Bubb Fenwick <[EMAIL PROTECTED]> [2007-10-24 00:38]:
>> On Tue, 23 Oct 2007, Stephen Hahn wrote:
>>
>>> * Richard Lowe <[EMAIL PROTECTED]> [2007-10-23 22:05]:
>>>> Valerie Bubb Fenwick <[EMAIL PROTECTED]> writes:
>>>>
>>>>> On Tue, 23 Oct 2007, Richard Lowe wrote:
>>>>>
>>>>>> Stephen Hahn <[EMAIL PROTECTED]> writes:
>>>>>>
>>>>>>> All the details are in the subcategories, but here's the current
>>>>>>> product/category (classification/product?) list that is published to
>>>>>>> bugs.opensolaris.org from the legacy DTS. (Some subcategories are
>>>>>>> excluded, apparently.)
>>>>>>>
>>>>>>
>>>>>> It'd be work syncing up with Derek, and the owners of the excluded
>>>>>> subcats (or even entire categories), to figure out which are
>>>>>> intentional,
>>>>>> and which are in error. Every so often we catch one that's hidden
>>>>>> because that's how things default.
>>>>>
>>>>> Also, Derek's tools don't pick up new cat/subcats by default. I try to
>>>>> let him know when these are added, but something automated would probably
>>>>> be better.
>>>>
>>>> Well, as I said in the other mail, I was mostly meaning so we didn't
>>>> fail to think about various sections just because we can't see them
>>>> right now.
>>>>
>>>> Assuming names stay the same, the mapping seems fairly straight
>>>> forward, if things are actually being adjusted, it would make sense to
>>>> see a larger list of product/cat/subcat tuples than "what we have
>>>> right now".
>>>
>>> I guess I was hoping we would validate that the current list makes any
>>> sense at all. Maybe there's a set of guidelines about new
>>> categories/subcategories that we could apply to the existing
>>> categories that might have predated such guidelines?
>>>
>>> What criteria do we use to allow/deny a new category or subcategory?
>>
>> Do you mean for current bugster maintenance or going forward? If you
>> want current rules, I can provide that.
>
> Current rules would be great. I'm curious if retroactively applied
> they might make things better (or if that's already happened).
So, Scott & I have a few basic rules/questions for what we accept as new
categories/subcategories in product solaris:
* Must already be *in* solaris (or soon heading that way) [1]
Reasoning: we don't want P1 project bugs causing confusion
about the quality of a certain build (if they don't actually
exist in that build)
* Must have a valid RM (Responsible Manager) and IE (Initial
Evaluator), and a sensible 1-line description
(this gets tricky for projects that are purely externally
contributed - we haven't come up with a good solution for
that yet)
* We try to discourage splitting subcategories so finely
so that only an expert could possibly figure out where to
file a bug.
* We want all drivers under "solaris/driver", instead of under
"solaris/kernel"
* Is there an obvious connection between each subcat name and its
proposed contents? Will someone naturally think to look there
to file a bug?
* Subcats for new hardware platforms should be created under the
"platform" category, not "kernel."
* Existing categories & subcats should be leveraged, where appropriate.
[1] there is another product, "development" which is used as a sandbox
for projects that are under development, which is a bit more of
a free for all.
I might be missing something, and like most things in Solaris, there
is always wiggle room. We mostly focus on keeping nonsense out of
the database.
We encourage people to disable categories & subcategories that were
either: never actually used, or for software that is no longer
supported. We often get requests along that line, and they are
pretty much always approved.
As far as retroactively cleaning it up: when I went through the
data for solaris & sunos for the BT+ to BT2 migration, I manually
closed a lot of categories/subcategories & junk products. Since
we've gone live, when we see someone trying to add to something
that is already confusing, we encourage them to clean everything
up as a part of their new request. Scott has also done a lot
of nagging of folks to clean up confusing & old things, as well
as keeping RM & IE pointing to actual people or aliases.
He's also helped to bring a lot of the hardware & driver things
in line.
Nobody really owns this data as a full time job, though, so it's
just been a "best spare-time effort" since go live of BT2 for
those of us in solaris.
If someone wants to go through that effort, I'd happily approve
all requests :-)
Valerie
--
Valerie Fenwick, http://blogs.sun.com/bubbva
Solaris Security Technologies, Developer, Sun Microsystems, Inc.
17 Network Circle, Menlo Park, CA, 94025. 650-786-0461
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
