[18:01] <arraybolt3> 11:47 <lubot> [telegram] <Michael> Hi team, does lubuntu has inbuilt night light filter/blue light filter?
[18:01] <arraybolt3> 11:48 <lubot> [telegram] <Michael> Or do we need to install a third party application?
[18:01] <arraybolt3> 11:58 <arraybolt3> We do not ship one by default.
[18:01] <arraybolt3> 11:59 <arraybolt3> That said, we could in future releases, and this is the perfect time for us to think about doing that since we're just starting to develop Lubuntu 24.04.
[18:01] <arraybolt3> Thoughts?
[18:04] <arraybolt3> Also see https://discourse.lubuntu.me/t/redshift-qt-for-lubuntu-20-10/1916
[18:06] <arraybolt3> I'd be happy to package Redshift-qt for Debian and ask tsimonq2 to sponsor it. Then it can be pulled into Ubuntu, seeded in Lubuntu, added to our packageset, and bingo.
[20:37] <Eickmeyer> That would be a situation of "don't ask for permission, ask for forgiveness."
[20:37] <Eickmeyer> In other words, JFDI.
 ditto
[20:46] <arraybolt3> haha
[20:46] <arraybolt3> I try to *NOT* live my that motto as much as I'm able to :P
[20:46] <arraybolt3> But anyway, /me adds that to The List and assigns it to myself
[20:47] <Eickmeyer> arraybolt3: When it comes to packaging stuff, feel empowered to just get it done. Don't feel like you need to ask for permission. Seeding is secondary and can be reviewed later.
[20:47] <arraybolt3> Makes sense.
[20:50] <tsimonq2> arraybolt3: Please be CoC compliant. ;P
[20:50] <tsimonq2> "The poorest decision of all is no decision: clarity of direction has value in itself. Sometimes all the data are not available, or consensus is elusive. A decision must still be made. There is no guarantee of a perfect decision every time - we prefer to err, learn, and err less in future than to postpone action indefinitely."
[20:50] <tsimonq2> "We invite anybody, from any company, to participate in any aspect of the project. Our community is open, and any responsibility can be carried by any contributor who demonstrates the required capacity and competence."
[20:50] <tsimonq2> arraybolt3: As a prospective MOTU, you should specifically feel empowered to maintain software within the wider Ubuntu universe (pun intended). :)
[20:50] <tsimonq2> arraybolt3: That includes introducing new software.
[20:51] <tsimonq2> arraybolt3: Seeding it however, *that's* where we come in.
[20:52] <arraybolt3> Well I know I could Just Do It if I wanted to, but since it was specifically to fulfill a feature request in Lubuntu, that's why I asked.
[20:52] <tsimonq2> *shrug* don't ask before doing with new packages, ask for new seed additions ;)
[20:52] <arraybolt3> If we're like "meh, we don't want that", then I'd rather focus my time elsewhere for this exact moment (like merge stealing and whatnot). If we're thinking "oooh, that looks nifty", then I'd like to jump on it.
[20:52] <tsimonq2> Ah, okay. Just gauging the room, I get it.
[20:53] <tsimonq2> Yeah, I'd say we should ship it.
[20:53] <tsimonq2> Fits within our philisophy to at least include that opt-in.
[20:53] <arraybolt3> kk, then it's something worth spending time on.
[20:54] <tsimonq2> arraybolt3: Thanks for what you do <3
[20:55] <arraybolt3> Thanks for your encouragement :)
[20:57] <Eickmeyer> Also, if something exists that might be even *remotely* useful, feel free to package it. Did you know I did that for a text-mode window manager (twin)?
[20:58] <Eickmeyer> It's never a waste of time if it's useful.
[21:00] <arraybolt3> Oh cool!
[21:03] <tsimonq2> teward: Kay, so...
[21:03] <tsimonq2> teward: We *need* the wiki.
[21:04] <tsimonq2> teward: I get it, stuff happens, but that wiki stuff, even if we just get it plaintext, is pretty critical.
[21:04] <tsimonq2> teward: The other stuff on Phab, well, we might want to move some tasks over but that's about it.
[21:04] <tsimonq2> teward: *At your convenience* could you please either spin up the Phab fork and migrate over (at least) the wiki, or could we get those plaintext files?
[21:05] <tsimonq2> @teward001: AFAIK the wiki and tasks are *not* affected by the AWS stuff.
[21:05] <teward> tsimonq2: so
[21:05] <teward> they aren't
[21:05] <teward> but
[21:05] <teward> it's being deployed in a sandbox and then limited-access it with extra security barriers
[21:05] <teward> but we need somewhere to *put* the wiki and tasks
[21:05] <teward> I'm not against finding alternative task handling solutions like redmine or something else
[21:05] <teward> or an alterantive wiki
[21:05] <teward> Phorge is also an alternative possibly if I clean-deploy it
[21:06] <teward> but i'm putting up several trillion security barriers in place before I open sanboxed Phab up again to limited-access
[21:06] <teward> because if it is breached i want to collect the bad guy's data :P
[21:07] <teward> we forget i'm an it security researcher xD
[21:07] <tsimonq2> I didn't forget I was just wanting the wiki back up XD
[21:08] <tsimonq2> I understood there was some Stuff, but let me know when we have sandbox access again.
[21:08] <tsimonq2> And, if possible, I think Phorge is our best stop-gap.
[21:08] <teward> as i said it'll be limited access i'll be putting some extra security controls in place and such to get to the box with limited access
[21:09] <teward> stuff ain't easy to deploy though so patience is a virtue
[21:09] <tsimonq2> Thus why I said at your convenience :) keep us posted.
[21:09] <tsimonq2> That being said, we have a *lot* of inaccessible docs right now, so the sooner we could (at the minimum) get plaintext copies, the better.
 tsimonq2: if we do go with Phorge it'll be set up by me with a whole slew of security controls on it
 if we dont then we just need alternatives
 not sure we need the whole phorge stack though for just two pieces
[22:27] <arraybolt3> Perhaps we can just make a Wiki repo on Gitea?
[22:31] <arraybolt3> that makes sense
[22:32] <arraybolt3> I didn't know there were different levels of wiki access.
 We also need a CI. I'm familiar with Jenkins, my vote is that to start. :P (re @teward001: tsimonq2: if we do go with Phorge it'll be set up by me with a whole slew of security controls on it)
[23:03]  * arraybolt3 thinks of Jenkins as "Security Vulnerabilities in a Box" :P
[23:04] <arraybolt3> Even a critical Qubes OS project once got their Jenkins server compromised when it got out of date.
[23:18] <teward> kc2bez: Doable with separate groups on Gitea.  lubuntu-council/ lubuntu-members/ lubuntu/  as base namespaces/orgs
[23:18] <teward> keeping access separate isn't hard it's just diligence and keeping up on it that matters
[23:24] <teward> CI is its own beast Simon
[23:24] <teward> and that'll take more time than the wiki
[23:24] <arraybolt3> Uploaded a cala-settings-ubuntu change to use sudo -E again, so now we'll get nice theming in the installer.
[23:24] <teward> both take more time than i have available today