Use Advanced Search to search the entire archive.
[Hudson-Dev] Re: [] The Future of Hudson
- From: "Trojan, Krzysztof" <krzysztof.trojan@...>
- To: "Kohsuke Kawaguchi" <kk@...>
- Cc: <dev@...>
- Subject: [Hudson-Dev] Re: [] The Future of Hudson
- Date: Tue, 1 Feb 2011 21:04:11 -0000
Hi,
So additionally to highjacking the project they also claim (or "suggest") to
have your consent:
On the new Hudson-ci.org one can read:
"Many of you may be aware that Andrew Bayer and Cloudbees (where Kohsuke
Kawaguchi now works) have confirmed their intent to fork Hudson into a new
community. We want the Hudson community to know that we have a dedicated team
that includes people from Oracle, as well as some of our partners and current
Hudson community members who will continue to build and grow the Hudson
project and community. Your current installations will continue to run fine,
and you won't need to change any code. You can still come to
http://www.hudson-ci.org/ for all things Hudson."
Don't know if you work Cloudbees ... but it does not necessarily mean you
gave the project away to them.
Let's see what will come out of this mess ... the Hudson was usable before
Oracle overtook it, we can always think about a fork ;)
But still I don't think I understand how one, especially a person of your
level of recognition, can be "removed" from any open source project.
Kind regards,
Chris
-----Original Message-----
From: kohsuke.kawaguchi@... [
mailto:kohsuke.kawaguchi@...] On Behalf Of
Kohsuke Kawaguchi
Sent: Tuesday, February 01, 2011 9:38 PM
To: Trojan, Krzysztof
Cc: dev@...
Subject: Re: [Hudson-Dev] Re: [] The Future of Hudson
No, I didn't hand over the project to Oracle. They feel they are
entitled to it, and I was simply removed from the project.
2011/2/1 Trojan, Krzysztof <krzysztof.trojan@...>:
>
What I am surprised is that Oracle was given ownership of the project.
>
I have not paid attention to the list for some time now, but as far as
>
I remember the latest approach on this by some Oracle employee
>
had rather cold welcome.
>
>
For me it looks like a highjack, not a fork ;)
>
But it seems Kohsuke gave it his blessing, and I respect his opinion here.
>
>
Regards,
>
Chris
>
>
-----Original Message-----
>
From: Eirik Bjørsnøs [mailto:eirbjo@...]
>
Sent: Tuesday, February 01, 2011 9:07 PM
>
To: susan.duncan@...
>
Cc: dev@...
>
Subject: [Hudson-Dev] Re: [] The Future of Hudson
>
>
unsubscribe
>
>
No, seriously: How do I get off this list?
>
>
The headers seem to indicate that an email to sympa@...
>
with a subject of "unsubscribe-dev" should do the trick, but sympa
>
replies that it finds no command.
>
>
Is this Oracle's way of building a "community"? Creating email lists
>
that people can't unsubscribe from?
>
>
Eirik.
>
>
>
On Tue, Feb 1, 2011 at 7:20 PM, <susan.duncan@...> wrote:
>
> All, Now that the fork has happened, we can start to put this saga
>
> behind us and get back to work. At this point we want to reassure you
>
> that Hudson-ci continues and has our full commitment. We have a
>
> dedicated team that includes people from Oracle, as well as some of our
>
> partners and current Hudson community members who will continue to
>
> build and grow the Hudson project and community.
>
>
>
> Your current installations will continue to run fine, and you won't
>
> need to change any code. You can still come to the newly designed
>
> http://www.hudson-ci.org/ for all things Hudson. Later this week we
>
> will announce a new release of Hudson. This release will primarily
>
> de-couple the Hudson code from the old auto-update center back to the
>
> official Hudson update center. If you use auto-update with version
>
> 1.395 or earlier, the auto-update will take you to a site that will ask
>
> you to install jenkins which will remove your Hudson installation. If
>
> you want to continue to use Hudson, you should install Hudson v1.396 or
>
> later when it becomes available later this week
>
>
>
> We have reverted to using the Hudson mailing lists on java.net but are
>
> open to discussion about creating a new google group. In addition
>
> java.net provides a forum that can be used to discuss user problems,
>
> ideas and other issues. There is a link to get to that at the top of
>
> the hudson-ci.org website. I would urge you to engage with other
>
> users.
>
>
>
> Also as part of the fork, the Hudson github project has been taken
>
> away. We have a current git repository on hudson.java.net where people
>
> can continue to check things in. We can also discuss moving this back
>
> to github once we get things settled. If you are interested in getting
>
> involved, and are not already registered as a committer, please let us
>
> know. This is your opportunity to help shape the future of Hudson.
>
>
>
> Our primary goals over the next months will be to fix high-priority
>
> bugs in the current edition of Hudson and formalize a development and
>
> release process that will allow users of Hudson to have more insight
>
> into what is being changed, why it is being changed, and when their
>
> bugs will be fixed. We will also continue the discussion that Winston
>
> started last month about what the next version of Hudson (v2) looks
>
> like. I look forward to working closely with the community on where to
>
> go from here.
>
>
>
> regards
>
>
>
> Susan
>
>
>
>
_____________
>
>
The information contained in this message is proprietary and/or
>
confidential. If you are not the intended recipient, please: (i) delete the
>
message and all copies; (ii) do not disclose, distribute or use the message
>
in any manner; and (iii) notify the sender immediately. In addition, please
>
be aware that any message addressed to our domain is subject to archiving
>
and review by persons other than the intended recipient. Thank you.
>
_____________
>
--
Kohsuke Kawaguchi
_____________
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner;
and (iii) notify the sender immediately. In addition, please be aware that
any message addressed to our domain is subject to archiving and review by
persons other than the intended recipient. Thank you.
_____________