Just in case you didn’t circle back, the other commenter is correct. Just like Debian repositories, Arch repositories also haven’t been poisoned like this . AUR has recently, but that’s equivalent of like on Debian adding 3rd party repos, but AUR is just a meta collection of those unofficial user repos basically. Arch documentation even warns against blindly installing from AUR, and to read the pkg build first since it’s basically the same thing as copy and pasting a curl command from a GitHub repo’s readme.

Oh and pangolin for a VPN tunneling replacement.

Proxmox communities are also good for some ideas, basically every sysadmin I know eventually spins up a cluster and builds their ideal tech stack that they wished they could use at work.

You should stick with more “corporate” or adjacent distros, that way they (or you) can purchase a support contract without having to reinstall or shift later down the line, so more like fedora or opensuse.

Postgress is more mainstream than SQL server in cloud native environments, no licensing. And plenty of managed option without too much of a lift and shift.

Next cloud might be an option to replace office 365, should look at open/only office (forget which one is active) along side libre office.

I think jitski can help replace zoom/teams, kind if.

Biggest hurdle will be excel and Active Directory Nothing else comes close to as feature (and hair pulling bug) filled as excel.

For AD there’s not even really an equivalent, but that can be a good thing. I would look into combining an Oauth service (keycloak is suppose to be good for “consumer” grade, Okta or whatever preferred cloud provide has for more professional) along with something like a casbin library (at least for servers/development).

I highly recommend following all the self hosted and open source communities here on Lemmy, I find new tech at least once a week from them that I consider taking to my bosses.

If possible it might help to have a couple demo PCs out so that they and try different desktop environments. Some might be more enthusiastic if they can not only play around with it when it’s up and running (and gives people something to do while your helping others) but also if the DE matches their “workflow better” it also gives you a chance to show them how to do common tasks. Maybe different demos have different “suites”, like here’s the gaming demo, here’s regular, productivity, etc

I agree with some of the other posts, I’d stick with 1 distro (whichever all the helpers are most comfortable with) so that you can speak confidently about it, and decrease the chances of something going wrong and you having to break out Google and the terminal. A DE is an easier choice to explain that different distros affecting and impacting things they can’t see. Especially if you might have to provide tech support during the beginning. Maybe just say a throw away line or 2 about there being different distros, just like there’s different kinds of cheese. Still same thing at its core, just different options.

I also recommend a couple spare external hard drives for them to back up their files.

I’d maybe do just a brief overview at the beginning. And go more in depth afterwards so they don’t get overloaded.

Thank you for the video, I’ll check it out!

Which standard should I be looking into if I want a second AP/device that connects to the “main” router wirelessly, that extends the network range. I live in an apartment and can’t run Ethernet.

What GPU are you using? What influenced you to add “Oibaf PPA” instead of using the default built in Mesa drivers that came with Mint? No judgement, just trying to figure out what led you here, so we can unravel it. Because as the other poster mentioned, Vulkan for Amd should have worked out of the box on a fresh install.

Edit, to clarify, did you add the repo because you thought that mint didn’t have drivers and that was the way to get them? Or was there a different reason you needed to add the repo?

This documentation is for bazzite, but they have a lot of the same stack under the hood. “Broadcom’s WL driver can be installed since it is needed by some hardware. Disabled by default. Enter “just use-broadcom-wl” to use it.”. You could try to see if aurura has the same “just” options, that’s where I would first research. If not, then yeah, “rpm-ostree” would be how you install the package, just like you said, just not sure of the commands for local files. Also there is a tool to “roll your own” distro built on top of any of the ublue work, it’s basically how bazzite and aurora exist. So you can layer the packages like the other option you said. https://github.com/ublue-os/image-template

It depends on what your metrics are for energy and resources. Are you talking about the end user hardware, or are you talking about developer time and effort. If it’s the former, you’re right, if it’s the latter you’re completely wrong. And while there’s merit to your point (if it is about end user storage, energy consumption, etc), that’s not really in short supply while open source developers free time is.