Table of Contents

Licensing

Introduction

There are a variety of options for licensing work produced by ODM ranging from copyright (all rights reserved) to copyleft (some rights reserved, sharealike) to public domain (do what you want) each with their respective pros and cons. This document will outline some of the issues and will contain reference for discussion.

Points for consideration

Data

Data in general means information in a structured format such as CSV,JSON,XML or other information that is meant to be machine readable or can easily be inserted into a Database and where any derivative work is not generally one that the user sees as opposed to creative works.

Please make sure you read a very interesting discussion at ODbL comments from Creative Commons

Creative Works

By creative works I mean prose, graphics and other works that is generally seen directly by the user or consumer of the information.

We need to investigate what the status of a creative work is when it is derived from an odbl source, for example, a graph, map or other visualization created using odbl data.

Publications

Code

A great resource for choosing OSS license is Choosing an OSS license doesnt' need to be scary that essentially takes you through step by step.

Datahub

odm-deployment License: GPLv3

ckanext-odm_utils License: AGPLv3

ckanext-odm_theme License: AGPLv3

CKAN_PHP License: AGPLv3

ckan License: AGPLv3

Multisite front-end

wpckan License: GPLv3

Wordpress License: GPLv3

mQtranslate License: GPLv3

Library

odm-library License: TBD

Localization

odm-localization License: TBD

Trademarks

There has to be some sort of open license exception for the ODM/ODC logo, trademark and other intellectual properties. This has to be investigated especially in the context of code release where we may allow code to be used and the logo to be displayed as advertising and endorsement but in no way give up any rights to it.

References