Difference between revisions of "Information Is Free"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(Why Is Information Free?)
m (Further Reading)
 
(8 intermediate revisions by 2 users not shown)
Line 11: Line 11:
 
== Exceptions To The Rule? ==
 
== Exceptions To The Rule? ==
  
There are seemingly no exceptions to the above rule including the knowledge on how to operate a certain business software is considered Free Information. However the 2nd principle of ''[[People Are Not]]'' has consequence on the first.  
+
There are no exceptions to the above rule with respect to the publically available interfaces of the software.  This means all the knowledge on how to operate an open source application should be made available as Free Information. However the second principle, that ''[[People Are Not]]'' , does have consequences for the first.  
  
  
 
== When People Are At Stake ==
 
== When People Are At Stake ==
  
A ''transactional or accounting information'' that has private value peculiar only between private parties in transaction are considered sacred and thus succumb to the [[People Are Not]] (Free) and falls out of the purview of the first Information Is Free principle.
+
*Any ''transactional'' or ''accounting'' information that relates to private parties in their transactions must be considered sacred and thus falls out of the purview of the first ''Information Is Free'' principle.
  
Information such as a ''business practice or formula'' that is of competitive advantage for a client user falls also under the category of personal value too.
+
*Information such as a ''business practices'' or ''formulas'' that a client or user does not wish to share, perhaps believing it offers them a competitive advantage, shall also be respected as private.
  
''Security information'' that may expose a person or 'people' to harm or danger or legal threat can also be looked upon as '''not''' free information.
+
*Finally, ''Security information'' that may expose a person or people to harm, danger or legal threat can also be looked upon as '''not''' free information.
  
Such cases are considered '' 'People Data' ''.
+
Such cases are considered '' 'Private Data' ''.
  
 +
== Applying 'Private Data' ==
  
== Applying 'People Data' ==
+
When ''Private Data'' exists within an application, it should be obscured (for example by substituting "*** Password " or "*** Place Your Formula Here ") in any public communications. In contemporary programming practice using ''meta-data'' can resolve the need to hard-code such data into an application. Thus a log dump that contains such Private Data can be kept private.
 
+
When ''People Data'' exist within an application, they should be blanked out and commented such as "*** Password " or "*** Place Your Formula Here ". In contemporary programming practice using ''meta-data'' can resolve the need to hard-code such data into an application. Thus a database dump that contain such People Data can be kept private.
+
  
 
==Other Open Policies==
 
==Other Open Policies==
Any policy can be suggested by anyone but it has to be voted before it is adopted as policy. Reasons for exploring such policies is to reconcile with the prime principle of ''Open Knowledge, Open Business and Open Community'' against the 2nd principle that ''People Are Not (Open)''.
+
Anyone may suggest policies that contribute to the open source nature of this community, though only consensus will legitimate their adoption. Such policies should attempt to reconcile the primary principle of ''Open Knowledge, Open Business and Open Community'' against the secondary principle that ''People Are Not'' (free to be abused).
 
*[[Policy Towards Compiere]]
 
*[[Policy Towards Compiere]]
 
*[[Policy Towards ComPiere's Partners]]
 
*[[Policy Towards ComPiere's Partners]]
Line 36: Line 35:
 
*[[Policy Towards Investment Grants]]
 
*[[Policy Towards Investment Grants]]
 
*[[Policy Towards Internal Forks]]
 
*[[Policy Towards Internal Forks]]
 +
 +
==Commendations==
 +
*Received mention in [http://blog.sourcekibitzer.org/?p=37 SourceKibitzer Blog]
 +
 +
==Download Area==
 +
*You can gain such free information from our SourceForge Project's [http://sourceforge.net/project/showfiles.php?group_id=176962 Download section] for the [http://sourceforge.net/project/showfiles.php?group_id=176962&package_id=235962 Documentation] or [http://sourceforge.net/project/showfiles.php?group_id=176962&package_id=215056 Movies]
 +
 +
=Further Reading=
 +
*[http://www.catb.org/~esr/writings/magic-cauldron/magic-cauldron.html#toc12 The Magic Cauldron]
 +
*[http://www.productivity501.com/standing-on-shoulders-of-giants/1917/ Shoulders of Giants]
 +
 
[[Category:Community]]
 
[[Category:Community]]

Latest revision as of 01:51, 19 December 2011

This is part of the 3-line mantra propounded by Red1

 Information Is Free
 People Are Not
 Contributors Are Priceless


Why Is Information Free?

Without free information, Open Source becomes a mockery. This simple concept of Open Knowledge allows an Open Source application to achieve a greater adoption rate than otherwise, and gain the reach and brand-recognition that is well-deserved for the creators of such information and Open Source software.

Exceptions To The Rule?

There are no exceptions to the above rule with respect to the publically available interfaces of the software. This means all the knowledge on how to operate an open source application should be made available as Free Information. However the second principle, that People Are Not , does have consequences for the first.


When People Are At Stake

  • Any transactional or accounting information that relates to private parties in their transactions must be considered sacred and thus falls out of the purview of the first Information Is Free principle.
  • Information such as a business practices or formulas that a client or user does not wish to share, perhaps believing it offers them a competitive advantage, shall also be respected as private.
  • Finally, Security information that may expose a person or people to harm, danger or legal threat can also be looked upon as not free information.

Such cases are considered 'Private Data' .

Applying 'Private Data'

When Private Data exists within an application, it should be obscured (for example by substituting "*** Password " or "*** Place Your Formula Here ") in any public communications. In contemporary programming practice using meta-data can resolve the need to hard-code such data into an application. Thus a log dump that contains such Private Data can be kept private.

Other Open Policies

Anyone may suggest policies that contribute to the open source nature of this community, though only consensus will legitimate their adoption. Such policies should attempt to reconcile the primary principle of Open Knowledge, Open Business and Open Community against the secondary principle that People Are Not (free to be abused).

Commendations

Download Area

Further Reading