Bureaucrats, developer, Administrators
9,854
edits
Licensed deliverables: Difference between revisions
m
XML schematics can't be licensed under GFDL. Changed to GPL
No edit summary |
m (XML schematics can't be licensed under GFDL. Changed to GPL) |
||
| Line 1: | Line 1: | ||
'''[[License]]d [[deliverables]]''' are registered with [[Sourceforge]] as several projects, e.g. dividing the project into three parts to deal with [[contested term]]s. | '''[[License]]d [[deliverables]]''' are registered with [[Sourceforge]] as several projects, e.g. dividing the project into three parts to deal with [[contested term]]s. | ||
*[[XML/DTD]] and [[XML/Schema]] documented also in [[ASN.1]] for [[Minimum Message Length]] and proof that the [[Consumerium protocol]] is efficient. ''This must probably be [[ | *[[XML/DTD]] and [[XML/Schema]] documented also in [[ASN.1]] for [[Minimum Message Length]] and proof that the [[Consumerium protocol]] is efficient. ''This must probably be [[GPL]], expressing the [[glossary]] and consepts as XML tags that are undisputed. If disputed then executables and label data must be involved, and the tag must be abstracted to something not disputed, to keep [[consensus]]:'' | ||
*[[Executable]]s which implement the undisputed protocol and basic XML data model / [[schema]] / [[foundation ontology]]; Programmers sharing some list of concerns collaborate to improve the way [[Consumerium]] signals those concerns to the [[consumer]]. This may include coding for specific [[hardware device]]s or [[wireless protocol]]s. Because this code actually generates [[consumer advice]], it is [[values-sensitive]]. Knowing who can be trusted with what code, who is and is not a saboteur working for the [[producer]]s, is a key problem for which we need a [[trust model]] of some kind (this starts with "who will not break builds"). ''License must reflect this. This will likely be a [[GPL]] or some other [[viral license]] with terms added to make it easy to keep code making similar assumptions coherent and not sabotaged by those with counter values and counter assumptions, e.g. WAR FTP does not let military users exploit it, nor contribute code to it.'' Goals: 1. code that works and has well advertised assumptions 2. keep code assuming one definition of each [[contested term]] together in one module 3. prevent [[bad copy problem]] and [[self-interested fork problem]] GPL creates - but [[open source]] is worse! A specific [[Consumerium License]] from which a variant [[factionally defined]] [[consortium license]] can be derived, may be the only/ugly solution here. Of course what creates controversy in code should ideally be delegated off to: | *[[Executable]]s which implement the undisputed protocol and basic XML data model / [[schema]] / [[foundation ontology]]; Programmers sharing some list of concerns collaborate to improve the way [[Consumerium]] signals those concerns to the [[consumer]]. This may include coding for specific [[hardware device]]s or [[wireless protocol]]s. Because this code actually generates [[consumer advice]], it is [[values-sensitive]]. Knowing who can be trusted with what code, who is and is not a saboteur working for the [[producer]]s, is a key problem for which we need a [[trust model]] of some kind (this starts with "who will not break builds"). ''License must reflect this. This will likely be a [[GPL]] or some other [[viral license]] with terms added to make it easy to keep code making similar assumptions coherent and not sabotaged by those with counter values and counter assumptions, e.g. WAR FTP does not let military users exploit it, nor contribute code to it.'' Goals: 1. code that works and has well advertised assumptions 2. keep code assuming one definition of each [[contested term]] together in one module 3. prevent [[bad copy problem]] and [[self-interested fork problem]] GPL creates - but [[open source]] is worse! A specific [[Consumerium License]] from which a variant [[factionally defined]] [[consortium license]] can be derived, may be the only/ugly solution here. Of course what creates controversy in code should ideally be delegated off to: | ||