Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 50335 invoked from network); 13 Aug 2007 18:11:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Aug 2007 18:11:37 -0000 Received: (qmail 76165 invoked by uid 500); 13 Aug 2007 18:11:34 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 76131 invoked by uid 500); 13 Aug 2007 18:11:34 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 76120 invoked by uid 99); 13 Aug 2007 18:11:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Aug 2007 11:11:34 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com designates 64.233.162.224 as permitted sender) Received: from [64.233.162.224] (HELO nz-out-0506.google.com) (64.233.162.224) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Aug 2007 18:11:30 +0000 Received: by nz-out-0506.google.com with SMTP id o1so490045nzf for ; Mon, 13 Aug 2007 11:11:09 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=PR/44xKFIYxwzxCCHumXaEhtHlkixYX/JrwI5QLiR537GImiv7+pqoklptscoDEh54KqQwNQrXgMUARkqGoWxefuowJTnEjpZar15h8SCqp6JqsfoTRW3tCfmG8XWVYcXIDQFaTDVjZ6wYFY663WQ4HD+V6bTmEatC4bldNK2iI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=r6Wb02d9c9/5fK0lOsU2eCYK+XyAdtPur02z059CZvTOpP2UQKUj8Uq0C/i6bfgvTfRP1ZpeNYYH1qptpiY98e8k2ENPX+tk2ygIEQ92fIb8iroPlbBw16j5Dw+fODdaxhWSzCxWq8fPfL+7j5Xo0jDM09bNiPQa4STojndjtG0= Received: by 10.142.105.14 with SMTP id d14mr699813wfc.1187028669002; Mon, 13 Aug 2007 11:11:09 -0700 (PDT) Received: by 10.142.101.21 with HTTP; Mon, 13 Aug 2007 11:11:08 -0700 (PDT) Message-ID: Date: Mon, 13 Aug 2007 14:11:08 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: Re: Apache Directory T-Shirts for LDAPCon In-Reply-To: <43b026c70708121714m1a0c9f93j97abccbd2d539e@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8669_14229935.1187028668767" References: <43b026c70708061455j327ec487nb73c8649bff990c6@mail.gmail.com> <43b026c70708111638v6a396b8fj274c910e42b61077@mail.gmail.com> <568753d90708111655q27d95a0fp95e2f510ef023018@mail.gmail.com> <46BECD4C.9020504@labeo.de> <43b026c70708120918k29459e90iaffbf7de4c9eff56@mail.gmail.com> <568753d90708121548t3e3d6d0fga5f73f4083dda77e@mail.gmail.com> <43b026c70708121714m1a0c9f93j97abccbd2d539e@mail.gmail.com> X-Google-Sender-Auth: 1ec4de3d64332d11 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_8669_14229935.1187028668767 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Yep things have been inconsistent all over because different people have capitalized Triplesec differently. I think Triplesec is fine and what was initially put forward when it was named so. Alex On 8/12/07, Chris Custine wrote: > > It doesn't really matter to me, but I went off of the Triplesec web site > which shows it as Triplesec everywhere I could see. > > > Chris > > On 8/12/07, Enrique Rodriguez wrote: > > > > On 8/12/07, Chris Custine wrote: > > > ... From a > > > branding perspective, you do not want variations of the logo, so we > > need to > > > pick one style or the other and use it everywhere because layout and > > > location is part of the logo and these two options are technically > > > different. > > > ... > > > > Along the same lines, is the 'S' in TripleSec (vs. Triplesec) upper- > > or lower-case? Again this isn't "Chris' fault" but it is inconsistent > > across the website, the T-shirt has it lowercase, and then I noticed > > Emmanuel used "TripleSec" in his email. IMO, I think it should be > > capitalized. > > > > I hadn't really noticed, but the centered tree does look better. > > > > Enrique > > > > ------=_Part_8669_14229935.1187028668767 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Yep things have been inconsistent all over because different people have capitalized
Triplesec differently.  I think Triplesec is fine and what was initially put forward when
it was named so. 

Alex

On 8/12/07, Chris Custine <ccustine@apache.org> wrote:
It doesn't really matter to me, but I went off of the Triplesec web site which shows it as Triplesec everywhere I could see.


Chris

On 8/12/07, Enrique Rodriguez <enriquer9@gmail.com> wrote:
On 8/12/07, Chris Custine <ccustine@apache.org> wrote:
> ...  From a
> branding perspective, you do not want variations of the logo, so we need to
> pick one style or the other and use it everywhere because layout and
> location is part of the logo and these two options are technically
> different.
> ...

Along the same lines, is the 'S' in TripleSec (vs. Triplesec) upper-
or lower-case?  Again this isn't "Chris' fault" but it is inconsistent
across the website, the T-shirt has it lowercase, and then I noticed
Emmanuel used "TripleSec" in his email.  IMO, I think it should be
capitalized.

I hadn't really noticed, but the centered tree does look better.

Enrique


------=_Part_8669_14229935.1187028668767--