Ticket #9549 (closed PLIP: wontfix)

Opened 6 years ago

Last modified 5 years ago

Content license policy

Reported by: dukebody Owned by:
Priority: minor Milestone: 4.x
Component: General Version:
Keywords: Cc:

Description

 http://plone.org/products/plone/roadmap/136

Plone should ship with a complete set of content licensing tools, including support for Creative Commons assignment, which allow for the selection and assignment of licenses to all content created inside of Plone on a per-object basis. Licenses should be correctly stored in the DC:Rights metatdata field, and adherence to creativecommon's best practices (their selection wizard, rdf machine readable rights declarations w/in the templates, etc) should be verified. Uniform, robust, content licensing support.

Proposed by

Jonah Bossewitch

Seconded by

Nate Aune

Proposal type

Process

Assigned to release

  • ContentLicensing

State

being-discussed

Definitions

  • Google's Advanced Search with Users Rights filtering
  • Yahoo's Flickr Creative Common's assignment and search
  • Other applications/platforms w/ CC support

Motivation

As the custodians of pre-eminent publishing platform, the Plone community has the opportunity and responsibility to take the lead on an important social justice issue that threatens culture, creativity, and democracy.

It is critically important - to the future of culture and creativity - that the IP of content be precisely managed. Content whose ownership rights need to be protected should be distinguished from content for which the owners choose to waive some of those righgs. The continuum of rights assignment should be carefully considered on any CMS. When it comes to license metadata, the sweet spot for assignment is at the point of content creation. This means CMS platforms are in a unique position (with a unique responsibility) to provide the tools for license assignment.

Now its culture, content, and creativity that are on the table, not just code. For more background, see Lessig on free culture, Benkler on Freedom in the Commons or Moglen's dotCommunist Manifesto.

Interestingly, good CC support should also translate into business opportunities within the NGO sector that Plone is targeting. If we have a compelling CC story, we have yet another differentiator between us and the commercial vendors, one which demonstrates synergy and ideological alignment between our community and many of the organizations that Plone companies are pitching and the communities that can help spread the gospel of Plone. The feature can become yet another good reason, perhaps a deciding one, for choosing Plone.

creativecommons.org has built sdk's, license selection wizards, and defined human, and machine readable formats for license information to be embedded in content. See their developers section for details.

We are already real close to being able to offer solid CC support. For Plone 3.0 we should follow through, and verify that it is well integrated and easy to enable.

Proposal

We have a stab at CC support in the collectiv PloneCreativeCommons

There have also been recent efforts to improve CC support in our outgoing RSS feeds

I think that CC licenses should actually be stored in the DC:Rights field, where they belong.

We also probably should work on a control_panel interface that allows site administrators to enable CC assignment on a per-site basis. Perhaps allowing site administrator to define a site-wide license, as opposed to allowing content authors to each select their own.

We may want to consider slightly better integration w/ CC's license selection wizard, as it appears that the current implementation redefines the licenses w/in the Tool.

We also may want to extend advanced search to allow for search according to license.

Finally, we should verify that the formats we are outputting match what CC has defined/expects.

Implementation

Forget about the PloneCreativeCommons UI. I think the best crack at this is similar to the technique that the mediawiki uses upon installation:

Except we would present this wizard in the Rights field of each object. And hopefully figure out a way not to wipe out the rest of the form submission when returning from the cc wizard.

Presumably, there would be a configuration area in the the control panel which would allow for the site administrator to assign site-wide licenses (or default licenses? Like with the discussion defualt/enabled/disabled feature), and perhaps even move the DC:Rights field from the properties tab to the main content editing tab (like DC:Subject is right now).

(sinlgle) Mediawiki installations are a breeze and it takes < 30 seconds to set one up if you have php/mysql installed. The experience is refreshing, if you have never tried it before.

CC's Web integration guide which covers the cc part of the equation, although other license designations, such as 'all rights reserved', 'public domain', 'GNU Free Documentation License' etc should also be supported.

Risks

Misconception in some circles that we are a bunch of hippies.

Misconception in other circles that we are not a bunch of hippies.

Participants

Jonah Bossewitch

Change History

comment:1 Changed 6 years ago by limi

  • Component changed from Unknown to Infrastructure
  • Milestone changed from Future to 4.x

For the record, I do think this should be implemented using the existing Rights field, similar to how Location should solve the geolocation parts.

This is mostly an issue of defining something that can fulfill the disovery needs. Anyway, shouldn't be too hard, but needs a re-think, and somebody willing to work on it. :)

comment:2 Changed 5 years ago by rossp

  • Status changed from new to closed
  • Resolution set to wontfix

PLEASE READ THIS AND RE-OPEN VALID PLIPS!

As we launch the new PLIP process we'd like to see which PLIPs:

  • are still appropriate/needed
  • still have owners/proposers/champions
  • still have available implementers

If this PLIP should still be considered for future releases of Plone please do re-open this ticket and assign an appropriate milestone. If it should be considered for the next release of Plone, use the 4.2 milestone. Also be sure to update the PLIP description, requester, owner, etc. and include a comment detailing recent progress and new plans. We will use all these details in the new continuous PLIP process.

comment:3 Changed 4 years ago by davisagli

  • Component changed from Infrastructure to General
Note: See TracTickets for help on using tickets.