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!

  • Dran@lemmy.world
    link
    fedilink
    arrow-up
    16
    arrow-down
    2
    ·
    3 days ago

    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

    • folekaule@lemmy.world
      link
      fedilink
      arrow-up
      10
      arrow-down
      1
      ·
      3 days ago

      I don’t know where you are, but this isn’t always enough. If it’s your employer’s IP it’s not yours to license to begin with.

      In my situation, it even extends to any hobby projects I work on and I don’t think my situation is unusual.

      That said, most employers don’t care about hobby projects with no earning potential.