Return-Path: X-Original-To: apmail-incubator-cloudstack-marketing-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-marketing-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD246D775 for ; Thu, 28 Feb 2013 20:10:20 +0000 (UTC) Received: (qmail 20273 invoked by uid 500); 28 Feb 2013 20:10:20 -0000 Delivered-To: apmail-incubator-cloudstack-marketing-archive@incubator.apache.org Received: (qmail 20254 invoked by uid 500); 28 Feb 2013 20:10:20 -0000 Mailing-List: contact cloudstack-marketing-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-marketing@incubator.apache.org Delivered-To: mailing list cloudstack-marketing@incubator.apache.org Received: (qmail 20246 invoked by uid 99); 28 Feb 2013 20:10:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 20:10:20 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [72.51.28.127] (HELO webmail.bbits.ca) (72.51.28.127) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 20:10:13 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by webmail.bbits.ca (Postfix) with ESMTP id AA4E4BD809A for ; Thu, 28 Feb 2013 12:09:51 -0800 (PST) X-Virus-Scanned: amavisd-new at bbits.ca Received: from webmail.bbits.ca ([127.0.0.1]) by localhost (webmail.bbits.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O9f2Y0IyogQH for ; Thu, 28 Feb 2013 12:09:47 -0800 (PST) Received: from kdamagePC2 (fibre.backbonetechnology.com [72.51.28.1]) by webmail.bbits.ca (Postfix) with ESMTPA id C9F513F80C9 for ; Thu, 28 Feb 2013 12:09:46 -0800 (PST) From: Sender: "Kelcey Damage \(BT\)" To: References: <063001ce15e8$58db8320$0a928960$@backbonetechnology.com> <1362079229.12839.140661198319469.6E071AAE@webmail.messagingengine.com> <064001ce15e9$fd977d50$f8c677f0$@apache.org> <1362080392.16338.140661198326597.7ADA3709@webmail.messagingengine.com> In-Reply-To: <1362080392.16338.140661198326597.7ADA3709@webmail.messagingengine.com> Subject: RE: FW: Wiki visual guidlines Date: Thu, 28 Feb 2013 12:09:42 -0800 Message-ID: <064c01ce15ef$8b8ec640$a2ac52c0$@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQG0LMI/LwKMP1c4ZrRkGg+LZMRmkwFIVEVeAjoW4DYBaPq5lpicKEJQ Content-Language: en-us X-Virus-Checked: Checked by ClamAV on apache.org Here is where it becomes debate. I fully agree with you, but I also believe (and we are on the marketing list) that consistency between publically facing article bearing our intent and branding is key. And leads to the perceived professionalism of our project. I don't mind wandering through some pages and updating header types. I certainly don't want to delay or slow down people fervently writing kickass wiki articles. But this brings up another question, what about grammar, etc? I'm willing to put in a couple hours a week and curate the wiki, but establishing norms upfront allows people willing to follow guides, the option. So really I'm not saying this is firm must follow or die guidelines, but something for willing. And for those with no time to format, perhaps someone like me will be willing to format for them? In fact people adding large content articles could reach out to myself or the list and request assistance in formatting and review. Just some ideas. -Kelcey >-----Original Message----- >From: Joe Brockmeier [mailto:jzb@zonker.net] >Sent: Thursday, February 28, 2013 11:40 AM >To: cloudstack-marketing@incubator.apache.org >Subject: Re: FW: Wiki visual guidlines > >Hi Kelcey, > >On Thu, Feb 28, 2013, at 01:29 PM, kdamage@apache.org wrote: >> I was just thinking right now I could write a whole page in headers >> which is silly, and there are 6 default headers, also bullet usage and >> etc. > >Are people doing this, or is this a "it might be a problem, someday"? > >I ask because if people are formatting things in a wildly inconsistent manner >right now, then we need to deal with that. > >If *not* then it seems like being over-proscriptive with style guidelines might >be a momentum blocker for someone who's keen on doing some docs on the >wiki. Not sure "go read the style guidelines first" is in keeping with "edit >boldly." > >(e.g., I don't want to chastise anyone for using h3 headers instead of h2, or >using red instead of green when they're doing good stuff or having the >impression of putting speed bumps in the way of getting up more >information.) > >Consistency isn't as important as accuracy and completeness, IMHO. > >All that said - if there's really wonky, unreadable stuff on the wiki - then let's >address that. > >Best, > >jzb >-- >Joe Brockmeier >jzb@zonker.net >Twitter: @jzb >http://www.dissociatedpress.net/