Re: SUM: Re: Changing the name of the ServiceMix project at the Codehaus
On 11/22/06, Guillaume Nodet [EMAIL PROTECTED] wrote: I was wondering if we could simply shut down the codehaus project and import back the remaining bits at Apache. As these parts depend on jboss (LGPL) or some proprietary libraries (XSQL), i was thinking that we could just import the code in a new area of servicemix (other than trunk) and not release it. Simply importing the code should be ok with legal, as soon as we do not release it afaik. Thoughts ? I'm not sure if incompatible code is allowed to be checked in as a long-term solution, is it? Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://activemq.org/ Apache ServiceMix - http://servicemix.org/ Castor - http://castor.org/
Re: SUM: Re: Changing the name of the ServiceMix project at the Codehaus
I will ask for clarifications on legal general incubator mailing list. On 11/23/06, Bruce Snyder [EMAIL PROTECTED] wrote: On 11/22/06, Guillaume Nodet [EMAIL PROTECTED] wrote: I was wondering if we could simply shut down the codehaus project and import back the remaining bits at Apache. As these parts depend on jboss (LGPL) or some proprietary libraries (XSQL), i was thinking that we could just import the code in a new area of servicemix (other than trunk) and not release it. Simply importing the code should be ok with legal, as soon as we do not release it afaik. Thoughts ? I'm not sure if incompatible code is allowed to be checked in as a long-term solution, is it? Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://activemq.org/ Apache ServiceMix - http://servicemix.org/ Castor - http://castor.org/ -- Cheers, Guillaume Nodet
Re: SUM: Re: Changing the name of the ServiceMix project at the Codehaus
On 9/19/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hej Bruce, bsnyder wrote: Could you please sketch the scope/content of the future codehaus project space in a few sentences? There is no predefined scope. The project at the Codehaus is only used to house addtions Apache ServiceMix that are not compatible with the Apache License. Just as with Apache ServiceMix, anyone can contribute. then IMHO BeyondServiceMix (4 results, with space 9k) and MixDepot (50k results) are best as they fulfill the posted requirements AND describe that anything related to ServiceMix may be placed in the codehaus project. For the first one: Is this already an illegal use of the name ServiceMix? Yeah, the use of ServiceMix is forbidden AFAIK because the ASF owns the term. And as far as MixDepot is concerned, according to http://www.mixdepot.net/, a company named Hybridized Sound holds the copyright. I think we need to keep brainstorming. Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://incubator.apache.org/activemq/ Apache ServiceMix - http://incubator.apache.org/servicemix/ Castor - http://castor.org/
Re: SUM: Re: Changing the name of the ServiceMix project at the Codehaus
On 9/28/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: bsnyder wrote: Yeah, the use of ServiceMix is forbidden AFAIK because the ASF owns the term. And as far as MixDepot is concerned, according to http://www.mixdepot.net/, a company named Hybridized Sound holds the copyright. I think we need to keep brainstorming. Too bad :-( As Smix is speakable (like twix) and sometimes used as abbreviation, we could just replace it, so try SmixDepot, BeyondSmix etc. Some ideas, not checked for any legal stuff smext (servicemix EXTensions) 1k results (similar to to taste in some languages) smixes (like spoken servicemix's) 1k smore (servicemix more), 300k smuff (servicemix stuff) 13k (very similar to snuff, an oral tabacco sold in Sweden) mixus (mix us) 300k CoMo (Components and more), 800M :-( so better combinations like SMixCoMo (zero results) We tend to abbreviate ServiceMix by calling it SMX (ess-emm-exx) and there are usually plays on that. Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://incubator.apache.org/activemq/ Apache ServiceMix - http://incubator.apache.org/servicemix/ Castor - http://castor.org/
Re: SUM: Re: Changing the name of the ServiceMix project at the Codehaus
I often use SMX as initials of ServiceMix. So how about appreviating ServiceMix Extras - Smextra or Smex? Which also include the SMX initials but are quite a different words? On 9/28/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: bsnyder wrote: Yeah, the use of ServiceMix is forbidden AFAIK because the ASF owns the term. And as far as MixDepot is concerned, according to http://www.mixdepot.net/, a company named Hybridized Sound holds the copyright. I think we need to keep brainstorming. Too bad :-( As Smix is speakable (like twix) and sometimes used as abbreviation, we could just replace it, so try SmixDepot, BeyondSmix etc. Some ideas, not checked for any legal stuff smext (servicemix EXTensions) 1k results (similar to to taste in some languages) smixes (like spoken servicemix's) 1k smore (servicemix more), 300k smuff (servicemix stuff) 13k (very similar to snuff, an oral tabacco sold in Sweden) mixus (mix us) 300k CoMo (Components and more), 800M :-( so better combinations like SMixCoMo (zero results) Georg -- View this message in context: http://www.nabble.com/Changing-the-name-of-the-ServiceMix-project-at-the-Codehaus-tf2203136.html#a6550479 Sent from the ServiceMix - Dev mailing list archive at Nabble.com. -- James --- http://radio.weblogs.com/0112098/
Re: SUM: Re: Changing the name of the ServiceMix project at the Codehaus
Interesting. 'sm' words in English often have negative or derogative connotations: Smut Smack Smug Small Smarm Smash Smatter Smear Smeg Smell Smirch Smit Smite Smithereens Smog Smother Smudge I would advise against 'sm' words for that reason. Other thoughts: intermixable.org overmix.org mixible.org premixed.org Terry
Re: SUM: Re: Changing the name of the ServiceMix project at the Codehaus
Overmix sounds good. On Thu, 28 Sep 2006 19:25 +0100 (BST), Terry Cox [EMAIL PROTECTED] wrote: Interesting. 'sm' words in English often have negative or derogative connotations: Smut Smack Smug Small Smarm Smash Smatter Smear Smeg Smell Smirch Smit Smite Smithereens Smog Smother Smudge I would advise against 'sm' words for that reason. Other thoughts: intermixable.org overmix.org mixible.org premixed.org Terry -- Cheers, Guillaume Nodet
SUM: Re: Changing the name of the ServiceMix project at the Codehaus
Hello from Sweden! I followed this discussion but did not yet get: What shall be hosted at the codehouse project site? Just some few components? Or shall it be a growing, open collection of components? Or something completely different? IMHO a wiki page is perfect for this task: Easy to collaborate keep the overview. Listing commenting proposals. Listing requirements. Reusable for later naming needs. We could always go for ServiceReMix May IMHO confuse outsiders: Is this a fork of the ServiceMix project? Or some kind of other re-use of SM? Well, here are a few that spring to mind to get the creative process rolling: InTheMix IMHO great for components etc, as they will be used inside Servicemix MixCentral MixDepot IMHO great when a bigger bunch of related packages/projects/examples/... shall be hosted/linked. MixBase MixCore May be misunderstood as servicemix-core or other internals BeyondServiceMix nice for things that complement ServiceMix To summarize the requirements: The name shall be * pronouncable (like distinction between acronym and abbreviation, e.g. VoIP and URL are speakable, whereas CSS and SVN are not) * showing clear separation from main project * somehow tying to the main project * search engine friendly (no command characters like - + etc.) * easy to find (not too many other results, even with common spelling errors [e.g. space inbetween single words of a compound one]) * usable in professional contexts, so no similarity (written/spelled/spoken) with swearwords and the like (maybe even in other common languages than just English, so Spanish, Chinese, Arabian, Russian, French, German etc.) Did I miss something? Just add... Have a sunny saturday, Georg -- View this message in context: http://www.nabble.com/Changing-the-name-of-the-ServiceMix-project-at-the-Codehaus-tf2203136.html#a6339623 Sent from the ServiceMix - Dev forum at Nabble.com.
Re: SUM: Re: Changing the name of the ServiceMix project at the Codehaus
On 9/16/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello from Sweden! I followed this discussion but did not yet get: What shall be hosted at the codehouse project site? Just some few components? Or shall it be a growing, open collection of components? Or something completely different? IMHO a wiki page is perfect for this task: Easy to collaborate keep the overview. Listing commenting proposals. Listing requirements. Reusable for later naming needs. We could always go for ServiceReMix May IMHO confuse outsiders: Is this a fork of the ServiceMix project? Or some kind of other re-use of SM? Well, here are a few that spring to mind to get the creative process rolling: InTheMix IMHO great for components etc, as they will be used inside Servicemix MixCentral MixDepot IMHO great when a bigger bunch of related packages/projects/examples/... shall be hosted/linked. MixBase MixCore May be misunderstood as servicemix-core or other internals BeyondServiceMix nice for things that complement ServiceMix To summarize the requirements: The name shall be * pronouncable (like distinction between acronym and abbreviation, e.g. VoIP and URL are speakable, whereas CSS and SVN are not) * showing clear separation from main project * somehow tying to the main project * search engine friendly (no command characters like - + etc.) * easy to find (not too many other results, even with common spelling errors [e.g. space inbetween single words of a compound one]) * usable in professional contexts, so no similarity (written/spelled/spoken) with swearwords and the like (maybe even in other common languages than just English, so Spanish, Chinese, Arabian, Russian, French, German etc.) Did I miss something? Just add... Have a sunny saturday, Georg Georg, the reason for part of the project to remain at the Codehaus is to house any extensions or components for ServiceMix using a license that is not compatible with the Apache License. Please see the following document for more information: http://people.apache.org/~cliffs/3party.html#category-x Regarding the name, the Apache Software Foundation now owns the name ServiceMix, so we're not able to use this name outside of that context. This is why this entire discussion got started. Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache Geronimo - http://geronimo.apache.org/ Apache ActiveMQ - http://incubator.apache.org/activemq/ Apache ServiceMix - http://incubator.apache.org/servicemix/ Castor - http://castor.org/
Re: SUM: Re: Changing the name of the ServiceMix project at the Codehaus
bsnyder wrote: I followed this discussion but did not yet get: What shall be hosted at the codehouse project site? Just some few components? Or shall it be a growing, open collection of components? Or something completely different? Georg, the reason for part of the project to remain at the Codehaus is to house any extensions or components for ServiceMix using a license that is not compatible with the Apache License. ... Regarding the name, the Apache Software Foundation now owns the name ServiceMix, so we're not able to use this name outside of that context. Bruce, thank you for explaining in more detail the reasons why 2 projects are needed :) Could you please sketch the scope/content of the future codehaus project space in a few sentences? Thank you, Georg -- View this message in context: http://www.nabble.com/Changing-the-name-of-the-ServiceMix-project-at-the-Codehaus-tf2203136.html#a6340992 Sent from the ServiceMix - Dev forum at Nabble.com.
