camel.js
camel.js copied to clipboard
matthewwilson
Please Rename Your Module...
Your module uses the Apache Software Foundation "Camel" trademark improperly. Can you rename it please?
Nope, if apache have a problem they can email me about it. Claus Ibsen starred this repository so I have approval from the main man!
I am a member of the Camel PMC. So you can consider this as us reaching out.
@matthewcodes I starred the project as I noticed the trademark violation, so I had a bookmark of this project.
A star is not an approval, and as an individual I cannot approve on behalf of the Apache Software Foundation.
This has happened before with others projects, that has been in the same situation where these project owners and their community understood the issue and have resolved this by using a different name.
You can find more details about ASF trademarks / mark at http://www.apache.org/foundation/marks/
Please reconsider this request to rename the project, you can call it something else than camel.js, or apachecamel.js.
If/when this project is renamed and not in violation with ASF trademarks then we from the Apache Camel community is happy to link to this project and for example myself as an individual point people in this direction for Camel-like routing for javascript. We have links to 3rd party projects from various pages such as:
http://camel.apache.org/user-stories.html http://camel.apache.org/components (bottom of this page)
@matthewcodes I think you should take this matter more seriously.
Please be more creative and come up with a realistic project name. Yeah naming projects is a hard problem in IT.
You can be inspired by the animal theme and name it related to that, and maybe with script in the name as its javascript based - or as I guess the ending .js in the name implies its javascript.
This isn't just about renaming the GitHub repository. The entire project is still referring to itself as camel.js ("npm install camel.js" for instance). This needs to be fixed, please.
Sorry, I got an email that said "done" so I came back to check things out. Anyway, the name is verbose. I might not have chosen that, but it's "cute" I guess. I like Claus' suggestion of using some other animal or something, but this is your project, so it's up to you. We just can't have projects calling themselves "camel", as that's a trademark of the foundation. We aren't trying to be difficult with this, but it is the foundation's duty to protect its marks against infringement.
One thing you might consider is donating this code to the Camel project (and the ASF) so that it can actually become "camel.js". I like the idea of having a camel-like library for node. Very interesting. The async nature of node lends itself very nicely to an integration library for sure.
If you want the name to be in the camel space, then maybe you can use one of the other names for camel, such as dromedary.
dromedary.js dromedary-script
And as @jwcarman says it could potential be cool to have Apache Camel module for node/javascript. There has been some people asking for a javascript client library to easily call Camel. Not necessary as a client EIP routing library.