License

[Ryan J Ollos]

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?:

• Adding license headers to each file.
• Adding a COPYING file with the license text.
• 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.

[Wertilq]

TBH, I haven't really thought about license, but go ahead with same as Trac have.

[Steffen Hoffmann]

Replying to Wertilq:

TBH, I haven't really thought about license, but go ahead with same as Trac have.

I fully understand, thinking the same some years ago. But it certainly matters to keep free code free and enable contributions of developers after an author discontinues support when going on to other projects.

[Steffen Hoffmann]

Replying to rjollos:

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

I saw the new plugin committed to the repository too. Thanks for checking and taking care to ask.

[Ryan J Ollos]

In 13973:

1.0: Added 3-Clause BSD license. Fixes #11825.

[Ryan J Ollos]

Thanks for the replies. I'll let you know if I have any other feedback after testing out the plugin.

Do you have any experience with HudsonTracPlugin, and if so could you comment on the differences between that plugin and yours?

[Wertilq]

I looked at the HudsonTracPlugin, when I began working on my plugin, but I didn't manage to salvage anything at all from it.

IIRC what it did was simply to add a link to Hudson in Trac, while my plugin uses the REST API for Jenkins to access Jenkins information. It aims to do an integration of Jenkins, into Trac using the REST API.

It's not finished though, and it was work made for CGI's #define-team, which I did my thesis project with, and my project there is now finished, I don't know if I will work more on the plugin.