Don't we already have OpenStack? Something, something OpenStack complicated, something, something. Sounds a bit like raison d'étre.
avidamoeba
joined 1 year ago
A wiki sounds like the right thing since you want to be able to see the current and previous versions of things. It's a bit easier to edit than straight Markdown in git, which is the other option I'd do. Ticketing systems like OpenProject are more useful for tracking many different pieces of work simultaneously, including future work. The process of changing your current networking setup from A to B would be tracked in OpenProject. New equipment to buy, cabling to do, software to install, descibing it in your wiki, and the progress on each of those. Your wiki would be in state A before you begin this ticket. Once you finish it, your wiki will be in state B. While in progress, the wiki would be somewhere between A and B. You could of course use just the wiki but it's nice to have a place where you can keep track of all the other things including being able to leave comments that provide context which allows you to resume at a later point in time. At several workplaces the standard setup that always gets entrenched is a ticketing system, a wiki and a version control. Version is only needed for tasks that include code. So the absolute core are the other two. If I had to reduce to a single solution, I'd choose a wiki since I could use separate wiki pages to track my progress as I go from A to B.
Good guy Ubuntu puts us on the radar.
I've long made using Linux a condition for free IT support. I assist with switching for the willing. It reduces the amount of support I have to do which allows me to support a lot more people. ☺️
The corpo I work for also uses Ubuntu on the developer workstations. Everyone I know in real life who uses Linux uses Ubuntu.
That's your mistake. I'm currently preparing a laptop with Linux for mine.
What's the benefit of dd-ing a home partition over rsync-a-ing a home directory's contents?
Partitioning (beyond what's needed to boot)? No. Logical volumes or datasets? Perhaps, but probably not for most trivial setups. Even swap is fine on a file if you need it and it simplifies disk encryption. Most of my machines run an EFI and an LVM partition. If I need a separate volume for something, I can always create it in LVM.
Dave Calhoun is this you?
The developer made extra low effort and missed a lib. 😅
AppImage is great at what it does - provide an ultra-low effort packaging solution for ad-hoc app distribution that enables a developer who won't spend the time to do rpm/deb/flatpak packaging. There are obvious problems, security and otherwise, that arise if you try using it for a large software collection. But then again some people use things like Homebrew and pacstall unironically so ...
And OpenStack is a mature open source project, tried, true, used in all sorts of data centers large and small, supported by multiple vendors. I'd take it any day before 10 VC-funded guys' project. I mean good for them for skinning that cat and if it gains a real community, I might bite.