[Hudson-Dev] Re: What is the governance of the new Hudson?
- From: "Christoph Kutzinski" <kutzi@...>
- To: dev@...
- Subject: [Hudson-Dev] Re: What is the governance of the new Hudson?
- Date: Mon, 14 Feb 2011 11:42:50 +0100
That's absolutely ridiculous.
The infrastructure was neither 'stolen' nor 'taken' from the community, as
they still are at the community.
The community decided to rename the project and not fork it.
I mean: what 'is' the community? The community is surely not the name, but
the people. And you can see by the number of the yes votes for the rename, by
the number of messages on the Jenkins user list (compared to the Hudson user
list) and by the echo on blogs and tweets that the people went with Jenkins.
By all means the community, which calls itself Hudson currently, is the fork.
I guess that you want to make it look the other way round for
business-political reasons, but that's simply not the truth.
-------- Original-Nachricht --------
> Datum: Sun, 13 Feb 2011 18:58:50 -0800 (PST)
> Von: Ted Farrell <ted.farrell@...>
> An: dev@...
> Betreff: [Hudson-Dev] Re: What is the governance of the new Hudson?
> Guys, I didn't mean to start more of this back and forth. You can sub in
> 'taken' instead of 'stolen'. Same principle. The Hudson community lost
> it's mailing lists, build infrastructure, update center, github repository
> and more without any say in the matter. Winston and team have been working
> hard to get that going again which has taken time away from them writing
> code. That is the point I am making.
> I appreciate that a small group of people in the old Hudson community
> wanted to do something different. And I don't want to quibble with numbers
> because it doesn't matter if the number was double or triple the 'yes' vote
> count. The point is that for the people who are still with the Hudson
> community/project, those assets are gone and they didn't have a say in the
> matter. That's a fact. Call it stolen. Call it taken. It's still a fact
> are gone. There is no such thing as a rebranding of a community when part
> of the community is still present.
> Forks happen all the time. They just normally happen with the group
> starting their own thing, instead of taking assets from the community.
> by definition is a fork of Hudson. There is no definition in the world
> where Hudson is a fork of Hudson. Again, I don't want to start the debate
> over again (at least not here and not during February when I can't drink
> ;). I appreciate the alternate point of view and the right to do what was
> done, but just not how it was done.
> Anyway, I'll use 'taken' if I have to reference it again. I hope I don't
> have to since we are mostly caught up with recovering from it all.
> From: Richard Bywater [mailto:rbywater@...]
> Sent: Sunday, February 13, 2011 6:32 PM
> To: dev@...
> Subject: [Hudson-Dev] Re: What is the governance of the new Hudson?
> Agreed - I'm assuming the infrastructure was not Oracle owned and
> therefore calling it stolen could even potentially be considered be
> Also I am a bit surprised that if Sonatype/Oracle had all these resources
> to spare, where were they prior to the fork?
> On Mon, Feb 14, 2011 at 3:28 PM, Slide <HYPERLINK
> "mailto:slide.o.mix@..."slide.o.mix@...> wrote:
> I think calling it stolen is a poor choice of words. It was a community
> decision, nothing was "stolen."
> On Feb 13, 2011 7:03 PM, "Ted Farrell" <HYPERLINK
> "mailto:ted.farrell@..." \nted.farrell@...> wrote:
> > Hi Emeric,
> > Oracle and Sonatype are working closely together. Sonatype had been
> doing a lot of work already and it was the same kind of things that we had
> talking about. You'll see more code coming from Oracle as well now that we
> are mostly caught up after having parts of the Hudson infrastructure
> stolen away from us during the Jenkins fork. Winston and team have been
> to getting the infrastructure back to normal, which is just about done. Now
> they are looking forward to cranking out some code.
> > The driver of Hudson should be the community. Oracle is fully backing
> the project so it will continue to grow and be supported. We are putting
> resources on it every week. We welcome everybody who wants to
> constructively participate.
> > As far as governance goes, we are hoping to make things more formal and
> post something soon. We are leaning towards an Eclipse model where there is
> a lead (Winston) and a PMC. I suggested this to Cloudbees and Andrew when
> we were discussing things in December, but Sacha thought that was too
> formal/heavyweight so I dropped it as a compromise. That is why it was not
> any of the documents we posted so far. Now that they have forked, we are
> leaning towards it again. I think following a well-proven process is better
> than making one up on our own, and I am interested in hearing others
> as well.
> > Let me know if you have any other questions.
> > thx.
> > -ted
> >> -----Original Message-----
> >> From: Emeric Vernat [mailto:HYPERLINK "mailto:evernat@..."
> >> Sent: Sunday, February 13, 2011 9:45 AM
> >> To: HYPERLINK "mailto:dev@..." \ndev@...
> >> Subject: [Hudson-Dev] What is the governance of the new Hudson?
> >> Hi Jason (and all),
> >> May I know why do you speak about where should be deployed
> >> hpi files and how should be managed sources, wiki and jira
> >> issues for plugins? ,  or  for example.
> >> Do you speak in the name of Oracle?
> >> In anycase, I did not read much what Oracle has to say about
> >> those things, compared to all that you have to say.
> >> Is Sonatype or yourself the new project lead of Hudson?
> >> Can you (or Oracle) clarify as soon as possible the people in
> >> the new governance of Hudson in order that we know who is
> >> driving this new Hudson?
> >> (For my boss it makes a big difference because he doesn't
> >> know Sonatype at the moment and he knows Oracle of course.)
> >> And is there a document available on the governance of the new Hudson?
> >> Thanks for your help on this.
> >> 
> >> http://java.net/projects/hudson/lists/dev/archive/2011-02/message/130
> >> 
> >> http://java.net/projects/hudson/lists/dev/archive/2011-02/message/90
> >> 
> >> http://java.net/projects/hudson/lists/dev/archive/2011-02/message/28