[07:02] <arraybolt3[m]> Do you think we should claim this team? https://launchpad.net/~pkg-lxqt-devel
[07:04] <arraybolt3[m]> It would allow us to have control over marking the importance of bugs in LXQt packages (for instance, a newly-reported regression in lxqt-config-brighness here: https://launchpad.net/~pkg-lxqt-devel, which should probably be assigned "Critical" status if it can be verified since it breaks previously existing functionality)
[07:04] <arraybolt3[m]> (At least I think it would allow us to do that.)
=== guiverc2 is now known as guiverc
[07:46] <guiverc> arraybolt3, I suspect it's before any current team members (LXQt/15.04 on launchpad), but I don't know.. Simon/tsimonq2 likely has best clue, if not Thomas or Lyn...  I suspect claiming the team won't change anything
[07:50] <arraybolt3> guiverc: Ah. That team is listed as the maintainer for https://launchpad.net/ubuntu/+source/lxqt-config, maybe it would be a better option to figure out how to get that switched over to the Lubuntu Developers instead. If that's even necessary.
[07:54] <guiverc> yeah that page highlights a reason to do it; or change ownership.. You need a Core-dev opinion though probably...  
[09:23] <kc2bez> arraybolt3[m]: Are you referencing bug 1989028
[09:23] <ubot93> Bug 1989028 in lxqt-config (Ubuntu) "22.04 Brightness shortcut keys do not work" [Undecided, New] https://launchpad.net/bugs/1989028
[09:24] <kc2bez> You don't need to be a team owner to change the importance, I can do that. I don't know which thing gives me the power to do that.
[09:26] <kc2bez> I wouldn't flip that to critical, it is a High or even Medium.
[09:38] <RikMills> kc2bez: for importance, be a member of bug control team
[10:12] <kc2bez> That makes sense. Thanks RikMills 
=== arraybolt3_ is now known as arraybolt3
=== arraybolt3_ is now known as arraybolt3