Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update ASF CLA FAQ.md #97

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update ASF CLA FAQ.md #97

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apache/license/ASF CLA FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@

提交者(Committer)必须签署 ICLA。他们以个人名义声明他们有权许可其贡献的代码。依据其雇主的所有权权益、可适用的各州和各国法律，以及其雇佣合同和业务政策的具体内容来审查提交者的 ICLA，就能发现他们是否可以就其所参与的特定项目中的任何特定提交作出该声明。

_译者注：“提交者/Committer”是由 ASF 定义的一种代码审核角色，详情请见：https://infra.apache.org/new-committers-guide.html， 而非普通意义上的代码贡献的提交者。_
_译者注：“提交者/Committer”是由 ASF 定义的一种具有提交代码和审核已提交代码权限的角色，详情请见：https://infra.apache.org/new-committers-guide.html， 而非普通意义上的代码贡献的提交者。_

提交者/ICLA 签署方可以将 CCLA 作为后备文件，以在相互冲突的法律、合同、政策和工作安排之间，消除所有的模糊之处。但我们从未要求必须这样做。许多提交者对他们在 ICLA 中的个人陈述很有信心，而许多其他提交者则认为，他们的公司用这份统括性文件来为他们自己的 ICLA 兜底能让他们放心。

Expand Down