Out of this set, I like #7 the most. Firstly, it is very clear and bold, so will work well at any size. I think the fact that the writing is a clear font in a dark colour works well. My next favourite is #9 - I like the cloud design for this one.
Paul On 26 June 2013 05:23, Amal Rangana <[email protected]> wrote: > Sending the modified with this. > > Thanks, > Amal > > > On Wed, Jun 26, 2013 at 9:34 AM, Isuru Perera <[email protected]> wrote: > >> +1 for #4 or #10 >> >> Could you please replace "O" of #4 or #10 with #6 and send us the designs. >> >> Thanks! >> >> >> On Wed, Jun 26, 2013 at 7:48 AM, Amal Rangana <[email protected]> wrote: >> >>> I have done some more logo designs and sending those with this. >>> >>> Thanks, >>> Amal >>> >>> >>> On Tue, Jun 25, 2013 at 6:41 AM, Amal Rangana <[email protected]> wrote: >>> >>>> I am doing some more designs according to the comments and will be >>>> sending those to the thread soon. >>>> >>>> Amal >>>> >>>> >>>> On Tue, Jun 25, 2013 at 6:19 AM, Samisa Abeysinghe < >>>> [email protected]> wrote: >>>> >>>>> If we could get the concept of "complete cloud" into the design, that >>>>> would be great. >>>>> >>>>> >>>>> >>>>> On Tue, Jun 25, 2013 at 5:55 AM, Jonathan Marsh <[email protected]>wrote: >>>>> >>>>>> Joe, >>>>>> >>>>>> I agree being explicit about what the logo should convey would help to >>>>>> evaluate the designs, as well as to spur new ones. Currently the logo >>>>>> designs seem to be clearly expressing only two ideas - "cloud" and >>>>>> "Apache". Additional concepts that might be considered could include: >>>>>> >>>>>> - scalability/elasticity >>>>>> - sharing (multi-tenancy, developer community) >>>>>> - openness in technology and community >>>>>> - a key layer in a complete cloud platform >>>>>> - foundation/framework which can plug into many different >>>>>> infrastructures >>>>>> - foundation/framework into which may different runtimes can >>>>>> be >>>>>> plugged in >>>>>> >>>>>> I don't think we could do ALL of these at once, but if you combine >>>>>> them in >>>>>> different pairs you might expand the base of imagery. >>>>>> >>>>>> -Jonathan >>>>>> >>>>>> -----Original Message----- >>>>>> From: Joe Brockmeier [mailto:[email protected]] >>>>>> Sent: Monday, June 24, 2013 5:09 AM >>>>>> To: [email protected] >>>>>> Cc: [email protected] >>>>>> Subject: Re: Apache Stratos Logo >>>>>> >>>>>> On Mon, Jun 24, 2013, at 04:22 AM, Amal Rangana wrote: >>>>>> > Sending the logo designs with this. >>>>>> >>>>>> I would suggest brainstorming a bit about the logo before throwing out >>>>>> finished designs, and ask what exactly you'd like to convey with the >>>>>> logo >>>>>> rather than being constrained by the first set of logos that are >>>>>> first to >>>>>> the project. >>>>>> >>>>>> Also - All of these designs incorporate the Apache feather w/some >>>>>> manner >>>>>> of text treatment. Might be nice to see something that gives Stratos >>>>>> its >>>>>> own look w/out the feather. (Use of the feather is not a requirement >>>>>> for >>>>>> the project logo.) >>>>>> >>>>>> Best, >>>>>> >>>>>> jzb >>>>>> -- >>>>>> Joe Brockmeier >>>>>> [email protected] >>>>>> Twitter: @jzb >>>>>> http://www.dissociatedpress.net/ >>>>>> >>>>> >>>>> >>>> >>> >> >> >> -- >> Isuru Perera >> Senior Software Engineer | WSO2, Inc. | http://wso2.com/ >> Lean . Enterprise . Middleware >> >> Twitter: http://twitter.com/chrishantha | LinkedIn: >> http://lk.linkedin.com/in/chrishantha/ >> > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo [email protected] wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
