• Quazatron@lemmy.world
    link
    fedilink
    English
    arrow-up
    88
    arrow-down
    12
    ·
    2 months ago
    1. Fork a project that you have a problem with;
    2. Write a strong worded manifesto;
    3. Revel in those sweet sweet internet clicks;
    4. Try to gather a team of seasoned engineers to keep and evolve the project;
    5. Most likely fail, look for the next controversy, repeat.
    • fluxx@mander.xyz
      link
      fedilink
      English
      arrow-up
      17
      arrow-down
      2
      ·
      2 months ago

      Yes, but what’s wrong with this? If you gather engineers that are capable to maintain it - what is the downside? Systemd could always have used a bit of competition, I think most of us can agree. Most of the forks of systemd will fail, but most of all projects fail after some time. I don’t think this situation will harm systemd ultimately and it shouldn’t.

      • Quazatron@lemmy.world
        link
        fedilink
        English
        arrow-up
        14
        arrow-down
        2
        ·
        2 months ago

        There’s nothing wrong with forking a project, IF you can and intend to maintain it – hell, that’s the whole basis of FOSS.

        Forking it to make a point with no intention to maintaining it is just an easy way to gather clicks and stir drama.

        IMHO the effort is better spent fighting the politicians that are shoving this down our throats, or should we fork all the tech that gets affected by bad political decisions?