Difference between revisions of "Liblicense"

From Creative Commons
Jump to: navigation, search
m (Reverted edits by CCID-jeremyhardin (talk) to last revision by Nathan Yergler)
 
(7 intermediate revisions by one other user not shown)
Line 11: Line 11:
 
* For a brief introduction video, check [http://blip.tv/file/1142312/ Asheesh Laroia talking about liblicense]
 
* For a brief introduction video, check [http://blip.tv/file/1142312/ Asheesh Laroia talking about liblicense]
 
* To see '''liblicense in action''' take a look at [[License tagger]], the cross platform file metadata editor.
 
* To see '''liblicense in action''' take a look at [[License tagger]], the cross platform file metadata editor.
 +
 +
== Features ==
 +
 +
* Extract and write license information for files
 +
* Supports enumeration of available licenses
 +
* Wraps internationalized license information for Creative Commons licenses
 +
* Bindings for dynamic languages (currently Python and Ruby)
 +
* Extensible support for file types using module system
 +
* No specific GUI library dependency allows applications to build the graphical chooser most appropriate for their platform.
  
 
== Future Improvements ==
 
== Future Improvements ==
Line 35: Line 44:
 
* 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 ==

Latest revision as of 20:53, 23 September 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.

Features

  • Extract and write license information for files
  • Supports enumeration of available licenses
  • Wraps internationalized license information for Creative Commons licenses
  • Bindings for dynamic languages (currently Python and Ruby)
  • Extensible support for file types using module system
  • No specific GUI library dependency allows applications to build the graphical chooser most appropriate for their platform.

Future Improvements

Architecture

System architecture.png

Liblicense Architecture - SVG

Bindings

Media

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

Download

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

See Also


Liblicense
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 }}