Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of kevan.miller@gmail.com
 designates 209.85.213.54 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: geronimo 2.2 upgrades
From: Kevan Miller <kevan.miller@gmail.com>
In-Reply-To: 
 <CABwW4fSt2uFN7xa5H5C6zn_o7UJAN_yv1QEUUpSnxW3gxbJypw@mail.gmail.com>
Date: Wed, 16 Nov 2011 18:47:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8A530AD3-2DC1-4EED-9E98-69A7CE65B977@gmail.com>
References: 
 <CABwW4fSt2uFN7xa5H5C6zn_o7UJAN_yv1QEUUpSnxW3gxbJypw@mail.gmail.com>
To: dev@geronimo.apache.org

Hi Trygve
Thanks for the email!

If anybody else struggles with Trygve's name, you might find this =
helpful: http://inogolo.com/pronunciation/Trygve (how could it be =
pronounced any other way!)

On Nov 16, 2011, at 4:37 PM, Trygve Sanne Hardersen wrote:

> Hello,
>=20
> Our company has done some work lately on upgrading the dependencies =
used by Geronimo 2.2. The most notable changes are:
<snip>
>=20
> As you can see the Axis2 integration is still quite buggy, and will =
have to be improved (we're not using it internally).
>=20
> Community
> Are you interested in having these changes merged back into the =
Geronimo source repository? We would be very happy to see them accepted =
in some way.

Those are some fairly significant changes. I haven't reviewed them in =
detail=85 In addition to the integration test issues, there are likely =
to be TCK issues to contend with.=20

In the rest of my note, I'm *not* going to be commenting on the details =
of these patches. There may be specific technical/philosophical problems =
with some of the changes. These problems would need to be resolved =
through community discussion. Note that this means there may be some =
give-and-take. There may be some parts of your changes that the =
community feels are wrong/incorrect. So, some parts of the patches may =
require change.

However, let's assume we can resolve any of these issues (I'd certainly =
hope so).

>=20
> We are aware that the first 3.0 beta has just been released =
(congrats!), and don't know how this fits into your 2.2 release policy. =
We have previously done internal Geronimo releases using patches, but as =
the changeset has grown, this approach is less and less practical. Our =
feeling is that we either have to get the work back into Geronimo in =
some way, or do a fork. One possibility is to branch 2.2, and apply our =
changes there.

There has been a lot of community focus on 3.0. However, this does not =
mean our 2.1/2.2 branches are closed down=85 I am expecting to see =
additional releases out of these branches=85 However, the scope of your =
changes may go beyond a normal 2.2.x service release. I wouldn't be a =
big fan of a 2.3 release. However, it's not impossible either...

So, my personal opinion -- I'd be interested in seeing your =
contributions make their way into Geronimo SVN. I would certainly hope =
that we can avoid a fork=85 I am assuming, however, that additional =
people (e.g. you) would be helping the community with integrating, =
testing, releasing, and *supporting* these changes. We're quite open to =
new contributors. And I would expect that it would not take long to =
become a committer on the project.

One final note -- I would not be in favor of *permanent* development on =
separate Geronimo branches (2.x vs. 3.x). So, I am assuming that given =
time -- the community would be working towards common goals.=20

>=20
> You can find the latest patches here:
>=20
> GShell - =
https://hypobytes.com/svn/ymir/patches/trunk/gshell-alpha-1-606434.patch
> Geronimo - =
https://hypobytes.com/svn/ymir/patches/trunk/geronimo-2.2-1188546.patch

Given the scope of these changes, I think a software grant would be =
required (either http://www.apache.org/licenses/software-grant.txt or =
http://www.apache.org/licenses/cla-corporate.txt ).=20

I'm sure there will be additional comments from other community members.=20=


--kevan=