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
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.
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
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