<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body text="#000000" bgcolor="#FFFFFF">FWIW, from my perspective
on the Project Navigator side, this format works great. We can actually
derive the age of the project from this information as well by
identifying the first release that has API data for a particular
project. I'm indifferent about where it lives, so I'd defer to you all
to determine the best spot. <br>
<br>
I really appreciate you all putting this together!<br>
<br>
Jimmy<br>
<span>
</span><br>
<blockquote style="border: 0px none;"
cite="mid:21865f75-a9fe-91dc-1c75-b6c53983756a@openstack.org"
type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:thierry@openstack.org"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Thierry Carrez</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">April
5, 2017 at 5:28 AM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><div><!----><br>Somehow missed
this thread, so will repost here comments I made elsewhere:<br><br>This
looks good, but I would rather not overload the releases<br>repository.
My personal preference (which was also expressed by<br>Doug in the TC
meeting) would be to set this information up in a<br>"project-navigator"
git repo that we would reuse for any information we<br>need to collect
from projects for accurate display on the project<br>navigator. If the
data is not maintained anywhere else (or easily<br>derivable from
existing data), we would use that repository to collect<br>it from
projects.<br><br>That way there is a clear place to go to to propose
fixes to the project<br>navigator data. Not knowing how to fix that data
is a common complaint,<br>so if we can point people to a git repo (and
redirect people from there<br>to the places where other bits of
information happen to live) that would<br>be great.<br><br></div></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:mordred@inaugust.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Monty Taylor</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">April
4, 2017 at 5:47 PM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">Hey all,
<br>
<br>As per our discussion in today's TC meeting, I have made a document
format for reporting versions to the project navigator. I stuck it in
the releases repo:
<br>
<br> <a class="moz-txt-link-freetext" href="https://review.openstack.org/453361">https://review.openstack.org/453361</a>
<br>
<br>Because there was already per-release information there, and the
governance repo did not have that structure.
<br>
<br>I've included pseudo-code and a human explanation of how to get from
a
service's version discovery document to the data in this document, but
also how it can be maintained- which is likely to be easier by hand than
by automation - but who knows, maybe we decide we want to make a
devstack job for each service that runs on tag events that submits a
patch to the releases repo. That sounds like WAY more work than once a
cycle someone adding a few lines of json to a repo - but *shrug*.
<br>
<br>Basing it on the version discovery docs show a few things:
<br>
<br>* "As a user, I want to consume an OpenStack Service's Discovery
Document" is a thing people might want to do and want to do consistently
across services.
<br>
<br>* We're not that far off from being able to do that today.
<br>
<br>* Still, like we are in many places, we're randomly different in a
few
minor ways that do not actually matter but make life harder for our
users.
<br>
<br>Thoughts and feedback more than welcome!
<br>Monty
<br>
<br>__________________________________________________________________________
<br>OpenStack Development Mailing List (not for usage questions)
<br>Unsubscribe:
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<br><a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
<br></div>
</blockquote>
<br>
</body></html>