Difference between revisions of "Liblicense"

From Creative Commons
Jump to: navigation, search
Line 35: Line 35:
* Debian and Ubuntu [http://mirrors.creativecommons.org/packages/ repositories].
* Debian and Ubuntu [http://mirrors.creativecommons.org/packages/ repositories].
* Read the [[Liblicense tutorial| tutorial]].
* Read the [[Liblicense tutorial| tutorial]].
=== Developers: Using git ===
If you want to check out the source code and develop on it, use this command:
git clone git://code.creativecommons.org/liblicense.git
git submodule init
git submodule update
That should give you a working copy you can commit to.  In case you wonder: the latter two commandsfill the directories
* icons/jurisdictions
* license.rdf
* licenses
with content from external repositories similar to ''svn:externals'' for Subversion.
== More Information ==
== More Information ==

Revision as of 21:06, 27 August 2015

Description of Software Low-level license metadata integration for applications.
Bug Tracker Link to Bug Tracker
Code Repository Link to Code repository
Mailing List Link to Mailing list

What is liblicense?

liblicense provides a straight-forward way for developers to build license-aware applications. liblicense utilizes a pluggable module system for reading and writing metadata from specific file types, allowing extensibility for specific content types.

Future Improvements


System architecture.png

Liblicense Architecture - SVG



See Operating System Mockups for ideas on how liblicense could be integrated into various platforms.


More Information

See Also

Have an idea about this page? Want to help build the CC ecosystem? Check out the challenges related to Liblicense, or add one of your own below.
Open Challenges
{{#ask: Is Complete::no

Related To::Liblicense|format=table}}

Completed Challenges
{{#ask: Is Complete::yes

Related To::Liblicense|format=table}}

{{#forminput:Challenge|35 Challenge[related_to]=Liblicense }}