News for hackers. Stuff that matters.

A comment on Pg_lakehouse: A DuckDB Alternative in Postgres. Parent comment

Re:Pg_lakehouse: A DuckDB Alternative in Postgres by swasheck on Wednesday June 12, 2024 @10:53PM (#40665445)
off-topic but i’m so licensing ignorant that each time something like this comes up i have no idea what’s being said. is there a good ELI5 resource where i can get started with licensing permissiveness?
[ Parent | on HN ]
Re:Pg_lakehouse: A DuckDB Alternative in Postgres by gavindean90 on Thursday June 13, 2024 @12:08AM (#40665844)
You can build closed source products into and on top of MIT and Apache licenses. AGPL code can’t be a part of a project unless you license everything that you write as a GPL kind of license as well.
[ Parent | on HN ]
Re:Pg_lakehouse: A DuckDB Alternative in Postgres by corytheboyd on Wednesday June 12, 2024 @10:57PM (#40665473)
I like the website GitHub put together, here’s the AGPL v3 page: https://choosealicense.com/licenses/agpl-3.0
[ Parent | on HN ]
Re:Pg_lakehouse: A DuckDB Alternative in Postgres by twelvechairs on Thursday June 13, 2024 @12:03AM (#40665813)
For an explanation in practice see below. From someone pro-AGPL seeking enforcement of the licence.

https://raymii.org/s/blog/I_enforced_the_AGPL_on_my_code_her...

[ Parent | on HN ]
Re:Pg_lakehouse: A DuckDB Alternative in Postgres by duncan-donuts on Wednesday June 12, 2024 @10:59PM (#40665487)
GNU is a good source for copyleft license info. Iirc they also address other open source licenses. https://www.gnu.org/licenses/licenses.html. Also https://choosealicense.com/ is good for some tldr info
[ Parent | on HN ]