Like many organizations, TagVault.org uses, develops and distributes source code and software. In today’s market, compliance with source code licenses and software entitlements is important. Being a technical organization and especially an organization focused on providing ease of entitlement management and member value, TagVault.org has defined policies on source code licensing.
The following details provide a high level perspective on the expectations TagVault.org has on various source code licensing issues:
- Source code developed by TagVault.org will be re-distributable to members and non-members either free, or at a cost, depending on the membership level. TagVault.org source code is developed using a license similar to the Apache 2.0 license(1). In general, members will have perpetual rights to use, reproduce, sell modify and create derivative works based on the source code in their own systems.See the TagVault.org source code license for more details.
- Member source code submitted to TagVault.org needs to be submitted under the Apache 2 license(1) to ensure flexibility of re-distribution as well as ensuring the creator of the source material has no restrictions on their use of the source code. TagVault.org does not expect to, nor does it desire to own the copyright to submitted code. TagVault.org does not currently accept source code with any other license structure.
- Utilities that are stand-alone utilities and are not integrated into any other tool, system, or distribution may be developed with the use of LGPL libraries(2).
- Utilities or modules that may be incorporated into a member’s tool, system, process or distribution will need to follow any restrictions the members put on licensing requirements.
- In all cases, for every tool, the name of the tool, module or library will be retained as will any licensing that’s applied to the item. These will be open for review by any member of TagVault.org at any time and will be published in an easily identified area on the TagVault.org web pages in the members section.
As the suite of tools and source code develops, these high level definitions of source code management may be modified. Please contact TagVault.org if you have any questions or concerns regarding these policies.
(1) Apache 2 license – this license is a flexible license that allows the entity that created the source code to retain full rights to the code, while allowing distribution of the source code to benefit the market. Organizations using source code licensed under the Apache 2 license are required to include any original copyright information, but may use the source code in any fashion they choose including incorporation of the source within commercial products. For more information, see the apache web site – http://www.apache.org/licenses/, or review the entry in Wikipedia –http://en.wikipedia.org/wiki/Apache_2_License.