Bug 254730 - Bugzilla doesn't assign new issues for base system and they hang without response for a long time
Summary: Bugzilla doesn't assign new issues for base system and they hang without resp...
Status: New
Alias: None
Product: Services
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Only Me
Assignee: Bugmeister
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-02 21:36 UTC by Yuri Victorovich
Modified: 2021-04-03 11:23 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Victorovich freebsd_committer 2021-04-02 21:36:12 UTC
The example is bug#254511

From the user's perspective once he files an issue with (or without) a patch attached somebody from the system should look into it and respond.

System auto-assigned it to "Nobody" and nothing is happening for days.

So what is the mechanism of FreeBSD reacting to such issues?

My suggestion:

Each category should have somebody attached who could look at the issue and at least make a determination for: (1) priority (2) the right person who can address it.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2021-04-03 11:23:58 UTC
(In reply to Yuri Victorovich from comment #0)
> System auto-assigned it to "Nobody" and nothing is happening for days.

The actual mailing list assignment is "freebsd-bugs@" which is the default assignee.  The "Nobody" is simply an annotation that the assignment is not specific to one person.

> So what is the mechanism of FreeBSD reacting to such issues?

It is the same as anything else: all done on a volunteer basis.

We have many people who do triage work to try to quickly assign issues to (at least) the relevant mailing lists.  But that is not the same as having people standing by to analyze the content.

I honestly do know what Bugmeister can be asked to do here.