The following issue has been updated:
Updater: Ross Gardler (mailto:ross@saafe.org)
Date: Mon, 21 Feb 2005 10:35 AM
Comment:
Reduced to Critical as this need not block the 0.7 release since we currently do not link
to any plugins with incompatible licenses.
Changes:
priority changed from Blocker to Critical
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.cocoondev.org//browse/FOR-427?page=history
---------------------------------------------------------------------
View the issue:
http://issues.cocoondev.org//browse/FOR-427
Here is an overview of the issue:
---------------------------------------------------------------------
Key: FOR-427
Summary: Need licensing element in plugins.xml
Type: Improvement
Status: Unassigned
Priority: Critical
Project: Forrest
Components:
Plugins (general issues)
Versions:
HEAD
Assignee:
Reporter: Ross Gardler
Created: Sat, 22 Jan 2005 2:31 PM
Updated: Mon, 21 Feb 2005 10:35 AM
Description:
Since plugins can be hosted on different sites they can be released under licenses other than
the Apache one. We need an element in plugins.xml that records the type of license a plugin
is released under. This element should be used by the plugin install process to verify that
the user agrees to the terms of that license before download and installation is started.
For example:
<license name="A.N.Other License" url="http://www.domain.org/licenseText"/>
would result in the user being asked to read the license at the supplied URL and then typing
yes to agree (no skips installation).
<license name="A.N.Other License">
This is the text of the license.
</license>
would result in the license text being displayed and the user being asked to agree.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|