<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><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">
<br>
-------- Forwarded Message --------<br>
Subject: [openstack-dev] Should project name be uppercase or lowercase?<br>
Date: Tue, 7 Jul 2015 18:21:57 +0900<br>
From: Yuiko Takada <<a href="mailto:yuikotakada0313@gmail.com" target="_blank">yuikotakada0313@gmail.com</a>><br>
Reply-To: OpenStack Development Mailing List (not for usage questions)<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
To: OpenStack Development Mailing List (not for usage questions)<br>
<<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<br>
<br>
<br>
Hi folks,<br>
<br>
I found the difference between wiki[1] and governance[2].<br></blockquote><div><br></div><div>Yes, we are aware of the differences. I have asked the OpenStack Foundation legal counsel and they do not have a legal reason to capitalize project names. </div><div><br></div><div>So, in documentation for consistency and to work on more valuable efforts, we need to stick to the established Documentation Conventions that have been in place since October 2013.</div><div><br></div><div><a href="https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_project_names">https://wiki.openstack.org/wiki/Documentation/Conventions#Service_and_project_names</a><br></div><div><br></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">
wiki says "Generally the capitalization of the project team names like<br>
swift is lowercase."<br>
But in governance, written as uppercase like "Nova", "Swift".<br></blockquote><div><br></div><div>I don't believe a machine-readable YAML file indicates style or conventions for capitalization for a collection. </div><div><br></div><div>Yes, I will be doing a patch for service names since it is a source of reference and if we think it will alleviate confusion I'll also lowercase the names of the projects in a separate patch.</div><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">
<br>
How do you think which should we use uppercase vs lowercase for<br>
representing project names?<br></blockquote><div><br></div><div>I'll be patching the governance repo with some guidelines we have been using to make them official. The projects.yaml file is the reference point for the service catalog and documentation, and the doc team maintains a lookup list on the wiki page referenced above.</div><div><br></div><div>Conventions for service names: </div><div><ul class="" style="color:rgb(0,0,0);font-family:sans-serif"><li>Uppercase first letter of first word only.</li><li>Do not use OpenStack in the name of the service.</li><li>Use module if it is consuming other services (such as heat).</li><li>Use service in general as that is mostly what is being added as projects.</li></ul></div><div>Conventions for project names:</div><div><ul><li>In documentation published to <a href="http://docs.openstack.org">docs.openstack.org</a>, use lower case for project names <span style="color:rgb(0,0,0);font-family:sans-serif">except at the beginning of a sentence or heading title. (Note that all heading titles use sentence case for ease of learning capitalization rules.)</span></li><li>In the service catalog, use lower case.</li></ul></div><div>I hope this clarification helps. Please let me know if you have any questions or concerns. </div><div><br></div><div>Thanks,</div><div>Anne</div><div><br></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">
<br>
<br>
[1]<a href="https://wiki.openstack.org/wiki/Documentation/Conventions" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Documentation/Conventions</a><br>
[2]<a href="http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml</a><br>
<br>
<br>
Best Regards,<br>
Yuiko Takada<span class=""><font color="#888888"><br>
<br>
<br>
<br>
-- <br>
Christian Berendt<br>
Cloud Solution Architect<br>
Tel.: <a href="tel:%2B49-171-5542175" value="+491715542175" target="_blank">+49-171-5542175</a><br>
Mail: <a 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 href="http://www.b1-systems.de" rel="noreferrer" target="_blank">http://www.b1-systems.de</a><br>
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>Anne Gentle</div><div>Rackspace</div><div>Principal Engineer</div><div><a href="http://www.justwriteclick.com" target="_blank">www.justwriteclick.com</a></div></div></div>
</div></div>