New Package I just wrote ~Licenses.jl~CommonLicenses.jl ! ~And I need help with naming…~ Overview I’ve found myself cutting and pasting an MIT license into my Pluto notebooks. We’ll all be writing more executable documents in 2023, so I wrote a simple package which queries https://spdx.org/licenses …

Ended up going with CommonLicenses, thanks all!

Yeah that’s definitely an option. I thought of OpenSourceLicenses, but this works for Creative Commons and other licenses too. I felt like the CC licenses are separate from software, but maybe that’s wrong?

That may be the best use for CharGPT I’ve seen. I’m terrible at naming things. Just ask my children, One and Two

So cute! But Base.eachindex is highly recommended here. :wink:

Can’t find anything wrong with “Licences”…

Yeah I now think open may be misleading .

[ANN] CommonLicenses.jl

Package Announcements

cadojo May 14, 2023, 7:26am 4

The spicy matrix has spoken, and I rather like OpenLicenses.

Topic		Replies	Views
Tooling for analysing dependency licenses Package Management	12	502	August 11, 2024
Copyright and license of Julia packages General Usage question	37	1248	July 18, 2025
[ANN] SPDX.jl: Reading and writing SPDX files Package Announcements	1	396	May 5, 2022
Package licenses: Contemplations and considerations Community package	131	4356	May 4, 2026
[ANN] SPDX.jl v0.2.0: Reading and Writing SPDX Files - Now with support for v2.3 of the specification Package Announcements	0	231	February 13, 2023

[ANN] CommonLicenses.jl

Related topics