<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Lauren,</p>
<p>I am taking a look at the Cinder page. All-in-all this looks
nice. Couple of thoughts/questions:</p>
<ul>
<li>The install guide doesn't go to the guide for Cinder, just to
the docs.openstack.org website. Is that intentional?</li>
<li>The "Find this service in the Marketplace" goes off to the
devbranch right now and requires authentication.<br>
</li>
<li>I like the Most Active contributors section. Would it be
possible to get the names in the same format (<First Name>
<Last Name>) and possibly include the IRC nick? I am
guessing you are getting different formats due to the way it is
queried. If you can't fix that, at least associating it with
the IRC nick would be good.</li>
</ul>
<p>Let me know if you have any questions. Looks like a good thing
for OpenStack to have.</p>
<p>Thanks!</p>
<p>Jay</p>
<p><br>
</p>
<br>
<br>
<div class="moz-cite-prefix">On 3/24/2017 11:57 AM, Lauren Sell
wrote:<br>
</div>
<blockquote
cite="mid:5B66DF63-04EF-4D86-912F-319AF20C8CB6@openstack.org"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Hi everyone,
<div class=""><br class="">
</div>
<div class="">We’ve been talking for some time about updating the
project navigator, and we have a draft ready to share for
community feedback before we launch and publicize it. One of the
big goals coming out of the joint TC/UC/Board meeting a few
weeks ago[1] was to help better communicate ‘what is openstack?’
and this is one step in that direction.<br class="">
<br class="">
A few goals in mind for the redesign:<br class="">
- Represent all official, user-facing projects and deployment
services in the navigator<br class="">
- Better categorize the projects by function in a way that makes
sense to prospective users (this may evolve over time as we work
on mapping the OpenStack landscape)<br class="">
- Help users understand which projects are mature and stable vs
emerging<br class="">
- Highlight popular project sets and sample configurations based
on different use cases to help users get started<br class="">
<br class="">
For a bit of context, we’re working to give each OpenStack
official project a stronger platform as we think of OpenStack as
a framework of composable infrastructure services that can be
used individually or together as a powerful system. This
includes the project mascots (so we in effect have logos to
promote each component separately), updates to the project
navigator, and bringing back the “project updates” track at the
Summit to give each PTL/core team a chance to provide an update
on their project roadmap (to be recorded and promoted in the
project navigator among other places!). <br class="">
<br class="">
We want your feedback on the project navigator v2 before it
launches. Please take a look at the current version on the
staging site and provide feedback on this thread.<br class="">
<br class="">
<a moz-do-not-send="true"
href="http://devbranch.openstack.org/software/project-navigator/"
class="">http://devbranch.openstack.org/software/project-navigator/</a><br
class="">
<br class="">
Please review the overall concept and the data and description
for your project specifically. The data is primarily pulled from
TC tags[2] and Ops tags[3]. You’ll notice some projects have
more information available than others for various reasons.
That’s one reason we decided to downplay the maturity metric for
now and the data on some pages is hidden. If you think your
project is missing data, please check out the repositories and
submit changes or again respond to this thread.<br class="">
<br class="">
Also know this will continue to evolve and we are open to
feedback. As I mentioned, a team that formed at the joint
strategy session a few weeks ago is tackling how we map
OpenStack projects, which may be reflected in the categories.
And I suspect we’ll continue to build out additional tags and
better data sources to be incorporated.<br class="">
<br class="">
Thanks for your feedback and help.<br class="">
<br class="">
Best,<br class="">
Lauren<br class="">
<br class="">
[1] <a moz-do-not-send="true"
href="http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/"
class="">http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/</a><br
class="">
[2] <a moz-do-not-send="true"
href="https://governance.openstack.org/tc/reference/tags/"
class="">https://governance.openstack.org/tc/reference/tags/</a><br
class="">
[3] <a moz-do-not-send="true"
href="https://wiki.openstack.org/wiki/Operations/Tags"
class="">https://wiki.openstack.org/wiki/Operations/Tags</a></div>
<div class=""><br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
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>
<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>
</pre>
</blockquote>
<br>
</body>
</html>