Update copyright and license #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
csarven
force-pushed
the
fix/copyright-license
branch
from
255b000 to
21ebcdd
Compare
jeswr
reviewed
Nov 22, 2024
| @@ -1,6 +1,6 @@ | |||
| MIT License | |||
|
|
|||
| Copyright (c) 2023 Solid | |||
| Copyright 2023 W3C Solid Community Group | |||
There was a problem hiding this comment.
Suggested change
| Copyright 2023 W3C Solid Community Group | |
| Copyright 2024 W3C Solid Community Group |
|
@csarven Is this still relevant and up to date. @hzbarcea or @michielbdejong could you please provide a review. |
|
@jeswr , some things have changed: The template should be like https://solidproject.org/ED/protocol (because it can't be "W3C ED"). Ditto the content about the copyright and status of this document section should be same as Solid Protocol's ED, or alternatively, go in the direction of something like the Solid Protocol CG-DRAFT. I'd like to step back from this PR (since it had no activity over a year about the fundamentals). I'm sure others can handle it from here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Action of https://github.com/solid/specification/blob/main/meetings/2023-09-27.md#chat-client-client-spec-new-work-item .
Updates copyright and license. The text is based on respec's template.
Going forward we shouldn't use "Contributors" as a separate field because it is generally covered by the group - see the copyright line and CLA. Specs are the product of many contributors, so either the list is really kept up to date or don't bother. Anything more significant than a contributor is going to be an editor or an author.
(I originally borrowed Contributors idea from some W3C specs, and introduced it into WAC, which is why some of these Solid specs are re-using, but this is all in flux and there are changes in practises at W3C.)
So, for the foreseeable future, I recommend sticking to only Editor and Author roles. I suggest @hzbarcea to follow-up on #2 (as also discussed in 2023-09-27) on how specifically they want to contribute, and to please make that change in the specification in a separate PR or commit, e.g., reuse template from https://solid.github.io/notifications/protocol re Authors/Editors .
Preview | Diff