开源 企业版 高校版 私有云 模力方舟 AI 队友
代码拉取完成,页面将自动刷新
加入 Gitee
与超过 1400万 开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)
免费加入
已有帐号? 立即登录
main
分支 (1)
标签 (1)
main
v1.0.0
克隆/下载
克隆/下载
提示
下载代码请复制以下命令到终端执行
为确保你提交的代码身份被 Gitee 正确识别,请执行以下命令完成配置
初次使用 SSH 协议进行代码克隆、推送等操作时,需按下述提示完成 SSH 配置
1 生成 RSA 密钥
2 获取 RSA 公钥内容,并配置到 SSH公钥
在 Gitee 上使用 SVN,请访问 使用指南
使用 HTTPS 协议时,命令行会出现如下账号密码验证步骤。基于安全考虑,Gitee 建议 配置并使用私人令牌 替代登录密码进行克隆、推送等操作
Username for 'https://gitee.com': userName
Password for 'https://userName@gitee.com': # 私人令牌
新建文件 新建 Diagram 文件
新建子模块
上传文件
贡献代码
同步代码
对比差异 通过 Pull Request 同步
同步更新到分支
通过 Pull Request 同步
将会在向当前分支创建一个 Pull
Request,合入后将完成同步
提示: 由于 Git 不支持空文件夾,创建文件夹后会生成空的 .keep 文件
Loading...
README
Apache-2.0
Apache-2.0
Apache-2.0

内容可能含有违规信息

# Apache 2.0 License Migration Guide ## ✅ What Has Been Done 1. **Updated README files** - Both `README.md` and `README_zh.md` have been updated to: - Change license badge from MIT to Apache 2.0 - Add language selection links (English | 简体中文) - Update license section with Apache 2.0 requirements 2. **Replaced LICENSE file** - The MIT License has been replaced with the full Apache License 2.0 text 3. **Created NOTICE file** - Added a NOTICE file as required by Apache 2.0 ## 📋 What You Still Need to Do ### 1. Add License Headers to Source Files (Recommended) Add the following header to the top of each significant source file (`.py`, `.js`, etc.): ```python # Copyright 2025 EverMem AI # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. ``` **You can automate this using a script:** ```bash # For Python files find src -name "*.py" -type f -exec sed -i '1i\ # Copyright 2025 EverMem AI\n\ #\n\ # Licensed under the Apache License, Version 2.0 (the "License");\n\ # you may not use this file except in compliance with the License.\n\ # You may obtain a copy of the License at\n\ #\n\ # http://www.apache.org/licenses/LICENSE-2.0\n\ #\n\ # Unless required by applicable law or agreed to in writing, software\n\ # distributed under the License is distributed on an "AS IS" BASIS,\n\ # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n\ # See the License for the specific language governing permissions and\n\ # limitations under the License.\n' {} \; ``` ### 2. Update pyproject.toml Update the license field in your `pyproject.toml`: ```toml [project] license = {text = "Apache-2.0"} # or license = "Apache-2.0" ``` ### 3. Review Third-Party Dependencies Check if any of your dependencies have license conflicts with Apache 2.0: ```bash # Install pip-licenses pip install pip-licenses # Check licenses pip-licenses --format=markdown --output-file=THIRD_PARTY_LICENSES.md ``` **Important**: Some licenses (like GPL) may not be compatible with Apache 2.0. Review and ensure compatibility. ### 4. Update NOTICE File (If Needed) If you use any third-party Apache-licensed code, add attribution to the NOTICE file: ``` This product includes software developed by [Project Name] ([URL]). ``` ### 5. Create CONTRIBUTING.md (If Not Exists) Add a section about license compliance: ```markdown ## License Agreement By contributing to this project, you agree that your contributions will be licensed under the Apache License 2.0. ``` ### 6. Notify Existing Contributors (Important!) Since you're changing from MIT to Apache 2.0, it's good practice to: 1. **Post an announcement** in your repository (GitHub Discussions or Issues) 2. **Notify all previous contributors** about the license change 3. **Get explicit consent** if possible (especially if there have been significant contributions) Example announcement: ```markdown ## License Change: MIT → Apache 2.0 We're migrating from MIT License to Apache License 2.0 to provide better patent protection and clearer terms for commercial use. **What this means:** - Users must include the Apache 2.0 license text - Users must state changes made to the code - Better patent protection for users and contributors If you have contributed to this project and have concerns about this change, please comment below. ``` ### 7. Update CI/CD (If Applicable) Add license checking to your CI pipeline: ```yaml # Example for GitHub Actions - name: Check License Headers run: | # Add script to verify all source files have proper headers ``` ### 8. Update Documentation Check and update any other documentation that mentions the license: - API documentation - Developer guides - Website (if any) - Package metadata ## 🔍 Key Differences: MIT vs Apache 2.0 | Aspect | MIT | Apache 2.0 | |--------|-----|------------| | **Patent Grant** | No explicit patent grant | Explicit patent rights grant | | **Trademark** | Not addressed | Explicitly does not grant trademark rights | | **Attribution** | Simple copyright notice | Requires keeping NOTICE file and attributions | | **Changes** | No requirement to state changes | Must state significant changes made | | **Length** | Very short (~200 words) | Much longer (full legal document) | | **Compatibility** | Highly compatible | Some restrictions (not GPL compatible) | ## ✨ Benefits of Apache 2.0 1. **Patent Protection** - Explicit patent license protects users from patent claims 2. **Contributor Protection** - Clear terms for contributions 3. **Enterprise Friendly** - Preferred by many enterprises for commercial use 4. **Trademark Protection** - Protects your project name and branding 5. **Change Tracking** - Requires documentation of modifications ## ⚠️ Legal Disclaimer **I am not a lawyer.** This guide provides general information about Apache 2.0 migration. For legal advice specific to your situation, especially if: - You have significant external contributors - Your project is already widely used - You're concerned about legal implications Please consult with a qualified attorney. ## 📚 Additional Resources - [Apache License 2.0 Official Text](https://www.apache.org/licenses/LICENSE-2.0) - [Apache License FAQ](https://www.apache.org/foundation/license-faq.html) - [Choosing a License Guide](https://choosealicense.com/) - [GitHub License Help](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository) ## ✅ Checklist - [x] Updated LICENSE file - [x] Updated README files - [x] Created NOTICE file - [ ] Add license headers to source files - [ ] Update pyproject.toml - [ ] Review third-party dependencies - [ ] Update NOTICE file with third-party attributions - [ ] Notify existing contributors - [ ] Update CONTRIBUTING.md - [ ] Update CI/CD pipeline - [ ] Update all documentation - [ ] Make announcement about license change --- **Next Steps**: Review this checklist and complete the remaining items. Start with adding license headers to source files and updating pyproject.toml.
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2025 EverMem AI Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
# License Change Summary - Apache 2.0 Migration ## 📋 Overview This document summarizes the changes made to migrate EverMemOS from MIT License to Apache License 2.0. **Date**: October 28, 2025 **Previous License**: MIT License **New License**: Apache License 2.0 ## ✅ Completed Changes ### 1. Documentation Updates #### README.md (English) - ✅ Added language selection links: `English | 简体中文` - ✅ Updated license badge from MIT to Apache 2.0 - ✅ Updated license section with Apache 2.0 requirements and key conditions #### README_zh.md (Chinese) - ✅ Added language selection links: `English | 简体中文` - ✅ Updated license badge from MIT to Apache 2.0 - ✅ Updated license section with Apache 2.0 requirements (Chinese translation) ### 2. License Files #### LICENSE - ✅ Replaced MIT License text with full Apache License 2.0 text - ✅ Copyright holder: EverMem AI - ✅ Copyright year: 2025 #### NOTICE (New) - ✅ Created NOTICE file as required by Apache 2.0 - ✅ Includes project name, copyright, and basic license information ### 3. Project Configuration #### pyproject.toml - ✅ Added license field: `license = {text = "Apache-2.0"}` - ✅ Ensures package metadata reflects the new license ## 📝 Key Changes Explained ### Language Selection Links Both README files now include language selection links at the top: ```markdown <p> <a href="README.md">English</a> | <a href="README_zh.md">简体中文</a> </p> ``` This makes it easy for users to switch between English and Chinese documentation. ### License Information Updates The license sections now clearly state the Apache 2.0 requirements: **English version:** - Must include a copy of the Apache 2.0 license - Must state any significant changes made to the code - Must retain all copyright, patent, trademark, and attribution notices - If a NOTICE file is included, must include it in distribution **Chinese version (中文版本):** - 必须包含 Apache 2.0 许可证副本 - 必须声明对代码所做的重大修改 - 必须保留所有版权、专利、商标和归属声明 - 如果包含 NOTICE 文件,必须在分发时包含该文件 ## 🔄 What's Next? For additional steps you may want to take, please refer to: - **APACHE_2.0_MIGRATION_GUIDE.md** - Complete migration guide with detailed checklist Key remaining tasks: 1. Add license headers to source files (optional but recommended) 2. Review third-party dependencies for license compatibility 3. Notify existing contributors about the license change 4. Update CONTRIBUTING.md with license agreement section 5. Add license checking to CI/CD pipeline ## 📊 Impact Assessment ### For Users - **More Protection**: Explicit patent rights grant - **Clear Terms**: Better defined terms for commercial use - **Attribution**: Must include license and NOTICE file when distributing ### For Contributors - **Patent Protection**: Automatic patent license for contributions - **Clear Guidelines**: Explicit terms for contribution licensing - **Enterprise Friendly**: More acceptable in corporate environments ### For Project - **Professional**: Apache 2.0 is widely recognized in enterprise - **Patent Protection**: Protects both users and maintainers - **Trademark Protection**: Explicitly reserves trademark rights ## 🔗 References - Apache License 2.0 Full Text: https://www.apache.org/licenses/LICENSE-2.0 - Apache License FAQ: https://www.apache.org/foundation/license-faq.html - Choosing a License: https://choosealicense.com/licenses/apache-2.0/ ## ✉️ Questions? If you have questions about this license change, please: 1. Check the APACHE_2.0_MIGRATION_GUIDE.md for detailed information 2. Open an issue on GitHub 3. Contact the maintainers --- **Thank you for your understanding and support!** *This change helps ensure the long-term sustainability and legal clarity of the EverMemOS project.*
举报
举报成功
我们将于2个工作日内通过站内信反馈结果给你!
请认真填写举报原因,尽可能描述详细。
请选择举报类型
取消
发送
误判申诉

此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。

如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。

取消
提交

简介

暂无描述
暂无标签
README
Apache-2.0
使用 Apache-2.0 开源许可协议
, Apache-2.0
使用 Apache-2.0 开源许可协议
, Apache-2.0
使用 Apache-2.0 开源许可协议
取消

发行版

暂无发行版

贡献者

全部

语言

近期动态

不能加载更多了
编辑仓库简介
简介内容
主页
马建仓 AI 助手
尝试更多
代码解读
代码找茬
代码优化
1
https://gitee.com/NovemberRain/EverMemOS.git
git@gitee.com:NovemberRain/EverMemOS.git
NovemberRain
EverMemOS
EverMemOS
main
点此查找更多帮助

搜索帮助

评论
仓库举报
回到顶部
登录提示
该操作需登录 Gitee 帐号,请先登录后再操作。
立即登录
没有帐号,去注册

AltStyle によって変換されたページ (->オリジナル) /