Opened 4 years ago

Closed 4 years ago

Reported by: Owned by: Ryan J Ollos Franz normal AttachmentPolicyPlugin normal license Steffen Hoffmann

Description

Hi, I noticed that there isn't a license specified in setup.py. Did you have a particular license in mind? You might consider using the BSD 3-Clause license, as Trac does.

Would you consider?:

• Specifying the license as an argument to setup in setup.py.

I'd be happy to take care of these activities if you give the go-ahead and indicate your license preference.

comment:3 in reply to:  2 Changed 4 years ago by Steffen Hoffmann

Sorry, but from a legal point of view this is not a real license, and this really matters, because licensing is business, no child-play, anyway. You may trust me, read more on the issues with this coder attitude disclaimer in a recent ticket for AccountManagerPlugin [1], or research the web on your own.

I'm coming a long way from Debian, and these guys tend to take legal stuff very serious. For what its worth I hope to convince you to move your preferences towards any of the common recognized free licenses like Apache, 3-clause BSD or MIT. I'm sure, this is what will serve all of us developers and users most in the long run. But certainly more discussion is welcome.

Thanks for consideration.

Steffen Hoffmann

[1] #10644, especially see the attachment

Last edited 4 years ago by Ryan J Ollos (previous) (diff)

comment:4 Changed 4 years ago by Franz

Well, when I recall correctly, I copied the BEERWARE from the AccountManagerPlugin. But it seems before ticket #10644. I am also fine with the 3-BSD license.

Thanks again for taking care about these topics.

comment:5 Changed 4 years ago by Ryan J Ollos

Resolution: → fixed new → closed

(In [13152]) Fixes #11085:

• Added BSD 3-Clause license with permission of author, adding license text in a COPYING file and adding headers to source code.
• Tidied up setup,py. Changed url to point to trac-hacks since this variable affects where defects are reported in the case that the user creates a ticket using the button on the Internal Error page.

comment:6 follow-ups:  7  8 Changed 4 years ago by Ryan J Ollos

Thanks for working that out guys. I also prefer the BSD 3-Clause so that there is no ambiguity, and it seems safest given the little I know about licenses.

I tidied up setup.py, but let me know if you'd like anything to be different than what I've done. I did some quick testing to check that everything is okay after the changes.

Have you considered also adding a WIKI_ATTACHMENT_DELETE permission? It seems like a staightforward extension of this plugin.

comment:7 in reply to:  6 Changed 4 years ago by Franz

Thanks for working that out guys. I also prefer the BSD 3-Clause so that there is no ambiguity, and it seems safest given the little I know about licenses.

Same for me. Thank you, Steffen.

I tidied up setup.py, but let me know if you'd like anything to be different than what I've done. I did some quick testing to check that everything is okay after the changes.

Thanks for taking care about that.

Have you considered also adding a WIKI_ATTACHMENT_DELETE permission? It seems like a staightforward extension of this plugin.

When I remember correctly the TICKET_ATTACHMENT_DELETE is also working for wiki attachments. Because at line 40-42 of attachment_policy.py I do not check the resource type.

But it seems to be more consistent having a WIKI_ATTACHMENT_DELETE permission. Another option would be to rename permission to ATTACHMENT_DELETE (maybe two permissions are too much for that issue?).

comment:8 in reply to:  6 Changed 4 years ago by Franz

Have you considered also adding a WIKI_ATTACHMENT_DELETE permission? It seems like a staightforward extension of this plugin.

I guess ticket #9276 already requests what you want.

Modify Ticket

Action
as closed The owner will remain Franz.
The resolution will be deleted. Next status will be 'reopened'.