# Package licenses: Contemplations and considerations

**URL:** <https://discourse.julialang.org/t/package-licenses-contemplations-and-considerations/117922>\
**Category:** Community\
**Tags:** package\
**Created:** [August 7, 2024, 2:59pm UTC](https://discourse.julialang.org/t/package-licenses-contemplations-and-considerations/117922 "2024-08-07T14:59:29Z")\
**Posts on this page:** 1\
**Showing post:** 54

<div class="post-metadata">

**Author:** ![tecosaur](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tecosaur/32/23206_2.png) [@tecosaur](https://discourse.julialang.org/u/tecosaur)\
**Post date:** [October 1, 2024, 12:55pm UTC](https://discourse.julialang.org/t/package-licenses-contemplations-and-considerations/117922/54 "2024-10-01T12:55:34Z")

</div>

As I keep on peeking at articles about software copyright online, there are a few pages I’ve come across recently that I think might be of (some) general interest.

1. The EUPL is currently a somewhat niche license (in terms of overall popularity, arguably it’s created by the largest institution to write a software license to date). Coming across [How to use the EUPL | Joinup](https://joinup.ec.europa.eu/collection/eupl/how-use-eupl), I was interested to see this bit (under "Why did the European Commission create the EUPL):

2. The [REUSE licensing model](https://reuse.software/) makes an argument for per-file license information, even when not required

3. A [blog post](https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code#why-have-the-copyright-statement) linked from a REUSE FAQ that goes into depth on what’s a good way to add file-level copyright statements, _and why_. Some key points:

---

_[View the full topic](https://discourse.julialang.org/t/package-licenses-contemplations-and-considerations/117922)._