hmn
/
orca
5
Fork 2
Code Issues 21 Pull Requests 1 Packages Projects Releases Wiki Activity

Licensing and copyright information #82

Merged
MartinFouilleul merged 1 commits from license_stuff into main 2023-09-11 09:11:15 +00:00
Conversation 3 Commits 1 Files Changed 120 +1924 -1154
MartinFouilleul commented 2023-09-07 15:10:00 +00:00
Collaborator
Copy Link

I added the license and fixed copyright notices in source files. The copyright notice reads:

/*************************************************************************
*
*  Orca -- A Runtime Environment for WebAssembly Applications
*  version 0.0.1
*
*  Copyright (C) 2023 Martin Fouilleul and the Orca project contributors
*  See LICENSE.txt for copyright and licensing information
*
**************************************************************************/

The license in AGPLv3, with additional terms and permissions (as provided for by section 7 of AGPLv3).

  • The first two additional terms are there to deter modified versions from presenting themselves as the original version, which is explicitly permitted by section 7, and is a good thing to have imo.
  • The third is an additional permission allowing people to distribute their orca wasm modules under the license of their choice, for the sole purpose of being loaded and run by the Orca runtime. This clears a potential concern developers might have that the AGPLv3 could require them to license their own code used in their wasm module as AGPLv3. I think at this point it is safe to have because it is a more permissive clause, but still protects the Orca code itself.

Let me know what you think or if you have any concerns with that.

I added the license and fixed copyright notices in source files. The copyright notice reads: ``` /************************************************************************* * * Orca -- A Runtime Environment for WebAssembly Applications * version 0.0.1 * * Copyright (C) 2023 Martin Fouilleul and the Orca project contributors * See LICENSE.txt for copyright and licensing information * **************************************************************************/ ``` The license in AGPLv3, with additional terms and permissions (as provided for by section 7 of AGPLv3). - The first two additional terms are there to deter modified versions from presenting themselves as the original version, which is explicitly permitted by section 7, and is a good thing to have imo. - The third is an additional permission allowing people to distribute their orca wasm modules under the license of their choice, for the sole purpose of being loaded and run by the Orca runtime. This clears a potential concern developers might have that the AGPLv3 could require them to license their own code used in their wasm module as AGPLv3. I think at this point it is safe to have because it is a more permissive clause, but still protects the Orca code itself. Let me know what you think or if you have any concerns with that.
rdunnington commented 2023-09-08 03:06:49 +00:00
Collaborator
Copy Link

I can't comment on the legal stuff since I don't have a lot of experience with licenses. In terms of the header block though, I think it could be simpler and avoid revs in the process. For example, if we went with a single-line copyright notice like:

// Copyright Martin Fouilleul and the Orca project contributors. See LICENSE for more information.

That would avoid the need for revs when/if:

  • The version revs
  • The year revs
  • The high-level description of the project changes
I can't comment on the legal stuff since I don't have a lot of experience with licenses. In terms of the header block though, I think it could be simpler and avoid revs in the process. For example, if we went with a single-line copyright notice like: `// Copyright Martin Fouilleul and the Orca project contributors. See LICENSE for more information.` That would avoid the need for revs when/if: * The version revs * The year revs * The high-level description of the project changes
MartinFouilleul commented 2023-09-08 12:21:42 +00:00
Author
Collaborator
Copy Link

Agreed for the version and high-level description. Copyright notices should include a date though. Strictly speaking, putting the notice in each file is not necessary in most jurisdictions, but it's recommended anyway (e.g. by the FSF and GNU), to make clear that the work is copyrighted. So I think we might as well put a well-formed notice.

Agreed for the version and high-level description. Copyright notices should include a date though. Strictly speaking, putting the notice in each file is not necessary in most jurisdictions, but it's recommended anyway (e.g. by the FSF and GNU), to make clear that the work is copyrighted. So I think we might as well put a well-formed notice.
👍 1
MartinFouilleul force-pushed license_stuff from a2a844517a to cae51a79c4 2023-09-10 10:43:26 +00:00 Compare
ilidemi commented 2023-09-10 11:09:22 +00:00
Collaborator
Copy Link

The license works for me and my contributions to Orca.

The license works for me and my contributions to Orca.
👍 1
MartinFouilleul force-pushed license_stuff from cae51a79c4 to 92c61d45cb 2023-09-10 11:12:16 +00:00 Compare
MartinFouilleul force-pushed license_stuff from 92c61d45cb to 06a7642055 2023-09-11 09:11:00 +00:00 Compare
MartinFouilleul merged commit 06a7642055 into main 2023-09-11 09:11:15 +00:00
MartinFouilleul deleted branch license_stuff 2023-09-11 09:11:15 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
macOS

   
windows
No Label
macOS
windows
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: hmn/orca#82
No description provided.
Delete Branch "license_stuff"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?