Shine Get

  • 0 Posts
  • 95 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle



  • Not to excuse the developer but I empathise with why they might have felt compelled to change the license.

    One of the biggest pains for any open source project is distributions and packagers who package the software themselves yet make changes or configure in non-standard ways which leads to major overheads for upstream as everyone submits bug reports for bugs introduced down stream and have nothing to do with them.

    I feel we, as a community, need to be more vocal about when a project has been modified from the original source for packaging or distribution (where those changes weren’t pushed upstream) to demand the project be renamed in that instance.

    I feel for these small developers who do this in their spare time and find the community forcing more work on them and damaging their reputation without any fault of the developer but someone downstream who doesn’t care not want to support what they’ve packaged.

    Perhaps there are other solutions? Before other projects decide to use awful licenses and infringe on rights just to try and tackle the problems created by downstream.










  • I’m in leadership at a place where we ship software to hundreds of millions of devices every other week and sure, it sucks to maintain legacy products, but you never sunset something without one hell of a grace period and plenty of warning. And not without feature parity if you’re rewriting to escape tech debt.

    There isn’t a valid excuse. They brought this upon themselves and their users knowingly and if they did it without knowing the consequences, that’s even more alarming.