You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Sean Schofield <se...@gmail.com> on 2005/05/30 16:21:01 UTC
Suggested codenames for new components subproject
Since a few of the developers don't like tomahawk :-( I wanted to
start a thread for name / code-name ideas for a components + goodies
subproject. I don't have any ideas offhand but lets get a list
together and pick one.
I know Manfred had a few suggestions when we last discussed this ...
sean
Re: Suggested codenames for new components subproject
Posted by Sylvain Vieujot <sv...@apache.org>.
I agree too on a meaningful name.
On Mon, 2005-05-30 at 14:33 -0400, Matt Blum wrote:
> I agree with Martin.
>
> I think a boring name like "components" would be much more meaningful
> than a cool name like "tomahawk."
>
> -Matt
>
>
> On 5/30/05, Martin Cooper <ma...@apache.org> wrote:
>
> I would suggest picking a meaningful name rather than some
> kind of code
> name, in the interest of transparency to your users. Someone
> seeing
> references to tomahawk or lonewolf or moccasin is going to
> have no clue
> what it's about. (This is why Jakarta Commons has a guideline
> on using
> meaningful names instead of "cool" names.)
>
> Oh, and by the way, a moccasin is also a kind of dangerous
> snake. ;-)
>
> --
> Martin Cooper
>
>
> On Mon, 30 May 2005, Sean Schofield wrote:
>
> > Since a few of the developers don't like tomahawk :-( I
> wanted to
> > start a thread for name / code-name ideas for a components +
> goodies
> > subproject. I don't have any ideas offhand but lets get a
> list
> > together and pick one.
> >
> > I know Manfred had a few suggestions when we last discussed
> this ...
> >
> > sean
> >
>
>
Re: Suggested codenames for new components subproject
Posted by Sylvain Vieujot <sv...@apache.org>.
Same for me.
+1 for Apache Faces Extensions
On Tue, 2005-05-31 at 09:11 -0700, Jon Travis wrote:
> I like this one best of all, actually.
>
> Can't tell you how much time I've spent making fun of jakarta
> projects based on their stupid names -- just looking at the
> subprojects now: "Cactus", "Slide", "Alexandria", "Agila",
> "Tomcat", "Velocity"
>
> They make no sense -- it's nice to see what a project has some
> association with by just looking at the name.
>
> -- Jon
>
>
> On May 31, 2005, at 8:52 AM, Martin Cooper wrote:
>
> >
> >
> > On Tue, 31 May 2005, Manfred Geiler wrote:
> >
> >
> >> 2005/5/31, Martin Marinschek <ma...@gmail.com>:
> >>
> >>> Oh my,
> >>>
> >>> I wonder where we will end up with this discussion!
> >>>
> >>
> >> That's what marketing departments are doing the whole day long, isn't
> >> it? Well, we do not have a marketing department. So, let's collect
> >> some further ideas. At the same time let's do not take this all too
> >> serious. Let's have fun. ;-)
> >>
> >> At least we have some kind of agreement on some parts of the official
> >> long name, right?
> >> It must contain "Apache" and it should contain "Faces" and
> >> "Extensions". So, we will finally end up in a name of the kind
> >> "Apache
> >> ... Faces Extensions". Right?
> >>
> >
> > So why not just Apache Faces Extensions? We're talking about
> > extensions to JSF, and not just MyFaces, and the added components
> > are also extensions of JSF, so Apache Faces Extensions says it all.
> >
> > --
> > Martin Cooper
> >
> >
> >
> >> Ok, let's try out the latest proposals:
> >> the Apache Tomahawk Faces Extensions project
> >> the Apache Appaloosa Faces Extensions project - short name:
> >> Apache loosa :-)
> >> the Apache Mocassin(s) Faces Extensions project
> >> the Apache Lonewolf Faces Extensions project
> >> the Apache Windeyes Faces Extensions project
> >>
> >> And here is my last minute stupid idea:
> >> Why not initiate a contest on the user list? First prize: a beer
> >> sponsored by me. :-)
> >> At least, that's what marketing departments do, if they are stuck...
> >>
> >> -Manfred
> >>
> >>
> >
> >
> >
>
Re: Suggested codenames for new components subproject
Posted by Jon Travis <jt...@p00p.org>.
I like this one best of all, actually.
Can't tell you how much time I've spent making fun of jakarta
projects based on their stupid names -- just looking at the
subprojects now: "Cactus", "Slide", "Alexandria", "Agila",
"Tomcat", "Velocity"
They make no sense -- it's nice to see what a project has some
association with by just looking at the name.
-- Jon
On May 31, 2005, at 8:52 AM, Martin Cooper wrote:
>
>
> On Tue, 31 May 2005, Manfred Geiler wrote:
>
>
>> 2005/5/31, Martin Marinschek <ma...@gmail.com>:
>>
>>> Oh my,
>>>
>>> I wonder where we will end up with this discussion!
>>>
>>
>> That's what marketing departments are doing the whole day long, isn't
>> it? Well, we do not have a marketing department. So, let's collect
>> some further ideas. At the same time let's do not take this all too
>> serious. Let's have fun. ;-)
>>
>> At least we have some kind of agreement on some parts of the official
>> long name, right?
>> It must contain "Apache" and it should contain "Faces" and
>> "Extensions". So, we will finally end up in a name of the kind
>> "Apache
>> ... Faces Extensions". Right?
>>
>
> So why not just Apache Faces Extensions? We're talking about
> extensions to JSF, and not just MyFaces, and the added components
> are also extensions of JSF, so Apache Faces Extensions says it all.
>
> --
> Martin Cooper
>
>
>
>> Ok, let's try out the latest proposals:
>> the Apache Tomahawk Faces Extensions project
>> the Apache Appaloosa Faces Extensions project - short name:
>> Apache loosa :-)
>> the Apache Mocassin(s) Faces Extensions project
>> the Apache Lonewolf Faces Extensions project
>> the Apache Windeyes Faces Extensions project
>>
>> And here is my last minute stupid idea:
>> Why not initiate a contest on the user list? First prize: a beer
>> sponsored by me. :-)
>> At least, that's what marketing departments do, if they are stuck...
>>
>> -Manfred
>>
>>
>
>
>
Re: Suggested codenames for new components subproject
Posted by Martin Cooper <ma...@apache.org>.
On Tue, 31 May 2005, Manfred Geiler wrote:
> 2005/5/31, Martin Marinschek <ma...@gmail.com>:
>> Oh my,
>>
>> I wonder where we will end up with this discussion!
>
> That's what marketing departments are doing the whole day long, isn't
> it? Well, we do not have a marketing department. So, let's collect
> some further ideas. At the same time let's do not take this all too
> serious. Let's have fun. ;-)
>
> At least we have some kind of agreement on some parts of the official
> long name, right?
> It must contain "Apache" and it should contain "Faces" and
> "Extensions". So, we will finally end up in a name of the kind "Apache
> ... Faces Extensions". Right?
So why not just Apache Faces Extensions? We're talking about extensions to
JSF, and not just MyFaces, and the added components are also extensions of
JSF, so Apache Faces Extensions says it all.
--
Martin Cooper
> Ok, let's try out the latest proposals:
> the Apache Tomahawk Faces Extensions project
> the Apache Appaloosa Faces Extensions project - short name: Apache loosa :-)
> the Apache Mocassin(s) Faces Extensions project
> the Apache Lonewolf Faces Extensions project
> the Apache Windeyes Faces Extensions project
>
> And here is my last minute stupid idea:
> Why not initiate a contest on the user list? First prize: a beer
> sponsored by me. :-)
> At least, that's what marketing departments do, if they are stuck...
>
> -Manfred
>
Re: Suggested codenames for new components subproject
Posted by Sean Schofield <se...@gmail.com>.
Not sure I agree with you that the name should contain Apache Faces
and Extensions (that's pretty long.) Keep in mind its only a
subproject - not a full project.
The full project is Apache MyFaces. I would propose on the website we
have a tab that says "mocassin, tomahawk, lonewolf, whatever ..."
Then when you tab to the page you will see a header like "MyFaces
Components + Goodies aka Tomahawk." This will let the user know that
Tomahawk is really the same thing.
I *really* do not like using the word extensions in the subproject
name. Especially when combined with MyFaces, it implies that the
contents extend MyFaces (which of course they do, but they also extend
the RI.) There are three appropriate words here: 'components',
'extensions/goodies.' An accurate description of this subproject
would require at least two words 'components+extensions' or
'components+goodies.'
So this brings us back to the codename. The codename is just
shorthand for components+goodies. We can still have the subproject's
page describe in more words what the intent of the subproject is. But
the SVN repository and jar file will use the codename.
sean
ps. I like mocassin too and I don't really mind the possible snake
connotation. (I also don't mind the tomahawk or lonewolf connotations
either.)
On 5/31/05, Manfred Geiler <ma...@gmail.com> wrote:
> 2005/5/31, Martin Marinschek <ma...@gmail.com>:
> > Oh my,
> >
> > I wonder where we will end up with this discussion!
>
> That's what marketing departments are doing the whole day long, isn't
> it? Well, we do not have a marketing department. So, let's collect
> some further ideas. At the same time let's do not take this all too
> serious. Let's have fun. ;-)
>
> At least we have some kind of agreement on some parts of the official
> long name, right?
> It must contain "Apache" and it should contain "Faces" and
> "Extensions". So, we will finally end up in a name of the kind "Apache
> ... Faces Extensions". Right?
> Ok, let's try out the latest proposals:
> the Apache Tomahawk Faces Extensions project
> the Apache Appaloosa Faces Extensions project - short name: Apache loosa :-)
> the Apache Mocassin(s) Faces Extensions project
> the Apache Lonewolf Faces Extensions project
> the Apache Windeyes Faces Extensions project
>
> And here is my last minute stupid idea:
> Why not initiate a contest on the user list? First prize: a beer
> sponsored by me. :-)
> At least, that's what marketing departments do, if they are stuck...
>
> -Manfred
>
Re: Suggested codenames for new components subproject
Posted by Manfred Geiler <ma...@gmail.com>.
2005/5/31, Martin Marinschek <ma...@gmail.com>:
> Oh my,
>
> I wonder where we will end up with this discussion!
That's what marketing departments are doing the whole day long, isn't
it? Well, we do not have a marketing department. So, let's collect
some further ideas. At the same time let's do not take this all too
serious. Let's have fun. ;-)
At least we have some kind of agreement on some parts of the official
long name, right?
It must contain "Apache" and it should contain "Faces" and
"Extensions". So, we will finally end up in a name of the kind "Apache
... Faces Extensions". Right?
Ok, let's try out the latest proposals:
the Apache Tomahawk Faces Extensions project
the Apache Appaloosa Faces Extensions project - short name: Apache loosa :-)
the Apache Mocassin(s) Faces Extensions project
the Apache Lonewolf Faces Extensions project
the Apache Windeyes Faces Extensions project
And here is my last minute stupid idea:
Why not initiate a contest on the user list? First prize: a beer
sponsored by me. :-)
At least, that's what marketing departments do, if they are stuck...
-Manfred
Re: Suggested codenames for new components subproject
Posted by Martin Marinschek <ma...@gmail.com>.
Oh my,
I wonder where we will end up with this discussion!
I like Matt's Appaloosa, but if I leave out the Appa, "loosa" does not
sound too great in my ears ;)
What about coming down to what the components are really about - being
modules, you are able to stack them together and create new things out
of them... Apache Lego is no possibility, I know ;) Maybe we should go
ask a native American about the Apache way of saying box?
I would have suggested Apache Pueblos, but I just learned that Pueblos
are the villages and not the houses, and well, the Pueblos people were
a different tribe, they just did trade with the Apache People... Does
anybody know how the white houses which are stacked to gether to form
a Pueblo (and hence very much resemble to modules to me ;) are called?
Apart from that, I still like Tomahawk the best. I don't mind a
martial name too much, as winning the market of web-application
frameworks is still some kind of war-fare ;)
And I liked Mocassins, too, but it being a deadly snake is a slight
problem I guess, I wouldn't want to wake associations with snakes,
rather a Tomahawk then..
regards,
Martin
On 5/31/05, Matt Blum <mb...@gmail.com> wrote:
> You make some good points. Still, "tomahawk" does have some negative
> connotations. How about "Appaloosa," after the breed of horse, which was
> originally bred by the Nez Perce tribe, and helped them to prosper?
>
> -Matt
>
>
> On 5/30/05, Sean Schofield <se...@gmail.com> wrote:
> > > You might want to take a look at the editor's note here:
> > >
> > >
> http://people.apache.org/~craigmcc/struts-shale-README.html
> > >
> > > for an explanation of why Shale was chosen for that project.
> >
> > I remember Craig's reasoning. My point is that shale is a catchy
> > name. A lot easier way to identify the subproject then calling it
> > "enhanced controller built on JSF."
> >
> > > Um, that last sentence is a non sequitur. Can stand alone => needs
> catchy
> > > name?
> >
> > My point is that this subproject is something that people may end up
> > using independently of MyFaces. If it had a codeword it would be
> > easier for people to refer to it without confusing it with the "core"
> > of MyFaces (which is a JSF implementation.)
> >
> > > If you're going to pick a code name, then I would recommend against
> > > "lonewolf", since it has connotations that are antithetical to The
> Apache
> > > Way and might send the wrong signal. See:
> > >
> > >
> http://www.m-w.com/cgi-bin/dictionary?book=Dictionary&va=lone+wolf&x=10&y=15
> >
> > I am familiar with the definition of lone wolf. Personally I doubt
> > anyone pays much attention to the "signals" a subprojects name might
> > be sending.
> >
> > > Martin Cooper
> >
> > sean
> >
>
>
Re: Suggested codenames for new components subproject
Posted by Matt Blum <mb...@gmail.com>.
You make some good points. Still, "tomahawk" does have some negative
connotations. How about "Appaloosa," after the breed of horse, which was
originally bred by the Nez Perce tribe, and helped them to prosper?
-Matt
On 5/30/05, Sean Schofield <se...@gmail.com> wrote:
>
> > You might want to take a look at the editor's note here:
> >
> > http://people.apache.org/~craigmcc/struts-shale-README.html
> >
> > for an explanation of why Shale was chosen for that project.
>
> I remember Craig's reasoning. My point is that shale is a catchy
> name. A lot easier way to identify the subproject then calling it
> "enhanced controller built on JSF."
>
> > Um, that last sentence is a non sequitur. Can stand alone => needs
> catchy
> > name?
>
> My point is that this subproject is something that people may end up
> using independently of MyFaces. If it had a codeword it would be
> easier for people to refer to it without confusing it with the "core"
> of MyFaces (which is a JSF implementation.)
>
> > If you're going to pick a code name, then I would recommend against
> > "lonewolf", since it has connotations that are antithetical to The
> Apache
> > Way and might send the wrong signal. See:
> >
> >
> http://www.m-w.com/cgi-bin/dictionary?book=Dictionary&va=lone+wolf&x=10&y=15
>
> I am familiar with the definition of lone wolf. Personally I doubt
> anyone pays much attention to the "signals" a subprojects name might
> be sending.
>
> > Martin Cooper
>
> sean
>
Re: Suggested codenames for new components subproject
Posted by Sean Schofield <se...@gmail.com>.
> You might want to take a look at the editor's note here:
>
> http://people.apache.org/~craigmcc/struts-shale-README.html
>
> for an explanation of why Shale was chosen for that project.
I remember Craig's reasoning. My point is that shale is a catchy
name. A lot easier way to identify the subproject then calling it
"enhanced controller built on JSF."
> Um, that last sentence is a non sequitur. Can stand alone => needs catchy
> name?
My point is that this subproject is something that people may end up
using independently of MyFaces. If it had a codeword it would be
easier for people to refer to it without confusing it with the "core"
of MyFaces (which is a JSF implementation.)
> If you're going to pick a code name, then I would recommend against
> "lonewolf", since it has connotations that are antithetical to The Apache
> Way and might send the wrong signal. See:
>
> http://www.m-w.com/cgi-bin/dictionary?book=Dictionary&va=lone+wolf&x=10&y=15
I am familiar with the definition of lone wolf. Personally I doubt
anyone pays much attention to the "signals" a subprojects name might
be sending.
> Martin Cooper
sean
Re: Suggested codenames for new components subproject
Posted by Martin Cooper <ma...@apache.org>.
On Mon, 30 May 2005, Sean Schofield wrote:
> IMO there is nothing wrong with a code name for a subproject. Look no
> further than the shale subproject. Its a lot easier to refer to that
> subproject as shale then to accurately capture that project with a
> "meaningful" one word name.
You might want to take a look at the editor's note here:
http://people.apache.org/~craigmcc/struts-shale-README.html
for an explanation of why Shale was chosen for that project.
> If we picked a codename that had some meaning behind it as well
> (lonewolf) that would be a bonus. We already call the project
> "components" and it is not really accurate as it contains both
> components and extensions. The subproject can stand on its own with
> any RI so IMO its important to give it a catchy shorthand name.
Um, that last sentence is a non sequitur. Can stand alone => needs catchy
name?
If you're going to pick a code name, then I would recommend against
"lonewolf", since it has connotations that are antithetical to The Apache
Way and might send the wrong signal. See:
http://www.m-w.com/cgi-bin/dictionary?book=Dictionary&va=lone+wolf&x=10&y=15
--
Martin Cooper
> sean
>
> On 5/30/05, John Fallows <jo...@gmail.com> wrote:
>> On 5/30/05, Matt Blum <mb...@gmail.com> wrote:
>>> I think a boring name like "components" would be much more meaningful than
>>> a cool name like "tomahawk."
>>
>> We need a balance between boring and cool that both captures
>> attention, yet remains informative.
>>
>> How about Tomahawk Faces Extensions as the official name, with just
>> tomahawk as a convenient short form for mailing lists, etc?
>>
>> Btw, I deliberately say "Extensions" over "Components" above because
>> there is obviously a lot more to extending Faces than just components.
>>
>> Kind Regards,
>> John Fallows.
>>
>
Re: Suggested codenames for new components subproject
Posted by Bruno Aranda <br...@gmail.com>.
I've been thinking all the afternoon-evening (GMT+1) in a meaningful name.
I've been trying to think on something that has to do with 'faces' and that
sounded like an indian name. First, I thought of 'hairs' (which are faces
'extensions'), but did not sound poetic... Then I thought of another
element, related to interface... the eyes... finally I got to the
indian-like name: "windeyes", which sounds good to me.
If I had to choose between lonewolf and tomahawk I would chose 'lonewolf' as
it is less martial and potential peace-lover users will like more...
I agree with John in the official name, that should include
*catchy-short-name* Faces Extensions. I think that names with more than two
syllabes are more difficult to remember, although tomahawk is rather
catchy...
Bruno
2005/5/30, Sean Schofield <se...@gmail.com>:
>
> IMO there is nothing wrong with a code name for a subproject. Look no
> further than the shale subproject. Its a lot easier to refer to that
> subproject as shale then to accurately capture that project with a
> "meaningful" one word name.
>
> If we picked a codename that had some meaning behind it as well
> (lonewolf) that would be a bonus. We already call the project
> "components" and it is not really accurate as it contains both
> components and extensions. The subproject can stand on its own with
> any RI so IMO its important to give it a catchy shorthand name.
>
> sean
>
> On 5/30/05, John Fallows <jo...@gmail.com> wrote:
> > On 5/30/05, Matt Blum <mb...@gmail.com> wrote:
> > > I think a boring name like "components" would be much more meaningful
> than
> > > a cool name like "tomahawk."
> >
> > We need a balance between boring and cool that both captures
> > attention, yet remains informative.
> >
> > How about Tomahawk Faces Extensions as the official name, with just
> > tomahawk as a convenient short form for mailing lists, etc?
> >
> > Btw, I deliberately say "Extensions" over "Components" above because
> > there is obviously a lot more to extending Faces than just components.
> >
> > Kind Regards,
> > John Fallows.
> >
>
Re: Suggested codenames for new components subproject
Posted by Sean Schofield <se...@gmail.com>.
IMO there is nothing wrong with a code name for a subproject. Look no
further than the shale subproject. Its a lot easier to refer to that
subproject as shale then to accurately capture that project with a
"meaningful" one word name.
If we picked a codename that had some meaning behind it as well
(lonewolf) that would be a bonus. We already call the project
"components" and it is not really accurate as it contains both
components and extensions. The subproject can stand on its own with
any RI so IMO its important to give it a catchy shorthand name.
sean
On 5/30/05, John Fallows <jo...@gmail.com> wrote:
> On 5/30/05, Matt Blum <mb...@gmail.com> wrote:
> > I think a boring name like "components" would be much more meaningful than
> > a cool name like "tomahawk."
>
> We need a balance between boring and cool that both captures
> attention, yet remains informative.
>
> How about Tomahawk Faces Extensions as the official name, with just
> tomahawk as a convenient short form for mailing lists, etc?
>
> Btw, I deliberately say "Extensions" over "Components" above because
> there is obviously a lot more to extending Faces than just components.
>
> Kind Regards,
> John Fallows.
>
Re: Suggested codenames for new components subproject
Posted by John Fallows <jo...@gmail.com>.
On 5/30/05, Matt Blum <mb...@gmail.com> wrote:
> I think a boring name like "components" would be much more meaningful than
> a cool name like "tomahawk."
We need a balance between boring and cool that both captures
attention, yet remains informative.
How about Tomahawk Faces Extensions as the official name, with just
tomahawk as a convenient short form for mailing lists, etc?
Btw, I deliberately say "Extensions" over "Components" above because
there is obviously a lot more to extending Faces than just components.
Kind Regards,
John Fallows.
Re: Suggested codenames for new components subproject
Posted by Matt Blum <mb...@gmail.com>.
I agree with Martin.
I think a boring name like "components" would be much more meaningful than a
cool name like "tomahawk."
-Matt
On 5/30/05, Martin Cooper <ma...@apache.org> wrote:
>
> I would suggest picking a meaningful name rather than some kind of code
> name, in the interest of transparency to your users. Someone seeing
> references to tomahawk or lonewolf or moccasin is going to have no clue
> what it's about. (This is why Jakarta Commons has a guideline on using
> meaningful names instead of "cool" names.)
>
> Oh, and by the way, a moccasin is also a kind of dangerous snake. ;-)
>
> --
> Martin Cooper
>
>
> On Mon, 30 May 2005, Sean Schofield wrote:
>
> > Since a few of the developers don't like tomahawk :-( I wanted to
> > start a thread for name / code-name ideas for a components + goodies
> > subproject. I don't have any ideas offhand but lets get a list
> > together and pick one.
> >
> > I know Manfred had a few suggestions when we last discussed this ...
> >
> > sean
> >
>
Re: Suggested codenames for new components subproject
Posted by Martin Cooper <ma...@apache.org>.
I would suggest picking a meaningful name rather than some kind of code
name, in the interest of transparency to your users. Someone seeing
references to tomahawk or lonewolf or moccasin is going to have no clue
what it's about. (This is why Jakarta Commons has a guideline on using
meaningful names instead of "cool" names.)
Oh, and by the way, a moccasin is also a kind of dangerous snake. ;-)
--
Martin Cooper
On Mon, 30 May 2005, Sean Schofield wrote:
> Since a few of the developers don't like tomahawk :-( I wanted to
> start a thread for name / code-name ideas for a components + goodies
> subproject. I don't have any ideas offhand but lets get a list
> together and pick one.
>
> I know Manfred had a few suggestions when we last discussed this ...
>
> sean
>
Re: Suggested codenames for new components subproject
Posted by Sean Schofield <se...@gmail.com>.
Did a search for some apache sites (the native american not the open
source foundation.) Found an interesting name:
Lonewolf
Might be appropriate b/c it can run "standalone" from MyFaces implementation.
Just a thought (still like tomahawk though.)
sean
On 5/30/05, Manfred Geiler <ma...@gmail.com> wrote:
> > Manfred suggested also "mocassins" ;)
>
> Yes!
> These boots are made for walking...
> :-)
>
Re: Suggested codenames for new components subproject
Posted by Manfred Geiler <ma...@gmail.com>.
> Manfred suggested also "mocassins" ;)
Yes!
These boots are made for walking...
:-)
Re: Suggested codenames for new components subproject
Posted by Matthias Wessendorf <mw...@gmail.com>.
I like tomahawk too.
Manfred suggested also "mocassins" ;)
On 5/30/05, Martin Marinschek <ma...@gmail.com> wrote:
> I like tomahawk...
>
> as long as it is buried in the backyard, and therefore stands as a
> symbol for peace ;)
>
>
> regards,
>
> Martin
>
> On 5/30/05, Sean Schofield <se...@gmail.com> wrote:
> > Since a few of the developers don't like tomahawk :-( I wanted to
> > start a thread for name / code-name ideas for a components + goodies
> > subproject. I don't have any ideas offhand but lets get a list
> > together and pick one.
> >
> > I know Manfred had a few suggestions when we last discussed this ...
> >
> > sean
> >
>
--
Matthias Wessendorf
Re: Suggested codenames for new components subproject
Posted by Martin Marinschek <ma...@gmail.com>.
I like tomahawk...
as long as it is buried in the backyard, and therefore stands as a
symbol for peace ;)
regards,
Martin
On 5/30/05, Sean Schofield <se...@gmail.com> wrote:
> Since a few of the developers don't like tomahawk :-( I wanted to
> start a thread for name / code-name ideas for a components + goodies
> subproject. I don't have any ideas offhand but lets get a list
> together and pick one.
>
> I know Manfred had a few suggestions when we last discussed this ...
>
> sean
>