Discussion
Loading...

Post

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Matt "msw" Wilson
@msw@mstdn.social  ·  activity timestamp 21 hours ago

“As adoption has grown, so has our responsibility to ensure the project remains sustainable and continues to thrive. That’s why, with the release of #liquibase 5.0, we are updating the license for Liquibase Community.”

#FreeSoftware #OpenSource #FLOSS #FOSS #OSS
https://www.liquibase.com/blog/liquibase-community-for-the-future-fsl

Strengthening Liquibase Community for the Future

Liquibase Community now uses the Functional Source License (FSL). Learn what this means for developers, contributors, and enterprises, and how it protects sustainability.
  • Copy link
  • Flag this post
  • Block
J Lou
@jlou@mastodon.social replied  ·  activity timestamp 21 hours ago

@msw if I felt this was necessary, I would develop a copyfarleft license

  • Copy link
  • Flag this comment
  • Block
Matt "msw" Wilson
@msw@mstdn.social replied  ·  activity timestamp 21 hours ago

@jlou I mean, copyleft licenses were designed to provide and protect freedoms for users of software.

They were not designed to help establish a business model where a sole producer of the software has a sustainable (and exclusive) source of revenue to stay solvent.

  • Copy link
  • Flag this comment
  • Block
J Lou
@jlou@mastodon.social replied  ·  activity timestamp 21 hours ago

@Mow Sure. Software licenses should protect the inalienable rights of developers making derivative works and workers using the software in production by requiring worker cooperative structure on legal entities engaged in commercial use. Developers have the right to democratically decide the destiny of their project not have some employer manage them with no accountability to the developers and other workers. Copyfarleft is about protecting more rights not sacrificing user rights.

  • Copy link
  • Flag this comment
  • Block
Matt "msw" Wilson
@msw@mstdn.social replied  ·  activity timestamp 20 hours ago

@jlou gotcha. I’m more used to the “copyfair” banner for that movement.

There are already licenses designed for commons based peer production, supporting capitalism-rejecting cooperatives. Never seemed to get far?

https://wiki.p2pfoundation.net/Copyfarleft

Copyfarleft - P2P Foundation

  • Copy link
  • Flag this comment
  • Block
J Lou
@jlou@mastodon.social replied  ·  activity timestamp 20 hours ago

@msw Peer Production license is more of a variation of a Creative Commons license not a software license. What you need is a compatibility license that can be upgraded to AGPLv3 or a Copyfarleft license, and only allows something if one of the two will allow it and is viral. This would allow both commons to share library code. Also, the potential Copyfarleft movement should be completely against permissive licenses. An analogue of the FSF was never made to push for this idea.

  • Copy link
  • Flag this comment
  • Block
d@nny disc@ mc²
@hipsterelectron@circumstances.run replied  ·  activity timestamp 20 hours ago

@msw @jlou tends to be difficult to agree on how to best protect people whereas there's no need to be too picky about how best to exploit them

  • Copy link
  • Flag this comment
  • Block
Matt "msw" Wilson
@msw@mstdn.social replied  ·  activity timestamp 21 hours ago

@jlou anyway, they went from LGPL to Apache after feedback from users years ago.

https://forum.liquibase.org/t/lgpl-license-problematic-apache-preferred/439

  • Copy link
  • Flag this comment
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.0-rc.3.1 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login