Changes

1* We (the working group) A will draft a logo requirements statement will be drafted -- what Code4Lib is, who we are, and any kind of "messages" or "themes" we think should be considered in the design process.2) * When we're satisfied with the draft, we send it past David Cloutman, who has offered to review it.3) * We make any adjustments we want based on David's feedback.4) * We send it out the Code4Lib list for group comments.5) * We change it, if necessary, based on the feedback.6) * We submit it to Stephanie so she can get started, requesting a few draft concepts for review and feedback.7) * We request volunteers to help review the drafts who have familiarity with the process of selecting a logo.8) * When the draft designs are available, the working group and the volunteers select one design to further develop (if needed)9) * We forward to Stephanie collated suggestions for anything we'd like to see in a final version.

 == Draft Requirements Document ==

Key themes to consider include software, technology, libraries, librarians, participation, openness, and collaboration. Also, the The group is very technically-inclined and savvy about writing, debugging, and deploying software. At the same time, the group has a playful attitude and has fun while doing serious work.

* The organization name (Code4Lib) must be included in the final logo. * The logo must be identifiable. * The logo should be simple and clear in concept. * It must be distinctive in the quality and originality of its visual image and not offend any sensitivities. * The concept should have relevance to the organization. * It must adapt well to electronic and printed media, to reproduction on small surfaces, and to use in color, both in positive and in negative form. * It must be free of any copyright or other intellectual property claims.