Governance Meeting Today

Amongst all the work this week with setting up project infrastructure, the first release of Jenkins and a flood of developer activity on GitHub, the interim governance board has decided to hold periodic virtual meetings.

The first meeting will be held today at 3pm PST (23:00 UTC) in the #jenkins channel on IRC (more details here).

In Kohsuke's post to the mailing list, he further explained the goals of such meetings:

We can use it to report/discuss various issues of the project (not bugs in code, but more project level stuff.) I also plan to report the infrastructure work that's done thus far.

We'd like to hear from you, and the point is to engage the broader community, so please join us.

This is a new thing, so it's not like we've figured this all out, but let's see how it goes.

If you don't have an IRC client, you can use the Freenode webchat client to join in, hope to see you there!


(This was sent as an email to the Hudson dev and users mailing lists after voting concluded, but I thought it'd be good to post it here as well.)

The vote is closed, and the results are in. More than half of the total votes were from ineligible voters, but the result would have been the same either way. The final result of all eligible votes is as follows: 214 votes to rename, and 14 for the status quo. You can see the individual votes hudson-jenkins-vote.

Hudson's future

First, my apologies for the lack of updates on the Hudson/Oracle situation for the last few weeks. While talks have been ongoing, the holidays have slowed things down, and we didn't want to send out information that would later turn out not to be true. We've been waiting for the talks to reach a resolution - and I believe they now have.

Since the migration problems, Oracle and representatives from the Hudson community have been involved in talks on the future of the project in a number of areas. The Hudson representatives have been myself, Kohsuke Kawaguchi, and Sacha Labourey (CEO of CloudBees and Kohsuke's boss), who was brought in to help provide experience with discussions on a corporate/executive level which neither Kohsuke nor I have, with Alan Harder and R. Tyler Croy advising on the side.

These talks have in many ways been fruitful - we came to working agreements with Oracle on the project infrastructure (such as mailing lists and SCM repository location), code review policy for Hudson core, and perhaps most significantly, a governance structure for the project going forward. Some issues are not yet entirely resolved, such as questions on restrictions on third party dependency licenses. But one issue, which we feel is the most significant issue of all, one for which we now believe no resolution is possible: the rights to the name Hudson.

Oracle has told us that they have trademark applications filed in both the EU and US for Hudson, based on Hudson's creation by Kohsuke while working at Sun. The problem is that this trademark ownership gives Oracle the ability to revoke the Hudson project's right to call itself Hudson at any time, and while Oracle has made an attempt to offer some guarantees (most notably, that binary releases of Hudson, once they've been released with the name Hudson attached, will always retain the right to the name), they are not offering any binding guarantee that the Hudson project will be able to retain its use of the name in perpetuity.

Therefore, to continue using the name Hudson means ceding some of the project's independence to Oracle - if the project and its governance board opted to go in a direction Oracle disapproved of, Oracle would be able to take away the naming rights. Or, in a less dramatic scenario, Oracle could insist on certain changes to the code, infrastructure decisions, process, etc, regardless of opposition from the Hudson development community, in order to retain the rights to the name.

In short, we'd be living under a sword of Damocles, regardless of the goodwill of the individuals we've been negotiating with at Oracle - Hudson as a project would be beholden to Oracle's whims for its continued use of its own name, and we believe that's not viable.

Installing plugins has always been easy, now it's fast too!

As one of the "men behind the scenes" of the Hudson project, a lot of my contributions tend to be in writing articles or handling infrastructure, anything to ensure folks like Kohsuke can continue to make Hudson great without being distracted by inane system administration tasks. This past week, one of my long-running infrastructure projects has finally "gone live," making downloads of plugins and packages faster than ever!

Some number of months ago I became frustrated with the download speeds reported by our international users, while the majority of Hudson's infrastructure is all colocated inside of the United States, there is a huge number of Hudson users and developers who are both in Europe and Asia.

After discussing things with some of the folks that run, a MirrorBrain powered redirector, I set out to build something similar. A mirroring network which could be easily managed and help direct users' downloads to the geographically closest and fastest mirror available.

Where are we mirrored?

Currently we have mirrors in a few locations within the United States, and one overseas:

Using the mirrors

If you've updated or installed plugins from within Hudson lately, guess what! You're already using mirrors! In fact, since we flipped the switch on January 7th, over 800 plugins and 600 hudson.war updates have been downloaded from the mirroring network!

Weekend Update with Andrew Bayer

[Ed. note Andrew was not involved in selecting this post's title - rtyler]

I wanted to give the Hudson community a quick update on the current status of the issues Tyler has discussed in the earlier posts here.

Friday afternoon, Kohsuke, CloudBees CEO Sacha Labourey and myself jumped on a conference call with Hudson contributor/Oracle employee Winston Prakash, Oracle manager Denis Tyrell and of course Ted Farrell.

We discussed a wide range of issues relating to the Hudson project, such as governance, the rights to the name Hudson, and the infrastructure hosting the Hudson project. While we didn't agree on resolutions to all issues, I feel real progress was made towards a framework that provides what the Hudson community needs while also preventing the sort of conflicts we've seen the last week or two.

More work has to be done - we'll be talking again next week, and I'm hoping we can reach agreement on the contentious issues by the end of the week.

Thanks for your patience.