3 Matching Annotations
  1. Jul 2024
    1. So, what can we do? In the short term, it’s very simple. If you care about the commons, you should put your work under a strong copyleft license like the AGPL. That way, we will get back to building that commons we lost because of web services. If someone ever complains that a web service broke because of your AGPL code, reply that the whole web service should be under the AGPL too.
  2. Oct 2021
    1. I know I would love the ability to add plausible analytics. They’re a great ethical choice for site analytics.

      Looks like it's AGPL, so it would not be possible to use on write.as...

  3. Nov 2015
    1. The company refuses to expand the core development team with non-employees

      From what I've seen these projects are often licensed under the AGPL and essentially amount to "loss leader source." Community === "add on builders" and "consumers" in the minds of the product team not future "land owners."

      Be sure the project is community lead (or in transition that way at least!) before you sign that CLA...or even bother with that patch.