You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by rv...@apache.org on 2023/04/05 09:26:38 UTC
[www-site] branch main updated: Adding Blue Oak Model License 1.0.0 as per LEGAL-639
This is an automated email from the ASF dual-hosted git repository.
rvs pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/www-site.git
The following commit(s) were added to refs/heads/main by this push:
new 0e4d79b58 Adding Blue Oak Model License 1.0.0 as per LEGAL-639
new 9cfbdf5ca Merge pull request #193 from rvs/main
0e4d79b58 is described below
commit 0e4d79b581494f3e072ec304995f120408cb487a
Author: Roman Shaposhnik <rv...@zededa.com>
AuthorDate: Wed Apr 5 12:25:06 2023 +0300
Adding Blue Oak Model License 1.0.0 as per LEGAL-639
Signed-off-by: Roman Shaposhnik <rv...@zededa.com>
---
content/legal/resolved.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/content/legal/resolved.md b/content/legal/resolved.md
index 94627ca7c..38eb8e25a 100644
--- a/content/legal/resolved.md
+++ b/content/legal/resolved.md
@@ -80,6 +80,7 @@ For inclusion in an Apache Software Foundation product, we consider the followin
- [The Unlicense](https://unlicense.org/)
- [Historical Permission Notice and Disclaimer](https://opensource.org/licenses/HPND)
- [Mulan Permissive Software Licenseļ¼Version 2](https://license.coscl.org.cn/MulanPSL2/)
+- [Blue Oak Model License 1.0.0](https://blueoakcouncil.org/license/1.0.0)
Many of these licenses have specific attribution terms that the project needs to adhered to, often by [adding
them to the NOTICE file](/dev/licensing-howto.html). Ensure you are doing this when including these works.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org