Re: Closing old Plasma 4 bugs
On vrijdag 8 juni 2018 22:37:56 CEST Nate Graham wrote: > This work is done; all the bugs and feature requests in the plasma4 > product have been closed. Hope all of your inboxes survived the onslaught! Nice! https://bugs.kde.org/weekly-bug-summary.cgi tells me User# Resolved n...@kde.org2627 which must be a record :-) -- https://www.valdyas.org | https://www.krita.org
Re: Closing old Plasma 4 bugs
On Sat, Jun 9, 2018 at 9:06 AM, Scott Harvey wrote: > Did anyone check how much space has been freed up in the Bugzilla database? The closure of bugs doesn't archive them from the database. Once entered into the system they're in there permanently. Cheers, Ben > On Jun 8, 2018, 3:39 PM -0500, Nate Graham , wrote: > > This work is done; all the bugs and feature requests in the plasma4 > product have been closed. Hope all of your inboxes survived the onslaught! > > Nate > > > > On 02/21/2018 07:21 AM, Nate Graham wrote: > > I have also cleaned up the bug triaging page: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > It's still a bit long, so any further editing to condense it a bit would > be welcome. > > Nate > > > > On 02/21/2018 07:16 AM, Nate Graham wrote: > > > > On 02/21/2018 06:26 AM, Nate Graham wrote: > > > > On Feb 21, 2018, at 12:59 AM, Ben Cooksley wrote: > > On Wed, Feb 21, 2018 at 9:34 AM, pointedstick > wrote: > I have editbugs power on bugs.kde.org, but cannot edit the > Importance field > or mark a bug as CLOSED on bugstest.kde.org. I appear to have the > new normal > permissions. > > > Thanks for confirming my testing Nate. > > I've now gone ahead and rolled this out on bugs.kde.org. > Everyone who had editbugs rights already (all 3,221 of us) have been > made members of the new (fully empowered) contributors group. > > If someone would like to announce this via a blog post please feel > free to do so as I likely won't have time in the next few days to do > so. > > > Fantastic! I'll do that. > > > Done: > https://pointieststick.wordpress.com/2018/02/21/its-now-much-easier-to-be-a-bug-triager/ > > > Nate > > >
Re: Closing old Plasma 4 bugs
On 08.06.2018 23:06, Scott Harvey wrote: Did anyone check how much space has been freed up in the Bugzilla database? None, because the bugs are still there; they just changed the status. On the other hand, we have some 2600+ less open tickets.
Re: Closing old Plasma 4 bugs
Did anyone check how much space has been freed up in the Bugzilla database? On Jun 8, 2018, 3:39 PM -0500, Nate Graham , wrote: > This work is done; all the bugs and feature requests in the plasma4 > product have been closed. Hope all of your inboxes survived the onslaught! > > Nate > > > > On 02/21/2018 07:21 AM, Nate Graham wrote: > > I have also cleaned up the bug triaging page: > > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > > > It's still a bit long, so any further editing to condense it a bit would > > be welcome. > > > > Nate > > > > > > > > On 02/21/2018 07:16 AM, Nate Graham wrote: > > > > > > > > > On 02/21/2018 06:26 AM, Nate Graham wrote: > > > > > > > > > > > > > On Feb 21, 2018, at 12:59 AM, Ben Cooksley wrote: > > > > > > > > > > > On Wed, Feb 21, 2018 at 9:34 AM, pointedstick > > > > > > wrote: > > > > > > I have editbugs power on bugs.kde.org, but cannot edit the > > > > > > Importance field > > > > > > or mark a bug as CLOSED on bugstest.kde.org. I appear to have the > > > > > > new normal > > > > > > permissions. > > > > > > > > > > Thanks for confirming my testing Nate. > > > > > > > > > > I've now gone ahead and rolled this out on bugs.kde.org. > > > > > Everyone who had editbugs rights already (all 3,221 of us) have been > > > > > made members of the new (fully empowered) contributors group. > > > > > > > > > > If someone would like to announce this via a blog post please feel > > > > > free to do so as I likely won't have time in the next few days to do > > > > > so. > > > > > > > > Fantastic! I'll do that. > > > > > > Done: > > > https://pointieststick.wordpress.com/2018/02/21/its-now-much-easier-to-be-a-bug-triager/ > > > > > > > > > Nate > > >
Re: Closing old Plasma 4 bugs
This work is done; all the bugs and feature requests in the plasma4 product have been closed. Hope all of your inboxes survived the onslaught! Nate On 02/21/2018 07:21 AM, Nate Graham wrote: I have also cleaned up the bug triaging page: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging It's still a bit long, so any further editing to condense it a bit would be welcome. Nate On 02/21/2018 07:16 AM, Nate Graham wrote: On 02/21/2018 06:26 AM, Nate Graham wrote: On Feb 21, 2018, at 12:59 AM, Ben Cooksley wrote: On Wed, Feb 21, 2018 at 9:34 AM, pointedstick wrote: I have editbugs power on bugs.kde.org, but cannot edit the Importance field or mark a bug as CLOSED on bugstest.kde.org. I appear to have the new normal permissions. Thanks for confirming my testing Nate. I've now gone ahead and rolled this out on bugs.kde.org. Everyone who had editbugs rights already (all 3,221 of us) have been made members of the new (fully empowered) contributors group. If someone would like to announce this via a blog post please feel free to do so as I likely won't have time in the next few days to do so. Fantastic! I'll do that. Done: https://pointieststick.wordpress.com/2018/02/21/its-now-much-easier-to-be-a-bug-triager/ Nate
Re: Closing old Plasma 4 bugs
On Sun, May 27, 2018 at 9:05 PM, Elvis Angelaccio wrote: > On Fri, May 11, 2018 at 11:06 PM Christoph Feck wrote: > >> On 11.02.2018 20:52, Nate Graham wrote: >> > All right, so let's give it a shot. How about we make it so that normal >> > users have full privilages except the following: >> > >> > - Can't bulk change >> > - Can't change Importance field > >> We now see regressions caused by this particular change: >> - new 'wishlist' tickets end up reported as 'normal' >> - crashes (even from DrKonqi) end up reported as 'normal' > >> Manual intervention is needed to correct these wrong states, >> see https://bugs.kde.org/show_bug.cgi?id=391187 > >> Unfortunately, bugzilla does not differentiate between own tickets and >> changing tickets from others, and I doubt it was our intention to >> remove existing abilities, so I propose to revert the permissions for >> the 'Severity' field. > >> Any objections? > > Hi Ben, Hi Elvis, > given that no one objected, is it possible to fix this regression? Christoph filed a ticket moments before your mail was sent, it should be actioned in the next few days. > > Thanks, > Elvis Cheers, Ben > > > > > >> > - Can't re-open bugs in the CLOSED state
Re: Closing old Plasma 4 bugs
On Fri, May 11, 2018 at 11:06 PM Christoph Feck wrote: > On 11.02.2018 20:52, Nate Graham wrote: > > All right, so let's give it a shot. How about we make it so that normal > > users have full privilages except the following: > > > > - Can't bulk change > > - Can't change Importance field > We now see regressions caused by this particular change: > - new 'wishlist' tickets end up reported as 'normal' > - crashes (even from DrKonqi) end up reported as 'normal' > Manual intervention is needed to correct these wrong states, > see https://bugs.kde.org/show_bug.cgi?id=391187 > Unfortunately, bugzilla does not differentiate between own tickets and > changing tickets from others, and I doubt it was our intention to > remove existing abilities, so I propose to revert the permissions for > the 'Severity' field. > Any objections? Hi Ben, given that no one objected, is it possible to fix this regression? Thanks, Elvis > > - Can't re-open bugs in the CLOSED state
Re: Closing old Plasma 4 bugs
Hello, Just to remind you that companies using KDE/Plasma on RHEL7 are still using plasma 4. I don't know if it has an impact but in case I wanted to point it out. Cheers, Olivier Le samedi 26 mai 2018, 05:09:06 CEST Nate Graham a écrit : > Kubuntu 18.04 has now now been out for a month, so if there are no > further objections, I'll begin preparations for this Plasma 4 mass bug > close. > > Nate > > > > On 02/14/2018 10:16 AM, Christoph Feck wrote: > > On 10.02.2018 21:24, Nate Graham wrote: > >> Hello folks, > >> We have more than 2,500 Plasma 4 bugzilla tickets that we don't intend > >> to look at or triage. We've already prevented new tickets from being > >> filed, but it doesn't do anyone any good to just have the old ones > >> sitting there. My sense is that most of the relevant bugs and wishlist > >> items are already represented in the plasmashell product, so what do you > >> think about doing a mass-close? > >> > >> I was thinking of closing them all with one of the following two > >> messages (top one for bugs, bottom one for wishlist items). What do you > >> think? > >> > >> Nate > >> > >> > >> > >> > >> > >> > >> > >> For bugs: > >> = > >> > >> Hello! > >> > >> This bug was filed for KDE Plasma 4, which reached end-of-support status > >> in October 2015. Developers have not been triaging Plasma 4 bugs since > >> that time. Happily, because KDE Plasma 5's desktop shell was been almost > >> completely rewritten for better performance and usability, it is likely > >> that this bug has already been resolved in Plasma 5. Additionally, bug > >> triaging resources are extremely limited; if you would like to get > >> involved in this effort, please see > >> https://community.kde.org/Get_Involved#Bug_Triaging > >> > >> Accordingly, and we hope you understand why we must close this bug. If > >> the issue described here is still present in KDE Plasma 5.12 or later, > >> please feel free to open a new ticket in the "plasmashell" product after > >> reading https://community.kde.org/Get_Involved/Bug_Reporting > >> > >> Thanks for your understanding! > >> > >> Nate Graham > >> > >> > >> > >> > >> > >> > >> For wishlist items: > >> === > >> > >> Hello! > >> > >> This feature request was filed for KDE Plasma 4, which reached > >> end-of-support status in October 2015. Developers have not been triaging > >> Plasma 4 requests since that time. Happily, because KDE Plasma 5's > >> desktop shell was been almost completely rewritten, it is likely that > >> this feature request has already been implemented in Plasma 5, or is no > >> longer applicable. Additionally, bug triaging resources are extremely > >> limited; if you would like to get involved in this effort, please see > >> https://community.kde.org/Get_Involved#Bug_Triaging > >> > >> Accordingly, and we hope you understand why we must close this feature > >> request. If the requested feature is still not implemented in KDE Plasma > >> 5.12 or later, please feel free to open a new ticket in the > >> "plasmashell" product after reading > >> https://community.kde.org/Get_Involved/Bug_Reporting > >> > >> Thanks for your understanding! > >> > >> Nate Graham > >> > > > > Hi Nate, > > > > had that on my TODO list, but happy to see you taking over for this task. > > > > I suggest to wait until Ubuntu 18.04 LTS is released, ideally a month > > longer to give people with LTS requirements time to update it. > > >
Re: Closing old Plasma 4 bugs
Yes, in fact I work for a company some of whose employees and customers use RHEL 7 (and 6, and 5, believe it or not...). In the end, I don't think it's relevant to us. KDE Plasma 4 wasn't the default shell in any of these distros anyway, so we are talking about an inherently old, niche use case. And anyway, Red Hat is expected to provide support for the very old software shipped in these distros, not upstreams like us. Nate On 05/26/2018 06:04 AM, Olivier Churlaud wrote: Hello, Just to remind you that companies using KDE/Plasma on RHEL7 are still using plasma 4. I don't know if it has an impact but in case I wanted to point it out. Cheers, Olivier Le samedi 26 mai 2018, 05:09:06 CEST Nate Graham a écrit : Kubuntu 18.04 has now now been out for a month, so if there are no further objections, I'll begin preparations for this Plasma 4 mass bug close. Nate On 02/14/2018 10:16 AM, Christoph Feck wrote: On 10.02.2018 21:24, Nate Graham wrote: Hello folks, We have more than 2,500 Plasma 4 bugzilla tickets that we don't intend to look at or triage. We've already prevented new tickets from being filed, but it doesn't do anyone any good to just have the old ones sitting there. My sense is that most of the relevant bugs and wishlist items are already represented in the plasmashell product, so what do you think about doing a mass-close? I was thinking of closing them all with one of the following two messages (top one for bugs, bottom one for wishlist items). What do you think? Nate For bugs: = Hello! This bug was filed for KDE Plasma 4, which reached end-of-support status in October 2015. Developers have not been triaging Plasma 4 bugs since that time. Happily, because KDE Plasma 5's desktop shell was been almost completely rewritten for better performance and usability, it is likely that this bug has already been resolved in Plasma 5. Additionally, bug triaging resources are extremely limited; if you would like to get involved in this effort, please see https://community.kde.org/Get_Involved#Bug_Triaging Accordingly, and we hope you understand why we must close this bug. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting Thanks for your understanding! Nate Graham For wishlist items: === Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in October 2015. Developers have not been triaging Plasma 4 requests since that time. Happily, because KDE Plasma 5's desktop shell was been almost completely rewritten, it is likely that this feature request has already been implemented in Plasma 5, or is no longer applicable. Additionally, bug triaging resources are extremely limited; if you would like to get involved in this effort, please see https://community.kde.org/Get_Involved#Bug_Triaging Accordingly, and we hope you understand why we must close this feature request. If the requested feature is still not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting Thanks for your understanding! Nate Graham Hi Nate, had that on my TODO list, but happy to see you taking over for this task. I suggest to wait until Ubuntu 18.04 LTS is released, ideally a month longer to give people with LTS requirements time to update it.
Re: Closing old Plasma 4 bugs
Kubuntu 18.04 has now now been out for a month, so if there are no further objections, I'll begin preparations for this Plasma 4 mass bug close. Nate On 02/14/2018 10:16 AM, Christoph Feck wrote: On 10.02.2018 21:24, Nate Graham wrote: Hello folks, We have more than 2,500 Plasma 4 bugzilla tickets that we don't intend to look at or triage. We've already prevented new tickets from being filed, but it doesn't do anyone any good to just have the old ones sitting there. My sense is that most of the relevant bugs and wishlist items are already represented in the plasmashell product, so what do you think about doing a mass-close? I was thinking of closing them all with one of the following two messages (top one for bugs, bottom one for wishlist items). What do you think? Nate For bugs: = Hello! This bug was filed for KDE Plasma 4, which reached end-of-support status in October 2015. Developers have not been triaging Plasma 4 bugs since that time. Happily, because KDE Plasma 5's desktop shell was been almost completely rewritten for better performance and usability, it is likely that this bug has already been resolved in Plasma 5. Additionally, bug triaging resources are extremely limited; if you would like to get involved in this effort, please see https://community.kde.org/Get_Involved#Bug_Triaging Accordingly, and we hope you understand why we must close this bug. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting Thanks for your understanding! Nate Graham For wishlist items: === Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in October 2015. Developers have not been triaging Plasma 4 requests since that time. Happily, because KDE Plasma 5's desktop shell was been almost completely rewritten, it is likely that this feature request has already been implemented in Plasma 5, or is no longer applicable. Additionally, bug triaging resources are extremely limited; if you would like to get involved in this effort, please see https://community.kde.org/Get_Involved#Bug_Triaging Accordingly, and we hope you understand why we must close this feature request. If the requested feature is still not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting Thanks for your understanding! Nate Graham Hi Nate, had that on my TODO list, but happy to see you taking over for this task. I suggest to wait until Ubuntu 18.04 LTS is released, ideally a month longer to give people with LTS requirements time to update it.
Re: Closing old Plasma 4 bugs
No objections from me. It was definitely not the intention to prevent users from being able to report wishlist tickets, or to prevent DrKonqi from being able to correctly file crash bugs. Nate On Fri, 11 May 2018 14:06:46 -0700 Christoph Feck wrote > On 11.02.2018 20:52, Nate Graham wrote: > > All right, so let's give it a shot. How about we make it so that normal > > users have full privilages except the following: > > > > - Can't bulk change > > - Can't change Importance field > > We now see regressions caused by this particular change: > - new 'wishlist' tickets end up reported as 'normal' > - crashes (even from DrKonqi) end up reported as 'normal' > > Manual intervention is needed to correct these wrong states, > see https://bugs.kde.org/show_bug.cgi?id=391187 > > Unfortunately, bugzilla does not differentiate between own tickets and > changing tickets from others, and I doubt it was our intention to > remove existing abilities, so I propose to revert the permissions for > the 'Severity' field. > > Any objections? > > > - Can't re-open bugs in the CLOSED state > > > >
Re: Closing old Plasma 4 bugs
On 11.02.2018 20:52, Nate Graham wrote: All right, so let's give it a shot. How about we make it so that normal users have full privilages except the following: - Can't bulk change - Can't change Importance field We now see regressions caused by this particular change: - new 'wishlist' tickets end up reported as 'normal' - crashes (even from DrKonqi) end up reported as 'normal' Manual intervention is needed to correct these wrong states, see https://bugs.kde.org/show_bug.cgi?id=391187 Unfortunately, bugzilla does not differentiate between own tickets and changing tickets from others, and I doubt it was our intention to remove existing abilities, so I propose to revert the permissions for the 'Severity' field. Any objections? - Can't re-open bugs in the CLOSED state
Re: Closing old Plasma 4 bugs
I have also cleaned up the bug triaging page: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging It's still a bit long, so any further editing to condense it a bit would be welcome. Nate On 02/21/2018 07:16 AM, Nate Graham wrote: On 02/21/2018 06:26 AM, Nate Graham wrote: On Feb 21, 2018, at 12:59 AM, Ben Cooksley wrote: On Wed, Feb 21, 2018 at 9:34 AM, pointedstick wrote: I have editbugs power on bugs.kde.org, but cannot edit the Importance field or mark a bug as CLOSED on bugstest.kde.org. I appear to have the new normal permissions. Thanks for confirming my testing Nate. I've now gone ahead and rolled this out on bugs.kde.org. Everyone who had editbugs rights already (all 3,221 of us) have been made members of the new (fully empowered) contributors group. If someone would like to announce this via a blog post please feel free to do so as I likely won't have time in the next few days to do so. Fantastic! I'll do that. Done: https://pointieststick.wordpress.com/2018/02/21/its-now-much-easier-to-be-a-bug-triager/ Nate
Re: Closing old Plasma 4 bugs
On 02/21/2018 06:26 AM, Nate Graham wrote: On Feb 21, 2018, at 12:59 AM, Ben Cooksley wrote: On Wed, Feb 21, 2018 at 9:34 AM, pointedstick wrote: I have editbugs power on bugs.kde.org, but cannot edit the Importance field or mark a bug as CLOSED on bugstest.kde.org. I appear to have the new normal permissions. Thanks for confirming my testing Nate. I've now gone ahead and rolled this out on bugs.kde.org. Everyone who had editbugs rights already (all 3,221 of us) have been made members of the new (fully empowered) contributors group. If someone would like to announce this via a blog post please feel free to do so as I likely won't have time in the next few days to do so. Fantastic! I'll do that. Done: https://pointieststick.wordpress.com/2018/02/21/its-now-much-easier-to-be-a-bug-triager/ Nate
Re: Closing old Plasma 4 bugs
> On Feb 21, 2018, at 12:59 AM, Ben Cooksley wrote: > >> On Wed, Feb 21, 2018 at 9:34 AM, pointedstick wrote: >> I have editbugs power on bugs.kde.org, but cannot edit the Importance field >> or mark a bug as CLOSED on bugstest.kde.org. I appear to have the new normal >> permissions. > > Thanks for confirming my testing Nate. > > I've now gone ahead and rolled this out on bugs.kde.org. > Everyone who had editbugs rights already (all 3,221 of us) have been > made members of the new (fully empowered) contributors group. > > If someone would like to announce this via a blog post please feel > free to do so as I likely won't have time in the next few days to do > so. Fantastic! I'll do that. Nate
Re: Closing old Plasma 4 bugs
On Wed, Feb 21, 2018 at 9:34 AM, pointedstick wrote: > I have editbugs power on bugs.kde.org, but cannot edit the Importance field > or mark a bug as CLOSED on bugstest.kde.org. I appear to have the new normal > permissions. Thanks for confirming my testing Nate. I've now gone ahead and rolled this out on bugs.kde.org. Everyone who had editbugs rights already (all 3,221 of us) have been made members of the new (fully empowered) contributors group. If someone would like to announce this via a blog post please feel free to do so as I likely won't have time in the next few days to do so. Cheers, Ben > > Nate > > > On Sat, 17 Feb 2018 23:51:42 -0800 Ben Cooksley > wrote > > Hi all, > > I've now put together the necessary changes and have deployed them on > the Bugzilla Testbed, at bugstest.kde.org. > If people could please login and verify things are working correctly > for them still that would be appreciated. > > I've given anyone with editbugs membership currently membership of the > new 'contributors' group which has the power to perform the three > actions we decided to restrict. > My testing indicates that everything is working correctly. > > Please note that bugstest.kde.org's email capability is disabled, so > you won't be able to create an account or reset your password if you > are unable to login. > (This does mean that nobody will see email relating to changes you > make there though) > > Thanks, > Ben > > > >
Re: Closing old Plasma 4 bugs
Hi all, I've now put together the necessary changes and have deployed them on the Bugzilla Testbed, at bugstest.kde.org. If people could please login and verify things are working correctly for them still that would be appreciated. I've given anyone with editbugs membership currently membership of the new 'contributors' group which has the power to perform the three actions we decided to restrict. My testing indicates that everything is working correctly. Please note that bugstest.kde.org's email capability is disabled, so you won't be able to create an account or reset your password if you are unable to login. (This does mean that nobody will see email relating to changes you make there though) Thanks, Ben
Re: Closing old Plasma 4 bugs
On 10.02.2018 21:24, Nate Graham wrote: Hello folks, We have more than 2,500 Plasma 4 bugzilla tickets that we don't intend to look at or triage. We've already prevented new tickets from being filed, but it doesn't do anyone any good to just have the old ones sitting there. My sense is that most of the relevant bugs and wishlist items are already represented in the plasmashell product, so what do you think about doing a mass-close? I was thinking of closing them all with one of the following two messages (top one for bugs, bottom one for wishlist items). What do you think? Nate For bugs: = Hello! This bug was filed for KDE Plasma 4, which reached end-of-support status in October 2015. Developers have not been triaging Plasma 4 bugs since that time. Happily, because KDE Plasma 5's desktop shell was been almost completely rewritten for better performance and usability, it is likely that this bug has already been resolved in Plasma 5. Additionally, bug triaging resources are extremely limited; if you would like to get involved in this effort, please see https://community.kde.org/Get_Involved#Bug_Triaging Accordingly, and we hope you understand why we must close this bug. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting Thanks for your understanding! Nate Graham For wishlist items: === Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in October 2015. Developers have not been triaging Plasma 4 requests since that time. Happily, because KDE Plasma 5's desktop shell was been almost completely rewritten, it is likely that this feature request has already been implemented in Plasma 5, or is no longer applicable. Additionally, bug triaging resources are extremely limited; if you would like to get involved in this effort, please see https://community.kde.org/Get_Involved#Bug_Triaging Accordingly, and we hope you understand why we must close this feature request. If the requested feature is still not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting Thanks for your understanding! Nate Graham Hi Nate, had that on my TODO list, but happy to see you taking over for this task. I suggest to wait until Ubuntu 18.04 LTS is released, ideally a month longer to give people with LTS requirements time to update it. Christoph
Re: Closing old Plasma 4 bugs
On Mon, Feb 12, 2018 at 8:52 AM, Nate Graham wrote: > All right, so let's give it a shot. How about we make it so that normal > users have full privilages except the following: > > - Can't bulk change > - Can't change Importance field > - Can't re-open bugs in the CLOSED state Sounds reasonable. I'll leave this open for another 24-48 hours or so to allow those who haven't yet commented the chance to do so, then we can look into actioning this. Nate, would you mind opening a ticket around that time to remind us to action this? Cheers, Ben > > Nate > > > > > On 02/11/2018 09:17 AM, David Edmundson wrote: >> >> >> Interesting. If the broader community is okay with this I see no >> reason why we couldn't rearrange the permissions and how they're >> currently setup. >> I would prefer to restrict the bulk change tools to developers still >> (as undoing the damage they do is much harder) but one-by-one changes >> should be fine to release I think. >> >> Totally fine with it, I think it'll really help. I've ended up filing >> quite a few sysadmin requests requesting editbugs be granted to various >> people. >> >> I'd like it to keep it so that even if normal users can reopen bugs from >> resolved, they can't from closed. >> >> David > >
Re: Closing old Plasma 4 bugs
All right, so let's give it a shot. How about we make it so that normal users have full privilages except the following: - Can't bulk change - Can't change Importance field - Can't re-open bugs in the CLOSED state Nate On 02/11/2018 09:17 AM, David Edmundson wrote: Interesting. If the broader community is okay with this I see no reason why we couldn't rearrange the permissions and how they're currently setup. I would prefer to restrict the bulk change tools to developers still (as undoing the damage they do is much harder) but one-by-one changes should be fine to release I think. Totally fine with it, I think it'll really help. I've ended up filing quite a few sysadmin requests requesting editbugs be granted to various people. I'd like it to keep it so that even if normal users can reopen bugs from resolved, they can't from closed. David
Re: Closing old Plasma 4 bugs
> Interesting. If the broader community is okay with this I see no > reason why we couldn't rearrange the permissions and how they're > currently setup. > I would prefer to restrict the bulk change tools to developers still > (as undoing the damage they do is much harder) but one-by-one changes > should be fine to release I think. > > Totally fine with it, I think it'll really help. I've ended up filing quite a few sysadmin requests requesting editbugs be granted to various people. I'd like it to keep it so that even if normal users can reopen bugs from resolved, they can't from closed. David
Re: Closing old Plasma 4 bugs
El diumenge, 11 de febrer de 2018, a les 4:06:58 CET, Nate Graham va escriure: > + kde-devel to widen the conversation > > On 02/10/2018 05:48 PM, Nicolás Alvarez wrote: > > Meanwhile... maybe you can do some loud blog posts calling for triagers? > > :) > > Sounds good. Before then, we need to clean up the wiki page for this: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > It's thorough and mostly up to date, but huge and intimidating. I've > been working to improve it, but assistance would be appreciated > > > Problem #2: the fact that you need to ask permission before gaining > write access to other people's hugs is a gigantic blockade to getting > more community bug triaging. A LibreOffice bug triager came by recently > and explained that they got an enormous amount more community bug > triaging by moving away from this policy and only locking down a few > things (like the priority and assignee, I think) and leaving the rest > open. He said that in particular it was a big boost to the number of > bugs (correctly) marked as duplicates and closed as fixed. > > Thoughts? We could give it a try worst case scenario if we see it doesn't work we can always revert, after all worst is we have to reopen/unduplicate some bugs, no? Cheers, Albert > > Nate
Re: Closing old Plasma 4 bugs
On Sun, Feb 11, 2018 at 07:29:01PM +1300, Ben Cooksley wrote: > On Sun, Feb 11, 2018 at 4:06 PM, Nate Graham wrote: > > On 02/10/2018 05:48 PM, Nicolás Alvarez wrote: > >> > >> Meanwhile... maybe you can do some loud blog posts calling for triagers? > >> :) > > > > > > Sounds good. Before then, we need to clean up the wiki page for this: > > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > > > It's thorough and mostly up to date, but huge and intimidating. I've been > > working to improve it, but assistance would be appreciated > > > > > > Problem #2: the fact that you need to ask permission before gaining write > > access to other people's hugs is a gigantic blockade to getting more > > community bug triaging. A LibreOffice bug triager came by recently and > > explained that they got an enormous amount more community bug triaging by > > moving away from this policy and only locking down a few things (like the > > priority and assignee, I think) and leaving the rest open. He said that in > > particular it was a big boost to the number of bugs (correctly) marked as > > duplicates and closed as fixed. > > Interesting. If the broader community is okay with this I see no > reason why we couldn't rearrange the permissions and how they're > currently setup. I can only speak for myself but I'd be very much in favor or loosening restrictions on bug permissions to at least allow for community bug triaging. It's the kind of task that requires community involvement anyways (for testing in environments devs can't easily reproduce) and I think anything we do that gives the broader user community more 'ownership' into the bug database would lead to a more accurate and useful bug database. Regards, - Michael Pyne
Re: Closing old Plasma 4 bugs
On Sun, Feb 11, 2018 at 4:06 PM, Nate Graham wrote: > + kde-devel to widen the conversation Hi Nate, > > > On 02/10/2018 05:48 PM, Nicolás Alvarez wrote: >> >> Meanwhile... maybe you can do some loud blog posts calling for triagers? >> :) > > > Sounds good. Before then, we need to clean up the wiki page for this: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > It's thorough and mostly up to date, but huge and intimidating. I've been > working to improve it, but assistance would be appreciated > > > Problem #2: the fact that you need to ask permission before gaining write > access to other people's hugs is a gigantic blockade to getting more > community bug triaging. A LibreOffice bug triager came by recently and > explained that they got an enormous amount more community bug triaging by > moving away from this policy and only locking down a few things (like the > priority and assignee, I think) and leaving the rest open. He said that in > particular it was a big boost to the number of bugs (correctly) marked as > duplicates and closed as fixed. Interesting. If the broader community is okay with this I see no reason why we couldn't rearrange the permissions and how they're currently setup. I would prefer to restrict the bulk change tools to developers still (as undoing the damage they do is much harder) but one-by-one changes should be fine to release I think. We basically operate in this manner for Phabricator already and haven't had issues to my knowledge (and if people are silly we always have the option of closing their accounts) > > Thoughts? > > Nate > Cheers, Ben
Re: Closing old Plasma 4 bugs
+ kde-devel to widen the conversation On 02/10/2018 05:48 PM, Nicolás Alvarez wrote: Meanwhile... maybe you can do some loud blog posts calling for triagers? :) Sounds good. Before then, we need to clean up the wiki page for this: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging It's thorough and mostly up to date, but huge and intimidating. I've been working to improve it, but assistance would be appreciated Problem #2: the fact that you need to ask permission before gaining write access to other people's hugs is a gigantic blockade to getting more community bug triaging. A LibreOffice bug triager came by recently and explained that they got an enormous amount more community bug triaging by moving away from this policy and only locking down a few things (like the priority and assignee, I think) and leaving the rest open. He said that in particular it was a big boost to the number of bugs (correctly) marked as duplicates and closed as fixed. Thoughts? Nate
Re: Closing old Plasma 4 bugs
The only thing we have is a way to do mass-edits without sending any email. That doesn't seem suitable for mass-closing; it's more for things like reassigning lots of bugs to another product. For closing I assume you do want to send email to the reporters. Maybe we can do some script to close the bugs spread over a longer period of time. I'll look into it. Meanwhile... maybe you can do some loud blog posts calling for triagers? :) -- Nicolás 2018-02-10 17:48 GMT-03:00 Nate Graham : > + sysad...@kde.org > > KDE Sysadmins, is there anything special we need to do before doing a mass > bug close? around 2,500 bugs would be closed in a short period of time. > > Martin, good idea. I'll remove that line. > > Nate > > > > On 02/10/2018 01:42 PM, Martin Flöser wrote: >> >> Am 2018-02-10 21:24, schrieb Nate Graham: >>> >>> Hello folks, >>> We have more than 2,500 Plasma 4 bugzilla tickets that we don't intend >>> to look at or triage. We've already prevented new tickets from being >>> filed, but it doesn't do anyone any good to just have the old ones >>> sitting there. My sense is that most of the relevant bugs and wishlist >>> items are already represented in the plasmashell product, so what do >>> you think about doing a mass-close? >>> >>> I was thinking of closing them all with one of the following two >>> messages (top one for bugs, bottom one for wishlist items). What do >>> you think? >> >> >> +1 on that. If you want to do that, please get in contact with sysadmin >> team before. They might have some requirements regarding mass closing of >> bugreports (at least in the past this resulted in email traffic which put us >> on spammer lists). >> >> Concerning the text: >> I would cut the "Developers have not been triaging Plasma 4 bugs since >> that time.", the message that it is EOL is sufficient for what we want to >> tell. Also it opens an attack vector (lazy devs don't look for bugs). >> >> For reference the message I put into KWin for mass closing bugs: >> >> As of git commit 34027455aaa2ee738c45987ca2d8cb7d65491bf0 window tiling >> support has been removed from KWin. This change will go into version 4.10, >> the upcoming release 4.9 still provides window tiling support. The >> discussion has been taken on the developer mailing list [1]. A short summary >> of the reasons here: >> * it is unmaintained >> * it is a mode not used by any of the core KWin team >> * original developer said at Akademy 2012 that he is not interested in >> picking up the work again >> * tiling has quite some bugs, e.g. multi screen not supported >> * is conflicting with other concepts in KWin, e.g. activities >> >> A result of this change is that we will not implement any new features or >> fix bugs related to window tiling. >> >> There is ongoing work to provide window tiling as an external KWin script. >> We encourage everyone to participate in this effort and to make it really >> rock and have it available once 4.10 is going to be released. The current >> state can be found in the git repository [2] in the directory >> kwin/scripts/tiling. >> >> [1] http://lists.kde.org/?l=kwin&m=133149673110558&w=2 >> [2] https://github.com/mgottschlag/kwin-tiling/ >> >> Cheers >> Martin >> >>> >>> Nate >>> >>> >>> >>> >>> >>> >>> >>> For bugs: >>> = >>> >>> Hello! >>> >>> This bug was filed for KDE Plasma 4, which reached end-of-support >>> status in October 2015. Developers have not been triaging Plasma 4 >>> bugs since that time. Happily, because KDE Plasma 5's desktop shell >>> was been almost completely rewritten for better performance and >>> usability, it is likely that this bug has already been resolved in >>> Plasma 5. Additionally, bug triaging resources are extremely limited; >>> if you would like to get involved in this effort, please see >>> https://community.kde.org/Get_Involved#Bug_Triaging >>> >>> Accordingly, and we hope you understand why we must close this bug. If >>> the issue described here is still present in KDE Plasma 5.12 or >>> later, please feel free to open a new ticket in the "plasmashell" >>> product after reading >>> https://community.kde.org/Get_Involved/Bug_Reporting >>> >>> Thanks for your understanding! >>> >>> Nate Graham >>> >>> >>> >>> >>> >>> >>> For wishlist items: >>> === >>> >>> Hello! >>> >>> This feature request was filed for KDE Plasma 4, which reached >>> end-of-support status in October 2015. Developers have not been >>> triaging Plasma 4 requests since that time. Happily, because KDE >>> Plasma 5's desktop shell was been almost completely rewritten, it is >>> likely that this feature request has already been implemented in >>> Plasma 5, or is no longer applicable. Additionally, bug triaging >>> resources are extremely limited; if you would like to get involved in >>> this effort, please see >>> https://community.kde.org/Get_Involved#Bug_Triaging >>> >>> Accordingly, and we hope you understand why we must close this feature >>> request. If the requested feature is still
Re: Closing old Plasma 4 bugs
+ sysad...@kde.org KDE Sysadmins, is there anything special we need to do before doing a mass bug close? around 2,500 bugs would be closed in a short period of time. Martin, good idea. I'll remove that line. Nate On 02/10/2018 01:42 PM, Martin Flöser wrote: Am 2018-02-10 21:24, schrieb Nate Graham: Hello folks, We have more than 2,500 Plasma 4 bugzilla tickets that we don't intend to look at or triage. We've already prevented new tickets from being filed, but it doesn't do anyone any good to just have the old ones sitting there. My sense is that most of the relevant bugs and wishlist items are already represented in the plasmashell product, so what do you think about doing a mass-close? I was thinking of closing them all with one of the following two messages (top one for bugs, bottom one for wishlist items). What do you think? +1 on that. If you want to do that, please get in contact with sysadmin team before. They might have some requirements regarding mass closing of bugreports (at least in the past this resulted in email traffic which put us on spammer lists). Concerning the text: I would cut the "Developers have not been triaging Plasma 4 bugs since that time.", the message that it is EOL is sufficient for what we want to tell. Also it opens an attack vector (lazy devs don't look for bugs). For reference the message I put into KWin for mass closing bugs: As of git commit 34027455aaa2ee738c45987ca2d8cb7d65491bf0 window tiling support has been removed from KWin. This change will go into version 4.10, the upcoming release 4.9 still provides window tiling support. The discussion has been taken on the developer mailing list [1]. A short summary of the reasons here: * it is unmaintained * it is a mode not used by any of the core KWin team * original developer said at Akademy 2012 that he is not interested in picking up the work again * tiling has quite some bugs, e.g. multi screen not supported * is conflicting with other concepts in KWin, e.g. activities A result of this change is that we will not implement any new features or fix bugs related to window tiling. There is ongoing work to provide window tiling as an external KWin script. We encourage everyone to participate in this effort and to make it really rock and have it available once 4.10 is going to be released. The current state can be found in the git repository [2] in the directory kwin/scripts/tiling. [1] http://lists.kde.org/?l=kwin&m=133149673110558&w=2 [2] https://github.com/mgottschlag/kwin-tiling/ Cheers Martin Nate For bugs: = Hello! This bug was filed for KDE Plasma 4, which reached end-of-support status in October 2015. Developers have not been triaging Plasma 4 bugs since that time. Happily, because KDE Plasma 5's desktop shell was been almost completely rewritten for better performance and usability, it is likely that this bug has already been resolved in Plasma 5. Additionally, bug triaging resources are extremely limited; if you would like to get involved in this effort, please see https://community.kde.org/Get_Involved#Bug_Triaging Accordingly, and we hope you understand why we must close this bug. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting Thanks for your understanding! Nate Graham For wishlist items: === Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in October 2015. Developers have not been triaging Plasma 4 requests since that time. Happily, because KDE Plasma 5's desktop shell was been almost completely rewritten, it is likely that this feature request has already been implemented in Plasma 5, or is no longer applicable. Additionally, bug triaging resources are extremely limited; if you would like to get involved in this effort, please see https://community.kde.org/Get_Involved#Bug_Triaging Accordingly, and we hope you understand why we must close this feature request. If the requested feature is still not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting Thanks for your understanding! Nate Graham
Re: Closing old Plasma 4 bugs
Am 2018-02-10 21:24, schrieb Nate Graham: Hello folks, We have more than 2,500 Plasma 4 bugzilla tickets that we don't intend to look at or triage. We've already prevented new tickets from being filed, but it doesn't do anyone any good to just have the old ones sitting there. My sense is that most of the relevant bugs and wishlist items are already represented in the plasmashell product, so what do you think about doing a mass-close? I was thinking of closing them all with one of the following two messages (top one for bugs, bottom one for wishlist items). What do you think? +1 on that. If you want to do that, please get in contact with sysadmin team before. They might have some requirements regarding mass closing of bugreports (at least in the past this resulted in email traffic which put us on spammer lists). Concerning the text: I would cut the "Developers have not been triaging Plasma 4 bugs since that time.", the message that it is EOL is sufficient for what we want to tell. Also it opens an attack vector (lazy devs don't look for bugs). For reference the message I put into KWin for mass closing bugs: As of git commit 34027455aaa2ee738c45987ca2d8cb7d65491bf0 window tiling support has been removed from KWin. This change will go into version 4.10, the upcoming release 4.9 still provides window tiling support. The discussion has been taken on the developer mailing list [1]. A short summary of the reasons here: * it is unmaintained * it is a mode not used by any of the core KWin team * original developer said at Akademy 2012 that he is not interested in picking up the work again * tiling has quite some bugs, e.g. multi screen not supported * is conflicting with other concepts in KWin, e.g. activities A result of this change is that we will not implement any new features or fix bugs related to window tiling. There is ongoing work to provide window tiling as an external KWin script. We encourage everyone to participate in this effort and to make it really rock and have it available once 4.10 is going to be released. The current state can be found in the git repository [2] in the directory kwin/scripts/tiling. [1] http://lists.kde.org/?l=kwin&m=133149673110558&w=2 [2] https://github.com/mgottschlag/kwin-tiling/ Cheers Martin Nate For bugs: = Hello! This bug was filed for KDE Plasma 4, which reached end-of-support status in October 2015. Developers have not been triaging Plasma 4 bugs since that time. Happily, because KDE Plasma 5's desktop shell was been almost completely rewritten for better performance and usability, it is likely that this bug has already been resolved in Plasma 5. Additionally, bug triaging resources are extremely limited; if you would like to get involved in this effort, please see https://community.kde.org/Get_Involved#Bug_Triaging Accordingly, and we hope you understand why we must close this bug. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting Thanks for your understanding! Nate Graham For wishlist items: === Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in October 2015. Developers have not been triaging Plasma 4 requests since that time. Happily, because KDE Plasma 5's desktop shell was been almost completely rewritten, it is likely that this feature request has already been implemented in Plasma 5, or is no longer applicable. Additionally, bug triaging resources are extremely limited; if you would like to get involved in this effort, please see https://community.kde.org/Get_Involved#Bug_Triaging Accordingly, and we hope you understand why we must close this feature request. If the requested feature is still not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting Thanks for your understanding! Nate Graham
Closing old Plasma 4 bugs
Hello folks, We have more than 2,500 Plasma 4 bugzilla tickets that we don't intend to look at or triage. We've already prevented new tickets from being filed, but it doesn't do anyone any good to just have the old ones sitting there. My sense is that most of the relevant bugs and wishlist items are already represented in the plasmashell product, so what do you think about doing a mass-close? I was thinking of closing them all with one of the following two messages (top one for bugs, bottom one for wishlist items). What do you think? Nate For bugs: = Hello! This bug was filed for KDE Plasma 4, which reached end-of-support status in October 2015. Developers have not been triaging Plasma 4 bugs since that time. Happily, because KDE Plasma 5's desktop shell was been almost completely rewritten for better performance and usability, it is likely that this bug has already been resolved in Plasma 5. Additionally, bug triaging resources are extremely limited; if you would like to get involved in this effort, please see https://community.kde.org/Get_Involved#Bug_Triaging Accordingly, and we hope you understand why we must close this bug. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting Thanks for your understanding! Nate Graham For wishlist items: === Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in October 2015. Developers have not been triaging Plasma 4 requests since that time. Happily, because KDE Plasma 5's desktop shell was been almost completely rewritten, it is likely that this feature request has already been implemented in Plasma 5, or is no longer applicable. Additionally, bug triaging resources are extremely limited; if you would like to get involved in this effort, please see https://community.kde.org/Get_Involved#Bug_Triaging Accordingly, and we hope you understand why we must close this feature request. If the requested feature is still not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting Thanks for your understanding! Nate Graham