Thanks, Shane! We appreciate your guidance. James
On Fri, Oct 4, 2013 at 5:12 PM, Shane Curcuru <a...@shanecurcuru.org> wrote: > (Please note the mix of mailing lists) > > The most important thing is that Apache product brands are referred to by > their full name - i.e. Apache Camel - in at least both the first and most > prominent places in a document. That means the title (either graphically in > the display, or the window title in a PDF viewer, whatever) should include > "Apache Camel" wherever practical. > > Beyond that, this looks like a great poster; I wasn't even aware of how many > different direct integration points are already out there! > > Since this is clearly educational materials, a cheatsheet, or additional > documentation about Apache Camel and related software that goes above and > beyond what the camel.apache.org website provides as normal documentation, > it's perfectly appropriate to include a footer or other "Created by" > attribution for whoever does the work to create this. So the logo in the > footer is fine, especially because it's not directly with the Camel name or > logo. It's certainly appropriate for your company to get credit for the > design! > > As a volunteer-run public charity that produces software for the public > good, we need to ensure that our trademarks are respected, especially by > software vendors of all stripes. However outside individuals and companies > producing extra educational materials about Apache software - like training, > books, and cool API docs like this - can help users to find out about and > make use of Apache software, which is a benefit to everyone. As long as our > brands are respected, we definitely appreciate the work people do like this. > > Thanks, > - Shane Curcuru > VP, Brand Management > > > > > On 10/4/13 5:00 PM, Christian Müller wrote: >> >> Hi Robert! >> >> Thanks for your good work. We appreciate it. It looks really cool and I >> think this poster provides a good overview which components do we have >> in each particular area. >> >> As outlined in [1] and mentioned by James, you should >> - refer to "The Apache Camel Components Poster" instead of "The Camel >> Components Poster" >> >> Thanks for your cooperation and willing to update the poster. >> >> I don't think it's an issue to have the "GLIESIAN, LLC." whatermark and >> footer, but prefer to have the trademarks ok. Therefore, I also put >> trademarks@ in CC to request their permission that you can publish/sell >> this poster [2] after the mentioned update. >> >> [1] http://www.apache.org/foundation/marks/#guidelines >> [2] http://gliesian.com/camel/TheCamelComponentPosterWithWatermark.pdf >> >> Best, >> >> Christian Müller >> V.P. Apache Camel >> >> >> On Fri, Oct 4, 2013 at 12:22 AM, gliesian <glies...@yahoo.com >> <mailto:glies...@yahoo.com>> wrote: >> >> Hi James, >> >> I looked at the cover of the "Camel in Action" book and "Apache" is >> not >> mentioned anywhere: >> >> http://www.amazon.com/Camel-Action-Claus-Ibsen/dp/1935182366/ref=sr_1_1?ie=UTF8&qid=1380838736&sr=8-1&keywords=camel+in+action >> >> So, I figured that the approach I took with the title of the poster >> was >> okay, "The Camel Components Poster". >> >> I do mention Apache in a few places on the poster... >> (1) Bottom left: Camel Components (Apache and External) >> (2) Bottom right: http://camel.apache.org/components.html >> (3) In some of the descriptions: e.g. Apache ServiceMix. >> >> I can update the poster anyway that is appropriate, please just let >> me know >> exactly what to do, and I will do it. >> >> Sincerely, >> Robert Liguori >> >> >> >> >> >> -- >> View this message in context: >> >> http://camel.465427.n5.nabble.com/The-Camel-Components-Poster-PDF-FREE-tp5740752p5740847.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> >> >
