-----Message d'origine-----
De : Discuss@... [mailto:Discuss@...] De la part de Satoshi Fujii
Envoyé : lundi 24 mai 2021 07:51
À : 'Discuss@...'
Objet : [ODL Discuss] CLA in opendaylight

Hi Team,

I'm new to OpenDaylight and am thinking of contributing to fix a bug.
Before that, I'd like to check licensing and agreements in the community.

Some of other LFN projects (e.g. ONAP, OPNFV) requires contributors to sign to CLA(Contributor License Agreements) before code submission.
In OpenDaylight, is it also required to do signing to CLA ?

and is there anything I should take a look for contribution, such as contributor guides in documentation.

Best Regards,
Satoshi

----
Satoshi Fujii (fujii-satoshi@...) FUJITSU LIMITED


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-----Original Message-----
From: guillaume.lambert@... <guillaume.lambert@...>
Sent: Wednesday, May 26, 2021 3:27 AM
To: Fujii, Satoshi/藤井 理史 <fujii-satoshi@...>; 'Discuss@...' <Discuss@...>
Subject: RE: CLA in opendaylight

Hello

Contrary to ONAP, OpenDaylight does not enforce CLA acceptance in its Gerrit web site
but proposes an equivalent directly in its technical charter, which also includes the licensing details.

You can find a copy of the OpenDaylight charter in the official website at
https://www.opendaylight.org/wp-content/uploads/sites/14/2018/01/ODL-Technical-Charter-LF-Projects-LLC-FINAL.pdf
or in the documentation at
https://docs.opendaylight.org/en/stable-silicon/_static/OpenDaylight-Technical-Charter-LFN-Projects-LLC-FINAL.pdf

Every contributor must abide by this charter and state it in the contribution process with a Developer Certificate of Origin sign-off.
http://developercertificate.org

Hope this helps

Best Regards
Guillaume

-----Message d'origine-----
De : Discuss@... [mailto:Discuss@...] De la part de Satoshi Fujii
Envoyé : lundi 24 mai 2021 07:51
À : 'Discuss@...'
Objet : [ODL Discuss] CLA in opendaylight

Hi Team,

I'm new to OpenDaylight and am thinking of contributing to fix a bug.
Before that, I'd like to check licensing and agreements in the community.

Some of other LFN projects (e.g. ONAP, OPNFV) requires contributors to sign to CLA(Contributor License Agreements) before code submission.
In OpenDaylight, is it also required to do signing to CLA ?

and is there anything I should take a look for contribution, such as contributor guides in documentation.

Best Regards,
Satoshi

----
Satoshi Fujii (fujii-satoshi@...) FUJITSU LIMITED


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.