in that case how about a logo for "Java Servlets", "JSP", "JPA", "JDBC" and "JTA" also :)

so, no logo == no identity ? not sure I am convinced about this argument or the case to have a logo for a spec but with that said its just my opinion.

Lets move forward with the logo contest. JSF is great, and there are 100 different marketings reasons why you should always establish a symbol for your brand or product - something that people recognize instantly as yours (the google G, the microsoft "window", Tony the Tiger..., Firefox, the ruby gem) Perl and JSF have a lot in common... multiple implementations slightly tarnished reputation from past versions (not so slightly in perl's case) no logo... the Camel book has become the de-facto symbol of Perl. No real web-accessible community center (multiple forums & mailing lists) What happened to perl? It's one of the best dynamic languages out there, but it's practically dead for new development. I'd like to avoid this fate with JSF2 if possible, and now is the perfect time to do it. Right as we are releasing, rebranding. --- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple" On Mon, 2009-11-09 at 16:15 -0500, Dan Allen wrote: > JSF is nearly a decade old and still has no recognizable logo. > While there are plenty of logos floating around for the different > implementations and component libraries, there's no face for JSF > itself. I've frequently come across this gap when putting together > presentations or websites that feature JSF. > > Thus, I pose the following two questions to the EG: > > 1. Do others agree that we should have a logo to represent JSF the > framework? > 2. Do you think we should host a contest for people to submit a > logo? The alternative would be to get an EG member (JBoss, Oracle, > Sun, an individual) to submit a candidate. > > Why a logo for JSF? JSF is unique in that it competes against other > web frameworks that are not part of the Java EE platform. We need > someway to represent the spec when standing JSF up against Wicket, > Tapestry, Struts, etc. We can't put the Mojarra or MyFaces logos in > there because that's not the true identity of JSF. > > Plus, the logo will be central to our effort to put together a > launch page for JSF, which I'll mention in a later e-mail. > > -Dan > > p.s. Hopefully we start a trend of specs including logos, even the > platform itself, but that is a topic for another conversation. > > -- > Dan Allen > Senior Software Engineer, Red Hat | Author of Seam in Action > Registered Linux User #231597 > > http://mojavelinux.com > http://mojavelinux.com/seaminaction > http://www.google.com/profiles/dan.j.allen

I'd have to disagree WRT Perl. It's long overdue for the death it so richly deserves. :P I do agree, though, with trying to come up with a logo for JSF. My failed attempts at crafting a logo for my local JUG is the best evidence that I can only contribute opinions and not options, though. :) On Nov 9, 2009, at 4:13 PM, Lincoln Baxter III wrote: > Lets move forward with the logo contest. > > JSF is great, and there are 100 different marketings reasons why you > should always establish a symbol for your brand or product - > something that people recognize instantly as yours (the google G, > the microsoft "window", Tony the Tiger..., Firefox, the ruby gem) > > Perl and JSF have a lot in common... > * multiple implementations > * slightly tarnished reputation from past versions (not so > slightly in perl's case) > * no logo... the Camel book has become the de-facto symbol of > Perl. > * No real web-accessible community center (multiple forums & > mailing lists) > What happened to perl? It's one of the best dynamic languages out > there, but it's practically dead for new development. > > I'd like to avoid this fate with JSF2 if possible, and now is the > perfect time to do it. Right as we are releasing, rebranding. > > --- > Lincoln Baxter, III > http://ocpsoft.com > http://scrumshark.com > "Keep it Simple" > > > On Mon, 2009-11-09 at 16:15 -0500, Dan Allen wrote: > > > JSF is nearly a decade old and still has no recognizable logo. > > While there are plenty of logos floating around for the different > > implementations and component libraries, there's no face for JSF > > itself. I've frequently come across this gap when putting together > > presentations or websites that feature JSF. > > > > Thus, I pose the following two questions to the EG: > > > > 1. Do others agree that we should have a logo to represent JSF the > > framework? > > 2. Do you think we should host a contest for people to submit a > > logo? The alternative would be to get an EG member (JBoss, Oracle, > > Sun, an individual) to submit a candidate. > > > > Why a logo for JSF? JSF is unique in that it competes against > > other web frameworks that are not part of the Java EE platform. We > > need someway to represent the spec when standing JSF up against > > Wicket, Tapestry, Struts, etc. We can't put the Mojarra or MyFaces > > logos in there because that's not the true identity of JSF. > > > > Plus, the logo will be central to our effort to put together a > > launch page for JSF, which I'll mention in a later e-mail. > > > > -Dan > > > > p.s. Hopefully we start a trend of specs including logos, even the > > platform itself, but that is a topic for another conversation. > > > > -- > > Dan Allen > > Senior Software Engineer, Red Hat | Author of Seam in Action > > Registered Linux User #231597 > > > > http://mojavelinux.com > > http://mojavelinux.com/seaminaction > > http://www.google.com/profiles/dan.j.allen Jason Lee, SCJP President, Oklahoma City Java Users Group Senior Java Developer, Sun Microsystems http://blogs.steeplesoft.com

+1 for a logo. It helps unify the different implementations and also helps with branding.

On Tue, Nov 10, 2009 at 5:35 PM, Dan Allen <dan.j.allen(a)gmail.com&gt; wrote: > On Tue, Nov 10, 2009 at 6:29 AM, Kito Mann <kito.mann(a)virtua.com&gt; wrote: > >> +1 for a logo. It helps unify the different implementations and also >> helps with branding. >> > > Great. I think this would be great to announce before JSF Summit so that > we can promote it there and build interest in submitting candidates. > > Lincoln and I will work on drafting the contest announcement. We'll post a > draft here for review and additional buy-in. > > Are there any legal concerns we have to consider before moving forward? If > not, Kito, would you be willing post the announcement about the contest > (when it is ready) on JSFCentral.com? Do you have a recommendation for how > to accept entries? An upload area or e-mail inbox? > No problem with announcing it on JSFCentral. I think e-mail is probably fine, as the volume is relatively low for these sort of contests, isn't it?