Re: Policy on stale bugs (was Re: Closing NEEDSINFO bugs after 30 days)

2018-11-16 Thread Andrew Crouthamel
will be well. In regards to Haralds script, it is fully functional now and appears to work very well. Original Message On Nov 16, 2018, 4:37 AM, Luigi Toscano wrote: > Andrew Crouthamel ha scritto: >> I've been spending a lot of time browsing, searching, and filtering

Re: Discourse

2018-10-29 Thread Andrew Crouthamel
, whether I want to or not. Switching to a forum system puts the power in the users hands, to decide what to receive. This would be a good opportunity to update our infrastructure we use for community discussion, and standardize on a smaller, more modern set of systems. Andrew Crouthamel

Re: Bugzilla template problems

2018-10-27 Thread Andrew Crouthamel
FYI boud, I finally got around to making the changes we agreed to a few weeks ago: https://phabricator.kde.org/D16474 Hopefully that helps. Andrew Crouthamel ‐‐‐ Original Message ‐‐‐ On Tuesday, October 23, 2018 4:49 PM, Boudewijn Rempt wrote: > On maandag 8 oktober 2018 21:10

Re: KDE at the LinuxDay Vorarlberg

2018-10-15 Thread Andrew Crouthamel
That's great to hear, the performance aspect is certainly one that is constantly echoed in Reddit and other social media. Andrew Crouthamel ‐‐‐ Original Message ‐‐‐ On Monday, October 15, 2018 12:09 PM, Kai Uwe Broulik wrote: > Hi all, > > on Saturday Myriam and I attended

Re: Bugzilla template problems

2018-10-08 Thread Andrew Crouthamel
one doesn't want to fill out everything, they don't have to. I've seen plenty of people deleting some of the template or not filling out some fields. Andrew Crouthamel

Re: Bugzilla template problems

2018-10-04 Thread Andrew Crouthamel
Why not just something generic: SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Andrew Crouthamel ‐‐‐ Original Message ‐‐‐ On Thursday, October 4, 2018 12:13 PM, Nate Graham wrote: >

Re: Improving Bugzilla Status Names

2018-09-30 Thread Andrew Crouthamel
Yeah I never really understood the purpose of that. Just set it to reported status then or confirmed. Whatever it was before. Original Message On Sep 30, 2018, 12:42 PM, Nate Graham wrote: > On 09/30/2018 10:39 AM, David Jarvie wrote: >> I think that REPORTED is an ideal term

Re: Improving Bugzilla Status Names

2018-09-30 Thread Andrew Crouthamel
I like OPENED as well. Original Message On Sep 29, 2018, 6:17 PM, Ben Cooksley wrote: > On Sun, Sep 30, 2018 at 9:44 AM Valorie Zimmerman > wrote: >> >> On Fri, Sep 28, 2018 at 1:48 AM Luigi Toscano >> wrote: >>> >>> Kai Uwe Broulik ha scritto: >>> > Hi, >>> > >>> > > Here

Re: Closing NEEDSINFO bugs after 30 days

2018-09-18 Thread Andrew Crouthamel
re information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! Andrew Crouthamel ‐‐‐ Original Message ‐‐‐ On Tuesday, September 18, 201

Re: Closing NEEDSINFO bugs after 30 days

2018-09-17 Thread Andrew Crouthamel
No problem, I can make that part of the procedure until we figure out an automated method. After two weeks, send out a reminder, then two weeks later close if no activity. Andrew Crouthamel ‐‐‐ Original Message ‐‐‐ On Monday, September 17, 2018 3:10 PM, Michael Reeves wrote: >

Re: Closing NEEDSINFO bugs after 30 days

2018-09-17 Thread Andrew Crouthamel
At worst case, we could edit bug/create/user-message.html.tmpl which is the text that shows at the top of the bug creation page. Andrew Crouthamel ‐‐‐ Original Message ‐‐‐ On Monday, September 17, 2018 2:38 PM, Scott Harvey wrote: > Can Bugzilla be configured to add boilerpl

Closing NEEDSINFO bugs after 30 days

2018-09-17 Thread Andrew Crouthamel
? Andrew Crouthamel

Re: Improving Bugzilla Status Names

2018-09-06 Thread Andrew Crouthamel
ms). Regarding closing wishlist items with, I believe RESOLVED > LATER is a good choice, it appears others are already doing that. Here is my follow-up change recommendation based on feedback and research: UNCONFIRMED -> REPORTED WONTFIX -> INTENTIONAL INVALID -> NOTABUG Andrew C

Re: Improving Bugzilla Status Names

2018-09-05 Thread Andrew Crouthamel
Does anyone else have comments on status names? The name itself or yay/nay on renames? Here are some updated proposed names based on feedback and thesaurus searching: UNCONFIRMED -> REPORTED or OPEN WONTFIX -> ASDESIGNED or INTENTIONAL INVALID -> NOTABUG or ERRONEOUS Andrew C

Re: Improving Bugzilla Status Names

2018-09-05 Thread Andrew Crouthamel
? I know that isn't perfect, but was the best we could come up with so far. Andrew Crouthamel Original Message On Sep 5, 2018, 12:03 AM, Nate Graham wrote: > On 09/04/2018 10:01 PM, Christoph Feck wrote: >> I still oppose to name a status NEW (again). It only attr

Improving Bugzilla Status Names

2018-09-04 Thread Andrew Crouthamel
feedback previously provided in the past two years. Feedback? Comments? Consensus? Thanks! Andrew Crouthamel

Re: Default bug editing privileges can't change Importance field

2018-09-04 Thread Andrew Crouthamel
Ok great, thanks for clearing that up. I'll make sure to add that information to the Bug Triaging wiki page. Sent from ProtonMail mobile Original Message On Sep 4, 2018, 2:46 AM, David Edmundson wrote: > It's not a mistake. From the thread where permissions are relaxed: >

Default bug editing privileges can't change Importance field

2018-09-03 Thread Andrew Crouthamel
Hi everyone, I am currently a standard user in Bugzilla, and noticed that I am unable to edit any of the Importance fields anywhere. I asked Nate about this and he told me he believes this is a mistake, as last he could recall, standard users should be able to change the second Importance