Talk:Open-source license
Computing B‑class High‑importance | ||||||||||
|
Computing B‑class Top‑importance | ||||||||||
|
While software in the public domain may conform with the principles put forth by the open source community (assuming the source is available), this article aims to deal with licenses considered to be open source (and specifically with those approved by the Open Source Intitiative). Since public domain software is under no license, I removed it from the list. -- Stephen Gilbert
Public domain software is explicitly approved as "open source" by the OSI, and it is listed along with other licenses in their own literature, so I've put it back. --LDC
They seem to be awfully quite about PD software over at OSI. I was halfway through a response saying how I couldn't find any references to PD software on their webpage, when I came across the change history of the Open Source Definition: 1.2 – added public-domain to clause 10., and 1.4 – Now explicit about source code requirement for PD software. It isn't, however, listed on their "approved licenses" page, which threw me off. And so, your revision stands. I'll just add that the source code must be available. -- Stephen Gilbert
I think we should create a seperate page for the list because in my point of view, it seems that the list is the biggest part of the article and it seems that attention has been made to that and not the rest of the article, i suggest it becomes a list --Saint-Paddy 22:48, 25 Apr 2004 (UTC)
Comparison Link broken
When I tried the link to the comparison of open source licenses, it did not work. May be a transient error, but if it persists an alternate link should be found, or it should be removed --12.28.106.123 13:58, 27 Jul 2004 (UTC)
Solaris and open source
I've removed two references to Solaris, one because it was obsolete and the other because it wasn't clear why it was there at all.
The first was under "Non-OSI source licenses". Sun briefly had a non-OSI release of some Solaris 8 source but that's long gone. The Solaris end-user license does not confer access to source.
The second was
- Some software licenses define an open standard basis and may or may not be similar to open source, like some versions of Solaris and PGP.
If this means "source code has been released that itself defines an open standard" that doesn't fit Solaris, since Solaris is based on open standards, not the other way around. Using it as an example here also opens a can of worms as to whether Solaris itself is open source, or just shares a code base with the open-source OpenSolaris project; I don't think it's worth taking this article down that path when better examples must be available. So, I changed the line to only refer to PGP. --NapoliRoma 00:41, 13 August 2006 (UTC)
Merge into comparison of free software licences?
I just found an article which contains the content of list of FSF approved software licences and this article, and the data is even formatted nicely. Seems like a good idea to merge these two articles into comparison of free software licences. Yes, no? --Gronky 12:42, 15 November 2007 (UTC)
Creative Commons, etc?
I often wonder, and I guess many other do to, why the creative commons licenses aren't open source. I recognise that this is a page about OSI stuff, but it would be useful to have a section detailing why other major free licenses aren't approved by OSI, especially creative commons licenses. --210.14.103.34 (talk) 11:39, 6 December 2007 (UTC)
Flaw in Export Regulations Clauses
As far as I know, no much-used OS License, and only one or two OS derived licenses for government agencies or corporations, takes explicit and easily understood notice of the following situation: a U.S. based software originator transfers OS material, under an OS License, to a party in a 2nd country (neither the U.S. nor a U.S. Export Regulations proscribed country.) This 2nd party then transfers the same or modified material, still under the OS License of origin, to a 3rd party who is a resident or a citizen. The 2nd party is not constrained by U.S. Export Regulations.
A few of the much-used OS Licenses implicitly forbid this 2nd->3rd party transfer, but the language is so indirect that most 2nd parties would either miss it completely or fail to understand it.
Why would anyone care? Perhaps because the 1st party would have violated U.S. Export regulations. But to my mind more importantly: because in order to grow the OS movement and expand its scope in a productive way, some developers and OS community folks would like to engage government and corporate entities in the OS movement. These entities are not likely to come in unless they can fully satisfy U.S. Export Regulations, both because they provide static targets for litigation under those regulations, and because they are likely to believe that their own clientele and potential development contributors may wish to have, at one and the same time, the greatest freedom in their contributions, and a clear commitment that their contributions will not violate the intentions of the regulations.
For those that do care, I would appreciate any comments, or suggestions as to the minimal but easily understandable additions or edits to existing OS Licenses that would clear the flaw. Schwenn (talk) 16:34, 3 July 2008 (UTC)
- Article talk pages aren't intended for use in discussing the subject matter in itself. However, in this case I think you're mistaken. The issue is explicitly addressed by the GPL, which says that any distribution restrictions over and above those in the GPL mean a revocation of the right to use or distribute the code at all. This is why until recently any cryptographic code in free software was developed and held outwith the US. If you have further questions on this issue I'd advise you to seek expert advice. Chris Cunningham (not at work) - talk 17:23, 3 July 2008 (UTC)
Categries
I resynced the categories with the OSI (http://www.opensource.org/licenses/category). It is important to remember that we must follow their lead on the categories (if we are to categorize at all). Anything else would be original research. Superm401 - Talk 05:07, 18 March 2009 (UTC)
libpng license
The current status of the libpng license - referred to on the page as the "libpng/zlib license" is unclear because of the addition of the UCITA clause to the license around 2000. I suggest a new category is required - "modified versions of OSI approved licenses", or something like that.
Jbowler (talk) 16:25, 30 June 2009 (UTC)
Requested move
The request to rename this article to Open-source license has been carried out.
If the page title has consensus, be sure to close this discussion using {{subst:RM top|'''page moved'''.}} and {{subst:RM bottom}} and remove the {{Requested move/dated|…}} tag, or replace it with the {{subst:Requested move/end|…}} tag. |
Open source license → Open-source license — like Open-source software — Neustradamus (✉) 19:31, 11 January 2010 (UTC)
- Support. Unless it's a trade name (in which case the "s" in "source" should be capitalised), the normal English grammar rules should apply. Wikipedia is not required to use bad grammar unless it is specifically intended. That doesn't appear to be the case here. — AjaxSmack 05:09, 14 January 2010 (UTC)
- Add'l info: WP:HYPHEN notes that hyphens are used "to link related terms in compound adjectives and adverbs." This is standard English usage on both sides of the pond (e.g., see Betty Schrampfer Azar. Understanding and Using English Grammar. 2nd ed. p. 203.) The Open Source Initiative organization follows this usage when the term is used as an adjective as it is used in the titles here ("...all other programs distributed on the same medium must be open-source software.", "Therefore we forbid any open-source license from locking...") — AjaxSmack 17:41, 14 January 2010 (UTC)