You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
@Hainish Is the license for HTTPS Everywhere actually GPLv3, and we just need to change the text around to make that clear, or is there some actual question about the overall license?
@Hainish I would like to have at least one open issue or pull request reflecting an ongoing discussion, or at least reflecting that my concerns have not been fully addressed.
@jeremyn Per #13062 (comment) and your response there: it sounds as though you do not think an EFF lawyer's word would be authoritative here in responding to your concerns, since as you see it this is less a matter of legal compliance than of the developer experience of other potential downstreams and contributors and your take on open source citizenship norms, which are social and technical issues more than legal issues. Am I right? I want to understand so I can potentially get people with the right expertise into any future discussion (whether it's in a GitHub issue, a mailing list thread, or elsewhere).
@brainwane I'm not sure what you are asking. Staff lawyers generally oppose open source licensing and support the status quo if their client isn't facing significant legal trouble. I don't expect an EFF staff lawyer to lead an effort to clarify licensing problems for the benefit of contributors and/or downstreams.
@jeremyn let's unpack what you've just said or implied.
You've implied that, when it comes to open source licensing, EFF staff lawyers should be expected to be as reluctant to promote or approve open source licensing as lawyers at the average company or organization. I haven't had that experience, and if you have, I'd like to know.
Where I asked about finding people to participate in a discussion, you have read me as talking about who would lead an effort to address your concerns. These are different things, and I would like for you to acknowledge that.
I'm finding this particular conversation difficult for a few reasons. I would very much like to work it out with you and I think a synchronous chat (e.g., on IRC) or phone call would help me a lot, not least because I'm having trouble reading your emotional cues. I'd be happy to then sum it up and report it back to this issue. May I email you to set that up? This does not have to be something that happens frequently, in case you are concerned about setting a precedent.
@brainwane I'm still not sure what you are asking me. You mentioned whether I "think an EFF lawyer's word would be authoritative". The only time a lawyer has been involved here, that I know of, is during an in-person meeting with @Hainish mentioned at #13062 (comment), which was so superficial that they did not correct a typo in a very short file, and before I made my later, more lengthy comments. So it would be incorrect to, for example, frame this discussion as saying that I've rejected the carefully researched findings of the EFF's legal team.
I'm sure that the lawyers who choose to work at the EFF are more sympathetic toward open source than the average lawyer. However any lawyer's primary responsibility is to protect and advise their actual client. They are not going to come in here and publicly raise doubts about their client's legal position out of a general sympathy for open source or for the benefit of contributors and downstreams who are not their clients. I would be interested in any specific legal argument they want to make but I assume their general statements will be to the effect of "my client is doing, and has done, things correctly".
It's unclear what you are expecting from me at the moment. The entire discussion is visible here and in #13062 and I don't think it requires unpacking or emotional considerations. I think my concerns are readily visible from this existing discussion. I don't know who the right person is at the EFF to respond. I think the concerns I've raised are straightforward and I hope we can avoid further "meta-discussion" like we're having now.
I would like to avoid private discussions related to this. Licensing confusion affects all contributors and downstreams, so the discussion should be visible to everyone.
For your quote:
Where I asked about finding people to participate in a discussion, you have read me as talking about who would lead an effort to address your concerns. These are different things, and I would like for you to acknowledge that.
I am unclear as to the point you are making but I want to acknowledge that I have read this and do not mean to offend you by leaving out reference to it.
I've reopened this issue since the discussion is still ongoing. Please don't re-close it unless another issue is opened to replace it, or someone says clearly that the discussion is over and we shouldn't talk about it anymore.
This discussion might go more smoothly if I make it clear what I want to achieve. None of this should contradict anything I've said up to this point.
Here's how I think this project should work. None of this should be surprising or novel for a FLOSS project:
every file in the project should have an easily identifiable license and copyright holder. The identification can be done either by a statement in the file, or by the file's location in the project's structure. If there are multiple copyright holders for a file, they should be indicated clearly in that file, for example:
# Original file copyright 2010 by ABC Foundation.# Modifications copyright 2011 by the EFF.
the terms of all licenses for code included in or distributed with the project should be followed, for example adding the license text to the project, putting in copyright notices, noting modifications in some way, etc.
the licensing and copyright status for all contributions should be made clear to contributors before they release their contributions, for example, before they submit a PR.
where possible, the EFF should relicense all code it releases under a single license, for simplicity.
code released under certain "dangerous" licenses such as the Affero GPL should be moved into other repositories.
Here are some current problems:
the repository is jumbled, for example it's not clear what parts of utils/ count as "HTTPS Everywhere", or which parts are derived from the Python Software Foundation build code.
the project doesn't entirely follow the terms of other licenses, such as noting modifications as the PSF license requires, or including the MIT license for CodeMirror.
the current LICENSE.txt is vague. For example, the rulesets section says "To the extent copyright applies to the rulesets, they can be used according to GPL v2 or later." Almost everything is copyrighted, so the first clause is not appropriate. FLOSS licensing is concerned mainly with distribution, not "use", so the intention of saying a thing can be "used according to GPL v2" is perhaps legally unclear.
perhaps most seriously, the project contains many thousands of contributions from people, many anonymous, who have contributed their code under arguably unclear licensing terms. It would be impossible to contact them all to have them relicense their code and/or assign copyright to the EFF, if that turned out to be necessary.
This is all "Licensing 101" stuff that should be clear to anyone with basic knowledge of open source legalities. I should not have to keep explaining it.
The intent here is not to meet some GitHub technical requirement for displaying license text. However the GitHub requirement is such a low bar that it raises questions that we cannot meet even that.
I think clarifying licensing is a matter of respect to the thousands of hours of contributor and maintainer time that has been volunteered toward this project. I hope the EFF sees it the same way.
I don't know how to proceed because I don't know how the EFF sees this problem. If the EFF sees this as a licensing problem, then it can figure out on its own who to talk to and what work needs to be done to solve it. If it wants my advice or suggestions, it should feel free to ask me. If on the other hand, the EFF sees this as a problem with an unhappy maintainer who keeps complaining about some trivial problems, then I would prefer we just stop talking about it altogether. At this point the problems should be clear enough.
the current LICENSE.txt is vague. For example, the rulesets section says "To the extent copyright applies to the rulesets, they can be used according to GPL v2 or later." Almost everything is copyrighted, so the first clause is not appropriate. FLOSS licensing is concerned mainly with distribution, not "use", so the intention of saying a thing can be "used according to GPL v2" is perhaps legally unclear.
This is language specifically crafted by EFF lawyers. The nuance is intentional. Raw data reflecting the HTTP to HTTPS mappings of websites on the internet constitutes a data source, lacking copyright since it lacks creative arrangement. Comments and arrangement are copyrightable. Thus the nuance. Your base assumption that "almost everything is copyrighted" is substantively false.
As we've repeatedly stated, separating out every separately licensed bit of code into its own repository is practically undesirable. #6749 (comment) is the latest case in point. We've had that discussion, and I find it to have diminishing returns.
the project doesn't entirely follow the terms of other licenses, such as noting modifications as the PSF license requires, or including the MIT license for CodeMirror.
The first part of the statement is untrue. See the following:
2. Subject to the terms and conditions of this License Agreement, PSF
hereby grants Licensee a nonexclusive, royalty-free, world-wide
license to reproduce, analyze, test, perform and/or display publicly,
prepare derivative works, distribute, and otherwise use Python
alone or in any derivative version, provided, however, that PSF's
License Agreement and PSF's notice of copyright, i.e., "Copyright (c)
2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation; All Rights
Reserved" are retained in Python alone or in any derivative version
prepared by Licensee.
3. In the event Licensee prepares a derivative work that is based on
or incorporates Python or any part thereof, and wants to make
the derivative work available to others as provided herein, then
Licensee hereby agrees to include in any such work a brief summary of
the changes made to Python.
These are the only relevant notes pertaining to the PSF-licensed part of our code. Both of these are being followed, both in master and my own python3 branches.
For CodeMirror, you're probably right. The PR adding CodeMirror should have included a note about the MIT license.
I think clarifying licensing is a matter of respect to the thousands of hours of contributor and maintainer time that has been volunteered toward this project. I hope the EFF sees it the same way.
To portray developer time as disrespected is to misconstrue of the efforts so many contributors have put into this project. The licensing is clear. All the more so when it dedicates the appropriate amount to the nuance of different aspects of the project. Please don't speak for the many different contributors who have been involved in this project and have a very different experience.
Contorting our LICENSE.txt for the sake of a perceived simplicity, at the cost of nuance and against the advice of EFFs legal team, is not something that will happen. We've hashed and rehashed this conversation: this issue is closed.
Adding copyright notices to the top of individual source code files is something that can be opened in a separate issue.
@Hainish You've made some specific arguments and then made it clear you don't want to discuss this further, so I will keep this response short.
I made the CodeMirror PR ( #13560 ), which you merged. I mentioned the MIT licensing situation in my first comment in that PR ( #13560 (comment) ):
Also, as the commit message says, this almost certainly requires another update to satisfy CodeMirror's MIT license. In #13062 (comment) I discuss some concerns I have about HTTPS Everywhere's approach to licensing, so for the time being I will let someone at the EFF figure out how to handle licensing here. Please feel free to push any needed changes directly to my branch.
I still leave it to you/the EFF to make appropriate licensing updates for that.
With regards to respect and to clarity, I'm a contributor and maintainer and I reserve the right to speak for myself. If any other contributors or maintainers feel I have spoken for them inappropriately, then to them I say I'm sorry.
Activity
jeremyn commentedon Dec 26, 2016
Pinging @Hainish .
jeremyn commentedon Oct 12, 2017
@Hainish Is the license for HTTPS Everywhere actually GPLv3, and we just need to change the text around to make that clear, or is there some actual question about the overall license?
brainwane commentedon Nov 28, 2017
(Some discussion ongoing in #13062.)
Hainish commentedon Jan 31, 2018
This discussion has been superceded by that in #13062
jeremyn commentedon Jan 31, 2018
@Hainish I would like to have at least one open issue or pull request reflecting an ongoing discussion, or at least reflecting that my concerns have not been fully addressed.
brainwane commentedon Jan 31, 2018
@jeremyn Per #13062 (comment) and your response there: it sounds as though you do not think an EFF lawyer's word would be authoritative here in responding to your concerns, since as you see it this is less a matter of legal compliance than of the developer experience of other potential downstreams and contributors and your take on open source citizenship norms, which are social and technical issues more than legal issues. Am I right? I want to understand so I can potentially get people with the right expertise into any future discussion (whether it's in a GitHub issue, a mailing list thread, or elsewhere).
jeremyn commentedon Jan 31, 2018
@brainwane I'm not sure what you are asking. Staff lawyers generally oppose open source licensing and support the status quo if their client isn't facing significant legal trouble. I don't expect an EFF staff lawyer to lead an effort to clarify licensing problems for the benefit of contributors and/or downstreams.
brainwane commentedon Jan 31, 2018
@jeremyn let's unpack what you've just said or implied.
You've implied that, when it comes to open source licensing, EFF staff lawyers should be expected to be as reluctant to promote or approve open source licensing as lawyers at the average company or organization. I haven't had that experience, and if you have, I'd like to know.
Where I asked about finding people to participate in a discussion, you have read me as talking about who would lead an effort to address your concerns. These are different things, and I would like for you to acknowledge that.
I'm finding this particular conversation difficult for a few reasons. I would very much like to work it out with you and I think a synchronous chat (e.g., on IRC) or phone call would help me a lot, not least because I'm having trouble reading your emotional cues. I'd be happy to then sum it up and report it back to this issue. May I email you to set that up? This does not have to be something that happens frequently, in case you are concerned about setting a precedent.
jeremyn commentedon Jan 31, 2018
@brainwane I'm still not sure what you are asking me. You mentioned whether I "think an EFF lawyer's word would be authoritative". The only time a lawyer has been involved here, that I know of, is during an in-person meeting with @Hainish mentioned at #13062 (comment), which was so superficial that they did not correct a typo in a very short file, and before I made my later, more lengthy comments. So it would be incorrect to, for example, frame this discussion as saying that I've rejected the carefully researched findings of the EFF's legal team.
I'm sure that the lawyers who choose to work at the EFF are more sympathetic toward open source than the average lawyer. However any lawyer's primary responsibility is to protect and advise their actual client. They are not going to come in here and publicly raise doubts about their client's legal position out of a general sympathy for open source or for the benefit of contributors and downstreams who are not their clients. I would be interested in any specific legal argument they want to make but I assume their general statements will be to the effect of "my client is doing, and has done, things correctly".
It's unclear what you are expecting from me at the moment. The entire discussion is visible here and in #13062 and I don't think it requires unpacking or emotional considerations. I think my concerns are readily visible from this existing discussion. I don't know who the right person is at the EFF to respond. I think the concerns I've raised are straightforward and I hope we can avoid further "meta-discussion" like we're having now.
I would like to avoid private discussions related to this. Licensing confusion affects all contributors and downstreams, so the discussion should be visible to everyone.
For your quote:
I am unclear as to the point you are making but I want to acknowledge that I have read this and do not mean to offend you by leaving out reference to it.
jeremyn commentedon Feb 2, 2018
I've reopened this issue since the discussion is still ongoing. Please don't re-close it unless another issue is opened to replace it, or someone says clearly that the discussion is over and we shouldn't talk about it anymore.
This discussion might go more smoothly if I make it clear what I want to achieve. None of this should contradict anything I've said up to this point.
Here's how I think this project should work. None of this should be surprising or novel for a FLOSS project:
the terms of all licenses for code included in or distributed with the project should be followed, for example adding the license text to the project, putting in copyright notices, noting modifications in some way, etc.
the licensing and copyright status for all contributions should be made clear to contributors before they release their contributions, for example, before they submit a PR.
where possible, the EFF should relicense all code it releases under a single license, for simplicity.
code released under certain "dangerous" licenses such as the Affero GPL should be moved into other repositories.
Here are some current problems:
the repository is jumbled, for example it's not clear what parts of
utils/count as "HTTPS Everywhere", or which parts are derived from the Python Software Foundation build code.the project doesn't entirely follow the terms of other licenses, such as noting modifications as the PSF license requires, or including the MIT license for CodeMirror.
the current
LICENSE.txtis vague. For example, the rulesets section says "To the extent copyright applies to the rulesets, they can be used according to GPL v2 or later." Almost everything is copyrighted, so the first clause is not appropriate. FLOSS licensing is concerned mainly with distribution, not "use", so the intention of saying a thing can be "used according to GPL v2" is perhaps legally unclear.perhaps most seriously, the project contains many thousands of contributions from people, many anonymous, who have contributed their code under arguably unclear licensing terms. It would be impossible to contact them all to have them relicense their code and/or assign copyright to the EFF, if that turned out to be necessary.
This is all "Licensing 101" stuff that should be clear to anyone with basic knowledge of open source legalities. I should not have to keep explaining it.
The intent here is not to meet some GitHub technical requirement for displaying license text. However the GitHub requirement is such a low bar that it raises questions that we cannot meet even that.
I think clarifying licensing is a matter of respect to the thousands of hours of contributor and maintainer time that has been volunteered toward this project. I hope the EFF sees it the same way.
I don't know how to proceed because I don't know how the EFF sees this problem. If the EFF sees this as a licensing problem, then it can figure out on its own who to talk to and what work needs to be done to solve it. If it wants my advice or suggestions, it should feel free to ask me. If on the other hand, the EFF sees this as a problem with an unhappy maintainer who keeps complaining about some trivial problems, then I would prefer we just stop talking about it altogether. At this point the problems should be clear enough.
Hainish commentedon Feb 6, 2018
This is language specifically crafted by EFF lawyers. The nuance is intentional. Raw data reflecting the HTTP to HTTPS mappings of websites on the internet constitutes a data source, lacking copyright since it lacks creative arrangement. Comments and arrangement are copyrightable. Thus the nuance. Your base assumption that "almost everything is copyrighted" is substantively false.
As we've repeatedly stated, separating out every separately licensed bit of code into its own repository is practically undesirable. #6749 (comment) is the latest case in point. We've had that discussion, and I find it to have diminishing returns.
The first part of the statement is untrue. See the following:
These are the only relevant notes pertaining to the PSF-licensed part of our code. Both of these are being followed, both in
masterand my ownpython3branches.For CodeMirror, you're probably right. The PR adding CodeMirror should have included a note about the MIT license.
To portray developer time as disrespected is to misconstrue of the efforts so many contributors have put into this project. The licensing is clear. All the more so when it dedicates the appropriate amount to the nuance of different aspects of the project. Please don't speak for the many different contributors who have been involved in this project and have a very different experience.
Contorting our
LICENSE.txtfor the sake of a perceived simplicity, at the cost of nuance and against the advice of EFFs legal team, is not something that will happen. We've hashed and rehashed this conversation: this issue is closed.Adding copyright notices to the top of individual source code files is something that can be opened in a separate issue.
jeremyn commentedon Feb 6, 2018
@Hainish You've made some specific arguments and then made it clear you don't want to discuss this further, so I will keep this response short.
I made the CodeMirror PR ( #13560 ), which you merged. I mentioned the MIT licensing situation in my first comment in that PR ( #13560 (comment) ):
I still leave it to you/the EFF to make appropriate licensing updates for that.
With regards to respect and to clarity, I'm a contributor and maintainer and I reserve the right to speak for myself. If any other contributors or maintainers feel I have spoken for them inappropriately, then to them I say I'm sorry.