-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove references to Disney. #72
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,5 @@ | ||
Copyright 2020 Disney Streaming Services | ||
Copyright 2024 respective contributors | ||
Copyright 2020-2024 Disney Streaming Services | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 👍 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd move this up to top of the file or otherwise I feel it'll never be updated. Maybe this:
Then when we update to 2025, both get updated. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why should both get updated, if the fork happens in 2024 and the Disney one never gets any contributions ever again ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree with moving the copyright up to the top so they're in pairs. This also avoids having to repeat the license fragment. Additionally, I would leave the DSS copyright backdated, for exactly the reasons @Baccata stated. Given that it's a fork, Disney has no claim on contributions made beyond that date. Regarding the Typelevel wording, I still have concerns about the "and respective contributors" bit (and all variants thereof). That's not the only reason the heading is problematic though, so these are all shades of legal gray. I understand "Typelevel" (without qualification) to refer to the broad collective of individuals who have touched the specific file, since Typelevel is no longer a legally incorporated entity nor has it established a work-for-hire arrangement with any of the constituent contributors. All of which is to say that the copyright is actually held by 1) Disney (for anything pre-fork either performed by Disney employees or covered under CLA), and 2) the individual personages who wrote the code, which makes the whole header kind of wrong unless we interpret "Typelevel" to be a way of referring to the amorphous collective loosely identified by There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for the feedback. I've moved the copyright up to the top, replaced Note that by deleting the additional License block, we're keeping to Disney Streaming's trademark edits of Section 6. Is that really something we want? I separated the two initially (and moved Disney streaming down the page) so that we could have the standard license. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah once again, this is something that we could use @djspiewak's opinion on. Daniel, the license of disneystreaming/weaver is essentially a copy of Apache 2, with an additional amendment giving some strict wording with regards to branding. This amended Apache 2 was more recently named I think generally speaking, you cannot distribute software under a less strict license than the one it was originally distributed under. That being said, the paragraph feels way overzealous. |
||
|
||
Licensed under the Apache License, Version 2.0 (the "Apache License") | ||
with the following modification; you may not use this file except in | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,7 +9,7 @@ to resurrect support for the effect types they use in repository they control. | |
|
||
You can read about the rationale for decision [here](https://github.com/disneystreaming/weaver-test/discussions/570). Feel free to ping us via a github discussion, if you seek to resurrect support for a given effect-type. | ||
|
||
If you are looking for documentation of the maintenance branch of weaver that did support other effect types, you can find it [over there](https://disneystreaming.github.io/weaver-test/docs/0.6.15/installation). | ||
If you are looking for documentation of the maintenance branch of weaver that did support other effect types, you can find it [over there](https://github.com/disneystreaming/weaver-test/blob/v0.6.15/docs/installation.md). | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Assuming the repo is archived and not deleted, we can still reference this. That said, I wonder if this portion of the docs could be removed entirely |
||
|
||
We will try to fix critical bugs on the 0.6/0.7 series, as they get found. | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think Daniel meant, "keep
Copyright 2024 Typelevel
and drop therespective contributors
part", but I don't think his firmware allows him to formulate that in a way that's not confusing to the rest of us, and my interpretation of his output stream may be wrong.So I'm referring myself to the source headers of other typelevel projects