Skip to content

Commit 595f7a7

Browse files
PooyaRakiPooyaRaki
committed
docs: update licensing information
1 parent 89c0b9b commit 595f7a7

File tree

4 files changed

+305
-2
lines changed

4 files changed

+305
-2
lines changed

‎CONTRIBUTING.md‎

Lines changed: 123 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
# Contribution Guide
2+
3+
Thank you for considering contributing to our project! We welcome contributions that align with our goals and help improve the project. To ensure that contributions are valuable and consistent, we ask that all contributors follow these guidelines.
4+
5+
---
6+
7+
## 📋 General Guidelines
8+
9+
1. **Understand the Project**
10+
Before contributing, take some time to understand the project's purpose, goals, and existing structure. Review the [README](./README.md) and other documentation.
11+
12+
2. **Respect the Code of Conduct**
13+
We are committed to maintaining a welcoming and inclusive environment.
14+
15+
3. **Check Existing Issues and Discussions**
16+
Review the [Issues](https://github.com/safe-global/safe-config-service/issues) and [Pull Requests](https://github.com/safe-global/safe-config-service/pulls) (PRs) sections before opening a new issue or starting a pull request (PR). Your idea might already be in progress or previously discussed.
17+
18+
---
19+
20+
## 🛠️ Contribution Process
21+
22+
### 1. Fork the Repository (Optional)
23+
24+
- Fork the repository to your GitHub account.
25+
- Clone your fork to your local machine.
26+
27+
### 2. Set Up Your Environment
28+
29+
- Follow the setup instructions in the [README.md](./README.md).
30+
31+
### 3. Create a New Branch
32+
33+
- Use a descriptive branch name (e.g., `feature/add-auth`, `bugfix/fix-crash`, or `docs/update-guide`).
34+
35+
### 4. Make Changes
36+
37+
- Ensure your changes are consistent with the project's coding style and standards.
38+
- Write clear and concise commit messages.
39+
40+
### 5. Test Your Changes
41+
42+
- Run all relevant tests and linters locally to ensure your changes work as expected.
43+
- Add new tests if you're introducing new functionality.
44+
45+
### 6. Open a Pull Request
46+
47+
- Go to the main repository and open a PR from your branch.
48+
- Use a clear title and provide a detailed description of your changes.
49+
- Link related issues (e.g., `Fixes #123`).
50+
- If your PR is still in progress, mark it as a draft.
51+
52+
---
53+
54+
## ⚠️ Guidelines for Pull Requests (PRs)
55+
56+
To prevent issues with PRs:
57+
58+
1. **Scope Your Changes**
59+
- Ensure each PR focuses on a single feature, bugfix, or improvement. Avoid combining unrelated changes.
60+
61+
2. **Communicate Before Major Changes**
62+
- For significant changes, open an issue first to gather feedback and ensure alignment.
63+
64+
3. **Adhere to Standards**
65+
- Follow the project’s coding style, structure, and standards.
66+
- Run all tests and ensure the build passes before submitting your PR.
67+
68+
4. **Avoid Unsolicited Large Changes**
69+
- Do not submit large-scale refactors, redesigns, or changes to critical functionality without prior discussion.
70+
71+
5. **Include Documentation**
72+
- Update documentation if your changes introduce new features or modify existing behavior.
73+
74+
---
75+
76+
## 🚩 PRs We Cannot Accept
77+
78+
To save time and maintain focus on meaningful improvements, we cannot accept PRs that:
79+
80+
- Do not align with the project's goals or roadmap.
81+
- Introduce unnecessary complexity or bloat.
82+
- Duplicate existing work or address issues already being worked on.
83+
- Include poorly tested or untested changes.
84+
- Lack meaningful context or description.
85+
- Make minor, inconsequential changes such as fixing typos, reformatting code without a functional purpose, or making stylistic adjustments that do not add value.
86+
- **Note:** If you find a typo or minor issue, please open an issue for discussion.
87+
88+
---
89+
90+
## 🧑‍🤝‍🧑 Getting Help
91+
92+
If you’re unsure about anything, don’t hesitate to ask for help! Open an issue or comment on an open one, and we’ll be happy to guide you.
93+
94+
---
95+
96+
We appreciate your contributions and effort to make this project better. Thank you for being a part of our community!
97+
98+
## Licensing & CLA
99+
100+
This repository contains code under two licensing regimes, split by a cut-over date:
101+
102+
- **Up to and including February 15, 2026**
103+
© Safe Ecosystem Foundation, licensed under the **MIT License**
104+
- **From February 17, 2026 onward**
105+
© Safe Labs GmbH, licensed under the
106+
**Functional Source License v1.1 (MIT Future License)**
107+
108+
By submitting a Pull Request, you agree that your contribution will be licensed under
109+
the regime applicable at the time your PR is merged.
110+
111+
For contributions merged on or after **February 17, 2026**, acceptance of the
112+
Safe Labs Contributor License Agreement (CLA) is required and enforced via CI.
113+
114+
For details, see:
115+
116+
- `LICENSE.md`
117+
- `NOTICE.md`
118+
119+
## Process
120+
121+
- Open an issue or Pull Request with a clear description of your change
122+
- Keep PRs focused and minimal
123+
- Follow the guidance in `README.md`

‎LICENSE‎

Lines changed: 141 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,38 @@
1-
MIT License
1+
# LICENSE
22

3-
Copyright (c) 2021 Safe Ecosystem Foundation
3+
This repository contains code developed at different points in time and under
4+
different ownership and licensing terms.
5+
6+
### A) Historical Code (up to and including February 16, 2026): MIT
7+
8+
All commits made **up to and including 2026-02-16** are:
9+
10+
- © Safe Ecosystem Foundation (SEF)
11+
- Licensed under the **MIT License**
12+
13+
A snapshot of the final SEF/MIT state is available under the Git tag:
14+
15+
- `sef-mit-final`
16+
17+
Use of the historical code is governed by the MIT License below.
18+
19+
### B) New Code (from February 17, 2026 onward): FSL-1.1-MIT (MIT Future License)
20+
21+
All commits made **on or after 2026-02-17** are:
22+
23+
- © Safe Labs GmbH
24+
- Licensed under the **Functional Source License, Version 1.1, MIT Future License** (“FSL-1.1-MIT”)
25+
26+
### No retroactive relicensing of MIT code
27+
28+
Nothing in this repository retroactively changes the MIT license terms granted by
29+
SEF for the historical code. The licensing boundary is defined solely by commit date.
30+
31+
---
32+
33+
# MIT License (SEF — historical code)
34+
35+
Copyright (c) 2022-2026 Safe Ecosystem Foundation
436

537
Permission is hereby granted, free of charge, to any person obtaining a copy
638
of this software and associated documentation files (the "Software"), to deal
@@ -19,3 +51,110 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
1951
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
2052
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
2153
SOFTWARE.
54+
55+
---
56+
57+
# Functional Source License v1.1 (MIT Future License) (Safe Labs — new code)
58+
59+
## Abbreviation
60+
61+
FSL-1.1-MIT
62+
63+
## Notice
64+
65+
Copyright `2026`, `Safe Labs GmbH`
66+
67+
## Terms and Conditions
68+
69+
### Licensor ("We")
70+
71+
The party offering the Software under these Terms and Conditions.
72+
73+
### The Software
74+
75+
The "Software" is each version of the software that we make available under
76+
these Terms and Conditions, as indicated by our inclusion of these Terms and
77+
Conditions with the Software.
78+
79+
### License Grant
80+
81+
Subject to your compliance with this License Grant and the Patents,
82+
Redistribution and Trademark clauses below, we hereby grant you the right to
83+
use, copy, modify, create derivative works, publicly perform, publicly display
84+
and redistribute the Software for any Permitted Purpose identified below.
85+
86+
### Permitted Purpose
87+
88+
A Permitted Purpose is any purpose other than a Competing Use. A Competing Use
89+
means making the Software available to others in a commercial product or
90+
service that:
91+
92+
1. substitutes for the Software;
93+
2. substitutes for any other product or service we offer using the Software
94+
that exists as of the date we make the Software available; or
95+
3. offers the same or substantially similar functionality as the Software.
96+
97+
Permitted Purposes specifically include using the Software:
98+
99+
1. for your internal use and access;
100+
2. for non-commercial education;
101+
3. for non-commercial research; and
102+
4. in connection with professional services that you provide to a licensee
103+
using the Software in accordance with these Terms and Conditions.
104+
105+
### Patents
106+
107+
To the extent your use for a Permitted Purpose would necessarily infringe our
108+
patents, the license grant above includes a license under our patents. If you
109+
make a claim against any party that the Software infringes or contributes to
110+
the infringement of any patent, then your patent license to the Software ends
111+
immediately.
112+
113+
### Redistribution
114+
115+
The Terms and Conditions apply to all copies, modifications and derivatives of
116+
the Software.
117+
118+
If you redistribute any copies, modifications or derivatives of the Software,
119+
you must include a copy of or a link to these Terms and Conditions and not
120+
remove any copyright notices provided in or with the Software.
121+
122+
### Disclaimer
123+
124+
THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR
125+
IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR
126+
PURPOSE, MERCHANTABILITY, TITLE OR NON-INFRINGEMENT.
127+
128+
IN NO EVENT WILL WE HAVE ANY LIABILITY TO YOU ARISING OUT OF OR RELATED TO THE
129+
SOFTWARE, INCLUDING INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES,
130+
EVEN IF WE HAVE BEEN INFORMED OF THEIR POSSIBILITY IN ADVANCE.
131+
132+
### Trademarks
133+
134+
Except for displaying the License Details and identifying us as the origin of
135+
the Software, you have no right under these Terms and Conditions to use our
136+
trademarks, trade names, service marks or product names.
137+
138+
## Grant of Future License
139+
140+
We hereby irrevocably grant you an additional license to use the Software under
141+
the MIT license that is effective on the second anniversary of the date we make
142+
the Software available. On or after that date, you may use the Software under
143+
the MIT license, in which case the following will apply:
144+
145+
Permission is hereby granted, free of charge, to any person obtaining a copy of
146+
this software and associated documentation files (the "Software"), to deal in
147+
the Software without restriction, including without limitation the rights to
148+
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
149+
of the Software, and to permit persons to whom the Software is furnished to do
150+
so, subject to the following conditions:
151+
152+
The above copyright notice and this permission notice shall be included in all
153+
copies or substantial portions of the Software.
154+
155+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
156+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
157+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
158+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
159+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
160+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

‎NOTICE.md‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# NOTICE — Ownership & Licensing Split (SEF → Safe Labs)
2+
3+
This repository is part of the Safe ecosystem and contains code owned and licensed
4+
under two different regimes, split by a cut-over date.
5+
6+
## 1) Up to and including 2026-02-15
7+
8+
- Owner: Safe Ecosystem Foundation (SEF)
9+
- License: MIT
10+
- Tag: `sef-mit-final` (final SEF/MIT snapshot)
11+
12+
## 2) From 2026-02-17 onward
13+
14+
- Owner: Safe Labs GmbH
15+
- License: Functional Source License v1.1 (MIT Future License) (“FSL-1.1-MIT”)
16+
17+
## Why this exists
18+
19+
Safe Ecosystem Foundation continues to steward public-good components of the Safe ecosystem.
20+
Safe Labs GmbH operates and commercially supports production-grade infrastructure and services.
21+
22+
This split is intended to provide:
23+
24+
- continued permissive availability of the historical MIT code
25+
- sustainable, security-focused development of operational services
26+
- clear terms for contributors and downstream users

‎README.md‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,3 +80,18 @@ To manually trigger the checks, run:
8080
```shell
8181
pre-commit run --all-files
8282
```
83+
84+
## Licensing
85+
86+
This repository contains code developed under two different ownership and licensing regimes, split by a defined cut-over date.
87+
88+
- **Up to and including February 16, 2026**
89+
Code is © Safe Ecosystem Foundation and licensed under the **MIT License**.
90+
The final SEF-owned MIT snapshot is tagged as: **`sef-mit-final`**
91+
- **From February 17, 2026 onward**
92+
New development is © Safe Labs GmbH and licensed under the
93+
**Functional Source License, Version 1.1 (MIT Future License)**.
94+
95+
Users who require a purely MIT-licensed codebase should base their work on the `sef-mit-final` tag. The historical MIT-licensed code remains MIT and is not retroactively relicensed.
96+
97+
For full details, see `LICENSE.md` and `NOTICE.md`.

0 commit comments

Comments
 (0)