Bug 198388 - schema: Add 'lib' component to 'Base System' product
Summary: schema: Add 'lib' component to 'Base System' product
Status: Open
Alias: None
Product: Services
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Some People
Assignee: Oleksandr Tymoshenko
Keywords: needs-qa
Depends on: 267349
Blocks: 191430
  Show dependency treegraph
Reported: 2015-03-07 14:30 UTC by Mark Linimon
Modified: 2022-10-28 03:01 UTC (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Mark Linimon freebsd_committer freebsd_triage 2015-03-07 14:30:54 UTC
Our src users are confused about how to classify certain bugs.  Some of the things affecting libraries get filed as 'kern' and some as 'bin'.  I suggest creating a new component 'lib' to hold them.
Comment 1 Oleksandr Tymoshenko freebsd_committer freebsd_triage 2018-02-23 20:28:03 UTC
Hi Mark,

Is this request still relevant?
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2018-02-25 06:38:48 UTC
(In reply to Oleksandr Tymoshenko from comment #1)

Yes, I'd still like to see it.

It would certainly serve us better than our 'misc' component :-)

Currently there are:

3387 in kern
1635 in bin
 388 in misc

which still suggests to me that we are not granular enough.

If we really wanted to break up the 'kern' conglomerate, the biggest ones we might want to break out are:

 - drivers
 - networking
 - filesystems

I hope you will at least agree that 3387 is not a "browseable" number :-)
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2018-02-25 08:02:22 UTC
I've had a list of potential new (non-repo path oriented) specific components to add to bugzilla for quite a while. 

The reason I haven't 'just added them' is because there is a communication (pre change announcement) that needs to be done prior to the change (with rationale if necessary), and that they all need to make sense both independently (in terms of offering the most obvious choice for how reporters classify issues), but also together, in terms of minimal (ideally zero) overlap.

Further, if any existing categories are replaced by the new set, then any auto-assignment (or other automatic) workflow things need to be identified and updated. 

Ultimately this is taxonomical problem that needs relatively careful consideration before its deployed, lest there be additional work required later on to move/reclassify bugs, which in Bugzilla is not painless
Comment 4 Kubilay Kocak freebsd_committer freebsd_triage 2018-02-25 08:05:00 UTC
On the previous note, and for this specific example, while 'lib ' *may* be obvious to some seasoned developers, I think its reasonable to say that it would not be obvious to regular users. It's not obvious to me either, and I would have trouble ascertaining whether to file a bug in 'lib' or not.