Jump to content

Talk:Licenses: Difference between revisions

1,529 bytes added ,  24 July 2003
m
Must remember to get permission from apache to modify their license
m (format)
m (Must remember to get permission from apache to modify their license)
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
* [[XML]] [[DTD]]s and [[Schema]]s are under [[GPL]]
Must remember to get permission from apache to modify their license, since it is copyrighted in itself. We wouldn't want to have a pirated license text would we ;) ?
 
:This much is true.
 
or [[LGPL]] (more licensing schemes are considered) - again viral so that no [[bad copy problem|bad copies]] or [[self-interested fork]]s can be created without us stopping them. 
 
: What the ******* rubbish troll shit is this? Can you explain 142.177.X.X??[[User:Juxo|Juxo]] 14:29 Jun 19, 2003 (EEST)
 
::Only the [[User:MotherOfTrolls]] can explain [[User:142.177.X.X]].  Until then, this one issue can be explained (below).  Trolls prefer however the term [[compost]] to "rubbish" or "shit", as their output is wholly [[organic]].
 
----
----
If you are considering any other license scheme than [[GPL]], which it said you were, [[LGPL]] must be the very next one considered, as it is viral but only to the library or schema level, i.e. does not infect anything that uses that code or library or schema at arm's length as long as it does not modify it.  [[GFDL]] is actually more like LGPL because GFDL has [[Invariant Section]]s and other [[Secondary Section]]s to which the normal viral rules don't apply.  These are like the calling code, or larger framework, that might rely on LGPL libraries.
If you are considering any other license scheme than [[GPL]], which it said you were, [[LGPL]] must be the very next one considered, as it is viral but only to the library or schema level, i.e. does not infect anything that uses that code or library or schema at arm's length as long as it does not modify it.  [[GFDL]] is actually more like LGPL because GFDL has [[Invariant Section]]s and other [[Secondary Section]]s to which the normal viral rules don't apply.  These are like the calling code, or larger framework, that might rely on LGPL libraries.
Line 22: Line 13:
It's not sourceforge nerds you need here, it's people from NGOs and charities and churches and institutes that study [[fair trade]], [[safe trade]], [[ethical investing]] and [[moral purchasing]] (especially).  Nerds want certainty, but those other groups want peace and justice.  Only you can decide who to satisfy. - trolls, eternal.
It's not sourceforge nerds you need here, it's people from NGOs and charities and churches and institutes that study [[fair trade]], [[safe trade]], [[ethical investing]] and [[moral purchasing]] (especially).  Nerds want certainty, but those other groups want peace and justice.  Only you can decide who to satisfy. - trolls, eternal.
----
----
Ok... this is brutal copy-paste from work copyrighted by OSDN, but I guess I can count on this being "fair use"


'''Changing licenses (from terms of use @ sf.net)''
One can change the license of a project later on (if it's legally possible for the license in question), but the source code released before the change will stay under the previous license.
 
:Of course, but then there's a risk of competing with improvements to that source code that stay in the old license regime, maybe bad copy problems.  There is lots of rightful social pressure against such changes as it splits community.  Also "if it's legally possible for the license in question" is critical, as it constrains one to using licenses that actually allow such changes.  Even so many are limited, like, GPL allows for successor versions of the GPL but doesn't even make it clear how to shift GPL material to LGPL.


--snip--
:For all these reasons we may be better off just changing the "Please note that..." to somehing like:


You may select a different Open Source license for your project at a later date, so long as you have the legal capability to do so, your file release clearly relates this change, and your Trove categorization is updated appropriately. It should be noted that license changes are not retroactive (i.e. you may not change the licensing terms of materials you have already released under one Open Source license).  
-----
Please note that all contributions to the Consumerium Wiki are considered to be donated without obligation to the [[Consumerim Governance Organization]] with all rights and releases.  These will be republished immediately in accord with best practices of materials under the GNU Free Documentation License, at the same URL as the material you chose to edit, within limits of our editorial and governance judgement. You are an equal participant in such judgement except for core questions which require specific legal and logistical and linguistic skill, where some expert judgement may guide the CGO in determining how best to factor and license contributions.  In that case you have input into which experts to trust, again via the CGO. Regarding your specific contribution at this moment:


--snip--
If you don't want your writing to be edited mercilessly and redistributed at will of the CGO, then don't submit it here.  Should the project disband or fail to reach agreement on [[licenses]], all material will be released under [[GFDL]] immediately.  You are also promising us that you wrote this yourself or copied it from a public domain or otherwise free resource, and that no copyright claim whatsoever, other than your own, is required to republish this material here or done it without obligation to the CGO, or for release under the GFDL with no secondary or invariant sections, no front-cover or back-cover text, and without the normal obligations to credit authorship in an obvious and visible way.  If you are contributing anonymously or pseudonymously, then in return for respect for your anonymity, you accept that we have no obligation to credit you at all.  '''DO NOT SUBMIT COPYRIGHTED WORK WITHOUT PERMISSION REGISTERED WITH THE CGO'''.
9,842

edits

We use only those cookies necessary for the functioning of the website.