Sorry, but I try to point out that the process is broken and give a few examples on how to fix the process.
On Thu, Mar 14, 2019 at 1:20 PM Andre Klapper <[email protected]> wrote: > > On Thu, 2019-03-14 at 12:35 +0100, John Erling Blad wrote: > > Blame games does not fix faulty processes. > > Hmm, why is this thread called "Question to WMF" instead of "Question > to developers"? > > > Why do we have bugs that isn't handled for years? > > Basically: Because you did not fix these bugs. Longer version: > https://www.mediawiki.org/wiki/Bug_management/Development_prioritization > > > Why is it easier to get a new feature than fixing an old bug? > > {{Citation needed}}. > If that was the case: Because your priority was to write code for a new > feature instead of fixing an old bug. Longer version: > https://www.mediawiki.org/wiki/Bug_management/Development_prioritization > > > Google had a problem with unfixed bugs, and they started identifying > > the involved developers each time the build was broken. That is pretty > > harsh, but what if devs somehow was named when their bugs were > > mentioned? What if there were some kind of public statistic? How would > > the devs react to being identified with a bug? Would they fix the bug, > > or just be mad about it? Devs at some of Googles teams got mad, but in > > the end the code were fixed. Take a look at "GTAC 2013 Keynote: > > Evolution from Quality Assurance to Test Engineering" [1] > > Not really - I see 60000 open bug reports in Chromium, for example: > https://bugs.chromium.org/p/chromium/issues/list > (Only if you want to imply that only "Google" was responsible for > fixing all bugs in that free and open source project, of course.) > > > What if we could show information from the bugs in Phabricator in a > > "tracked" template at other wiki-projects, identifying the team > > responsible and perhaps even the dev assigned to the bug? Imagine the > > creds the dev would get when the bug is fixed! Because it is easy to > > loose track of pages with "tracked" templates we need some other means > > to show this information, and our "public monitor" could be a special > > page with the same information. > > Feel free to extend https://www.mediawiki.org/wiki/Template:Tracked > > > We say we don't want voting over bugs, but by saying that we refuse > > getting stats over how many users a specific bug hits, and because of > > that we don't get sufficient information (metrics) to make decisions > > about specific bugs. > > I disagree. Different people see different priorities. Longer version: > https://www.mediawiki.org/wiki/Bug_management/Development_prioritization > > > What if users could give a "this hits me too" from a "tracked" > > template. That would give a very simple metric on how important it is > > to fix a problem. > > It does not, because software development is not a popularity contest: > https://www.mediawiki.org/wiki/Bug_management/Development_prioritization > Voting would create expectations that nobody will fulfill. > > Cheers, > andre > -- > Andre Klapper | Bugwrangler / Developer Advocate > https://blogs.gnome.org/aklapper/ > > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
