You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/02/08 16:35:00 UTC
[jira] [Comment Edited] (LEGAL-601) Can we host examples under MIT license?
[ https://issues.apache.org/jira/browse/LEGAL-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488989#comment-17488989 ]
Kenneth Knowles edited comment on LEGAL-601 at 2/8/22, 4:34 PM:
----------------------------------------------------------------
Yes [~jochen@apache.org] we are deliberately making things more difficult for ourselves :-). The intent is to simplify it for our users. There are certainly differences between ASL2 and MIT. Most notably section 4 "redistribution" items (b) and (d).
(b) "You must cause any modified files to carry prominent notices stating that You changed the files". It is perhaps minor for us to ask users to have their files carry prominent notices stating they modified them. But it is also quite pointless. I expect compliance with this requirement to be pretty rare.
(d) [~jmclean] my mistake capitalizing NOTICE and thanks for the clarification. Yes, we could (and perhaps must) include a NOTICE file in the template repo, and a user would only have to modify it if they needed one for their own purposes anyhow.
It seems that the consensus here is similar to my initial point on the linked thread: it will be a bureaucratic pain to do anything out of the ordinary, maybe not worth the trouble for making things slightly better for those few users who are aware of the additional requirements of the ASL2.
was (Author: kenn):
Yes [~jochen@apache.org] we are deliberately making things more difficult for ourselves :-). The intent is to simplify it for our users. There are certainly differences between ASL2 and MIT. Most notably section 4 "redistribution" items (b) and (d).
(b) "You must cause any modified files to carry prominent notices stating that You changed the files". It is perhaps minor for us to ask users to have their files carry prominent notices stating they modified them. But it is also quite pointless. I expect compliance with this requirement to be pretty rare.
(d) [~jmclean] my mistake capitalizing NOTICE and thanks for the clarification. Yes, we could (and perhaps must) include a NOTICE file in the template repo, and a user would only have to modify it if they needed one for their own purposes anyhow.
It seems that the consensus here is similar to my initial point on the linked thread: it will be a bureaucratic pain to do anything out of the ordinary.
> Can we host examples under MIT license?
> ---------------------------------------
>
> Key: LEGAL-601
> URL: https://issues.apache.org/jira/browse/LEGAL-601
> Project: Legal Discuss
> Issue Type: Question
> Reporter: Kenneth Knowles
> Priority: Major
>
> Context: Beam intends to host "just clone and go" repositories as examples for users to start with (https://lists.apache.org/thread/x16ykz3lrtc48sgo4m7sxgjlyp1y1ffl)
> Question: Since the purpose of these repos is not to be distributed software as part of our releases, but for users to download and modify, we wondered if MIT license (or similar) could be used (https://lists.apache.org/thread/krncccn7dbzgcgc91cg1t1793rvjtwhs)
> Related: We haven't discussed whether the examples are to be archived via any release process or not. Any perspective on this general area would be appreciated.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org