You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Daniel Kulp <da...@iona.com> on 2006/10/06 20:01:05 UTC
[VOTE] Officially rename the project to Apache CXF
I'd like to vote to officially rename the project to Apache CXF.
I'm extremely +1.
There are a lot reasons to do so: (summary of previous discussions)
1) All of our Apache resources are "CXF". If someone goes to apache to
looking for CeltiXfire using the "normal Apache" URL's and such, they won't
find it. Example: if they send a note to celtixfire-dev-subsribe, it would
bounce, etc...
2) Branding - It seems like all of us are calling it CXF in our
communication. However, the "Apache Branding" would require it to use the
full project name. It would be good if it matched to avoid confusion for
users. (Example: in a note on the incubator list during the recent
issues, someone asked why we were calling it CXF.) Anyway, a lot of people
are already associating CXF with the project. Let's build on that.
3) Our package name, jars, install dir, etc.. all use "cxf" right now. No
work would need to be done there. (I'm lazy, I admit it.)
4) No wacky CamelCase spellings to cause confusions and branding issues.
(Celtixfire, CeltiXfire, CeltiXFire, etc..)
5) Already I18N capable. :-) Seriously, we had some chats on IRC
about "how to pronounce" some of the other ideas. Example: Apparently the
word "foam" is hard to pronounce in some locales. Also, "Celtic" is
pronounced different in various locales as well.
6) Break some ties with the "messes" that we've been involved in. I keep
hearing nicknames like "celtic-miss-fire" and such. That's not good. The
recent events certainly didn't help things. A semi-clean slate is probably
a good idea. Make them think of new nicknames. :-)
7) However, by keeping the initials, there is "some" tie to the previous
projects, but the tie is broken enough to make it clear, this really is
something new and better.
8) The top two google links for CXF are already our own confluence space.
Nice job everyone. :-) CXF is an acronym for "Chemical eXchange Format",
but that really shouldn't matter for us.
Thanks!
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194 F:781-902-8001
daniel.kulp@iona.com
Re: [VOTE] Officially rename the project to Apache CXF
Posted by peter royal <pr...@apache.org>.
On Oct 6, 2006, at 11:01 AM, Daniel Kulp wrote:
> I'd like to vote to officially rename the project to Apache CXF.
+1
-pete
--
proyal@apache.org - http://fotap.org/~osi
Re: [VOTE] Officially rename the project to Apache CXF
Posted by Kevin Conner <Ke...@jboss.com>.
Daniel Kulp wrote:
> I'd like to vote to officially rename the project to Apache CXF.
+1
Kev
Re: [VOTE] Officially rename the project to Apache CXF
Posted by Mika Göckel <mi...@gmx.de>.
-1 (non-binding)
just because we're using the abbreviation CXF for convenience reasons
doesn't mean it's a good name at all.
Please name some successful projects with such a short, non speaking
acronym as a name, if any they are few.
I've got 615.000 hits with this acronym on german google, how will you
ensure people are finding us?
How should people talk about CXF? Is it cee-eks-eff? What does it mean,
where's the story? Does it create phantasies? No.
"Anyway, a lot of people
are already associating CXF with the project."
Sorry, Daniel, but a lot of people means a couple of thousands, not the bunch reading incubator-general. If we were on tss with the name, I would agree, but at this time there are only a few having associated the name with the project.
To summarize: I don't think acronyms are good names for projects, I recommend finding a better name now.
Cheers,
Mika
Daniel Kulp schrieb:
> I'd like to vote to officially rename the project to Apache CXF.
>
> I'm extremely +1.
>
>
> There are a lot reasons to do so: (summary of previous discussions)
>
> 1) All of our Apache resources are "CXF". If someone goes to apache to
> looking for CeltiXfire using the "normal Apache" URL's and such, they won't
> find it. Example: if they send a note to celtixfire-dev-subsribe, it would
> bounce, etc...
>
> 2) Branding - It seems like all of us are calling it CXF in our
> communication. However, the "Apache Branding" would require it to use the
> full project name. It would be good if it matched to avoid confusion for
> users. (Example: in a note on the incubator list during the recent
> issues, someone asked why we were calling it CXF.) Anyway, a lot of people
> are already associating CXF with the project. Let's build on that.
>
> 3) Our package name, jars, install dir, etc.. all use "cxf" right now. No
> work would need to be done there. (I'm lazy, I admit it.)
>
> 4) No wacky CamelCase spellings to cause confusions and branding issues.
> (Celtixfire, CeltiXfire, CeltiXFire, etc..)
>
> 5) Already I18N capable. :-) Seriously, we had some chats on IRC
> about "how to pronounce" some of the other ideas. Example: Apparently the
> word "foam" is hard to pronounce in some locales. Also, "Celtic" is
> pronounced different in various locales as well.
>
> 6) Break some ties with the "messes" that we've been involved in. I keep
> hearing nicknames like "celtic-miss-fire" and such. That's not good. The
> recent events certainly didn't help things. A semi-clean slate is probably
> a good idea. Make them think of new nicknames. :-)
>
> 7) However, by keeping the initials, there is "some" tie to the previous
> projects, but the tie is broken enough to make it clear, this really is
> something new and better.
>
> 8) The top two google links for CXF are already our own confluence space.
> Nice job everyone. :-) CXF is an acronym for "Chemical eXchange Format",
> but that really shouldn't matter for us.
>
> Thanks!
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194 F:781-902-8001
> daniel.kulp@iona.com
>
>
--
cyber:con gmbh
Mika Göckel
Rathausallee 10
53757 Sankt Augustin
tel (+49)2241 / 9350 0
fax (+49)2241 / 9350 99
mob (+49) 172 / 279 2771
skype mika.goeckel
email mika@cybercon.de
Re: [VOTE] Officially rename the project to Apache CXF
Posted by Andrea Smyth <an...@iona.com>.
+1
Andrea.
Daniel Kulp wrote:
>I'd like to vote to officially rename the project to Apache CXF.
>
>
Re: [VOTE] Officially rename the project to Apache CXF
Posted by Balaji Ravi <ba...@gmail.com>.
+1
On 10/6/06, Mark Little <ma...@jboss.com> wrote:
>
> +1
>
> On 6 Oct 2006, at 19:01, Daniel Kulp wrote:
>
> >
> > I'd like to vote to officially rename the project to Apache CXF.
> >
> > I'm extremely +1.
> >
> >
> > There are a lot reasons to do so: (summary of previous discussions)
> >
> > 1) All of our Apache resources are "CXF". If someone goes to
> > apache to
> > looking for CeltiXfire using the "normal Apache" URL's and such,
> > they won't
> > find it. Example: if they send a note to celtixfire-dev-subsribe,
> > it would
> > bounce, etc...
> >
> > 2) Branding - It seems like all of us are calling it CXF in our
> > communication. However, the "Apache Branding" would require it to
> > use the
> > full project name. It would be good if it matched to avoid
> > confusion for
> > users. (Example: in a note on the incubator list during the recent
> > issues, someone asked why we were calling it CXF.) Anyway, a lot
> > of people
> > are already associating CXF with the project. Let's build on that.
> >
> > 3) Our package name, jars, install dir, etc.. all use "cxf" right
> > now. No
> > work would need to be done there. (I'm lazy, I admit it.)
> >
> > 4) No wacky CamelCase spellings to cause confusions and branding
> > issues.
> > (Celtixfire, CeltiXfire, CeltiXFire, etc..)
> >
> > 5) Already I18N capable. :-) Seriously, we had some chats on IRC
> > about "how to pronounce" some of the other ideas. Example:
> > Apparently the
> > word "foam" is hard to pronounce in some locales. Also, "Celtic" is
> > pronounced different in various locales as well.
> >
> > 6) Break some ties with the "messes" that we've been involved in.
> > I keep
> > hearing nicknames like "celtic-miss-fire" and such. That's not
> > good. The
> > recent events certainly didn't help things. A semi-clean slate is
> > probably
> > a good idea. Make them think of new nicknames. :-)
> >
> > 7) However, by keeping the initials, there is "some" tie to the
> > previous
> > projects, but the tie is broken enough to make it clear, this
> > really is
> > something new and better.
> >
> > 8) The top two google links for CXF are already our own confluence
> > space.
> > Nice job everyone. :-) CXF is an acronym for "Chemical
> > eXchange Format",
> > but that really shouldn't matter for us.
> >
> > Thanks!
> > --
> > J. Daniel Kulp
> > Principal Engineer
> > IONA
> > P: 781-902-8727 C: 508-380-7194 F:781-902-8001
> > daniel.kulp@iona.com
>
Re: [VOTE] Officially rename the project to Apache CXF
Posted by Mark Little <ma...@jboss.com>.
+1
On 6 Oct 2006, at 19:01, Daniel Kulp wrote:
>
> I'd like to vote to officially rename the project to Apache CXF.
>
> I'm extremely +1.
>
>
> There are a lot reasons to do so: (summary of previous discussions)
>
> 1) All of our Apache resources are "CXF". If someone goes to
> apache to
> looking for CeltiXfire using the "normal Apache" URL's and such,
> they won't
> find it. Example: if they send a note to celtixfire-dev-subsribe,
> it would
> bounce, etc...
>
> 2) Branding - It seems like all of us are calling it CXF in our
> communication. However, the "Apache Branding" would require it to
> use the
> full project name. It would be good if it matched to avoid
> confusion for
> users. (Example: in a note on the incubator list during the recent
> issues, someone asked why we were calling it CXF.) Anyway, a lot
> of people
> are already associating CXF with the project. Let's build on that.
>
> 3) Our package name, jars, install dir, etc.. all use "cxf" right
> now. No
> work would need to be done there. (I'm lazy, I admit it.)
>
> 4) No wacky CamelCase spellings to cause confusions and branding
> issues.
> (Celtixfire, CeltiXfire, CeltiXFire, etc..)
>
> 5) Already I18N capable. :-) Seriously, we had some chats on IRC
> about "how to pronounce" some of the other ideas. Example:
> Apparently the
> word "foam" is hard to pronounce in some locales. Also, "Celtic" is
> pronounced different in various locales as well.
>
> 6) Break some ties with the "messes" that we've been involved in.
> I keep
> hearing nicknames like "celtic-miss-fire" and such. That's not
> good. The
> recent events certainly didn't help things. A semi-clean slate is
> probably
> a good idea. Make them think of new nicknames. :-)
>
> 7) However, by keeping the initials, there is "some" tie to the
> previous
> projects, but the tie is broken enough to make it clear, this
> really is
> something new and better.
>
> 8) The top two google links for CXF are already our own confluence
> space.
> Nice job everyone. :-) CXF is an acronym for "Chemical
> eXchange Format",
> but that really shouldn't matter for us.
>
> Thanks!
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194 F:781-902-8001
> daniel.kulp@iona.com
RE: [VOTE] Officially rename the project to Apache CXF
Posted by "Lin, Bozhong" <Bo...@iona.com>.
0 (non-binding)
In principle I agree that the project name should be changed, as from my experieces of workoing on distribution module. However, I also feel that CXF name is no better than CeltiXfire, we have used it in every project places simply because it is handy. My +1 is ready for any better name, and we should consider a better name.
Cheers,
Bo
________________________________
From: Kulp, John Daniel
Sent: Fri 10/6/2006 2:01 PM
Cc: cxf-dev@incubator.apache.org
Subject: [VOTE] Officially rename the project to Apache CXF
I'd like to vote to officially rename the project to Apache CXF.
I'm extremely +1.
Re: [VOTE] Officially rename the project to Apache CXF
Posted by Jiang Ning <ni...@iona.com>.
+1
Daniel Kulp wrote:
>I'd like to vote to officially rename the project to Apache CXF.
>
>
>
Willem
Re: [VOTE] Officially rename the project to Apache CXF
Posted by Jim Jagielski <ji...@jaguNET.com>.
On Oct 6, 2006, at 2:01 PM, Daniel Kulp wrote:
>
> I'd like to vote to officially rename the project to Apache CXF.
>
> I'm extremely +1.
>
>
+1... it's already, I think, a fait accompli, imo :)
Re: [VOTE] Officially rename the project to Apache CXF
Posted by Scott Nicholls <sn...@virtuas.com>.
+1 (non-binding)
Daniel Kulp wrote:
> I'd like to vote to officially rename the project to Apache CXF.
>
> I'm extremely +1.
>
>
> There are a lot reasons to do so: (summary of previous discussions)
>
> 1) All of our Apache resources are "CXF". If someone goes to apache to
> looking for CeltiXfire using the "normal Apache" URL's and such, they won't
> find it. Example: if they send a note to celtixfire-dev-subsribe, it would
> bounce, etc...
>
> 2) Branding - It seems like all of us are calling it CXF in our
> communication. However, the "Apache Branding" would require it to use the
> full project name. It would be good if it matched to avoid confusion for
> users. (Example: in a note on the incubator list during the recent
> issues, someone asked why we were calling it CXF.) Anyway, a lot of people
> are already associating CXF with the project. Let's build on that.
>
> 3) Our package name, jars, install dir, etc.. all use "cxf" right now. No
> work would need to be done there. (I'm lazy, I admit it.)
>
> 4) No wacky CamelCase spellings to cause confusions and branding issues.
> (Celtixfire, CeltiXfire, CeltiXFire, etc..)
>
> 5) Already I18N capable. :-) Seriously, we had some chats on IRC
> about "how to pronounce" some of the other ideas. Example: Apparently the
> word "foam" is hard to pronounce in some locales. Also, "Celtic" is
> pronounced different in various locales as well.
>
> 6) Break some ties with the "messes" that we've been involved in. I keep
> hearing nicknames like "celtic-miss-fire" and such. That's not good. The
> recent events certainly didn't help things. A semi-clean slate is probably
> a good idea. Make them think of new nicknames. :-)
>
> 7) However, by keeping the initials, there is "some" tie to the previous
> projects, but the tie is broken enough to make it clear, this really is
> something new and better.
>
> 8) The top two google links for CXF are already our own confluence space.
> Nice job everyone. :-) CXF is an acronym for "Chemical eXchange Format",
> but that really shouldn't matter for us.
>
> Thanks!
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194 F:781-902-8001
> daniel.kulp@iona.com
>
>
>
>
Re: I18N and L10N stuff...
Posted by Mark Little <ma...@jboss.com>.
Hi Dan. I'll look into that when I get back.
Mark.
On 2 Nov 2006, at 20:21, Daniel Kulp wrote:
>
> Mark,
>
> I had sent a note to Cliff asking if it was OK. I haven't heard back
> from him. I'll re-send.
>
> That said, to be usable, we'd need it to basically be a maven 2 plugin
> preferrably, but at the very least, have it available in the maven2
> repositories. If you could figure out how to get it callable from
> maven, that would be great.
>
> Dan
>
>
> On Thursday November 02 2006 9:35 am, Mark Little wrote:
>> No feedback must mean everyone is happy ;-)
>>
>> I'll take a look at this the week after next when I get back from
>> SCUBA diving in the Red Sea :-) and my broken machine is fixed :-(
>>
>> Mark.
>>
>> On 26 Oct 2006, at 23:36, Mark Little wrote:
>>> Owing to server outages, this seemed to get lost first time round.
>>>
>>> Mark.
>>>
>>> On 23 Oct 2006, at 18:47, Mark Little wrote:
>>>> I notice from looking at the code that although there's an
>>>> approach to what log implementation to use for
>>>> internationalization/localization support, there's nothing formal
>>>> for creating resource bundles. Maybe I missed it though. However,
>>>> under the assumption I'm correct, one thing I'd like to suggest to
>>>> solve this issue would be to use the resource bundle doclet that
>>>> was developed by Hewlett-Packard, and now freely available (under
>>>> LGPL) from JBoss. Take a look http://docs.jboss.org/process-guide/
>>>> en/html/internationalization.html#d0e3916 and specifically at
>>>> 11.2.6 (Creating Resource Bundles). You can ignore the references
>>>> to the logger implementation because, as I said above, that seems
>>>> to be taken care of already in CXF.
>>>>
>>>> This doclet has been used successfully in many of the HP NetAction
>>>> products (in 2000/2001/2002) and subsequently in the Arjuna
>>>> Transaction Service/Message Service implementations. If this looks
>>>> to be of interest, then I'd be happy to work with whoever to
>>>> incorporate the ant task that runs the doclet into the build
>>>> scripts and produce an update to the wiki page for developers to
>>>> follow when writing text that goes into a resource bundle. I know
>>>> it's covered by LGPL, but I assume that since this would only
>>>> affect the building of CXF and not something that gets shipped
>>>> with the product, it should be alright to use.
>>>>
>>>> Mark.
>>>>
>>>> On 6 Oct 2006, at 23:06, Mark Little wrote:
>>>>> I'll take a look at the wiki page and come up to speed on that.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Mark.
>>>>>
>>>>> On 6 Oct 2006, at 21:09, Daniel Kulp wrote:
>>>>>> Mark,
>>>>>>
>>>>>> On Friday October 06 2006 3:57 pm, Mark Little wrote:
>>>>>>> Your I18N reference got me thinking. Can someone point me at
>>>>>>> the I18N/
>>>>>>> L10N approach taken for CXF? What I mean is the rules and tools
>>>>>>> for
>>>>>>> generating resource bundles and using them within the code. If
>>>>>>> there's no solution in place, we may have an open source tool
>>>>>>> that the project might want to consider.
>>>>>>
>>>>>> There is some "older" stuff on the old Celtix wiki related to
>>>>>> that:
>>>>>> http://wiki.objectweb.org/celtix/Wiki.jsp?
>>>>>> page=Internationalizatio
>>>>>> n and:
>>>>>> http://wiki.objectweb.org/celtix/Wiki.jsp?page=CeltixLogging
>>>>>>
>>>>>> Not a lot though and what is there needs to be copied to the CXF
>>>>>> space.
>>>>>>
>>>>>> Good question though. :-)
>>>>>>
>>>>>> If you see areas in the code that aren't doing the I18N stuff,
>>>>>> file bugs
>>>>>> (or fix it).
>>>>>>
>>>>>> Thanks!
>>>>>> --
>>>>>> J. Daniel Kulp
>>>>>> Principal Engineer
>>>>>> IONA
>>>>>> P: 781-902-8727 C: 508-380-7194 F:781-902-8001
>>>>>> daniel.kulp@iona.com
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194 F:781-902-8001
> daniel.kulp@iona.com
Re: I18N and L10N stuff...
Posted by Daniel Kulp <da...@iona.com>.
Mark,
I had sent a note to Cliff asking if it was OK. I haven't heard back
from him. I'll re-send.
That said, to be usable, we'd need it to basically be a maven 2 plugin
preferrably, but at the very least, have it available in the maven2
repositories. If you could figure out how to get it callable from
maven, that would be great.
Dan
On Thursday November 02 2006 9:35 am, Mark Little wrote:
> No feedback must mean everyone is happy ;-)
>
> I'll take a look at this the week after next when I get back from
> SCUBA diving in the Red Sea :-) and my broken machine is fixed :-(
>
> Mark.
>
> On 26 Oct 2006, at 23:36, Mark Little wrote:
> > Owing to server outages, this seemed to get lost first time round.
> >
> > Mark.
> >
> > On 23 Oct 2006, at 18:47, Mark Little wrote:
> >> I notice from looking at the code that although there's an
> >> approach to what log implementation to use for
> >> internationalization/localization support, there's nothing formal
> >> for creating resource bundles. Maybe I missed it though. However,
> >> under the assumption I'm correct, one thing I'd like to suggest to
> >> solve this issue would be to use the resource bundle doclet that
> >> was developed by Hewlett-Packard, and now freely available (under
> >> LGPL) from JBoss. Take a look http://docs.jboss.org/process-guide/
> >> en/html/internationalization.html#d0e3916 and specifically at
> >> 11.2.6 (Creating Resource Bundles). You can ignore the references
> >> to the logger implementation because, as I said above, that seems
> >> to be taken care of already in CXF.
> >>
> >> This doclet has been used successfully in many of the HP NetAction
> >> products (in 2000/2001/2002) and subsequently in the Arjuna
> >> Transaction Service/Message Service implementations. If this looks
> >> to be of interest, then I'd be happy to work with whoever to
> >> incorporate the ant task that runs the doclet into the build
> >> scripts and produce an update to the wiki page for developers to
> >> follow when writing text that goes into a resource bundle. I know
> >> it's covered by LGPL, but I assume that since this would only
> >> affect the building of CXF and not something that gets shipped
> >> with the product, it should be alright to use.
> >>
> >> Mark.
> >>
> >> On 6 Oct 2006, at 23:06, Mark Little wrote:
> >>> I'll take a look at the wiki page and come up to speed on that.
> >>>
> >>> Thanks,
> >>>
> >>> Mark.
> >>>
> >>> On 6 Oct 2006, at 21:09, Daniel Kulp wrote:
> >>>> Mark,
> >>>>
> >>>> On Friday October 06 2006 3:57 pm, Mark Little wrote:
> >>>>> Your I18N reference got me thinking. Can someone point me at
> >>>>> the I18N/
> >>>>> L10N approach taken for CXF? What I mean is the rules and tools
> >>>>> for
> >>>>> generating resource bundles and using them within the code. If
> >>>>> there's no solution in place, we may have an open source tool
> >>>>> that the project might want to consider.
> >>>>
> >>>> There is some "older" stuff on the old Celtix wiki related to
> >>>> that:
> >>>> http://wiki.objectweb.org/celtix/Wiki.jsp?page=Internationalizatio
> >>>>n and:
> >>>> http://wiki.objectweb.org/celtix/Wiki.jsp?page=CeltixLogging
> >>>>
> >>>> Not a lot though and what is there needs to be copied to the CXF
> >>>> space.
> >>>>
> >>>> Good question though. :-)
> >>>>
> >>>> If you see areas in the code that aren't doing the I18N stuff,
> >>>> file bugs
> >>>> (or fix it).
> >>>>
> >>>> Thanks!
> >>>> --
> >>>> J. Daniel Kulp
> >>>> Principal Engineer
> >>>> IONA
> >>>> P: 781-902-8727 C: 508-380-7194 F:781-902-8001
> >>>> daniel.kulp@iona.com
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194 F:781-902-8001
daniel.kulp@iona.com
Re: I18N and L10N stuff...
Posted by Mark Little <ma...@jboss.com>.
No feedback must mean everyone is happy ;-)
I'll take a look at this the week after next when I get back from
SCUBA diving in the Red Sea :-) and my broken machine is fixed :-(
Mark.
On 26 Oct 2006, at 23:36, Mark Little wrote:
> Owing to server outages, this seemed to get lost first time round.
>
> Mark.
>
>
> On 23 Oct 2006, at 18:47, Mark Little wrote:
>
>> I notice from looking at the code that although there's an
>> approach to what log implementation to use for
>> internationalization/localization support, there's nothing formal
>> for creating resource bundles. Maybe I missed it though. However,
>> under the assumption I'm correct, one thing I'd like to suggest to
>> solve this issue would be to use the resource bundle doclet that
>> was developed by Hewlett-Packard, and now freely available (under
>> LGPL) from JBoss. Take a look http://docs.jboss.org/process-guide/
>> en/html/internationalization.html#d0e3916 and specifically at
>> 11.2.6 (Creating Resource Bundles). You can ignore the references
>> to the logger implementation because, as I said above, that seems
>> to be taken care of already in CXF.
>>
>> This doclet has been used successfully in many of the HP NetAction
>> products (in 2000/2001/2002) and subsequently in the Arjuna
>> Transaction Service/Message Service implementations. If this looks
>> to be of interest, then I'd be happy to work with whoever to
>> incorporate the ant task that runs the doclet into the build
>> scripts and produce an update to the wiki page for developers to
>> follow when writing text that goes into a resource bundle. I know
>> it's covered by LGPL, but I assume that since this would only
>> affect the building of CXF and not something that gets shipped
>> with the product, it should be alright to use.
>>
>> Mark.
>>
>>
>>
>> On 6 Oct 2006, at 23:06, Mark Little wrote:
>>
>>> I'll take a look at the wiki page and come up to speed on that.
>>>
>>> Thanks,
>>>
>>> Mark.
>>>
>>>
>>> On 6 Oct 2006, at 21:09, Daniel Kulp wrote:
>>>
>>>>
>>>> Mark,
>>>>
>>>> On Friday October 06 2006 3:57 pm, Mark Little wrote:
>>>>> Your I18N reference got me thinking. Can someone point me at
>>>>> the I18N/
>>>>> L10N approach taken for CXF? What I mean is the rules and tools
>>>>> for
>>>>> generating resource bundles and using them within the code. If
>>>>> there's no solution in place, we may have an open source tool that
>>>>> the project might want to consider.
>>>>
>>>> There is some "older" stuff on the old Celtix wiki related to that:
>>>> http://wiki.objectweb.org/celtix/Wiki.jsp?page=Internationalization
>>>> and:
>>>> http://wiki.objectweb.org/celtix/Wiki.jsp?page=CeltixLogging
>>>>
>>>> Not a lot though and what is there needs to be copied to the CXF
>>>> space.
>>>>
>>>> Good question though. :-)
>>>>
>>>> If you see areas in the code that aren't doing the I18N stuff,
>>>> file bugs
>>>> (or fix it).
>>>>
>>>> Thanks!
>>>> --
>>>> J. Daniel Kulp
>>>> Principal Engineer
>>>> IONA
>>>> P: 781-902-8727 C: 508-380-7194 F:781-902-8001
>>>> daniel.kulp@iona.com
>>
Re: I18N and L10N stuff...
Posted by Mark Little <ma...@jboss.com>.
Owing to server outages, this seemed to get lost first time round.
Mark.
On 23 Oct 2006, at 18:47, Mark Little wrote:
> I notice from looking at the code that although there's an approach
> to what log implementation to use for internationalization/
> localization support, there's nothing formal for creating resource
> bundles. Maybe I missed it though. However, under the assumption
> I'm correct, one thing I'd like to suggest to solve this issue
> would be to use the resource bundle doclet that was developed by
> Hewlett-Packard, and now freely available (under LGPL) from JBoss.
> Take a look http://docs.jboss.org/process-guide/en/html/
> internationalization.html#d0e3916 and specifically at 11.2.6
> (Creating Resource Bundles). You can ignore the references to the
> logger implementation because, as I said above, that seems to be
> taken care of already in CXF.
>
> This doclet has been used successfully in many of the HP NetAction
> products (in 2000/2001/2002) and subsequently in the Arjuna
> Transaction Service/Message Service implementations. If this looks
> to be of interest, then I'd be happy to work with whoever to
> incorporate the ant task that runs the doclet into the build
> scripts and produce an update to the wiki page for developers to
> follow when writing text that goes into a resource bundle. I know
> it's covered by LGPL, but I assume that since this would only
> affect the building of CXF and not something that gets shipped with
> the product, it should be alright to use.
>
> Mark.
>
>
>
> On 6 Oct 2006, at 23:06, Mark Little wrote:
>
>> I'll take a look at the wiki page and come up to speed on that.
>>
>> Thanks,
>>
>> Mark.
>>
>>
>> On 6 Oct 2006, at 21:09, Daniel Kulp wrote:
>>
>>>
>>> Mark,
>>>
>>> On Friday October 06 2006 3:57 pm, Mark Little wrote:
>>>> Your I18N reference got me thinking. Can someone point me at the
>>>> I18N/
>>>> L10N approach taken for CXF? What I mean is the rules and tools for
>>>> generating resource bundles and using them within the code. If
>>>> there's no solution in place, we may have an open source tool that
>>>> the project might want to consider.
>>>
>>> There is some "older" stuff on the old Celtix wiki related to that:
>>> http://wiki.objectweb.org/celtix/Wiki.jsp?page=Internationalization
>>> and:
>>> http://wiki.objectweb.org/celtix/Wiki.jsp?page=CeltixLogging
>>>
>>> Not a lot though and what is there needs to be copied to the CXF
>>> space.
>>>
>>> Good question though. :-)
>>>
>>> If you see areas in the code that aren't doing the I18N stuff,
>>> file bugs
>>> (or fix it).
>>>
>>> Thanks!
>>> --
>>> J. Daniel Kulp
>>> Principal Engineer
>>> IONA
>>> P: 781-902-8727 C: 508-380-7194 F:781-902-8001
>>> daniel.kulp@iona.com
>
Re: I18N and L10N stuff...
Posted by Mark Little <ma...@jboss.com>.
I'll take a look at the wiki page and come up to speed on that.
Thanks,
Mark.
On 6 Oct 2006, at 21:09, Daniel Kulp wrote:
>
> Mark,
>
> On Friday October 06 2006 3:57 pm, Mark Little wrote:
>> Your I18N reference got me thinking. Can someone point me at the
>> I18N/
>> L10N approach taken for CXF? What I mean is the rules and tools for
>> generating resource bundles and using them within the code. If
>> there's no solution in place, we may have an open source tool that
>> the project might want to consider.
>
> There is some "older" stuff on the old Celtix wiki related to that:
> http://wiki.objectweb.org/celtix/Wiki.jsp?page=Internationalization
> and:
> http://wiki.objectweb.org/celtix/Wiki.jsp?page=CeltixLogging
>
> Not a lot though and what is there needs to be copied to the CXF
> space.
>
> Good question though. :-)
>
> If you see areas in the code that aren't doing the I18N stuff, file
> bugs
> (or fix it).
>
> Thanks!
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194 F:781-902-8001
> daniel.kulp@iona.com
I18N and L10N stuff...
Posted by Daniel Kulp <da...@iona.com>.
Mark,
On Friday October 06 2006 3:57 pm, Mark Little wrote:
> Your I18N reference got me thinking. Can someone point me at the I18N/
> L10N approach taken for CXF? What I mean is the rules and tools for
> generating resource bundles and using them within the code. If
> there's no solution in place, we may have an open source tool that
> the project might want to consider.
There is some "older" stuff on the old Celtix wiki related to that:
http://wiki.objectweb.org/celtix/Wiki.jsp?page=Internationalization
and:
http://wiki.objectweb.org/celtix/Wiki.jsp?page=CeltixLogging
Not a lot though and what is there needs to be copied to the CXF space.
Good question though. :-)
If you see areas in the code that aren't doing the I18N stuff, file bugs
(or fix it).
Thanks!
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194 F:781-902-8001
daniel.kulp@iona.com
I18N/L10N
Posted by Mark Little <ma...@jboss.com>.
Sending again, with a more appropriate subject line.
Mark.
On 6 Oct 2006, at 20:57, Mark Little wrote:
>
> On 6 Oct 2006, at 19:01, Daniel Kulp wrote:
>>
>> 5) Already I18N capable. :-) Seriously, we had some chats on IRC
>> about "how to pronounce" some of the other ideas. Example:
>> Apparently the
>> word "foam" is hard to pronounce in some locales. Also, "Celtic" is
>> pronounced different in various locales as well.
>
> Your I18N reference got me thinking. Can someone point me at the
> I18N/L10N approach taken for CXF? What I mean is the rules and
> tools for generating resource bundles and using them within the
> code. If there's no solution in place, we may have an open source
> tool that the project might want to consider.
>
> Mark.
>
>
Re: [VOTE] Officially rename the project to Apache CXF
Posted by Mark Little <ma...@jboss.com>.
On 6 Oct 2006, at 19:01, Daniel Kulp wrote:
>
> 5) Already I18N capable. :-) Seriously, we had some chats on IRC
> about "how to pronounce" some of the other ideas. Example:
> Apparently the
> word "foam" is hard to pronounce in some locales. Also, "Celtic" is
> pronounced different in various locales as well.
Your I18N reference got me thinking. Can someone point me at the I18N/
L10N approach taken for CXF? What I mean is the rules and tools for
generating resource bundles and using them within the code. If
there's no solution in place, we may have an open source tool that
the project might want to consider.
Mark.
Re: [VOTE][RESULT] Officially rename the project to Apache CXF
Posted by Kevin Conner <Ke...@jboss.com>.
Christoph Sturm wrote:
> doesnt apache style voting work in a way that one -1 is a veto and
> thus the proposal cant be accepted?
I believe this is only true of code modifications.
Kev
Re: [VOTE][RESULT] Officially rename the project to Apache CXF
Posted by Daniel Kulp <da...@iona.com>.
> On 10/9/06, Daniel Kulp <da...@iona.com> wrote:
> > 14 +1s (12 binding)
> > 1 +0s (1 binding)
> > 1 0s (1 binding)
> > 1 -1 (1 binding)
> >
> > Congrats! We have a name, at least for now. :-)
>
> doesnt apache style voting work in a way that one -1 is a veto and
> thus the proposal cant be accepted?
From:
http://apache.org/foundation/voting.html
Votes on procedural issues follow the common format of majority rule
unless otherwise stated. That is, if there are more favourable votes than
unfavorable ones, the issue is considered to have passed.
For the most part, there are only two votes where a -1 is a veto:
1) Code modifications - the -1 must also have a technical reason for the
veto.
2) In the Incubator, the iPMC can "veto" a release. Like a code
modification, there should be a technical reason that the podling should
fix to turn the -1 into a +1. Out of the incubator, a release isn't
veto-able.
Enjoy!
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194 F:781-902-8001
daniel.kulp@iona.com
Re: [VOTE][RESULT] Officially rename the project to Apache CXF
Posted by Christoph Sturm <ch...@gmail.com>.
hey
On 10/9/06, Daniel Kulp <da...@iona.com> wrote:
>
> 14 +1s (12 binding)
> 1 +0s (1 binding)
> 1 0s (1 binding)
> 1 -1 (1 binding)
>
> Congrats! We have a name, at least for now. :-)
>
doesnt apache style voting work in a way that one -1 is a veto and
thus the proposal cant be accepted?
regards
chris
[VOTE][RESULT] Officially rename the project to Apache CXF
Posted by Daniel Kulp <da...@iona.com>.
This vote has passed with: (using everyone on the initial commiter list
on the proposal as "binding" votes)
+1 (dkulp, ejohnson, asakala, dmoynihan, mlittle, bravi, pjones,
jjagielski, kconnor, willem, asmyth, proyal) (nonbind: enolan,
snicholls)
+0 (ddiephouse)
0 (blin)
-1 (mgockel)
14 +1s (12 binding)
1 +0s (1 binding)
1 0s (1 binding)
1 -1 (1 binding)
Congrats! We have a name, at least for now. :-)
Dan
On Friday October 06 2006 2:01 pm, Daniel Kulp wrote:
> I'd like to vote to officially rename the project to Apache CXF.
>
> I'm extremely +1.
>
>
> There are a lot reasons to do so: (summary of previous discussions)
>
> 1) All of our Apache resources are "CXF". If someone goes to apache
> to looking for CeltiXfire using the "normal Apache" URL's and such,
> they won't find it. Example: if they send a note to
> celtixfire-dev-subsribe, it would bounce, etc...
>
> 2) Branding - It seems like all of us are calling it CXF in our
> communication. However, the "Apache Branding" would require it to use
> the full project name. It would be good if it matched to avoid
> confusion for users. (Example: in a note on the incubator list
> during the recent issues, someone asked why we were calling it CXF.)
> Anyway, a lot of people are already associating CXF with the project.
> Let's build on that.
>
> 3) Our package name, jars, install dir, etc.. all use "cxf" right now.
> No work would need to be done there. (I'm lazy, I admit it.)
>
> 4) No wacky CamelCase spellings to cause confusions and branding
> issues. (Celtixfire, CeltiXfire, CeltiXFire, etc..)
>
> 5) Already I18N capable. :-) Seriously, we had some chats on IRC
> about "how to pronounce" some of the other ideas. Example: Apparently
> the word "foam" is hard to pronounce in some locales. Also, "Celtic"
> is pronounced different in various locales as well.
>
> 6) Break some ties with the "messes" that we've been involved in. I
> keep hearing nicknames like "celtic-miss-fire" and such. That's not
> good. The recent events certainly didn't help things. A semi-clean
> slate is probably a good idea. Make them think of new nicknames.
> :-)
>
> 7) However, by keeping the initials, there is "some" tie to the
> previous projects, but the tie is broken enough to make it clear, this
> really is something new and better.
>
> 8) The top two google links for CXF are already our own confluence
> space. Nice job everyone. :-) CXF is an acronym for "Chemical
> eXchange Format", but that really shouldn't matter for us.
>
> Thanks!
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194 F:781-902-8001
> daniel.kulp@iona.com
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194 F:781-902-8001
daniel.kulp@iona.com
Re: [VOTE] Officially rename the project to Apache CXF
Posted by Dan Diephouse <da...@envoisolutions.com>.
I have to agree with Hani that CXF still sucks as a name. However, its
better than CeltiXfire. In principle I'm -1, but in practicality I'm +1
because I haven't heard a better name - so I give it a +0.
- Dan
Hani Suleiman wrote:
> Oh I dunno, adoption? Community acceptance? The whole minor issue of
> brand?
>
> It's a silly name that'd hard to type, hard to pronounce, and means
> absolutely nothing.
>
> On Oct 6, 2006, at 3:17 PM, Peter Jones wrote:
>
>>
>> +1
>>
>> After all, what's in a name? ;)
>>
>> I'd say make the de facto official.
>>
>> Cheers,
>> Peter
>>
>> On Fri, Oct 06, 2006 at 02:01:05PM -0400, Daniel Kulp wrote:
>>
>>>
>>> I'd like to vote to officially rename the project to Apache CXF.
>>>
>>> I'm extremely +1.
>>>
>>>
>>> There are a lot reasons to do so: (summary of previous discussions)
>>> [...]
>>
>>
>> --
>> Peter Jones
>> IONA Technologies Inc.
>> E-Mail: mailto:peter.jones@iona.com
>> Tel: (w) 709-738-3725 x22 | Fax: 709-738-3745
>> 84-86 Elizabeth Ave. St. John's, NL A1A 1W7 Canada
>
>
--
Dan Diephouse
(616) 971-2053
Envoi Solutions LLC
http://netzooid.com
Re: [VOTE] Officially rename the project to Apache CXF
Posted by Hani Suleiman <ha...@formicary.net>.
Oh I dunno, adoption? Community acceptance? The whole minor issue of
brand?
It's a silly name that'd hard to type, hard to pronounce, and means
absolutely nothing.
On Oct 6, 2006, at 3:17 PM, Peter Jones wrote:
>
> +1
>
> After all, what's in a name? ;)
>
> I'd say make the de facto official.
>
> Cheers,
> Peter
>
> On Fri, Oct 06, 2006 at 02:01:05PM -0400, Daniel Kulp wrote:
>>
>> I'd like to vote to officially rename the project to Apache CXF.
>>
>> I'm extremely +1.
>>
>>
>> There are a lot reasons to do so: (summary of previous discussions)
>> [...]
>
> --
> Peter Jones
> IONA Technologies Inc.
> E-Mail: mailto:peter.jones@iona.com
> Tel: (w) 709-738-3725 x22 | Fax: 709-738-3745
> 84-86 Elizabeth Ave. St. John's, NL A1A 1W7 Canada
Re: [VOTE] Officially rename the project to Apache CXF
Posted by Peter Jones <pe...@iona.com>.
+1
After all, what's in a name? ;)
I'd say make the de facto official.
Cheers,
Peter
On Fri, Oct 06, 2006 at 02:01:05PM -0400, Daniel Kulp wrote:
>
> I'd like to vote to officially rename the project to Apache CXF.
>
> I'm extremely +1.
>
>
> There are a lot reasons to do so: (summary of previous discussions)
> [...]
--
Peter Jones
IONA Technologies Inc.
E-Mail: mailto:peter.jones@iona.com
Tel: (w) 709-738-3725 x22 | Fax: 709-738-3745
84-86 Elizabeth Ave. St. John's, NL A1A 1W7 Canada