search

oasis-open-projects / administration

OASIS OP Administrator tracking records
Other
2 stars 2 forks source link

License OSLC OP sample code under BSD-3-Clause #18

Closed berezovskyi closed 3 years ago

berezovskyi commented 3 years ago

Opening this issue to track it centrally. The original issues are filed under:

CC @chet-ensign and @jamienewlaw

berezovskyi commented 3 years ago

@jamienewlaw @chet-ensign @OASIS-OP-Admin any progress on this? Any input required from our side?

berezovskyi commented 3 years ago

@jamienewlaw @chet-ensign @OASIS-OP-Admin another reminder given that the OSLC Core spec just moved to OASIS Standard call for consent phase. We'd like to announce at least the first repo in question (reference implementation) with the OSLC Core OASIS Standard when it is published (provided a call concludes successfully, of course). Please prioritize assigning license to oslc-op/refimpl if you can. Apache license that is used by the rest of the Open Project is fine with us, whatever helps us finalize the release.

OASIS-OP-Admin commented 3 years ago

Hi Andrew - It took me some digging to catch back up. I'm going to run my reply past Jamie before I send it. I think I have misunderstood so I'm trying to lay things out logically. I'll try to get my reply to you tomorrow.

berezovskyi commented 3 years ago

Thank you!

chet-ensign commented 3 years ago

Hi Andrew,

Again, sorry for the delay. I have gone back through the tickets to sort out the issues and I think I understand now. To recap the situation:

The problem that I was having came from characterizing the request as 'dual licensing.' If I'm correct, a better way to describe the situation is that, in the code itself, you need to be able to associate the correct license with the corresponding parts of the code.

If this is correct, then I think the case for the Lyo code is resolved: the license statement that came with the code stays with the code. Anyone reading it will find it and will know - aha; this is reused code and here's the license that applies to it.

For the code that the OP is producing, it is licensed under whatever OASIS-approved license ( https://www.oasis-open.org/policies-guidelines/open-projects-process/#repository-specification-licenses) you approved to govern your work. That list includes both BSD-3 and EPL v1.0 and v2.0. The way we associate code with a license, both to advise contributors of their obligations up front, and to advise users of its terms later, is by naming the license in the codebase in a LICENSE.md file.

The issue here is that you've set those repos up without declaring a license that applies in a LICENSE.md file. Because you have a small group of contributors, you, Jim, and Jad, I think you can go back and add LICENSE.md files to the repos with their consent, declaring either EPL or BSD. To make it clear what license applies where, ideally the repo(s) should be grouped by applicable license. That's what our rules call Group Releases: https://www.oasis-open.org/policies-guidelines/open-projects-process/#releases-and-group-releases-applicable-licenses. From a rules point of view, your approved output is drawn from a group of related repos. From a user point of view, they can find each license by self-help by just finding the LICENSE.md tags.

It might be a good idea, as a courtesy, to add a statement at the top of the relevant LICENSE files stating that portions of the code are reused from the Eclipse Lyo project and their licenses apply to that code. It's not required, so long as you authors have concluded that it's OK to freely re-use that code (due to its open source licenses), but it seems like better form and more polite to give attribution.

Also, the PGB should pass a motion approving those repos as whatever license.

Declaring the repo to be x license doesn't override the Lyo license. That might have been where some of the concern came from. Whoever pulls the Lyo code into the OP repo takes the responsibility for it being OK to use in the project under its license.

To recap:

Does this address the problem?

Thanks,

/chet

On Thu, Aug 12, 2021 at 7:46 AM Andrew Berezovskyi @.***> wrote:

@jamienewlaw https://github.com/jamienewlaw @chet-ensign https://github.com/chet-ensign @OASIS-OP-Admin https://github.com/OASIS-OP-Admin another reminder given that the OSLC Core spec just moved to OASIS Standard call for consent phase. We'd like to announce at least the first repo in question (reference implementation) with the OSLC Core OASIS Standard when it is published (provided a call concludes successfully, of course). Please prioritize assigning license to oslc-op/refimpl if you can. Apache license that is used by the rest of the Open Project is fine with us, whatever helps us finalize the release.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/oasis-open-projects/administration/issues/18#issuecomment-897570884, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACYUWRNVNYLFB4EIHL4RQILT4OYAFANCNFSM4WCV53YQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

-- Chet Ensign

Chief Technical Community Steward

OASIS Open

+1 201-341-1393 <+1+201-341-1393> @.*** www.oasis-open.org

chet-ensign commented 3 years ago

Dear Chet,

Thank you for your reply. The LICENSE files were missing precisely because we were awaiting for your reply. I have now merged two license files for the Apache License v2.0 (as per OSLC OP charter) and opened two PGB ballots:

https://lists.oasis-open-projects.org/g/oslc-op-pgb/topic/ballot_to_approve_licensing/84974692?p=,,,50,0,0,0::recentpostdate%2Fsticky,,,50,2,0,84974692 https://lists.oasis-open-projects.org/g/oslc-op-pgb/topic/ballot_to_approve_licensing/84974751?p=,,,50,0,0,0::recentpostdate%2Fsticky,,,50,2,0,84974751

To be clear, we abandon the idea of dual-licensing OP code. We will consider adding a COPYING file to the repos to retain the copyright notices of the code reused by us, including Lyo (if you know a way to generate this file for all transitive dependencies of a Java project, we’ll appreciate a pointer).

Thank you all for your help!

–Andrew.

From: Chet Ensign @.> Date: Wednesday, 18 August 2021, W33 at 16:37 To: oasis-open-projects/administration @.> Cc: oasis-open-projects/administration @.>, Andrii Berezovskyi @.>, Jamie Clark @.>, Claudia Rauch @.> Subject: Re: [oasis-open-projects/administration] License OSLC OP sample code under BSD-3-Clause (#18)

Hi Andrew,

Again, sorry for the delay. I have gone back through the tickets to sort out the issues and I think I understand now. To recap the situation:

The problem that I was having came from characterizing the request as 'dual licensing.' If I'm correct, a better way to describe the situation is that, in the code itself, you need to be able to associate the correct license with the corresponding parts of the code.

If this is correct, then I think the case for the Lyo code is resolved: the license statement that came with the code stays with the code. Anyone reading it will find it and will know - aha; this is reused code and here's the license that applies to it.

For the code that the OP is producing, it is licensed under whatever OASIS-approved license (https://www.oasis-open.org/policies-guidelines/open-projects-process/#repository-specification-licenses) you approved to govern your work. That list includes both BSD-3 and EPL v1.0 and v2.0. The way we associate code with a license, both to advise contributors of their obligations up front, and to advise users of its terms later, is by naming the license in the codebase in a LICENSE.md file.

The issue here is that you've set those repos up without declaring a license that applies in a LICENSE.md file. Because you have a small group of contributors, you, Jim, and Jad, I think you can go back and add LICENSE.md files to the repos with their consent, declaring either EPL or BSD. To make it clear what license applies where, ideally the repo(s) should be grouped by applicable license. That's what our rules call Group Releases: https://www.oasis-open.org/policies-guidelines/open-projects-process/#releases-and-group-releases-applicable-licenses. From a rules point of view, your approved output is drawn from a group of related repos. From a user point of view, they can find each license by self-help by just finding the LICENSE.md tags.

It might be a good idea, as a courtesy, to add a statement at the top of the relevant LICENSE files stating that portions of the code are reused from the Eclipse Lyo project and their licenses apply to that code. It's not required, so long as you authors have concluded that it's OK to freely re-use that code (due to its open source licenses), but it seems like better form and more polite to give attribution.

Also, the PGB should pass a motion approving those repos as whatever license.

Declaring the repo to be x license doesn't override the Lyo license. That might have been where some of the concern came from. Whoever pulls the Lyo code into the OP repo takes the responsibility for it being OK to use in the project under its license.

To recap:

Does this address the problem?

Thanks,

/chet

On Thu, Aug 12, 2021 at 7:46 AM Andrew Berezovskyi @.**@.>> wrote:

@jamienewlawhttps://github.com/jamienewlaw @chet-ensignhttps://github.com/chet-ensign @OASIS-OP-Adminhttps://github.com/OASIS-OP-Admin another reminder given that the OSLC Core spec just moved to OASIS Standard call for consent phase. We'd like to announce at least the first repo in question (reference implementation) with the OSLC Core OASIS Standard when it is published (provided a call concludes successfully, of course). Please prioritize assigning license to oslc-op/refimpl if you can. Apache license that is used by the rest of the Open Project is fine with us, whatever helps us finalize the release.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/oasis-open-projects/administration/issues/18#issuecomment-897570884, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACYUWRNVNYLFB4EIHL4RQILT4OYAFANCNFSM4WCV53YQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

-- [https://drive.google.com/uc?id=1hIW4KA06CCJq7fj33aZ_yzDDDxaXDW8c]

Chet Ensign

Chief Technical Community Steward

OASIS Open

[https://cdn2.hubspot.net/hubfs/53/tools/email-signature-generator/icons/phone-icon-2x.png]

+1 201-341-1393<tel:+1+201-341-1393>

[https://cdn2.hubspot.net/hubfs/53/tools/email-signature-generator/icons/email-icon-2x.png]

@.**@.>

[https://cdn2.hubspot.net/hubfs/53/tools/email-signature-generator/icons/link-icon-2x.png]

www.oasis-open.orghttps://www.oasis-open.org