<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hello Everyone, <br><br>We just finished our combined defcore + defcore capabilities meeting. Thanks to everyone that attended and provided feedback, notes from the meeting are bellow.<br><br>Action items for everyone interested in DefCore:<br>1. Review the initial draft for the process and provide feedback: https://review.openstack.org/#/c/165216<br>2. Tell us how many core reviewers we should have for openstack/defcore project. During the meeting, we talked about having a smaller group of core reviewers. Right now, core reviewers are myself, Rob Hirschfeld, and Chris Hoge. If you think the group should be larger, list your reasons. We do have additional volunteers for core reviewers.<br><br>Thank you,<br><br>Egle<br><br><br>Meeting Notes:<br><a href="https://etherpad.openstack.org/p/DefCoreScale.8" target="_blank">https://etherpad.openstack.org/p/DefCoreScale.8</a><br><br><div id="magicdomid16"><span class="author-a-z85zl3z87zz68zz84zaz71zz68zz89zz67z0pez70z6">Note: Today's meeting will be combined with the DefCore capabilities meeting.</span></div><div id="magicdomid17"><br></div><div id="magicdomid18"><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf"># Agenda</span></div><div id="magicdomid19"><ul class="list-bullet1"><li><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf">Feedback on Initial draft of the DefCore Process</span><span class="author-a-z85zl3z87zz68zz84zaz71zz68zz89zz67z0pez70z6"> ( </span><span class="author-a-z85zl3z87zz68zz84zaz71zz68zz89zz67z0pez70z6 url"><a href="https://review.openstack.org/#/c/165216">https://review.openstack.org/#/c/165216</a></span><span class="author-a-z85zl3z87zz68zz84zaz71zz68zz89zz67z0pez70z6"> )</span></li></ul></div><div id="magicdomid20"><ul class="list-bullet1"><li><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf">Core reviewers for defcore: </span><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf url"><a href="https://review.openstack.org/#/admin/groups/uuid-ad95fb605fa544dab35712194df7faaa10ec7a22,members">https://review.openstack.org/#/admin/groups/uuid-ad95fb605fa544dab35712194df7faaa10ec7a22,members</a></span></li></ul></div><div id="magicdomid21"><ul class="list-bullet1"><li><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf">Reminder: submit/discuss tests that should be flagged</span></li></ul></div><div id="magicdomid22"><br></div><div id="magicdomid23"><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf">Roll Call:</span></div><div class="ace-line" id="magicdomid1487"><ul class="list-bullet1"><li><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf">Egle Sigler (Co-Chair, Rackspace)</span></li></ul></div><div class="ace-line" id="magicdomid1488"><ul class="list-bullet1"><li><span class="author-a-z87zz87zz74zz78zz65zz65zvz70zz89z27z89zn3z89zz84z">Chris Lee (DreamHost)</span></li></ul></div><div class="ace-line" id="magicdomid1489"><ul class="list-bullet1"><li><span class="author-a-z85zl3z87zz68zz84zaz71zz68zz89zz67z0pez70z6">Mark T. Voelker (VMware)</span></li></ul></div><div class="ace-line" id="magicdomid1490"><ul class="list-bullet1"><li><span class="author-a-z84z01lz79zgz78zz72zwf0n3z81zf2">Jim Meyer (HP)</span></li></ul></div><div class="ace-line" id="magicdomid1491"><ul class="list-bullet1"><li><span class="author-a-z81zz74zz72zz75zanv56vz122zr5abz88z">Carol Barrett (Intel)</span></li></ul></div><div class="ace-line" id="magicdomid1492"><ul class="list-bullet1"><li><span class="author-a-z81z1gz69zz78zdhpz78znnz74zukgz80z">Will Auld (Intel)</span></li></ul></div><div class="ace-line" id="magicdomid1493"><ul class="list-bullet1"><li><span class="author-a-xz66zz76zwz77zrlk5q67tz82zz80zz69z">Catherine Diep (IBM)</span></li></ul></div><div class="ace-line" id="magicdomid1494"><ul class="list-bullet1"><li><span class="author-a-z75zz68zkpecqz85zz73zmz74zfz68zz86zz82zn">Vince Brunssen (IBM)</span></li></ul></div><div class="ace-line" id="magicdomid1495"><ul class="list-bullet1"><li><span class="author-a-fngz82z7z90zz77zz69ziz87zpz78zz83z0z87zv">Van Lindberg (Rackspace)</span></li></ul></div><div class="ace-line" id="magicdomid1496"><ul class="list-bullet1"><li><span class="author-a-ekz89z1z78z4a1z81zz66z9uaz65zz66z2">Adrian Otto (Rackspace)</span></li></ul></div><div class="ace-line" id="magicdomid157"><br></div><div class="ace-line" id="magicdomid165"><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf">Notes:</span></div><div class="ace-line" id="magicdomid742"><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf">
Definition for designated sections missing, they are in the lexicon.rst
file. Need to iterate on the definition more before going in.</span><span class="author-a-z84z01lz79zgz78zz72zwf0n3z81zf2"> [1]</span></div><div class="ace-line" id="magicdomid529"><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf">
Core reviewers will appoint other core reviewers. Take it to the
mailing list. Propose a small list. Chris Lee from dreamhost
volunteered. Van L is also willing. Jim </span><span class="author-a-z85zl3z87zz68zz84zaz71zz68zz89zz67z0pez70z6">and Mark </span><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf">also happy to be a reviewers and happy to be excluded.</span><span class="author-a-z75zz68zkpecqz85zz73zmz74zfz68zz86zz82zn"> Vince Brunssen (IBM) would also be willing to be a core reviewer.</span></div><div class="ace-line" id="magicdomid1066"><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf"> For .03 tests, </span><span class="author-a-fngz82z7z90zz77zz69ziz87zpz78zz83z0z87zv">See decision below. </span></div><div class="ace-line" id="magicdomid961"><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf"> </span></div><div class="ace-line" id="magicdomid1067"><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf"> Question about Foundation requirements, C1.3 and C2.</span></div><div class="ace-line" id="magicdomid1150"><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf"> For section C1.4, should clearly label the published self-tests as unreviewed. </span></div><div class="ace-line" id="magicdomid1281"><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf"> Rocky would like release management items in the process. </span></div><div class="ace-line" id="magicdomid1053"><span class="author-a-4l09ri5z85zaz70z5z68zz89zjvf"> </span></div><div class="ace-line" id="magicdomid254"><br></div><div class="ace-line" id="magicdomid798"><span class="author-a-fngz82z7z90zz77zz69ziz87zpz78zz83z0z87zv">Decision on UUIDs vs Fully-Qualified names (FQNs):</span></div><div class="ace-line" id="magicdomid1497"><ul class="list-bullet1"><li><span class="author-a-fngz82z7z90zz77zz69ziz87zpz78zz83z0z87zv">FQNs will be used for 2015.03</span></li></ul></div><div class="ace-line" id="magicdomid1498"><ul class="list-bullet1"><li><span class="author-a-fngz82z7z90zz77zz69ziz87zpz78zz83z0z87zv">The
question of FQNs vs UUIDs is re-evaluated for each spec release until
the social and technical issues with UUIDs are resolved (or UUIDs are
dropped)</span></li></ul></div><div class="ace-line" id="magicdomid1499"><ul class="list-bullet1"><li><span class="author-a-fngz82z7z90zz77zz69ziz87zpz78zz83z0z87zv">When UUIDs are adopted, there is a major version bump for the json spec.</span></li></ul></div><div class="ace-line" id="magicdomid1500"><ul class="list-bullet1"><li><span class="author-a-xz66zz76zwz77zrlk5q67tz82zz80zz69z">UUID related bug filed: </span></li></ul></div><div class="ace-line" id="magicdomid1501"><ul class="list-bullet1"><li><span class="author-a-xz66zz76zwz77zrlk5q67tz82zz80zz69z url"><a href="https://bugs.launchpad.net/tempest/+bug/1433700">https://bugs.launchpad.net/tempest/+bug/1433700</a></span></li></ul></div><div class="ace-line" id="magicdomid1504"><br></div><div class="ace-line" id="magicdomid1526"><span class="author-a-z84z01lz79zgz78zz72zwf0n3z81zf2">[1] Here's the snip from </span><span class="author-a-z84z01lz79zgz78zz72zwf0n3z81zf2 url"><a href="https://review.openstack.org/#/c/165216/3/lexicon.rst">https://review.openstack.org/#/c/165216/3/lexicon.rst</a></span><span class="author-a-z84z01lz79zgz78zz72zwf0n3z81zf2">:</span><span class="author-a-z85zl3z87zz68zz84zaz71zz68zz89zz67z0pez70z6"> (note: please comment in Gerrit, not here)</span></div><div class="ace-line" id="magicdomid1506"><span class="author-a-z84z01lz79zgz78zz72zwf0n3z81zf2"> Mark T. Voelker 18 Mar 2015 10:36a</span></div><div class="ace-line" id="magicdomid1507"><span class="author-a-z84z01lz79zgz78zz72zwf0n3z81zf2">
Shamail had a good suggestion that we add a definition of designated
sections here, but I'm not sure that has been completely worked out.
Vaguely, we have something like this (pulling liberally from some of
Rob's earlier slides and modifying slightly since the integrated release
is on the way out):</span></div><div class="ace-line" id="magicdomid1508"><ul class="list-bullet1"><li><span class="author-a-z84z01lz79zgz78zz72zwf0n3z81zf2">Designated
Sections - portions of the OpenStack codebase that must be used in
order to meet the OpenStack trademark. Designated sections fulfill one
or more of three criteria: 1) they provide the project-external REST
API; 2) are shared and provide common functionality for all options; 3)
implement logic that is critical for cross-platform operation.
Designated sections must exist in the OpenStack gerrit namespace and
have corresponding tests. Code that meets the following criteria will
not be considered designated: provides vendor-specific functionality,
are explicitly intended by the project maintainers to be replaceable,
extend the project REST API in a new or different way, or code that is
being deprecated.</span></li></ul></div><div class="ace-line" id="magicdomid1509"><span class="author-a-z84z01lz79zgz78zz72zwf0n3z81zf2">That's a bit wordy compared to the other definitions here, but it's a start. What do folks think?</span></div><div class="ace-line" id="magicdomid1510"><br></div><div class="ace-line" id="magicdomid745"><br></div><br><br>
</div></body>
</html>