<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText">The Cross Project team meeting discussed the following specs today:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">> * Discuss openstack-spec: log guidelines [1]<o:p></o:p></p>
<p class="MsoPlainText">> * Discuss openstack-spec: OSProfiler [2]<o:p></o:p></p>
<p class="MsoPlainText">> * Open discussion & announcements<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> [1] <a href="https://review.openstack.org/#/c/132552/">
https://review.openstack.org/#/c/132552/</a><o:p></o:p></p>
<p class="MsoPlainText">> [2] <a href="https://review.openstack.org/#/c/134839/">
https://review.openstack.org/#/c/134839/</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For [1], the log guidelines spec is likely to reach approval for merge by the next meeting on 1/13. The spec has not been discussed on any mailing list for a while, so might be flying a bit under the radar. This log guidelines spec is
high level and states a number of best practices for developers when writing the logging chunks of their project code. It also codifies the set of log levels: Error; Warning; Info; etc. and removes the AUDIT level.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Operators and others who hold an interest in this: *<b>PLEASE REVIEW [1] AND COMMENT ON THE REVIEW BY 1/13</b>* Lack of comments, as always, implies approval. If there is only light discussion of the spec, it will be approved. If there
is lively discussion, the discussion will move towards consensus before final approval.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The spec will then be used to expand the code review checklist so that its contents are enforced.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For [2], the OSProfiler spec is not as far along, but if you as an Ops (or interested developer) sees an issue or has a suggestion for improvement, you should also comment on this review. The profiler already has code in use and is considered
useful by a number of developers and some DevOps, which is why this spec and its review is being highlighted for this audience.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ops, if you’ve never commented on a review before, don’t let that hurdle stop you. Check out this page:
<a href="http://docs.openstack.org/infra/manual/developers.html#code-review">http://docs.openstack.org/infra/manual/developers.html#code-review</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It tells you how to post a review. It doesn’t tell you that you need get an account on Launchpad.net, but that info is here:<o:p></o:p></p>
<p class="MsoNormal"><a href="http://docs.openstack.org/infra/manual/developers.html#account-setup">http://docs.openstack.org/infra/manual/developers.html#account-setup</a> . I’m not sure if you have to be a member of OpenStack for commenting, but I’m sure
folks will chime in if you do;-)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If working through these docs is hard for you, go out to IRC and folks will help get you started so you *<b>can</b>* comment on the reviews.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Also, if there is a section of the spec that you feel needs broader attention, start a discussion of it on the mailing list. Please reference the review and the part of the spec you want to discuss, but put it out there on the mailing
list so the issues/suggestions you have get addressed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">--Rocky <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>