On Tue, May 27, 2025 at 04:10:06PM -0400, Kelly Cullinane wrote:
> An Entity CLA (eCLA) is not used for TC work so that doesn't apply here.
Now I am confused.
The text at this link:
https://cla-assistant.io/oasis-open/Open-Repo-adminStates:
OASIS Open Repositories: Individual Contributor License Agreement (CLA)
In order to contribute intellectual property into an OASIS Open
Repository, you must agree to be bound by the terms of this Agreement
("CLA"), so that it is clear what terms apply to your intellectual
property contributions. This is a license by you as an individual, for
your protection as a contributor as well as for the protection of OASIS
Open and all who use the donated material. You are required to agree to
this CLA before you contribute to an OASIS Open Repository. You can do
so by completing the online form below.
so far so good... but:
For a corporation, organization or other entity that has assigned
employees or contractors to contribute to an OASIS Open Repository, an
Entity CLA also should be used for contributing any intellectual
property owned by that entity. Signing of an Entity CLA does not remove
the need for every developer or contributor to sign their own CLA as an
individual, to cover any contributions not owned by the entity signing
the Entity CLA.
Please provide your employer's or organization's name below, if you
indicate that you are contributing material as part of your employment
or engagement with them.
and now you are saying Entity is not used for an Open Repo?
then what does this text mean?
Can it just be ignored?
> The iCLA is a bit different and will be signed when someone goes to make a pull
> request on an appropriate open repo. We have a bot that sits on the Open Repos
> that prevents the PR from going through until that iCLA is signed. There is the
> option to sign the iCLA before making a PR since some find that easier. That
> can be done by going here:
https://cla-assistant.io/thanks! That bot simply asks for email, full name, individual or
entity, and entity name.
My understanding is that as long as there is an electronic
record of CLA being signed, we are good.
Are you saying that the two paragraphs above, and the requirement to
select individual/entity and entity name, are actually moot and can
be ignored?
Thanks for the clarification.
> On Tue, May 27, 2025 at 3:43 PM Michael S. Tsirkin <
mst@redhat.com> wrote:
>
> Thank you Kelly. To make sure I understand: that text says:
>
> An Entity CLA also should be used for contributing any intellectual
> property owned by that entity.
>
> However, no link to the Entity CLA is provided.
>
>
> On Tue, May 27, 2025 at 02:46:36PM -0400, Kelly Cullinane wrote:
> > Hi Michael,
> >
> > The link you provided in your recent email (https://cla-assistant.io/
> oasis-open
> > /Open-Repo-admin) is the most current version of the CLA.
> >
> > Thank you.
> >
> > On Sat, May 24, 2025 at 6:31 AM Michael S. Tsirkin <
mst@redhat.com>
> wrote:
> >
> > On Mon, May 19, 2025 at 08:42:46AM -0400, Michael S. Tsirkin wrote:
> > > Hello!
> > >
> > > Some contribitors reach out to us to create and maintain
> > > a set of tests for virtio implementations in the framework
> > > of OASIS TC Open Repositories.
> > > However, we need to figure out the rules.
> >
> >
> > Any update here? It has been a week.
> >
> > Unless we hear otherwise we'll assume all contributors
> > agreeing to the CLA at the only available link:
> >
https://cla-assistant.io/oasis-open/Open-Repo-admin> > is sufficient.
> >
> > Thanks!
> >
> >
> > >
> > > The official rules say:
> > >
https://www.oasis-open.org/open-repositories/#licensingRules> > > Each TC Open Repository shall be subject to a Contributor License
> > Agreement (“CLA”).
> > > And CLA here is a link to:
> > >
https://www.oasis-open.org/resources/open-repositories/cla/> > >
> > > which is a dead link.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > The page here:
> > >
> > >
https://www.oasis-open.org/faq-tc-repo/> > >
> > > states:
> > >
> > >
> > > 7. Who may contribute to a TC Open Repository?
> > > Anyone who agrees to be bound by the repository’s licensing
> requirement
> > by signing the appropriate contributor licensing agreement (CLA) may
> > contribute, subject to evaluation of GitHub pull requests. The
> purpose of
> > the CLA is to confirm that each contributor is willing to grant the
> open
> > license rights associated with that repository.
> > >
> > >
> > > where "CLA" in alternatively a link to:
> > >
> > >
https://www.oasis-open.org/resources/open-repositories/cla/> individual-cla
> > >
> > > which is a dead link, or
> > >
> > >
https://cla-assistant.io/oasis-open/Open-Repo-admin> > >
> > > which is alive.
> > >
> > > There also appears to be an entity CLA link:
> > >
> > >
https://www.oasis-open.org/resources/open-repositories/cla/> entity-cla
> > >
> > > which is also a dead link.
> > >
> > >
> > >
> > > Questions:
> > >
> > >
> > >
> > >
> > > The rules state:
> > >
> > >
> > > Each person making a repo contribution must be bound to the terms
> of the
> > > CLA, by obtaining their signature (which may be an equivalent
> electronic
> > > assent) in a manner appropriate to the web resources tools employed
> to
> > > implement that repository; and those signatures shall be recorded
> and
> > > maintained in an auditable manner.
> > >
> > >
> > >
> > >
> > > Out preferred method is not github, it is email so we want to ask
> > > contributors to include a signature line together with each
> > > controbution. For example, we would display this prominently:
> > >
> > >
> > > If you agree to the CLA (text of CLA) then include the following
> > > line with your contribution:
> > >
> > >
> > > Signed-off-by: <>
> > >
> > >
> > >
> > > Also, could you please supply the text of the CLA?
> > >
> > > Would appreciate a prompt response.
> > > Thanks!
> > >
> > >
> > >
> > > --
> > > MST
> >
> >
>
>
Original Message:
Sent: 5/19/2025 8:43:00 AM
From: Michael S. Tsirkin
Subject: CLA for OASIS TC Open Repositories unavailable
Hello!
Some contribitors reach out to us to create and maintain
a set of tests for virtio implementations in the framework
of OASIS TC Open Repositories.
However, we need to figure out the rules.
The official rules say:
https://www.oasis-open.org/open-repositories/#licensingRules
Each TC Open Repository shall be subject to a Contributor License Agreement (“CLA”).
And CLA here is a link to:
https://www.oasis-open.org/resources/open-repositories/cla/
which is a dead link.
The page here:
https://www.oasis-open.org/faq-tc-repo/
states:
7. Who may contribute to a TC Open Repository?
Anyone who agrees to be bound by the repository’s licensing requirement by signing the appropriate contributor licensing agreement (CLA) may contribute, subject to evaluation of GitHub pull requests. The purpose of the CLA is to confirm that each contributor is willing to grant the open license rights associated with that repository.
where "CLA" in alternatively a link to:
https://www.oasis-open.org/resources/open-repositories/cla/individual-cla
which is a dead link, or
https://cla-assistant.io/oasis-open/Open-Repo-admin
which is alive.
There also appears to be an entity CLA link:
https://www.oasis-open.org/resources/open-repositories/cla/entity-cla
which is also a dead link.
Questions:
The rules state:
Each person making a repo contribution must be bound to the terms of the
CLA, by obtaining their signature (which may be an equivalent electronic
assent) in a manner appropriate to the web resources tools employed to
implement that repository; and those signatures shall be recorded and
maintained in an auditable manner.
Out preferred method is not github, it is email so we want to ask
contributors to include a signature line together with each
controbution. For example, we would display this prominently:
If you agree to the CLA (text of CLA) then include the following
line with your contribution:
Signed-off-by: <>
Also, could you please supply the text of the CLA?
Would appreciate a prompt response.
Thanks!
--
MST</mst@redhat.com></mst@redhat.com>