Please add a "man" (or "doc") component to the Base System product for PRs concerning documentation in the base system as opposed to the doc tree (e.g. #63084).
A 'man page' component separate from the 'Documentation' component is good.
Maybe it is better to add it to the 'Documentation' product and call the existing Documentation component 'Website' ?
I think you're confusing products and components.
I assume that the Documentation product corresponds to the doc tree, which is much more than the website (the handbook has been published in print several times in the past).
What I asked for is a man component for the Base System product, which corresponds to the base tree.
I don't believe the bug tracker should be divided by the tree. Instead it should be divided by where people are likely to look for bugs that are related to them.
The question to me is whether people are likely to look under "Documentation" for man page related bugs, or whether they are likely to look under their own subsystem and notice doc bugs on the way.
"I assume that the Documentation product corresponds to the doc tree, which is much more than the website (the handbook has been published in print several times in the past)."
I am very familiar with this. What I am proposing (somewhat lightly) is to have a "Handbook/FAQ/etc." component, "Website" component, and a "man pages" component. One thing I'm concerned about is that most people won't differentiate between the website and the articles.
Is this still relevant? Looks like Documentation/Documentation category works for submitter so far.
Yes, it is still relevant. Man pages are part of the base system, and a PR for an error or omission in a man page should be filed under the “Base System” product, not the “Documentation” product.
(In reply to Dag-Erling Smørgrav from comment #6)
I agree with Eitan: Bugzilla components structure should be reflection of code tree structure, it should be based on workflows for reporting/fixing bugs. And from this point of view adding "man" component to base system makes sense, IMO. It's more about visibility of PRs and who works on them. I don't think many src developers are subscribed to freebsd-docs@ which is default assignee for Documentation/Documentation component, so unless someone alerts developer about specific PR or developer routinely checks bugzilla man PR is going unnoticed.
I ran the idea of "man" component with freebsd-bugs@ as default assignee and freebsd-docs@ as default Cc by docs team IRC channel and got some positive feedback so I emailed doceng@ asking them if this approach would negatively affect their workflow.
doceng@ approved creating component for manpages PRs with bugs@ as a default assignee and doc@ as a default Cc.
After some consideration and discussing it was decided to create component as a part of Documentation product. Products/components should be described from the perspective of the reporter given how they interact/think about the system and for such user man pages are part of documentation.
I'll start migrating PRs to new component next week.
Closing as fixed: all man-related PRs have been migrated to the new component.
MARKED AS SPAM