this post was submitted on 17 Feb 2025
891 points (99.0% liked)

Linux

50579 readers
1622 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

My company's buyout has been completed, and their IT team is in the final stages of gutting our old systems and moving us on to all their infra.

Sadly, this means all my Linux and FOSS implementations I've worked on for the last year are getting shut down and ripped out this week. (They're all 100% Microsoft and proprietary junk at the new company)

I know it's dumb to feel sad about computers and software getting shut down, but it feels sucky to see all my hours of hard work getting trashed without a second thought.

That's the nature of a corpo takeover though. Just wanted to let off some steam to some folks here who I know would understand.

FOSS forever! ✊

Edit: Thanks, everybody so much for the kind words and advice!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 88 points 1 week ago (16 children)

Hoard a copy of your work. Even if your new overlords are gutting and replacing it, ot might be useful elsewhere one day.

Source: Similar situation once upon a time. I am currently using on a daily basis what was once replaced in a different company.

[–] [email protected] 77 points 1 week ago* (last edited 1 week ago) (13 children)

Please be careful when copying anything that could be considered your employer's intellectual property (almost certainly anything you built as an employee falls into this category) off of that employer's systems.

And definitely be even more careful about using one employer's IP for a new employer (neither company would be pleased to discover this).

[–] [email protected] 16 points 1 week ago (2 children)

Depends on where you work and what their policies are. My work does have many strict policies on following licenses, protecting sensitive data, etc

My solution was to MIT license and open source everything I write. It follows all policies while still giving me the flexibility to fork/share the code with any other institutions that want to run something similar.

It also had the added benefit of forcing me to properly manage secrets, gitignores, etc

[–] [email protected] 7 points 1 week ago

That seems like a good idea.

load more comments (1 replies)
load more comments (11 replies)
load more comments (13 replies)