Closed Bug 1126453 Opened 5 years ago Closed 5 years ago

Tracking bug for all bugzilla issues which are non critical but would be awesome to have

Categories

(bugzilla.mozilla.org :: General, defect)

Production
defect
Not set

Tracking

()

RESOLVED INVALID

People

(Reporter: jmaher, Unassigned)

Details

No description provided.
I'm guessing this is more about BMO than Bugzilla itself.
Assignee: general → nobody
Component: Bugzilla-General → General
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
Depends on: 364693
Depends on: 685254
Depends on: 356934
Depends on: 1020817
Depends on: 1020388
Depends on: 577958
Depends on: 325315
Depends on: 342113
Depends on: 369612
Depends on: 442205
Depends on: 609301
Depends on: 1009639
Depends on: 666594
Depends on: 158525
Depends on: 225872
Depends on: 1059419
Depends on: 208711
I don't see the point to have such a bug (besides spamming a lot of users). All bugs are "awesome to have", else they would already be closed as wontfix.
Depends on: 380732
Depends on: 103587
Depends on: 456974
Depends on: 244360
Depends on: 344606
Depends on: 464688
Depends on: 464528
contributors can come here and see a list of bugs related, we can embed queries easier in wiki pages, we can find bugs easier.
@jmaher: 
There is no criteria given what "would be awesome to have" should mean. How am I supposed to update the list here without being able to read your mind?

Contributors should check for open tickets with higher priority values instead. Or bugs tagged as suitable for newcomers. Or bugs tagged with a certain Target Milestone. There are many ways already out there.

And how do "contributors come here" and find out about the existence of this specific ticket? Why should contributors contribute to downstream bmo instead of upstream development?
sorry, but i don't think this is the place to track bugs you personally think would be awesome to fix.

(In reply to Joel Maher (:jmaher) from comment #3)
> contributors can come here and see a list of bugs related, we can embed
> queries easier in wiki pages, we can find bugs easier.

(In reply to Andre Klapper from comment #4)
> @jmaher: 
> Contributors should check for open tickets with higher priority values
> instead. Or bugs tagged as suitable for newcomers. Or bugs tagged with a
> certain Target Milestone. There are many ways already out there.

+1 we already have a mechanism for new contributors to find bugs to work on -- "good first bugs".
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
No longer depends on: 158525
I guess there is no awesome non critical work a contributor can do :(
Joel: Please read comments 3 to 5.
Well it is sad as most of these bugs have existing for years and no contributor found them.  Almost no point in having them filed.  This bug was intended to bring visibility to the bugs and reduce the amount of work needed to discover more work to do.  it sounds like folks didn't like the title of the bug, that is easy to change.  But nevertheless it is probably not a worthwhile effort.
There's no evidence that any contributors have been looking for them, either.  Bugzilla has a very small contributor base; the reasons I've identified being that it is

* a legacy product (i.e. not very shiny, not a lot of cutting-edge tech)
* quite large (hard to get acquainted with)

but probably most importantly

* written in Perl (not a language new programmers tend to learn).

We have good first bugs, and we do get some contributors dropping in and fixing them and others.  We have a lot of documentation in getting involved with the Bugzilla project (https://wiki.mozilla.org/Bugzilla) and a mailing list and IRC where we help people get started and pick a bug.

Finally, I'm not aware of any other Mozilla projects that have tracker bugs serving as lists of "bugs I would personally like to see someone fix", so I don't see the value of having one specifically for Bugzilla.  I understand what you are trying to do, but I think there are other, better ways to accomplish your goal.
You need to log in before you can comment on or make changes to this bug.