[jira] Updated: (FOR-427) Need licensing element in plugins.xml
[ http://issues.apache.org/jira/browse/FOR-427?page=all ] Ross Gardler updated FOR-427: - Fix Version: (was: 0.8-dev) 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. was: 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. Environment: > Need licensing element in plugins.xml > - > > Key: FOR-427 > URL: http://issues.apache.org/jira/browse/FOR-427 > Project: Forrest > Type: Improvement > Components: Plugins (general issues) > Versions: 0.7 > Reporter: Ross Gardler > Priority: Critical > > 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-427) Need licensing element in plugins.xml
The following issue has been updated: Updater: David Crossley (mailto:[EMAIL PROTECTED]) Date: Thu, 14 Apr 2005 9:00 PM Comment: Schedule for 0.8 and tidy the Description. Changes: description changed from 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: 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). This is the text of the license. would result in the license text being displayed and the user being asked to agree. to 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. Fix Version changed to 0.8 - 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) Fix Fors: 0.8 Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Sat, 22 Jan 2005 2:31 PM Updated: Thu, 14 Apr 2005 9:00 PM 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. - 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
[JIRA] Updated: (FOR-427) Need licensing element in plugins.xml
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) 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: 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). This is the text of the 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
