PyACL

The GNU GPL is not the right license for PyACL

Bug #377623 reported by Gustavo Narea
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
PyACL
Confirmed
Critical
Gustavo Narea
PyACL 1.0a1

Bug Description

PyACL should use a GPL-compatible license with which users of PyACL-powered libraries/applications can use the software with no problems at all.

The main reason to create Booleano was repoze.what 2. So it'd be contradictory for repoze.what to rely on the copyleft license GNU GPL.

After checking various licenses, I've decided to switch to the MIT X License with the non-advertisement clause.

Revision history for this message
Gustavo Narea (gnarea) wrote :

I'll fix this asap.

Changed in pyacl:
assignee: nobody → Gustavo Narea (gnarea)
importance: Undecided → Critical
milestone: none → 1.0a1
status: New → Confirmed
Revision history for this message
David H. Bronke (whitelynx) wrote :

Is there any chance of this happening soon? I'd like to look at using PyACL in another one of my projects (http://projects.g33xnexus.com/epic/wiki/Overview/) which is also MIT-licensed, and I'd rather not have to depend on a GPL-licensed library.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.