<div dir="ltr"><div><div><div>After reviewing the guidelines <a href="http://www.openstack.org/brand/openstack-trademark-policy/" target="_blank" style="font-size:12.8000001907349px">http://www.openstack.org/brand/openstack-trademark-policy/</a></div><div style="font-size:12.8000001907349px">and <a href="http://www.openstack.org/brand/" target="_blank" style="font-size:12.8000001907349px">http://www.openstack.org/brand/</a>, I see that there is rigor protecting and using for the OpenStack mark ("OpenStack") and logos. Interestingly there is a non-working link in the second paragraph of the Trademark Policy page that was supposed to go to the marks themselves. Without that link working it's hard to say if the individual projects were listed there. This is also of note because the only time I saw mention of the projects, they were capitalized: </div><div style="font-size:12.8000001907349px"><br></div><div style><span style="font-size:12.8000001907349px"><a href="http://www.openstack.org/brand/openstack-trademark-policy/">http://www.openstack.org/brand/openstack-trademark-policy/</a></span></div><div style><span style="font-size:12.8000001907349px">The "Powered by OpenStack" Logo, shown immediately below, may be used by individuals, organizations, and companies that use formally released OpenStack Compute (Nova) code in their application or product.</span></div><div style><span style="font-size:12.8000001907349px"><br></span></div><div style><span style="font-size:12.8000001907349px">The Storage Powered by OpenStack Logo, shown immediately below, may be used by individuals, organizations, and companies that use formally released OpenStack Object Storage (Swift) code in their application or product.</span></div><div style>------</div><div style><br></div><div style>Having the legal policies and the majority of people using the initial uppercase strengthens the argument for updating the capitalization conventions in favor of it. </div><div style><br></div><div style>Certainly the project code names are not the legal names and won't be trademarked but they are proper names and proper nouns. Since the formal/legal names for the projects are capitalized doing the same for the code names doesn't place any importance, it just provides consistency. A friend can be named Michael but go by Mike. He wouldn't go by mike. </div><div style><br></div><div style>Having all mention of the project code name as lowercase does add simplicity but at the cost of accuracy and clarity. Simplicity can also be found with the proper noun is capitalized rule. It essentially boils down to "only the CLI is lowercase" and has the added benefit of already being used commonly and provides clarity to writing.</div><div style>Examples:</div><div style>The Nova team has...</div><div style>for the OpenStack Compute (code name Nova) project. Nova is the...</div><div style>To use the nova CLI...</div><div style>In the terminal type: nova --help </div><div style><br></div><div style>All that said, I certainly agree that the legal/form name should be used when possible. Indeed the Documentation team has been doing so for years so there would be fairly little updating needed for many of those guides for a switch to an initial capitalization. </div><div><br></div><div><br></div></div></div><div class="gmail_extra"><span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Side note: Since we have a rule for sentence capitalization for headings, would it be okay for me to add that to the Conventions page? I don't see any mention of it. </div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"> </div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div>It's here:<br></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><a href="https://wiki.openstack.org/wiki/Documentation/Markup_conventions#Headings" target="_blank">https://wiki.openstack.org/wiki/Documentation/Markup_conventions#Headings</a> </div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">and here: </div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><a href="https://wiki.openstack.org/wiki/Documentation/Conventions/DocBook#Headings" target="_blank">https://wiki.openstack.org/wiki/Documentation/Conventions/DocBook#Headings</a></div></blockquote></span><div><br></div><div>Aha, I was thinking of it as a general convention, not tool specific. Thanks for the links!</div></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Looks like consensus is currently:</div><div class="gmail_extra">Keep all lowercase - 3</div><div class="gmail_extra">Use initial uppercase - 3</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks,</div><div class="gmail_extra">Amanda</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 30, 2015 at 1:21 PM, Anne Gentle <span dir="ltr"><<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Sat, May 30, 2015 at 2:39 PM, APlimpton <span dir="ltr"><<a href="mailto:aplimpton@gmail.com" target="_blank">aplimpton@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Looks like HAProxy and other pieces that are sold separately or trademarked should follow their own standard for capitalization (per IBM style guide again). </div><div><br></div></div></blockquote><div><br></div></span><div>I was going to note the same about HAProxy -- it's a proper name with associated capitalization rules. Same as your other examples, Meg.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>Thanks for the support, Meg :) Funny enough I thought this was going to be more of a case where most everyone had shifted to using the initial uppercase and the Conventions page just hadn't been updated to reflect it. Sorry to be putting a ripple in the pond.</div><div><br></div></div></blockquote><div><br></div></span><div>Not at all, and please don't take any of this as a personal affront or anything. I'm glad you're looking around and questioning. We love yours and Meg's fresh eyes!</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>Given that it goes against general usage and most style guides, it would beneficial to know why the proper noun is being lowercased. I get the need to avoid making Everything Look Important, and wholeheartedly agree, but this is specifically for one small set of names. OpenStack gets two capitalizations, the projects functional names and all the releases have a initial one. We clearly didn't disapprove of them in general, so why here? </div></div></blockquote><div> <br></div></span></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>It's tangled up in the lack of clarity around trademark use for a couple of years. Now that there's more rigor around the use of the OpenStack trademark, how about you take a look at why you think project names should be capitalized and post here. </div><div><a href="http://www.openstack.org/brand/openstack-trademark-policy/" target="_blank">http://www.openstack.org/brand/openstack-trademark-policy/</a><br></div><div>and</div><div><a href="http://www.openstack.org/brand/" target="_blank">http://www.openstack.org/brand/</a><br></div><div><br></div><div>When I read through those, I still come up with the conventions we have in place. Here are my reasons pro lowercase:</div><div><br></div><div>- The team/project names like nova, swift, etc. names are never going to be trademarked so no extra import should be imparted by using the capitalize-for-proper-name convention.</div><div>- We don't pursue legal reasoning in trademarking the name, but do try to find a unique name that's unused in the software industry. It's not a proper name. </div><div>- We have gotten cease and desist for the use of quantum for example, and by lowercasing we may be less likely to be in violation of some corner/edge legal name case.</div><div>- The file name such as nova.conf actually has to be lowercase in Linux-based operating systems.</div><div>- The nova-<name> service or daemon names also have to be lowercase in Linux-based operating systems. </div><div>- The nova, swift Command Line Interface (CLI) tools also have to be run in lowercase in Linux-based operating systems. </div><div>- The lower case always as a rule rather than exception helps simplify editing and guidance.</div><span><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Side note: Since we have a rule for sentence capitalization for headings, would it be okay for me to add that to the Conventions page? I don't see any mention of it. </div></div></blockquote><div><br></div><div><br></div></span><div>It's here:</div><div><a href="https://wiki.openstack.org/wiki/Documentation/Markup_conventions#Headings" target="_blank">https://wiki.openstack.org/wiki/Documentation/Markup_conventions#Headings</a><br></div><div>and here:</div><div><a href="https://wiki.openstack.org/wiki/Documentation/Conventions/DocBook#Headings" target="_blank">https://wiki.openstack.org/wiki/Documentation/Conventions/DocBook#Headings</a><br></div><div><br></div><div>Thanks,</div><div><div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Thanks,</div><div>Amanda</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 29, 2015 at 3:24 PM, Meg McRoberts <span dir="ltr"><<a href="mailto:dreidellhasa@yahoo.com" target="_blank">dreidellhasa@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div style="color:rgb(0,0,0);font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:12px;background-color:rgb(255,255,255)"><div dir="ltr">I'll go along with the wishes of the majority but I do agree with Amanda here, that capitalizing the names of the projects</div><div dir="ltr">would make both the writing and the reading easier.</div><div dir="ltr"><br></div><div dir="ltr">What about services that are not projects per se, such as HAProxy, MySQL, MongoDB, Pacemaker, Corosync...? Some of these exist</div><div dir="ltr">outside the OpenStack world and everyone is used to them being capitalized in a certain way. But it seems quite awkward</div><div dir="ltr">to capitalize these when services that are projects are not capitalized.<br></div><div dir="ltr"><br></div><div dir="ltr">I just went through a piece of doc and changed HAProxy to haproxy. The title of the section is "HAProxy nodes" so I had to</div><div dir="ltr">make that "Haproxy nodes" to conform to the standard for capitalization in headers. I suppose I could rewrite it to be "The haproxy nodes"</div><div dir="ltr">but I would much prefer to have the keyword begin the header.<br></div><div><br><span></span></div><div dir="ltr"><span>As I said, I'll go along but Amanda deserves a little support ;-)</span></div><div dir="ltr"><span>meg</span></div><br> <blockquote style="border-left-width:2px;border-left-style:solid;border-left-color:rgb(16,16,255);margin-left:5px;margin-top:5px;padding-left:5px"> <div style="font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:12px"> <div style="font-family:HelveticaNeue,'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;font-size:16px"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold">From:</span></b> Anne Gentle <<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>><br> <b><span style="font-weight:bold">To:</span></b> APlimpton <<a href="mailto:aplimpton@gmail.com" target="_blank">aplimpton@gmail.com</a>> <br><b><span style="font-weight:bold">Cc:</span></b> "<a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.openstack.org</a>" <<a href="mailto:openstack-docs@lists.openstack.org" target="_blank">openstack-docs@lists.openstack.org</a>> <br> <b><span style="font-weight:bold">Sent:</span></b> Friday, May 29, 2015 2:56 PM<br> <b><span style="font-weight:bold">Subject:</span></b> Re: [OpenStack-docs] Style Question for Project Names<br> </font> </div><div><div> <div><br><div><div dir="ltr"><br><div><br><div>On Fri, May 29, 2015 at 4:36 PM, APlimpton <span dir="ltr"><<a rel="nofollow" href="mailto:aplimpton@gmail.com" target="_blank">aplimpton@gmail.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>I see several people are fine with how the convention is and would prefer for it to remain as is because they do not see a need for the change. </div><div><br></div><div>Because I do see a need, the burden is on me to further explain what I’m seeing and why it suggests that using a capital letter with the project names is needed. </div><div><br></div><div>When I say inconsistencies I mean that a handful of the OpenStack documentation manuals and a few wiki pages use the lowercase. On all other guides, references, manuals, websites, pages, blogs and various other communications the capitalized letter is used by the community (OpenStack and general). This strong majority of people using the capitalized version indicates that there has been a shift in the usage and we should update our convention accordingly. </div><div><br></div><div>This is supported by the fact that these project names are names/proper nouns and as such should be capitalized. Having the release code names capitalized but not the project code names is inconsistent. If the name is to be a proper noun w/ all lowercase then all sentences that start with the project name will need to be reworded (source: IBM Style Guide used per the Conventions wiki page). </div><div><br></div><div>An additional benefit to using the initial uppercase with project names is that it helps reduce confusion. Each project uses the project name three distinct ways with the exact same case. The project name, the CLI name and the command that is used. For example: nova, nova, nova. As a component of the project, the CLI name and the command should be lowercase (source: IBM Style Guide). Using a capitalized letter with the project name immediately distinguishes it as being not the project component and helps make sentence creation and updating less convoluted.</div><div><br></div><div>If this makes sense to most of you and the consensus is reached to change to the initial uppercase I will be happy to find and make those changes. If the consensus is to keep it all lowercase then I’ll go ahead and attempt correction for the majority of docs, which will take a little longer. If keeping all lowercase, it may also be a good idea to remind the other contributors about the conventions page so they will be aware in the future. Either way I am believer in consistency and clarity. :)</div></div></blockquote><div><br></div><div>Agreed. Thanks for bringing the issue forward. Even when writing a blog post for the Rackspace blog two weeks ago, I had two editors tell me to capitalize the project/team name. However they were fine with lowercase once I pointed out our conventions. We have the power to enforce lowercase so why not put your energy towards the lowercase preference that we've had for years?</div><div><br></div><div>One rule we have for simplicity's sake is to use sentence case for all titles, and the reasoning behind this is that it's fewer rules to explain and enforce (plus there are two competing Title Case styles from certain references). I sense we have the same simplicity goal with "always lower case project names" because once people start uppercasing what they think is Important then Everything Is Important if you Know what I Mean. :)</div><div><br></div><div>I'd ask you to activate towards lowercase and help enforce that as standard rather than advocating for Upper Case All the Time. </div><div><br></div><div>Really though, I said I'd get out of the way on this one. Hope my reasoning makes sense.</div><div>Anne</div><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Thanks,<br>Amanda</div></div><div><div><div><br><div>On Fri, May 29, 2015 at 1:37 PM, Shilla Saebi <span dir="ltr"><<a rel="nofollow" href="mailto:shilla.saebi@gmail.com" target="_blank">shilla.saebi@gmail.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">+1<br>
<br>
Sent from my iPhone<br>
<div><div><br>
> On May 29, 2015, at 4:22 PM, Christian Berendt <<a rel="nofollow" href="mailto:christian@berendt.io" target="_blank">christian@berendt.io</a>> wrote:<br>
><br>
>> On 05/29/2015 09:40 PM, Andreas Jaeger wrote:<br>
>> We're following the current convention for some time already and I see<br>
>> no reason to change, let's keep the current convention. If there're<br>
>> problems, let's fix them...<br>
><br>
> +1<br>
><br>
> --<br>
> Christian Berendt<br>
> Cloud Computing Solution Architect<br>
> Mail: <a rel="nofollow" href="mailto:berendt@b1-systems.de" target="_blank">berendt@b1-systems.de</a><br>
><br>
> B1 Systems GmbH<br>
> Osterfeldstraße 7 / 85088 Vohburg / <a rel="nofollow" href="http://www.b1-systems.de/" target="_blank">http://www.b1-systems.de</a><br>
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537<br>
><br>
> _______________________________________________<br>
> OpenStack-docs mailing list<br>
> <a rel="nofollow" href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a><br>
> <a rel="nofollow" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br>
_______________________________________________<br>
OpenStack-docs mailing list<br>
<a rel="nofollow" href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a><br>
<a rel="nofollow" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-docs mailing list<br>
<a rel="nofollow" href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a><br>
<a rel="nofollow" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Anne Gentle<br><a rel="nofollow" href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a></div>
</div></div></div><br>_______________________________________________<br>OpenStack-docs mailing list<br><a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br><br><br></div> </div></div></div> </div> </blockquote> </div></div></blockquote></div><br></div>
</div></div></blockquote></div></div></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div>Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a></div>
</font></span></div></div>
</blockquote></div><br></div></div>