Difference between revisions of "Logo Design Process"
m (→History: Fixed a broken URL) |
|||
| (29 intermediate revisions by 15 users not shown) | |||
| Line 1: | Line 1: | ||
| + | __NOTOC__ | ||
This page will document the process we are undertaking to create a logo for Code4Lib. | This page will document the process we are undertaking to create a logo for Code4Lib. | ||
| + | == Working Group == | ||
| + | |||
| − | + | * Roy Tennant | |
| + | * Ranti Junus | ||
| + | * Emily Molanphy | ||
| − | Code4Lib Logo Design Briefing and Requirements | + | == Process == |
| + | |||
| + | * We (the working group) will draft a logo requirements statement -- what Code4Lib is, who we are, and any kind of "messages" or "themes" we think should be considered in the design process. | ||
| + | * When we're satisfied with the draft, we send it past David Cloutman, who has offered to review it. | ||
| + | * We make any adjustments we want based on David's feedback. | ||
| + | * We send it out the Code4Lib list for group comments. | ||
| + | * We change it, if necessary, based on the feedback. | ||
| + | * We submit it to Stephanie so she can get started, requesting a few draft concepts for review and feedback. | ||
| + | * We request volunteers to help review the drafts who have familiarity with the process of selecting a logo. | ||
| + | * When the draft designs are available, the working group and the volunteers select one design to further develop (if needed) | ||
| + | * We forward to Stephanie collated suggestions for anything we'd like to see in a final version. | ||
| + | |||
| + | == Requirements Document == | ||
| + | |||
| + | '''Code4Lib Logo Design Briefing and Requirements''' | ||
| + | |||
| + | ''About Code4Lib'' | ||
| − | |||
Code4Lib is a loose collaboration of library software developers and technologists interested in learning, sharing their experiences, and having fun. There is no "membership", you simply participate. There is no "organization", you simply lead. Anyone who wishes to be involved with an activity (for example, the Code4Lib Journal) simply does it. | Code4Lib is a loose collaboration of library software developers and technologists interested in learning, sharing their experiences, and having fun. There is no "membership", you simply participate. There is no "organization", you simply lead. Anyone who wishes to be involved with an activity (for example, the Code4Lib Journal) simply does it. | ||
There are many ways to participate. Code4Lib offers a web site, a wiki, a chatroom, a mailing list, an RSS aggregation service, a journal, and a conference. | There are many ways to participate. Code4Lib offers a web site, a wiki, a chatroom, a mailing list, an RSS aggregation service, a journal, and a conference. | ||
| − | Key themes to consider include software, technology, libraries, librarians, participation, openness, and collaboration. | + | Key themes to consider include software, technology, libraries, librarians, participation, openness, and collaboration. 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. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| + | ''Logo requirements:'' | ||
| + | * 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. | ||
== History == | == History == | ||
| Line 36: | Line 51: | ||
A [http://serials.infomotions.com/code4lib/archive/2008/200811/1993.html call for volunteers] to draft a requirements document was then made, and Ranti Junus and Emily Molanphy volunteered. | A [http://serials.infomotions.com/code4lib/archive/2008/200811/1993.html call for volunteers] to draft a requirements document was then made, and Ranti Junus and Emily Molanphy volunteered. | ||
| + | |||
| + | On January 5, 2009, Stephanie Brinley submitted a set of [http://roytennant.com/c4ldesigns.pdf draft concepts] and Roy Tennant called for volunteers with experience in a logo design process to view and comment on the concepts. | ||
| + | |||
| + | The following Code4Lib participants volunteered to help review the designs and comment: Sean Hannan, Karen Schneider, Rob Styles, Steve Toub, Tito Sierra, and David Cloutman. | ||
| + | |||
| + | On January 8, 2009, Roy Tennant [http://roytennant.com/1-8-09.txt replied to Stephanie] with the summarized response from the reviewers. | ||
| + | |||
| + | On January 12, 2009, Stephanie Brinley replied with a set of [http://roytennant.com/c4l_finalvariations.pdf final variations] in response to our feedback. | ||
| + | |||
| + | On January 16, 2009, the group decided to go with option #1, while checking with Stephanie that the colors were actual Pantone colors. | ||
| + | |||
| + | On January 29, 2009, Roy Tennant created [https://code4lib.org/2009/01/29/code4lib-logo.html a page on the code4lib web site] for all of the files and instructions. | ||
Latest revision as of 22:38, 13 February 2019
This page will document the process we are undertaking to create a logo for Code4Lib.
Working Group
- Roy Tennant
- Ranti Junus
- Emily Molanphy
Process
- We (the working group) will draft a logo requirements statement -- what Code4Lib is, who we are, and any kind of "messages" or "themes" we think should be considered in the design process.
- When we're satisfied with the draft, we send it past David Cloutman, who has offered to review it.
- We make any adjustments we want based on David's feedback.
- We send it out the Code4Lib list for group comments.
- We change it, if necessary, based on the feedback.
- We submit it to Stephanie so she can get started, requesting a few draft concepts for review and feedback.
- We request volunteers to help review the drafts who have familiarity with the process of selecting a logo.
- When the draft designs are available, the working group and the volunteers select one design to further develop (if needed)
- We forward to Stephanie collated suggestions for anything we'd like to see in a final version.
Requirements Document
Code4Lib Logo Design Briefing and Requirements
About Code4Lib
Code4Lib is a loose collaboration of library software developers and technologists interested in learning, sharing their experiences, and having fun. There is no "membership", you simply participate. There is no "organization", you simply lead. Anyone who wishes to be involved with an activity (for example, the Code4Lib Journal) simply does it.
There are many ways to participate. Code4Lib offers a web site, a wiki, a chatroom, a mailing list, an RSS aggregation service, a journal, and a conference.
Key themes to consider include software, technology, libraries, librarians, participation, openness, and collaboration. 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.
Logo requirements:
- 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.
History
On September 19, 2008 Roy Tennant posted a suggestion on the Code4Lib mailing list that we create a logo for this group.
There was enough interest expressed that Roy put up an online poll. The result of that vote indicated a strong interest in creating a logo, but the preferred process for doing so was not clear.
A run-off vote was then held, and "Professional Option 1" won the vote, which was "We accept Stephanie Brinley's kind offer, request a few different ideas, vote on those ideas to settle on one, and the final version is created from the winning idea."
A call for volunteers to draft a requirements document was then made, and Ranti Junus and Emily Molanphy volunteered.
On January 5, 2009, Stephanie Brinley submitted a set of draft concepts and Roy Tennant called for volunteers with experience in a logo design process to view and comment on the concepts.
The following Code4Lib participants volunteered to help review the designs and comment: Sean Hannan, Karen Schneider, Rob Styles, Steve Toub, Tito Sierra, and David Cloutman.
On January 8, 2009, Roy Tennant replied to Stephanie with the summarized response from the reviewers.
On January 12, 2009, Stephanie Brinley replied with a set of final variations in response to our feedback.
On January 16, 2009, the group decided to go with option #1, while checking with Stephanie that the colors were actual Pantone colors.
On January 29, 2009, Roy Tennant created a page on the code4lib web site for all of the files and instructions.
