settingsLogin | Registersettings

[openstack-dev] Project Navigator Updates - Feedback Request

0 votes

Hi everyone,

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.

A few goals in mind for the redesign:
- Represent all official, user-facing projects and deployment services in the navigator
- 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)
- Help users understand which projects are mature and stable vs emerging
- Highlight popular project sets and sample configurations based on different use cases to help users get started

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!).

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.

http://devbranch.openstack.org/software/project-navigator/ http://devbranch.openstack.org/software/project-navigator/

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.

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.

Thanks for your feedback and help.

Best,
Lauren

[1] http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/ http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/
[2] https://governance.openstack.org/tc/reference/tags/ https://governance.openstack.org/tc/reference/tags/
[3] https://wiki.openstack.org/wiki/Operations/Tags https://wiki.openstack.org/wiki/Operations/Tags


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Apr 24, 2017 in openstack-dev by Lauren_Sell (2,240 points)   5

30 Responses

0 votes

If I start typing something in the search box, I get an "Authentication
Required" popup that captures the remaining keystrokes that I intended to
type into the search box.

Then if I do manage to type a complete search term into the box, and press
Enter, that "Authentication Required" popup pops up again, and the search
doesn't happen.

(I'm guessing it's probably a mistake and you didn't intend this to be
authentication-protected...)

Neil

On Fri, Mar 24, 2017 at 4:58 PM Lauren Sell lauren@openstack.org wrote:

Hi everyone,

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.

A few goals in mind for the redesign:
- Represent all official, user-facing projects and deployment services in
the navigator
- 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)
- Help users understand which projects are mature and stable vs emerging
- Highlight popular project sets and sample configurations based on
different use cases to help users get started

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!).

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.

http://devbranch.openstack.org/software/project-navigator/

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.

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.

Thanks for your feedback and help.

Best,
Lauren

[1]
http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/
[2] https://governance.openstack.org/tc/reference/tags/
[3] https://wiki.openstack.org/wiki/Operations/Tags


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 24, 2017 by neil_at_tigera.io (3,740 points)   2 3
0 votes

Lauren,

Can we also update the sample configurations? We should certainly have Neutron now in the HTC (since nova-network deprecation)

Tim

From: Lauren Sell lauren@openstack.org
Reply-To: "OpenStack Development Mailing List (not for usage questions)" openstack-dev@lists.openstack.org
Date: Friday, 24 March 2017 at 17:57
To: "OpenStack Development Mailing List (not for usage questions)" openstack-dev@lists.openstack.org
Subject: [openstack-dev] Project Navigator Updates - Feedback Request

Hi everyone,

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.

A few goals in mind for the redesign:
- Represent all official, user-facing projects and deployment services in the navigator
- 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)
- Help users understand which projects are mature and stable vs emerging
- Highlight popular project sets and sample configurations based on different use cases to help users get started

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!).

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.

http://devbranch.openstack.org/software/project-navigator/

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.

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.

Thanks for your feedback and help.

Best,
Lauren

[1] http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/
[2] https://governance.openstack.org/tc/reference/tags/
[3] https://wiki.openstack.org/wiki/Operations/Tags


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 24, 2017 by Tim_Bell (16,440 points)   1 6 10
0 votes

Neil sorry about that, problem solved, please re test
regards

2017-03-24 14:02 GMT-03:00 Neil Jerram neil@tigera.io:

If I start typing something in the search box, I get an "Authentication
Required" popup that captures the remaining keystrokes that I intended to
type into the search box.

Then if I do manage to type a complete search term into the box, and press
Enter, that "Authentication Required" popup pops up again, and the search
doesn't happen.

(I'm guessing it's probably a mistake and you didn't intend this to be
authentication-protected...)

Neil

On Fri, Mar 24, 2017 at 4:58 PM Lauren Sell lauren@openstack.org wrote:

Hi everyone,

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.

A few goals in mind for the redesign:
- Represent all official, user-facing projects and deployment services in
the navigator
- 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)
- Help users understand which projects are mature and stable vs emerging
- Highlight popular project sets and sample configurations based on
different use cases to help users get started

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!).

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.

http://devbranch.openstack.org/software/project-navigator/

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.

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.

Thanks for your feedback and help.

Best,
Lauren

[1] http://superuser.openstack.org/articles/community-leadership-charts-
course-openstack/
[2] https://governance.openstack.org/tc/reference/tags/
[3] https://wiki.openstack.org/wiki/Operations/Tags



OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:
unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Sebastian Marcet
https://ar.linkedin.com/in/smarcet
SKYPE: sebastian.marcet


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 24, 2017 by Sebastian_Marcet (220 points)  
0 votes

Thanks, Sebastian, it looks good now.

On Fri, Mar 24, 2017 at 5:12 PM Sebastian Marcet smarcet@gmail.com wrote:

Neil sorry about that, problem solved, please re test
regards

2017-03-24 14:02 GMT-03:00 Neil Jerram neil@tigera.io:

If I start typing something in the search box, I get an "Authentication
Required" popup that captures the remaining keystrokes that I intended to
type into the search box.

Then if I do manage to type a complete search term into the box, and press
Enter, that "Authentication Required" popup pops up again, and the search
doesn't happen.

(I'm guessing it's probably a mistake and you didn't intend this to be
authentication-protected...)

Neil

On Fri, Mar 24, 2017 at 4:58 PM Lauren Sell lauren@openstack.org wrote:

Hi everyone,

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.

A few goals in mind for the redesign:
- Represent all official, user-facing projects and deployment services in
the navigator
- 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)
- Help users understand which projects are mature and stable vs emerging
- Highlight popular project sets and sample configurations based on
different use cases to help users get started

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!).

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.

http://devbranch.openstack.org/software/project-navigator/

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.

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.

Thanks for your feedback and help.

Best,
Lauren

[1]
http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/
[2] https://governance.openstack.org/tc/reference/tags/
[3] https://wiki.openstack.org/wiki/Operations/Tags


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Sebastian Marcet
https://ar.linkedin.com/in/smarcet
SKYPE: sebastian.marcet


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 24, 2017 by neil_at_tigera.io (3,740 points)   2 3
0 votes

Yes, definitely. We’ve started updating the sample configs with web apps and big data (primarily driven by the Enterprise Working Group and Kathy Cacciatore on the Foundation team) and are about to publish eCommerce. We could pull down HTC or some of the other outdated ones for now until we’re able to update them.

On Mar 24, 2017, at 12:08 PM, Tim Bell Tim.Bell@cern.ch wrote:

Lauren,

Can we also update the sample configurations? We should certainly have Neutron now in the HTC (since nova-network deprecation)

Tim

From: Lauren Sell <lauren@openstack.org lauren@openstack.org>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org>
Date: Friday, 24 March 2017 at 17:57
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org>
Subject: [openstack-dev] Project Navigator Updates - Feedback Request

Hi everyone,

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.

A few goals in mind for the redesign:
- Represent all official, user-facing projects and deployment services in the navigator
- 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)
- Help users understand which projects are mature and stable vs emerging
- Highlight popular project sets and sample configurations based on different use cases to help users get started

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!).

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.

http://devbranch.openstack.org/software/project-navigator/

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.

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.

Thanks for your feedback and help.

Best,
Lauren

[1] http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/
[2] https://governance.openstack.org/tc/reference/tags/ https://governance.openstack.org/tc/reference/tags/
[3] https://wiki.openstack.org/wiki/Operations/Tags https://wiki.openstack.org/wiki/Operations/Tags


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 24, 2017 by Lauren_Sell (2,240 points)   5
0 votes

On 3/24/2017 11:57 AM, Lauren Sell wrote:
Hi everyone,

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.

A few goals in mind for the redesign:
- Represent all official, user-facing projects and deployment services
in the navigator
- 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)
- Help users understand which projects are mature and stable vs emerging
- Highlight popular project sets and sample configurations based on
different use cases to help users get started

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!).

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.

http://devbranch.openstack.org/software/project-navigator/

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.

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.

Thanks for your feedback and help.

Best,
Lauren

[1] http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/
[2] https://governance.openstack.org/tc/reference/tags/
[3] https://wiki.openstack.org/wiki/Operations/Tags


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Overall I like the groupings of the projects in the main page. When I
drill into Nova, a couple of things:

  1. The link for the install guide goes to the home page for docs.o.o
    rather than https://docs.openstack.org/project-install-guide/ocata/ - is
    that intentional?

  2. The "API Version History" section in the bottom right says:

"Version v2.1 (Ocata) - LATEST RELEASE"

And links to https://releases.openstack.org/. The latest compute
microversion in Ocata was actually 2.42:

https://docs.openstack.org/developer/nova/api_microversion_history.html

I'm wondering how we can better sort that out. I guess "API Version
History" in the navigator is meant more for major versions and wasn't
intended to handle microversions? That seems like something that should
be dealt with at some point as more and more projects are moving to
using microversions.

--

Thanks,

Matt


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 24, 2017 by mriedemos_at_gmail.c (15,720 points)   2 4 10
0 votes

On 24/03/17 12:57, Lauren Sell wrote:
Hi everyone,

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.

A few goals in mind for the redesign:
- Represent all official, user-facing projects and deployment services
in the navigator
- 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)
- Help users understand which projects are mature and stable vs emerging
- Highlight popular project sets and sample configurations based on
different use cases to help users get started

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!).

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.

http://devbranch.openstack.org/software/project-navigator/

Some of the groupings seem a little bit strange. It's weird to see Heat
and Horizon, which are essentially just two different user interfaces to
OpenStack, in different groups. Also strange to see Senlin in a
different group to Heat, since they both do autoscaling. I can't imagine
why Mistral is listed under "Security, Identity and Compliance". There's
quite a few more that look odd to me as well, mostly as a result of
stuff that I might have expected to all land together in a catch-all
like "Application Services" being split into more specific categories,
like Freezer going under Storage.

Also this trend of not having links, just areas of the screen with
attached JavaScript to switch to a new page when you click on them, is
breaking the web. There are 47 things to dig into on this page. I should
be allowed to open tabs!!!

In list view, everything 'links' (I use the term loosely) to
http://devbranch.openstack.org/software/releases/ocata/components/undefined
(nice 404 page btw :)

When hitting the back button after you navigate away - which you have to
do, because you can't open in a new tab - the display always reverts to
tiles view.

  • ZB

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.

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.

Thanks for your feedback and help.

Best,
Lauren

[1] http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/
[2] https://governance.openstack.org/tc/reference/tags/
[3] https://wiki.openstack.org/wiki/Operations/Tags


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 24, 2017 by Zane_Bitter (21,640 points)   4 6 9
0 votes

On Fri, 24 Mar 2017, 5:06 p.m. Lauren Sell, lauren@openstack.org wrote:

Hi everyone,

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.

A few goals in mind for the redesign:
- Represent all official, user-facing projects and deployment services in
the navigator
- 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)
- Help users understand which projects are mature and stable vs emerging
- Highlight popular project sets and sample configurations based on
different use cases to help users get started

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!).

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.

http://devbranch.openstack.org/software/project-navigator/

I've tried the site on a mobile phone, overall it looks fine, but after
clicking on a project, the text in the project details table is not
readable.

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.

Should Tempest / QA be in the list?

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.

Thanks for your feedback and help.

Best,
Lauren

[1]
http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/
[2] https://governance.openstack.org/tc/reference/tags/
[3] https://wiki.openstack.org/wiki/Operations/Tags


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 25, 2017 by Andrea_Frittoli (5,920 points)   1 2 3
0 votes

Hi Matt,

Thanks for the feedback.

On Mar 24, 2017, at 3:50 PM, Matt Riedemann mriedemos@gmail.com wrote:

Overall I like the groupings of the projects in the main page. When I drill into Nova, a couple of things:

  1. The link for the install guide goes to the home page for docs.o.o rather than https://docs.openstack.org/project-install-guide/ocata/ https://docs.openstack.org/project-install-guide/ocata/ - is that intentional?

Good point. We’ll directly the link to the install guide and also change the wording in the project details to something along the lines of “Nova is included in the install guide” since it’s not linking directly to the project-specific install guide.

  1. The "API Version History" section in the bottom right says:

"Version v2.1 (Ocata) - LATEST RELEASE"

And links to https://releases.openstack.org/ https://releases.openstack.org/. The latest compute microversion in Ocata was actually 2.42:

https://docs.openstack.org/developer/nova/api_microversion_history.html https://docs.openstack.org/developer/nova/api_microversion_history.html

I'm wondering how we can better sort that out. I guess "API Version History" in the navigator is meant more for major versions and wasn't intended to handle microversions? That seems like something that should be dealt with at some point as more and more projects are moving to using micro versions.

Agreed, we could use some guidance here. From what we can tell, each team logs these a little bit differently, so there’s no easy way for us to pull them. Could we output the correct link as a tag for each project, or does anyone have a recommendation?

Thanks!

--

Thanks,

Matt


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 27, 2017 by Lauren_Sell (2,240 points)   5
0 votes

I have a few comments on the updated Project Navigator.

  1. I hope this is mostly automated at this point? The current content for Project Navigator is very out of date (Mitaka?) and folks have asked why projects are not listed there.
  2. What is the policy around the tags? For octavia I see that standard deprecation isn’t listed there even though our neutron-lbaas repository does have the tag. Granted, I need to update the octavia repository to also have the tag, but with projects that have multiple sub-projects, how is this listing determined?
  3. How is the project age determined? I see that octavia shows one year, but it has been an active project since 2014. 2012 if you count neutron-lbaas (now part of octavia). This could be confusing for folks that have attended summit sessions in the past or downloaded the packages previously.
  4. API version history is another item I am curious to understand how it is calculated. It seems confusing with actual project API versions/microversions when it links to the releases page. API version history is not a one-to-one relationship with project releases.
  5. The “About this project” seems to come from the developer documentation. Is this something the PTL can update?
  6. Is there a way to highlight that a blank adoption is because a project was not included in the survey? This can also be deceiving and lead someone to think that a project is unused. (Looking at page 54 of the April survey from 2016 I expect load balancing is widely used)
  7. Finally, from reading my above questions/comments, it would be nice to have a “PTL guide to project navigator”.

Thank you for updating this, folks have asked us why octavia was not listed.

Michael

From: Lauren Sell [mailto:lauren@openstack.org]
Sent: Friday, March 24, 2017 9:58 AM
To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org
Subject: [openstack-dev] Project Navigator Updates - Feedback Request

Hi everyone,

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.

A few goals in mind for the redesign:
- Represent all official, user-facing projects and deployment services in the navigator
- 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)
- Help users understand which projects are mature and stable vs emerging
- Highlight popular project sets and sample configurations based on different use cases to help users get started

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!).

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.

http://devbranch.openstack.org/software/project-navigator/

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.

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.

Thanks for your feedback and help.

Best,
Lauren

[1] http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/
[2] https://governance.openstack.org/tc/reference/tags/
[3] https://wiki.openstack.org/wiki/Operations/Tags


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Mar 28, 2017 by Michael_Johnson (4,380 points)   4 5
...