Hi Jürgen,

Jürgen Ragaller schrieb:

[…]

To promote the Lenya Design Contest I created a visual element for the Contest (you can find it on the same page).
What do you think about it?

IMO this is a good idea. Would it be possible to use the standard Lenya logo (incl. the brand name "apache" and the feather)? I think there should be only one version of the logo (the "built with" is a compromise because of the narrow column width).

You're right. We should use one Lenya logo. What about promoting the design contest as an addition to the Logo - see my latest suggestion. I got carried away a bit with the previous suggestion ;-). Logo-Design is a nice thing...

I like this one better than the previous one. I'm not sure how attached you are to your creation – a friend of mine is a designer and familiar with logos and such things, shall I ask her if she'd like to make another suggestion?


I added a bugzilla entry for the redesign contest
https://issues.apache.org/bugzilla/show_bug.cgi?id=46887
- the description «bug»-description needs some changes...- I doubt it is still possible to change it.
Does anyone now how to change a bug-description?

? - I might have to delete the existing one and create a new one.

Yes, I guess the only other option would be to ask the infrastructure team to give you permissions for the Bugzilla DB :)

My suggestion about the time line of the contest would be to end it at the end of may.

+1

I put in the dates for the timeline.

TODO:
- Promote the contest

Unfortunately I can't change any wiki pages ATM (I contacted infra@), but I'd offer to publish the announcement on these sites:

* Facebook: Apache Lenya group
* cocoonforum.de
* becompany.ch
* cmswire.com (request)
* apachenews.org (request)
* Xing: Content Management group, Web-Design group

-- Andreas


--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to