<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body text="#000000" bgcolor="#FFFFFF">And the yaml to html
translation occurs here:
<a class="moz-txt-link-freetext" href="https://github.com/OpenStackweb/openstack-org/tree/master/software">https://github.com/OpenStackweb/openstack-org/tree/master/software</a>
We're actually testing many of the new features Thierry mentioned on the
master branch now.<br>
<span>
</span><br>
<blockquote style="border: 0px none;"
cite="mid:20181123000723.d2lub2bc5gdad3fq@yuggoth.org" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:2px solid #EDF1F4;padding-top:10px;"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:fungi@yuggoth.org"
style="color:#485664
!important;padding-right:6px;font-weight:500;text-decoration:none
!important;">Jeremy Stanley</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#909AA4"><span style="padding-left:6px">November
22, 2018 at 6:07 PM</span></font></div> </div></div>
<div style="color:#909AA4;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><div><!---->[...]<br><br>The
source code is available from<br><a class="moz-txt-link-freetext" href="https://git.openstack.org/cgit/openstack/openstack-map/tree/">https://git.openstack.org/cgit/openstack/openstack-map/tree/</a>
and<br>patches can be submitted through the Gerrit instance at<br><a class="moz-txt-link-freetext" href="https://review.openstack.org/">https://review.openstack.org/</a>
but I don't see any defect tracker set<br>up for that repository (yet
anyway).<br></div></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:2px solid #EDF1F4;padding-top:10px;"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true"
href="mailto:francois.magimel@alumni.enseeiht.fr" style="color:#485664
!important;padding-right:6px;font-weight:500;text-decoration:none
!important;">François Magimel</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#909AA4"><span style="padding-left:6px">November
22, 2018 at 4:50 PM</span></font></div> </div></div>
<div style="color:#909AA4;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><div>Hi Thierry,<br><br>Thanks
about your summary. I was not be able to be at this presentation to ask
my question, so I'll go with this mail. Where can we open bugs for this
project ? Is there an IRC channel ? And where yaml files are translated
to HTML ?<br><br>Thank you again for this useful map,<br>François<br><br></div><div><!----><br><br></div></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:2px solid #EDF1F4;padding-top:10px;"> <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:#485664
!important;padding-right:6px;font-weight:500;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="#909AA4"><span style="padding-left:6px">November
22, 2018 at 10:26 AM</span></font></div> </div></div>
<div style="color:#909AA4;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">Hi everyone,
<br>
<br>The OpenStack community produces a complex landscape of services and
other deliverables. Presenting those to the rest of the world in a way
that is comprehensive, makes sense and is not overwhelming has been a
constant challenge.
<br>
<br>During this forum session in Berlin we presented the status of
various
efforts and websites, and discussed next steps. You can see the notes of
the session at:
<br>
<br><a class="moz-txt-link-freetext" href="https://etherpad.openstack.org/p/BER-better-expose-what-we-produce">https://etherpad.openstack.org/p/BER-better-expose-what-we-produce</a>
<br>
<br>The plan going forward is to:
<br>
<br>1. Continue improving the information presented on
openstack.org/software and make more elements driven by the
openstack/openstack-map repository YAML files. Immediate next steps
include rolling out a new "Overview" page, providing an example YAML
template, adding project update video links to the YAML for easier
update, and finishing compiling "dependency" information from teams. We
will also consider adding diagrams, although it creates a lot of
consistency challenges.
<br>
<br>2. Make the pages less about the teams and more about the software.
That
involves creating team pages (or enriching those from the governance
website) and link to them instead of displaying information on the
software page.
<br>
<br>3. Brainstorm ways to move the "drivers list" (currently displayed
in
the "marketplace" using outdated data from stackalytics Drivers page)
directly on the software page
<br>
<br>4. For deployment tools, include data from the deployment tool
comparison effort (discussed in another session), and consider making
room for third-party tools as well. Also as a comparison point see
<a class="moz-txt-link-freetext" href="https://kubernetes.io/docs/setup/pick-right-solution/">https://kubernetes.io/docs/setup/pick-right-solution/</a>
<br>
<br>5. For SDKs, include non-developed-locally language SDKs in a
separate
tab, and engage with the groups working on SDK certification /
validation to see if there is any additional information we can show.
Also as a comparison point see
<a class="moz-txt-link-freetext" href="https://kubernetes.io/docs/reference/using-api/client-libraries/">https://kubernetes.io/docs/reference/using-api/client-libraries/</a>
<br>
<br>Thanks !
<br>
<br></div>
</blockquote>
<br>
</body></html>