Bug 1012754 - New Feature - License Management
Summary: New Feature - License Management
Keywords:
Status: NEW
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Documentation
Version: 1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On: 809312
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-27 05:31 UTC by Matthew Casperson
Modified: 2023-02-21 23:20 UTC (History)
1 user (show)

Fixed In Version:
Clone Of: 809312
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Matthew Casperson 2013-09-27 05:31:16 UTC
A number of tags have been defined under the Common->License category. These
tags are either the names of the various licenses, as well as two special tags:
Tag Incompatibility Info and Tag Compatibility Info.

The license tags should be applied to topics as appropriate. This indicates how
the topic is licensed.

To indicate that two licenses are not compatible, create a topic with the two
license tags assigned, and then assign the Tag Incompatibility Info tag. The
presence of the Tag Incompatibility Info tag does two things: it indicates that
any other license tag assigned to the topic are incompatible with each other,
and that this topic contains information on why they are incompatible. Topic
23152 is an example of a topic that defines CC-BY-SA and GFDL as being
incompatible.

In DocBuilder there is a new licenses menu. To access it click the Pressgang
logo in the top left hand corner of the document, and select Licenses.

This menu shows two things: a list of all the licenses applied to topics in the
document (with the ability to then scroll to those topics that have the license
tags applied), and a list of any license combination that is marked as invalid
by the existence of a topic like 23152.

The spec http://docbuilder.usersys.redhat.com/21464/ has had the GFDL and
CC-BY-SA license tags assigned to it. If you view the spec in DocBuilder,
you'll see that both licenses are listed in the "Licenses Present" menu, and
that the combination of these two licenses is marked as a conflict in the
"License Conflicts" menu.

Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:


Note You need to log in before you can comment on or make changes to this bug.