Skip to content

Commit aaaa292

Browse files
committed
Add ADR002: Use CC BY-SA 4.0 License
1 parent 8fd2c2a commit aaaa292

File tree

1 file changed

+48
-0
lines changed

1 file changed

+48
-0
lines changed
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
# 2. Use CC BY-SA 4.0 License
2+
3+
Date: 2025-11-25
4+
5+
## Status
6+
7+
Accepted
8+
9+
## Context
10+
11+
We need to choose an appropriate license for this architecture documentation repository. The documentation will contain:
12+
- Architecture Decision Records (ADRs)
13+
- Process documentation
14+
- Technical governance guidelines
15+
- Standards and best practices
16+
17+
The license should:
18+
- Allow others to learn from and adapt our architectural decisions
19+
- Ensure that derivative works remain open and accessible
20+
- Require attribution to SciLifeLab
21+
- Be compatible with collaborative development via GitHub issues and pull requests
22+
23+
## Decision
24+
25+
We will use the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license for this repository.
26+
27+
## Consequences
28+
29+
### Positive
30+
31+
- **Share-alike provision**: Any derivative works must be distributed under the same or compatible license, ensuring the documentation remains open
32+
- **Attribution requirement**: Users must give appropriate credit, which helps maintain visibility of SciLifeLab's contributions
33+
- **Wide adoption**: CC BY-SA 4.0 is widely recognized and understood in the open-source community (used by Wikipedia and many documentation projects)
34+
- **Flexibility**: Others can freely use, adapt, and build upon our architectural decisions while keeping them accessible
35+
- **Non-software focus**: CC licenses are specifically designed for creative works and documentation, making them more appropriate than software licenses (MIT, GPL, etc.)
36+
37+
### Negative
38+
39+
- **Not suitable for code**: Any code examples should be licensed separately under a software license
40+
- **Compatibility considerations**: Share-alike requirement may limit how others can combine our documentation with other licensed content
41+
- **No warranty disclaimer**: Users should be aware that architectural decisions are provided "as-is" without guarantees of suitability
42+
43+
### Neutral
44+
45+
- The license file (LICENSE) has been added to the repository root
46+
- A license badge and information have been added to the README
47+
- Future code repositories may need different licenses (e.g., MIT, Apache 2.0) appropriate for software
48+

0 commit comments

Comments
 (0)