Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of adisakala@gmail.com designates
 64.233.166.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=YYYm1vtTIlI35y4OVIwfos/ZrfzVWozi5o60HC029Jvm44lh6ukk191Y1m1iIElE5C/w+edm0eEejsxGzJ08vqYu9uKAmPbSoOAbSuuMExbzzz23QkzI2UdD+5gHWIvC6AnNBUwVC8jv4Wh+D9w9W1z7euY2Px09oThtxwT6Lxg=
Message-ID: <570a43f00606301124w40311e66x7fe84f9c79e1446d@mail.gmail.com>
Date: Fri, 30 Jun 2006 14:24:00 -0400
From: "Adinarayana Sakala" <adisakala@gmail.com>
To: general@incubator.apache.org
Subject: Re: [PROPOSAL] CeltiXfire Project
In-Reply-To: <96B81E06-42CF-420F-95AE-EA84EE9F3253@jaguNET.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <296718BFC6B9E94FB0A809F55834237ACDE8CE@amereast-ems2.IONAGLOBAL.COM>
	 <44998F4B.2030108@gmx.de>
	 <5c902b9e0606211210t315d6eauad5ba9bd7edce57b@mail.gmail.com>
	 <4499ACFF.40303@envoisolutions.com>
	 <5c902b9e0606211430s24a4b4b6o5dc12a5be18d5494@mail.gmail.com>
	 <f470f68e0606300458h57b17c60l4e9546171ff48376@mail.gmail.com>
	 <88f5d710606300501k5a87e772nad1ce0e271facb0@mail.gmail.com>
	 <19845898-18A5-4371-884B-CDB0CE6ED678@jaguNET.com>
	 <44A52763.9080609@envoisolutions.com>
	 <96B81E06-42CF-420F-95AE-EA84EE9F3253@jaguNET.com>

Hi Jim and Dan,

Yes, Celtix team might have do point releases as well.

- Adi

On 6/30/06, Jim Jagielski <jim@jagunet.com> wrote:
> Yes, up until the podling can make releases, the old
> "external" projects still can do releases. However,
> it's expected that once the podling starts releases,
> that the 2 external ones shut down.
>
> On Jun 30, 2006, at 9:30 AM, Dan Diephouse wrote:
>
> > Hi Jim,
> > Even once we're in the incubator the XFire project will still have
> > to do releases. We have a 1.2 release in progress and will be doing
> > bug fix releases as well.  Additionally, I would imagine IONA might
> > want to issue a bug fix release at some point for Celtix. I can't
> > really comment on them though.
> >
> > - Dan
> >
> > Jim Jagielski wrote:
> >
> >> We've handled these types of things before, for example
> >> with SpamAssassin and Cayenne, when external codebases
> >> were being folded into the incubator. What they've done
> >> is mention on the old sites that the projects are
> >> now ASF Incubator projects, etc... The intent is that
> >> until the code has been relicensed to the AL 2.0, we
> >> cannot host it here, but as soon as that happens, the
> >> old sites no longer host the current codebases, just
> >> the old ones.
> >>
> >> At no time should Celtix and XFire continue parallel
> >> development with what is in the Incubator after the
> >> podling has started.
> >>
> >> On Jun 30, 2006, at 8:01 AM, Paul Fremantle wrote:
> >>
> >>> Robert +1
> >>>
> >>> I think also, given that I understand that the Celtix and XFire
> >>> projects will remain alive outside, at least for the initial future,
> >>> that it would help reduce confusion to have a separate and distinct
> >>> name for the Apache project.
> >>>
> >>> Paul
> >>>
> >>> On 6/30/06, robert burrell donkin
> >>> <robertburrelldonkin@gmail.com>  wrote:
> >>>
> >>>> On 6/21/06, Justin Erenkrantz <justin@erenkrantz.com> wrote:
> >>>> >
> >>>> > On 6/21/06, Dan Diephouse <dan@envoisolutions.com> wrote:
> >>>> > > Currently the plan is to leave both the old websites & docs
> >>>> will at the
> >>>> > > old locations. And XFire will be making release until
> >>>> Celtixfire
> >>>> > > releases a .0 release. I think Celtix will probably make
> >>>> some  1.x or
> >>>> > > 1.0.x releases as well.
> >>>> >
> >>>> > Given that, I think it's probably prudent to consider
> >>>> alternative names.
> >>>>
> >>>>
> >>>> +1
> >>>>
> >>>> > Is this official policy? Or do we just need to come to some
> >>>> consensus as
> >>>> > > to whether or not this will be confusing for our users?
> >>>> >
> >>>> > Our naming policy is to strive very hard not to conflict with any
> >>>> > other projects.  If those projects are going to continue
> >>>> independently
> >>>> > of CeltiXfire, then I'd view that as a conflict we should avoid.
> >>>>
> >>>>
> >>>> i wonder as well whether iona may need to consider whether they
> >>>> really
> >>>> understand the implications of choosing this name for the
> >>>> apache  project.
> >>>> the ASF would own the Apache CeltiXFire trademark and the
> >>>> community is very
> >>>> sensitive to issues around usage especially with regard to
> >>>> marketing.
> >>>>
> >>>> our model is different from objectweb and it is likely that the
> >>>> existing
> >>>> approach that iona takes when marketing celtix would need to be
> >>>> changed.
> >>>> apache is really centered on individuals. corporations of all
> >>>> kinds as well
> >>>> as many individuals find space to coorporate by this focus.
> >>>> this  corporation
> >>>> transparency implies neutrality. AIUI this is very different to
> >>>> the approach
> >>>> taken at (for example) objectweb.
> >>>>
> >>>> in addition, it is possible that iona may wish to maintain
> >>>> separate patched
> >>>> versions of the apache codebase. this may cause difficulties if
> >>>> iona needed
> >>>> to promote these products using an apache trademark.
> >>>>
> >>>> quite a lot of energy would be required for iona to maintain
> >>>> marketing
> >>>> material making extensive use of a possible Apache CeltiXFire
> >>>> trademark. a
> >>>> growing number of projects are also known to the outside by
> >>>> marketing names
> >>>> (for example apache derby). this allows a much greater degree
> >>>> of  freedom as
> >>>> well as building separate value for their corporation in their
> >>>> brand.
> >>>>
> >>>> this may help to explain the trend towards unique but non-
> >>>> descriptive names
> >>>> for projects.
> >>>>
> >>>> - robert
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Paul Fremantle
> >>> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> >>>
> >>> http://bloglines.com/blog/paulfremantle
> >>> paul@wso2.com
> >>>
> >>> "Oxygenating the Web Service Platform", www.wso2.com
> >>>
> >>> --------------------------------------------------------------------
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>> For additional commands, e-mail: general-help@incubator.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >
> >
> > --
> > Dan Diephouse
> > (616) 971-2053
> > Envoi Solutions LLC
> > http://netzooid.com
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Adi Sakala
http://celtix.objectweb.org

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org