<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">Just checking on the
progress of this. :)<br>
<span>
</span><br>
<blockquote style="border: 0px none;"
cite="mid:7a291c20-cb80-cfa3-5f15-d6af2713af7f@inaugust.com" 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: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
7, 2017 at 7:05 AM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><br>
<br>There is a new repo now:
<br>
<br><a class="moz-txt-link-freetext" href="http://git.openstack.org/cgit/openstack/project-navigator-data">http://git.openstack.org/cgit/openstack/project-navigator-data</a>
<br>
<br>I have pushed up two different patches with two different
approaches:
<br>
<br><a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/454691">https://review.openstack.org/#/c/454691</a>
<br><a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/454688">https://review.openstack.org/#/c/454688</a>
<br>
<br>One is a single file per release. The other is a file per service
per
release.
<br>
<br>Benefits of the single-file are that it's a single file to pull and
parse.
<br>
<br>Benefits of the multi-file approach are that projects can submit
documents for themselves as patches without fear of merge conflicts, and
that the format is actually _identical_ to the format for version
discovery from the API-WG, minus the links section.
<br>
<br>I think I prefer the multi-file approach, but would be happy either
way.
<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>
<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:jimmy@openstack.org"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Jimmy McArthur</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
6, 2017 at 3:51 PM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Cool. Thanks Monty!<br>
<span>
</span><br>
<br>
<div>__________________________________________________________________________<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></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
6, 2017 at 3:21 PM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">On 04/06/2017 11:58 AM, Jimmy
McArthur wrote:
<br><blockquote type="cite">Assuming this format is accepted, do you all
have any sense of when this
<br>data will be complete for all projects?
<br></blockquote>
<br>Hopefully "soon" :)
<br>
<br>Honestly, it's not terribly difficult data to produce, so once we're
happy with it and where it goes, crowdsourcing filling it all in should
go quickly.
<br>
<br><blockquote type="cite"><blockquote type="cite">Jimmy McArthur
<a class="moz-txt-link-rfc2396E" href="mailto:jimmy@openstack.org"><mailto:jimmy@openstack.org></a>
<br>April 5, 2017 at 8:59 AM
<br>FWIW, from my perspective on the Project Navigator side, this format
<br>works great. We can actually derive the age of the project from this
<br>information as well by identifying the first release that has API
data
<br>for a particular project. I'm indifferent about where it lives, so
I'd
<br>defer to you all to determine the best spot.
<br>
<br>I really appreciate you all putting this together!
<br>
<br>Jimmy
<br>
<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>Thierry Carrez <a class="moz-txt-link-rfc2396E" href="mailto:thierry@openstack.org"><mailto:thierry@openstack.org></a>
<br>April 5, 2017 at 5:28 AM
<br>
<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>Monty Taylor <a class="moz-txt-link-rfc2396E" href="mailto:mordred@inaugust.com"><mailto:mordred@inaugust.com></a>
<br>April 4, 2017 at 5:47 PM
<br>Hey all,
<br>
<br>As per our discussion in today's TC meeting, I have made a document
<br>format for reporting versions to the project navigator. I stuck it
in
<br>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
<br>governance repo did not have that structure.
<br>
<br>I've included pseudo-code and a human explanation of how to get from
a
<br>service's version discovery document to the data in this document,
but
<br>also how it can be maintained- which is likely to be easier by hand
<br>than by automation - but who knows, maybe we decide we want to make a
<br>devstack job for each service that runs on tag events that submits a
<br>patch to the releases repo. That sounds like WAY more work than once
a
<br>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
<br>Document" is a thing people might want to do and want to do
<br>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
<br>minor ways that do not actually matter but make life harder for our
<br>users.
<br>
<br>Thoughts and feedback more than welcome!
<br>Monty
<br>
<br>__________________________________________________________________________
<br>
<br>OpenStack Development Mailing List (not for usage questions)
<br>Unsubscribe:
<br><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></blockquote>
<br>
<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>
<br></blockquote>
<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>
<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:jimmy@openstack.org"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Jimmy McArthur</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
6, 2017 at 11:58 AM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Assuming this format is
accepted, do you all have any sense of when this data will be complete
for all projects? <br>
<span>
</span><br>
<br>
<div>__________________________________________________________________________<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></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:jimmy@openstack.org"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Jimmy McArthur</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 8:59 AM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
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>
<br>
<div>__________________________________________________________________________<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></div>
</blockquote>
<br>
</body></html>