Fellowship Hacks » Projects » Blog » License

License for blog posts

This task is part of the FellowshipHacks/Projects/Blog project.

Goal

In EZ, each blog post can be assigned a license statement; in WP there are different plugins to manage license of content. We have to choose the best plugin and set up a procedure to migrate license information from EZ to WP.

People

People working on this task.

Volunteers are always welcome! Have a look at FellowshipHacks to know how you can help

Status

Last updated on: 090118

We have extracted license data from EZ; we have to select the WP license plugin to use and write the corresponding data migration procedure.

Subtasks

TODO

  • Test this Per Post Creative Commons License plugin (thanks Giacomo) and compare it to the "Progressive license" plugin (see below)

  • If no other plugins are available, choose the best existing plugin
  • Set up a data migration procedure

DONE

  • Set #Requirements for plugins

  • Extract license information from EZ. Done as part of the content migration task.

Notes

Requirements

  • Compatibility with WPMU
  • Support for per-post license (not only per-blog)
  • Support for licenses present in EZ (GNU GPL/FDL, CC free licenses, public domain), or easy to add.
  • Minimal impact on WPMU database

Potentially useful plugins

  • Progressive license plugin: http://wordpress.org/extend/plugins/progressive-license/

    • Only per-blog
    • Tested

    • attitude: So long, Progressive license plugin seems to be the closest to what we need. I managed to hack it and add additional licences by default, but only problem we have with it is that it doesn't allow changing license per post. It can assign license image to every post though. I will investigate further on this, and report here. We should also check how hard we need a possibility for licensing per post since I assume that the most of bloggers chose one license. Oh yes, this plugin gives possibility for making time periods, in other words, one license can last for some time and than gets replaced by another. Example: http://blogs.fsfe.org/attitude/

    • cri: I've noticed that the RSS-imported posts don't get the license chosen in the plugin, unless one select a license in the admin panel "If all licenses expire use this license: "; this could be useful: we could easily append the original EZ license to imported posts, and use the new per-blog license only for future posts.

Other per-blog license plugins

Other (not useful)

CategoryFellowshipHacksTasks