Bugzilla – Full Text Bug Listing
| Summary: | Please provide a plain text (.txt) version of the Eclipse Public License | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Andreas Sewe <sewe> | ||||
| Component: | License | Assignee: | Generic Inbox <license> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | minor | ||||||
| Priority: | P3 | CC: | bradbell, chris.guindon, janet.campbell, mike.milinkovich, mike, phoenix.ui-inbox, sharon.corbett, wayne.beaton | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
Created attachment 206796 [details]
Text version of the EPL.
I've attached a text version of the HTML document /org/documents/epl-v1.0.html
I believe that it's a reasonable text-only version of the original document, rendered with a little help from lynx:
lynx -dump epl-v10.html > epl-v10.txt
Janet, Mike: Any issue with just pushing the text version of the document? I don't think there is anything inherently wrong with a text version. But Janet will need to review this version before declaring it OK, as formatting counts when it comes to interpretation. (In reply to comment #3) > I don't think there is anything inherently wrong with a text version. But > Janet will need to review this version before declaring it OK, as formatting > counts when it comes to interpretation. I have created a python script that automatically converts the html version to a plain text version; see https://projects.coin-or.org/CppAD/browser/trunk/bin/epl_html2txt.py Perhaps this would be easier to check for correctness ? Perhaps it can be improved ? I've also hit this problem of, and found this bug about, having a TXT of EPL, in the context of http://blog2.vorburger.ch/2014/10/eclipse-public-license-enforcement-in.html (http://jira.codehaus.org/browse/MLICENSE-113), and have taken the one from http://opensource.org/licenses/eclipse-1.0.txt which is linked from https://www.eclipse.org/org/documents/epl-v10.php via http://opensource.org/licenses/eclipse-1.0.php (In reply to Mike Milinkovich from comment #3) > I don't think there is anything inherently wrong with a text version. But > Janet will need to review this version before declaring it OK, as formatting > counts when it comes to interpretation. The attached version of the document is fine. Thanks for checking. So should I post this plain text version as an additional format option on the right hand nav of https://www.eclipse.org/org/documents/epl-v10.php ? This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. (In reply to Eclipse Genie from comment #8) > This bug hasn't had any activity in quite some time. Maybe the problem got > resolved, was a duplicate of something else, or became less pressing for > some reason - or maybe it's still relevant but just hasn't been looked at > yet. > > If you have further information on the current state of the bug, please add > it. The information can be, for example, that the problem still occurs, that > you still want the feature, that more information is needed, or that the bug > is (for whatever reason) no longer relevant. > > -- > The automated Eclipse Genie. Is there a web address where one can obtain an official plan text version of the license https://www.eclipse.org/legal/epl-v10.html ? (In reply to Brad Bell from comment #9) > (In reply to Eclipse Genie from comment #8) > > This bug hasn't had any activity in quite some time. Maybe the problem got > > resolved, was a duplicate of something else, or became less pressing for > > some reason - or maybe it's still relevant but just hasn't been looked at > > yet. > > > > If you have further information on the current state of the bug, please add > > it. The information can be, for example, that the problem still occurs, that > > you still want the feature, that more information is needed, or that the bug > > is (for whatever reason) no longer relevant. > > > > -- > > The automated Eclipse Genie. > > > Is there a web address where one can obtain an official plan text version of > the license > https://www.eclipse.org/legal/epl-v10.html > ? Not that I know of. SPDX lists two HTML renditions of the license, plus providing its own [1]: One at eclipse.org and one at opensource.org. [1] <https://spdx.org/licenses/EPL-1.0.html> This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. Plain text versions of EPL-1.0 and EPL-2.0 can be found via the following URLs: https://www.eclipse.org/org/documents/epl-1.0/EPL-1.0.txt https://www.eclipse.org/org/documents/epl-2.0/EPL-2.0.txt |
Build Identifier: As far as I can see, there is not plain text (.txt) rendering of the Eclipse Public License. However, such a rendering would be useful, e.g., for being linked to from Maven POMs. Currently, many projects resort to pointing at a non-eclipse.org version of the EPL as a workaround: <license> <name>Eclipse Public License 1.0</name> <url>http://repository.jboss.org/licenses/epl-1.0.txt</url> <distribution>repo</distribution> </license> Pointing to the HTML document at <http://www.eclipse.org/legal/epl-v10.html> is not always an option; Maven's maven-project-info-reports-plugin attempts to include the resource at license/url verbatim into the output, which results in garbled HTML. Reproducible: Always