JavaOne summary

The word most used was open, specially by Sun, trying to
push OpenJDK, OpenSolaris and all their other open projects.
The openness of the conference made my head go around. That’s
related to the second most used word that was…. community.
Interesting how all the big companies talk about their communities,
in which most (all?) of the people is paid by them. Two examples, the Redmonk Unconference celebrated the day previous to the conference in
the CommunityOne section, first you have to register, then they don’t
let some people in because problems with the card readers. Second,
the servlet talk from Sun where they revealed their road map for 3.0
while the some
other members of the expert group
saw it there for first time.

Besides the political movements, there were some interesting
discussions about community (again), open source and repositories at
the Unconference, that I think it was the only educative
session I went to. I don’t mean that’s the only worth, I mean it’s
the only I went to ;) We ended at the Thirsty Bear to continue the
evangelization, and the usual (and some new) jokes about the
new company name
while drinking Albario
from home!

Tuesday was marked at the booth by an avalanche of people to get
the stamp for the Eclipse Foundation t-shirt, people really fought
for it. Hani decided to come by the booth so I told Dave to attack
and that’s why we ended
being evil
, although not individually ;). The day ended at the
Tangosol party, some kind of bachelor party after their marriage with
Oracle. After a short stop in the Irish pub for some shots the day
almost goes completely wrong for listening to some guy Club
suggestions’, that we decided to ignore and return to the hotel for
security reasons after getting there and see the people lining.

Wednesday, well, I have some gaps in my memory, I know for sure we
went to the Eclipse party, although it looked more like an Apache
party, followed by the Google party at the W hotel where things
started to go wrong. We managed to pass the Google Engineering Filter
(TM), or what it’s the same, the Google engineer playing doorman. Get
a job at Google to end at the door of a party, too sad. Even more
jokes about our
new name
, including domain registrations (what is the limit for a
geek party?), and some serious conversations with Lauren (as serious as they could be given the circumstances)
including some French practice.

After enough beer and wine we made the move for more serious
drinks to the House of Shields, while somebody of our team (don’t
ask names please) was offered a wheelchair by the hotel staff given
his conditions as we would know the following day. At the next bar I
could practice the few Russian words I know (why wouldn’t I have
listened more carefully when I was learning them!). One of the top
moments was when Dan
Nipplehouse
was randomly bitten by some drunk girl in a place
that you’ll have to imagine. What he forgot to say is that he bit her
back in the same place.

Thursday, well, let’s go to the interesting part, after a short
stop in the Thirsty Bear enjoying Spanish wine and paella and trying
to stop Debbie from stealing
my jacket, which by the way was a great success among with the gold
shoes
. We were convinced to move to another place where the
Cenqua guys were having dinner… and some more fun. As Matt
wrote:

“To protect the innocent, and perhaps not so innocent, I
won’t go into too much details about who we managed to drag along.
Let’s just say it involved a little obfuscation. There were some
abstractions in the design that definitely did
not
leak, no matter how hard we looked.”

Which basically means that the Cenqua guys have some kind of
visual problem, or a strange taste. Well, the Cenqua guys and
Bileblog Hani, target of very embarrassing pictures, and who lost
200$ in a bet with us and will be donated to a charity of his choice.
After the unnameable place we move on to the Starlight room at the
top of the Sir Francis Drake hotel, were some random guys recognized
or very famous Sebastian
and more drinks followed until we were kicked out. Gregor
offered to continue the party on his place but it seemed wise to call
the night before getting in front of his camera. Unfortunately James
wasn’t wise enough
.

At the end, the usual suspects as last year, with the exception of
the Spring guys, maybe they
were too busy counting money
;). Somebody said, there are
thousands of people in this conference, but no more than 200 that
really matter. And I would add, from those 200 you get the most
networking opportunities after the conference, at the bar. Good to
meet you all, it was fun!

See you at JavaOne

I’ll be at JavaOne next week in San Francisco, starting Monday at Redmonk Unconference, and through the week around the DevZuz booth or in any of the parties.

I may blog if I have the time, but it’s pretty likely that the preferred communication method this time it’s going to be twitter, with all these crazy people using it, how sad is that? But not at the bar, that’s for sure, there the only option will be face to face.

A new company, DevZuz, and Maestro 1.2

This week the new brand for our company was announced.
DevZuz is the evolution of
Simula Labs, Mergere’s parent company. Don’t miss also the release of
Maestro
1.2
, a distribution based on Maven, Archiva (repository
management) and Continuum (continuous integration) with the tools
needed to manage open source adoption in the enterprise.

I was going to write an entry about it, but as Brett
already won me at it
, I’m going to copy and paste and save time
for other entries ;)

Other than “What does DevZuz mean?”, the main question I
am getting is “Why change the name?”

The reality of the two companies today is that they have a single,
simple and clear goal: to help enterprises adopt open source
projects and development processes
. Unifying under a single brand
gives us the opportunity for a “fresh start” that reflects
that specific focus. Far from being the end
of Mergere
, we are continuing to do what we are doing well now,
but additionally making some very positive changes (particularly in
relation to our community involvement).

As DevZuz, we will expand on our development and support for
Maestro, which is an enterprise-ready distribution of Maven
technologies now coming up on its one-year anniversary. Maestro,
which remains a free download, provides the foundation that is used
behind the firewall to enable artifact-based development practices
(and consume open source technologies). We will continue to provide
support, training and consulting services for Maestro customers.

In addition, DevZuz can now provide hosted
services
that build on top of Maestro to help enterprises manage
their open source governance and support.

We are also expanding our network of partners
to provide additional services, and to continue to provide commercial
support for key open source technologies.

More information can be found at our brand
new web site
. There you’ll also find that we have released
Maestro 1.2
.

One of the exciting developments is a re-emphasis on our
contribution to the open source communities we participate in.
Mergere has made significant contributions to open source over the
last two years in terms of development resources, free services and
the contribution of the first free book about Maven 2. These will, of
course, continue – but as DevZuz, we have established specific roles
and practices to improve our community involvement. Our aim is for
our participation in those communities to be completely transparent.

Though DevZuz is not “the Maven company”, DevZuz is
committed to making Maven and its subprojects successful as a
community in it’s own right. In particular, we will be focusing on
helping produce more frequent releases in the community, in addition
to the tested Maestro product suite. You can expect a lot more to
come in this area – and this is exciting news for Maven users and
developers alike.

In addition to our continued participation in Maven, DevZuz is
leading the Eclipse
Kepler
project proposal as a community effort.

I’m personally pleased with this direction – we have interesting
and different problems to solve while continuing to focus on open
source development.