| 2009-02-24 19:44:09 |
Karl Fogel |
description |
(This request results from a thread with kiko, joey, mrevell, bac, kfogel, which in turn followed from bug #332160.)
We'd like to redo the choose-a-license area on the project creation page.
It's getting long (21 licenses!), and now we need to add some new CC licenses. So let's shunt the more exotic licenses off into a separate block that people only see if they can't find the license they want on the main page. The guiding principle here is:
"Launchpad should accept any license that we know is open source, but we should try to steer people toward the common ones."
So now the main project-creation page would offer these options:
"We strongly recommend one of the following licenses:
GNU GPL version 3
GNU Affero GPL version 3
BSD (revised)
MIT / X License
GNU GPL version 2
GNU LGPL version 2.1
GNU LGPLv3
Apache 2.0
Public Domain / Creative Commons 0
[then slightly separated from the above list come these two options, which presumably open up into an AJAX-y panel or something]:
Other open source licenses...
Proprietary license...
* "More open source licenses..." would offer the remaining open source licenses (taken from our current list):
Academic Free License
Artistic License
Common Public License
Eclipse Public License
Educational Community License
Mozilla Public License
Open Software License
Perl License
PHP License
Python License
Zope Public License
Plus these two new ones:
Creative Commons Attribution (for non-software projects)
Creative Commons Attribution-ShareAlike (for non-software projects)
Plus a final escape hatch in case the needed license isn't listed:
Other: [text field to enter info about other open source license]
* "Proprietary license..." would steer you in the right direction for that (our offering for private and/or proprietary projects is a work-in-progress right now, I think Brad knows more)
I will update https://help.launchpad.net/Legal/ProjectLicensing to talk about how non-software projects are okay (that's what bug #332160 was originally about).
Regarding UI:
Obviously, let the force flow within you and do what you think is right :-). Joey Stanford had some ideas:
"..., if the project is a doc or a website which is under GFDL or CC, that should also be on that [second] licensing page. An AJAX choice box there would make that transition either: if project then show project licenses, elseif doc then show doc licenses."
In reply, I said:
"Didn't quite understand that... (we don't have a 'project type' field right now, AFAICT.)"
Joey responded:
"I'm thinking about how the ajax screen would flow. Instead of having the project and doc licenses mixed, we could simply separate them onto two different panels."
One final note: I've left GFDL (the GNU Free Documentation License) off the list for now, considering it such a mess that I want to relegate it to the "other" box. However, if we get a lot of requests for it, we can add it to the list. |
(This request results from a thread with kiko, joey, mrevell, bac, kfogel, which in turn followed from bug #332160.)
We'd like to redo the choose-a-license area on the project creation page.
It's getting long (21 licenses!), and now we need to add some new CC licenses. So let's shunt the more exotic licenses off into a separate block that people only see if they can't find the license they want on the main page. The guiding principle here is:
"Launchpad should accept any license that we know is open source, but we should try to steer people toward the common ones."
So now the main project-creation page would offer these options:
"We strongly recommend one of the following licenses:
GNU GPL version 3
GNU Affero GPL version 3
BSD (revised)
MIT / X License
GNU GPL version 2
GNU LGPL version 2.1
GNU LGPLv3
Apache 2.0
Public Domain / Creative Commons 0
[then slightly separated from the above list come these two options, which presumably open up into an AJAX-y panel or something]:
Other open source licenses...
Proprietary license...
* "More open source licenses..." would offer the remaining open source licenses (taken from our current list):
Academic Free License
Artistic License
Common Public License
Eclipse Public License
Educational Community License
Mozilla Public License
Open Software License
Perl License
PHP License
Python License
Zope Public License
Plus these two new ones:
Creative Commons Attribution (for non-software projects)
Creative Commons Attribution-ShareAlike (for non-software projects)
Plus a final escape hatch in case the needed license isn't listed:
Other: [text field to enter info about other open source license]
* "Proprietary license..." would steer you in the right direction for that (our offering for private and/or proprietary projects is a work-in-progress right now, I think Brad knows more)
I will update https://help.launchpad.net/Legal/ProjectLicensing to talk about how non-software projects are okay (that's what bug #332160 was originally about).
Regarding UI:
Obviously, let the force flow within you and do what you think is right :-). Joey Stanford had some ideas:
"..., if the project is a doc or a website which is under GFDL or CC, that should also be on that [second] licensing page. An AJAX choice box there would make that transition either: if project then show project licenses, elseif doc then show doc licenses."
In reply, I said:
"Didn't quite understand that... (we don't have a 'project type' field right now, AFAICT.)"
Joey responded:
"I'm thinking about how the ajax screen would flow. Instead of having the project and doc licenses mixed, we could simply separate them onto two different panels."
One final note: I've left GFDL (the GNU Free Documentation License) off the list for now, as it's really several licenses that offer different degrees of freedom, and dealing with that could be complicated from a UI perspective. However, if we get a lot of requests for it, we can add it and sort out those issues. |
|
