Apache Kato Logo Competition

The Apache Kato logon competition has been opened up for the community to choose a logo to represent the project.
This page has been largely copied from the Apache Solr project, who shared their experiences choosing a logo here: http://wiki.apache.org/solr/LogoContest .

Logo Criteria

The desired concept that the logo is to convey hasn't been decided upon by the community yet. Here are some ideas that have come up in the past:

The name Kato was chosen as he is a famous sidekick, both to the Green Hornet and to Inspector Clouseau in the Pink Panther film series. There is also the Kato Native American tribe, but that association was accidental.
Carrion eaters, such as crows, have been put forward. In some cultures, crows have an association with the souls of the dead.
The Kato Technique, a means of detecting parasite eggs in faeces, has been mentioned. This may be incredibly apt, but it's not an association we want if we want to be taken seriously.

Look and Feel Guidelines

Submissions must include a usable web version (PNG preferred) and a scalable vector, print quality version of the logo
The logo will be used to promote Apache Kato and should evoke the overall Apache Software Foundation brand (community-centric open source development, delivering the highest quality, standards compliant software)
The logo must incorporate the full project name: Apache Kato
- NOTE: The word "Apache" may be in a smaller font then "Kato"
The logo should not incorporate images that are exclusively specific to Native American culture. However, symbols that have broad or multiple meanings are acceptable in evoking a Native American theme. Thus, a feather, which has many possible applications, would be appropriate, but a headdress would not be.
The logo should not incorporate any overt cultural or religious symbolism
The logo may incorporate other imagery, abstract symbols or a catchphrase, so long as the full project name is included somewhere in the logo. To this extent, the full project name can be displayed in a smaller font size than the main image, if there exists a main image
The logo must reflect the values of the community
The logo must adapt well to electronic and print media, to reproduction on small surfaces, and to use in color or in grayscale.
For tips on creating logos suitable for print media, please review this or any other web guides you might find helpful: http://www.sorrentomesa.com/education/techtips.html
If the logo incorporates non-standards fonts, you must be able to provide us with the font should your logo be selected

NOTE - Submissions that do not meet the above criteria will not be considered for voting. If there is any confusion if your submission is valid, feel free to post a message to the user group.

Process & Legal Guidelines

Acknowledgment to the winning entry will be provided on the project web site at http://incubator.apache.org/kato
The Apache Software Foundation reserves the right to select no winning entry, if it deems that the submissions do not meet the needs of the organization
If the Logo is selected, the contributor must assign all rights to the selected images to the Apache Software Foundation
Logo must be free of any copyright or any other intellectual property claims
Logo must not incorporate or extend existing trademarks of other companies

How To Enter

Please attach logo entries to Jira issue KATO-4. You will need a Jira ID if you don't already have one, which you can sign up for at http://issues.apache.org/jira/. Initial submissions may just be the "web" quality image, but if your entry is selected to be the new Kato Log you must provide the "scalable vector, print quality version of the logo" prior to the selecting being official.

When you attach your logo, be sure to choose the option to grant a license to the ASF:

Grant license to ASF for inclusion in ASF works (as per the Apache Software License)

Multiple entries may be submitted by a single person (but bear in mind: voting will be for an entry, not the person who submitted them so multiple entries will compete against each other). If after submitting an entry and getting feedback from people, you would like to replace it with a new entry, you may do this (using the same Jira login) via the manage attachments page.

Supporting "branding" images (ie: favicon, small version, large version, black and white version, etc...) are not necessary, but may be included and considered as a factor by the community when voting.

Voting

Once the Deadline for Submissions has been reached, all of the eligible images will be collected onto a new "ballot" web page for viewing and posted to a new thread with the subject "[VOTE] COMMUNITY LOGO PREFERENCES" on the kato-dev mailing list. Any and all members of the Kato community are encouraged to reply to this thread and list (up to) 5 ranked choices by listing the Jira attachment URLs. Votes will be assigned a point value based on rank. For each vote, 1st choice has a point value of 5, 5th place has a point value of 1, and all others follow a similar pattern.

For example, the following email...

From: A. KatoUser <akatouser@somedomain.tld>
Subject: Re: [VOTE] LOGO PREFERENCES

https://issues.apache.org/jira/secure/attachment/3748234/akato-logo-20090415.jpg https://issues.apache.org/jira/secure/attachment/12347444/akato-logo2-20090416.jpg

...would earn 5 points for akato-logo-20090415.jpg and 4 points for akato-logo2-20090416.jpg

Once the Deadline for Community Voting has been reached, Kato committers will consider the point totals for each Logo from the community vote and a thread with the subject "[VOTE] LOGO" will be started on the kato-dev mailing list where a final (binding) vote will be held. This vote will (most likely) use the same ranked preference method as the community preference vote, however the standard "-1" option for vetoing may also be used (since this is ultimately a vote to commit a change)
Time Line

Deadline for Submissions: TBD.
Deadline for Community Voting: TBD
- (At least 96 Hours after the "ballot" URL has been posted in the "[VOTE] COMMUNITY LOGO PREFERENCES" thread)
Deadline for Binding Committer Vote: TBD
- (At least 96 Hours after the start of the "[VOTE] LOGO" thread with a summary of the community votes)

These deadlines may be extended as needed.

Discussion and Questions

Discussion about any of the Logo Submissions, or questions about the Logo Contest process or rules should be conducted on the kato-dev mailing list.