Travis Plugin Abandoned - Adopt?

[Bill Prin]

Hi Jenkins-sci,

I have been interested in using the Travis plugin at work.

https://github.com/jenkinsci/travis-yml-plugin

However, the project seems to have been abandoned. It doesn't work at all without the PR here, which has not been merged:

https://github.com/jenkinsci/travis-yml-plugin/pull/1

Travis is also quite complex and there are many features and improvements that could be added. I have started making a few small (unreleased) changes myself. 

I have tried to email the maintainer masakinakagawa a few months back and he has not responded to me.

Now, I would be happy to adopt the plugin, but there is one big problem. My employer (Google) is happy to contribute to OSS but seeing as the company is a huge legal target, our legal counsel is quite strict about complying to various licenses. The issue with the current Travis plugin is that there is no license anywhere on the repo. I know the Jenkins doc say it's "assumed' to be MIT, but we all know what happens with assumptions. So, if I did take ownership of it, I'd want to re-write it, probably in Java. It's currently only a few hundred lines of Ruby so this isn't a big effort. It would be under the Apache 2.0 license, so still an extremely permissive license. 

Alternatively, maybe someone else could take over the plugin, and I could just submit PRs to them. That would be simpler since it's easier to give code away with a correct license then take ownership of code without one at all.

I know Travis is pretty popular so it'd be nice to see this plugin get going again. Let me know what you think!

Bill

[Gavin]

Did you hear anything back about this?

My vote is to rewrite in java, I tried to follow the flow of the ruby apis to create PRs a few times and got confused.

Gavin

[Daniel Beck]

I don't think the Ruby Runtime is in a particularly great shape right now anyway, so if you can keep backwards compatibility, it should be no problem to do this. Especially if the plugin is as small as you're saying. Maybe increase the major version to indicate a big (even if only internal) change as well.

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a1016105-b974-48e6-b8ce-2074b177c20a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Bill Prin]

Sounds like Java rewrite is the way to, sounds good to me, I'll update this thread when I have something to show.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/kJrk7H1Y1uA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/A4574D3B-24CD-4186-B4DF-628B7B6FF324%40beckweb.net.