Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Jimmy McArthur]

Dmitry,

It's a good question. Right now, not very well. For this update, we 
worked to get as many projects as we could updated within the existing 
template. Post-Boston, we will revisit projects that have multiple API 
services (or otherwise don't quite fit into the project template) to see 
how we can better represent them within the navigator.  If you have any 
thoughts on the matter, please feel free to send them our way.


Thank you!
Jimmy


Dmitry Tantsur 
April 24, 2017 at 9:29 AM
Quick question, sorry for top-posting. How does it represent projects 
that have several API services, like Baremetal or Telemetry?





__ 


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Dmitry Tantsur]

Quick question, sorry for top-posting. How does it represent projects that have 
several API services, like Baremetal or Telemetry?


On 03/24/2017 05:57 PM, 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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Yuval Brik]

Missed this thread. Seems like Karbor is listed under "Security, Identity & 
Compliance" instead of "Storage, Backup & Recovery".

Couldn't find where these categories are taken from.

How can I fix that?


--Yuval


From: Lauren Sell 
Sent: Friday, March 24, 2017 7:57:52 PM
To: OpenStack Development Mailing List (not for usage questions)
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

-
This email and any files transmitted and/or attachments with it are 
confidential and proprietary information of
Toga Networks Ltd., and intended solely for the use of the individual or entity 
to whom they are addressed.
If you have received this email in error please notify the system manager. This 
message contains confidential
information of Toga Networks Ltd., and is intended only for the individual 
named. If you are not the named
addressee you should not disseminate, distribute or copy this e-mail. Please 
notify the sender immediately
by e-mail if you have received this e-mail by mistake and delete this e-mail 
from your system. If you are not
the intended recipient you are notified that disclosing, copying, distributing 
or taking any action in reliance on
the contents of this information is strictly prohibited.


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

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Jimmy McArthur]

Yes, you need to be added to the Ops Tags here: 
https://github.com/openstack/ops-tags-team/tree/master/ocata  That's 
part of the Adoption and Maturity tags.



Afek, Ifat (Nokia - IL/Kfar Sava) <mailto:ifat.a...@nokia.com>
April 3, 2017 at 2:16 AM

Hi Jimmy,

Regarding the difference between neutron.yaml and vitrage.yaml – the 
only thing I see is the different release-model. Anything else that I 
missed?


Thanks,

Ifat.

*From: *Jimmy McArthur 
*Reply-To: *"OpenStack Development Mailing List (not for usage 
questions)" 

*Date: *Thursday, 30 March 2017 at 19:23
*To: *"OpenStack Development Mailing List (not for usage questions)" 

*Subject: *Re: [openstack-dev] Project Navigator Updates - Feedback 
Request




*Afek, Ifat (Nokia - IL/Kfar Sava)* <mailto:ifat.a...@nokia.com>

March 30, 2017 at 11:01 AM



Under “API Versions” there should also be Newton

This is something we are currently attempting to sort out. Projects 
don't have a consistent method for listing the APIs. See previous thread.


Why aren’t the adoption and maturity specified?

In order for us to get more info about your project, we need to have 
the proper tags. Compare 
http://git.openstack.org/cgit/openstack/releases/plain/deliverables/ocata/neutron.yaml 
vs 
http://git.openstack.org/cgit/openstack/releases/plain/deliverables/ocata/vitrage.yaml   
As well as here: 
https://github.com/openstack/ops-tags-team/tree/master/ocata


Thanks,
Jimmy

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Jimmy McArthur <mailto:ji...@openstack.org>
March 30, 2017 at 11:23 AM


Afek, Ifat (Nokia - IL/Kfar Sava) <mailto:ifat.a...@nokia.com>
March 30, 2017 at 11:01 AM


·Under “API Versions” there should also be Newton

This is something we are currently attempting to sort out. Projects 
don't have a consistent method for listing the APIs. See previous thread.


·Why aren’t the adoption and maturity specified?

In order for us to get more info about your project, we need to have 
the proper tags. Compare 
http://git.openstack.org/cgit/openstack/releases/plain/deliverables/ocata/neutron.yaml 
vs 
http://git.openstack.org/cgit/openstack/releases/plain/deliverables/ocata/vitrage.yaml   
As well as here: 
https://github.com/openstack/ops-tags-team/tree/master/ocata


Thanks,
Jimmy


Thanks,

Ifat.

*From: *Lauren Sell 
*Reply-To: *"OpenStack Development Mailing List (not for usage 
questions)" 

*Date: *Friday, 24 March 2017 at 19:57
*To: *"OpenStack Development Mailing List (not for usage questions)" 


*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 o

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Afek, Ifat (Nokia - IL/Kfar Sava)]

Hi Jimmy,

Regarding the difference between neutron.yaml and vitrage.yaml – the only thing 
I see is the different release-model. Anything else that I missed?

Thanks,
Ifat.

From: Jimmy McArthur 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, 30 March 2017 at 19:23
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] Project Navigator Updates - Feedback Request



Afek, Ifat (Nokia - IL/Kfar Sava)<mailto:ifat.a...@nokia.com>
March 30, 2017 at 11:01 AM



Under “API Versions” there should also be Newton
This is something we are currently attempting to sort out. Projects don't have 
a consistent method for listing the APIs. See previous thread.


Why aren’t the adoption and maturity specified?
In order for us to get more info about your project, we need to have the proper 
tags. Compare 
http://git.openstack.org/cgit/openstack/releases/plain/deliverables/ocata/neutron.yaml
 vs 
http://git.openstack.org/cgit/openstack/releases/plain/deliverables/ocata/vitrage.yaml
   As well as here: https://github.com/openstack/ops-tags-team/tree/master/ocata

Thanks,
Jimmy



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

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Jimmy McArthur]

I think this is a bit of a roadblock for us getting the new Navigator 
up, so the sooner we can come to a decision the better :) Thanks for 
raising the issue with the TC!



Thierry Carrez 
March 31, 2017 at 3:43 AM

I like the idea to provide unified API information, however I'm not sure
the Technical Committee should stand in the way of getting that
information updated. The less we force through strict governance
processes, the better, so everything that can be maintained by some
other group should be.

This is closer to documentation than governance, so I wonder if this
document should not be maintained at the API WG or the Docs team or
service catalog level -- just keeping the same team names so that
information can be easily cross-referenced with the governance repository.

I'll raise the discussion in open discussion at the next TC meeting.

Brian Rosmaita 
March 29, 2017 at 9:23 PM
On 3/29/17 12:55 AM, Jimmy McArthur wrote:
[snip]

See what you think of these. They add an "apis" section to the glance
section of projects.yaml in the governance repo.

http://paste.openstack.org/show/604775/ has a complete history, where
for each release, the complete set of versions of the API that are
available in that release (and their statuses) are listed.

http://paste.openstack.org/show/604776/ has an abbreviated history,
where only the changes in available APIs are listed from version to
version, and if there's no change, the release isn't listed at all.

I don't know if this format would work for microversions, though. (And
I don't know if it's a good idea in the first place.)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Jimmy McArthur 
March 28, 2017 at 11:55 PM

Brian,

Thanks for the response. This is a tough one. Currently we're pulling 
API data manually for each project. That is no longer tenable when 
we're talking about 40+ projects. Plus, this is info is something that 
is really sought after by the community. Some thoughts below:

Brian Rosmaita 
March 28, 2017 at 10:25 PM
On 3/27/17 5:01 PM, Lauren Sell wrote:
I don't have a helpful recommendation here, but the version history 
for Glance is incorrect as well. We maintain a version history in the 
glance api-ref [0], but that's probably not much help (and, as you 
point out, is idiosyncratic to Glance anyway). At this point, though, 
my primary concern is that it's showing a deprecated API version as 
the latest release. What format would it be useful for you to get 
this data in?

What we really need is the following:

* A project history, including the date of project inception that's 
included in the TC tags.
* An API history in an easily digestible format that all projects 
share. So whether you're doing micro releases or not, just something 
that allows us to show, based on a release timeline, which API 
versions per project are applicable for each OpenStack release. This 
really needs to be consistent from project to project b/c at the 
moment everyone handles it differently.

thanks,
brian

[0]
https://developer.openstack.org/api-ref/image/versions/index.html#version-history

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Brian Rosmaita 
March 28, 2017 at 10:25 PM
On 3/27/17 5:01 PM, Lauren Sell wrote:

Hi Matt,

Thanks for the feedback.


On Mar 24, 2017, at 3:50 PM, Matt Riedemann  wrote:

[snip]

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 micro versions.

Agreed, we could use some guidance here. From what we can tell, each team

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Dave McCowan (dmccowan)]

On 3/31/17, 4:43 AM, "Thierry Carrez"  wrote:

>Brian Rosmaita wrote:
>> On 3/29/17 12:55 AM, Jimmy McArthur wrote:
>> [snip]
>>> What we really need is the following:
>>>
>>> * A project history, including the date of project inception that's
>>> included in the TC tags.
>>> * An API history in an easily digestible format that all projects
>>>share.
>>> So whether you're doing micro releases or not, just something that
>>> allows us to show, based on a release timeline, which API versions per
>>> project are applicable for each OpenStack release. This really needs to
>>> be consistent from project to project b/c at the moment everyone
>>>handles
>>> it differently.
>> 
>> See what you think of these.  They add an "apis" section to the glance
>> section of projects.yaml in the governance repo.
>> 
>> http://paste.openstack.org/show/604775/ has a complete history, where
>> for each release, the complete set of versions of the API that are
>> available in that release (and their statuses) are listed.
>> 
>> http://paste.openstack.org/show/604776/ has an abbreviated history,
>> where only the changes in available APIs are listed from version to
>> version, and if there's no change, the release isn't listed at all.
>> 
>> I don't know if this format would work for microversions, though.  (And
>> I don't know if it's a good idea in the first place.)
>
>I like the idea to provide unified API information, however I'm not sure
>the Technical Committee should stand in the way of getting that
>information updated. The less we force through strict governance
>processes, the better, so everything that can be maintained by some
>other group should be.
>
>This is closer to documentation than governance, so I wonder if this
>document should not be maintained at the API WG or the Docs team or
>service catalog level -- just keeping the same team names so that
>information can be easily cross-referenced with the governance repository.
>
>I'll raise the discussion in open discussion at the next TC meeting.
>
>-- 
>Thierry Carrez (ttx)

There used to be an item on Navigator for "Existence of quality packages
in popular distributions."   It was removed, with the intent to replace it
with a better way to maintain and update this information. [1][2]

Is now a good time to re-implement this tag as well?

[1] https://bugs.launchpad.net/openstack-org/+bug/1656843
[2] https://github.com/OpenStackweb/openstack-org/pull/59




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

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Thierry Carrez]

Brian Rosmaita wrote:
> On 3/29/17 12:55 AM, Jimmy McArthur wrote:
> [snip]
>> What we really need is the following:
>>
>> * A project history, including the date of project inception that's
>> included in the TC tags.
>> * An API history in an easily digestible format that all projects share.
>> So whether you're doing micro releases or not, just something that
>> allows us to show, based on a release timeline, which API versions per
>> project are applicable for each OpenStack release. This really needs to
>> be consistent from project to project b/c at the moment everyone handles
>> it differently.
> 
> See what you think of these.  They add an "apis" section to the glance
> section of projects.yaml in the governance repo.
> 
> http://paste.openstack.org/show/604775/ has a complete history, where
> for each release, the complete set of versions of the API that are
> available in that release (and their statuses) are listed.
> 
> http://paste.openstack.org/show/604776/ has an abbreviated history,
> where only the changes in available APIs are listed from version to
> version, and if there's no change, the release isn't listed at all.
> 
> I don't know if this format would work for microversions, though.  (And
> I don't know if it's a good idea in the first place.)

I like the idea to provide unified API information, however I'm not sure
the Technical Committee should stand in the way of getting that
information updated. The less we force through strict governance
processes, the better, so everything that can be maintained by some
other group should be.

This is closer to documentation than governance, so I wonder if this
document should not be maintained at the API WG or the Docs team or
service catalog level -- just keeping the same team names so that
information can be easily cross-referenced with the governance repository.

I'll raise the discussion in open discussion at the next TC meeting.

-- 
Thierry Carrez (ttx)

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

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Jim Rollenhagen]

On Thu, Mar 30, 2017 at 12:04 PM, Jimmy McArthur 
wrote:

> This (http://paste.openstack.org/show/604775/) is absolutely perfect. I
> feel like the format could work for microversions as well. Anyone from
> Neutron or another microversion project that could weigh in?
>

This mostly seems fine to me, a couple problems I see:

* so far projects using microversions haven't been deprecating
microversions (though I'm working on making that a thing), so I see this
bloating quickly. Ironic has over 30 supported versions as of Ocata, Nova
has even more, etc.
* I'm not sure that the governance repo is the right place for this, though
I don't have a better suggestion.
* if we do put it here, we should do it per deliverable, as some projects
may have more than one deliverable with an API (e.g. when nova spins
placement out to its own repo).

Thanks for proposing this, Brian! :)

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

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Jimmy McArthur]

Afek, Ifat (Nokia - IL/Kfar Sava) <mailto:ifat.a...@nokia.com>
March 30, 2017 at 11:01 AM


·Under “API Versions” there should also be Newton

This is something we are currently attempting to sort out. Projects 
don't have a consistent method for listing the APIs. See previous thread.


·Why aren’t the adoption and maturity specified?

In order for us to get more info about your project, we need to have the 
proper tags. Compare 
http://git.openstack.org/cgit/openstack/releases/plain/deliverables/ocata/neutron.yaml 
vs 
http://git.openstack.org/cgit/openstack/releases/plain/deliverables/ocata/vitrage.yaml   
As well as here: 
https://github.com/openstack/ops-tags-team/tree/master/ocata


Thanks,
Jimmy


Thanks,

Ifat.

*From: *Lauren Sell 
*Reply-To: *"OpenStack Development Mailing List (not for usage 
questions)" 

*Date: *Friday, 24 March 2017 at 19:57
*To: *"OpenStack Development Mailing List (not for usage questions)" 


*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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Jimmy McArthur]

This (http://paste.openstack.org/show/604775/) is absolutely perfect. I 
feel like the format could work for microversions as well. Anyone from 
Neutron or another microversion project that could weigh in?


Another great thing about this, is we can use this API version history 
to determine project age, which again is a manual thing we're doing 
right now.


Thanks!! Would love to hear others opinions on this?

Brian Rosmaita 
March 29, 2017 at 9:23 PM
On 3/29/17 12:55 AM, Jimmy McArthur wrote:
[snip]

See what you think of these. They add an "apis" section to the glance
section of projects.yaml in the governance repo.

http://paste.openstack.org/show/604775/ has a complete history, where
for each release, the complete set of versions of the API that are
available in that release (and their statuses) are listed.

http://paste.openstack.org/show/604776/ has an abbreviated history,
where only the changes in available APIs are listed from version to
version, and if there's no change, the release isn't listed at all.

I don't know if this format would work for microversions, though. (And
I don't know if it's a good idea in the first place.)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Jimmy McArthur 
March 28, 2017 at 11:55 PM

Brian,

Thanks for the response. This is a tough one. Currently we're pulling 
API data manually for each project. That is no longer tenable when 
we're talking about 40+ projects. Plus, this is info is something that 
is really sought after by the community. Some thoughts below:

Brian Rosmaita 
March 28, 2017 at 10:25 PM
On 3/27/17 5:01 PM, Lauren Sell wrote:
I don't have a helpful recommendation here, but the version history 
for Glance is incorrect as well. We maintain a version history in the 
glance api-ref [0], but that's probably not much help (and, as you 
point out, is idiosyncratic to Glance anyway). At this point, though, 
my primary concern is that it's showing a deprecated API version as 
the latest release. What format would it be useful for you to get 
this data in?

What we really need is the following:

* A project history, including the date of project inception that's 
included in the TC tags.
* An API history in an easily digestible format that all projects 
share. So whether you're doing micro releases or not, just something 
that allows us to show, based on a release timeline, which API 
versions per project are applicable for each OpenStack release. This 
really needs to be consistent from project to project b/c at the 
moment everyone handles it differently.

thanks,
brian

[0]
https://developer.openstack.org/api-ref/image/versions/index.html#version-history

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Brian Rosmaita 
March 28, 2017 at 10:25 PM
On 3/27/17 5:01 PM, Lauren Sell wrote:

Hi Matt,

Thanks for the feedback.


On Mar 24, 2017, at 3:50 PM, Matt Riedemann  wrote:

[snip]

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 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?


I don't have a helpful recommendation here, but the version history for
Glance is incorrect as well.  We maintain a version history in the
glance api-ref [0], but that's probably not much help (and, as you point
out, is idiosyncratic to Glance anyway).  At this point, though, my
primary co

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Afek, Ifat (Nokia - IL/Kfar Sava)]

Thanks Lauren,

A few issues regarding the Vitrage page:


· Vitrage is currently listed under “Management Tools” category. As a 
Root Cause Analysis service, it doesn’t manage anything, just provides insights 
to the user (or to other projects). Can you please move it under ‘Data and 
Analytics’ category?

· Please write that Vitrage is a “Root Cause Analysis Service” without 
“RCA” and parenthesis (which are misplaced at the moment).

· Under “API Versions” there should also be Newton

· Why aren’t the adoption and maturity specified?

Thanks,
Ifat.


From: Lauren Sell 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, 24 March 2017 at 19:57
To: "OpenStack Development Mailing List (not for usage questions)" 

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Brian Rosmaita]

On 3/29/17 12:55 AM, Jimmy McArthur wrote:
[snip]
> What we really need is the following:
> 
> * A project history, including the date of project inception that's
> included in the TC tags.
> * An API history in an easily digestible format that all projects share.
> So whether you're doing micro releases or not, just something that
> allows us to show, based on a release timeline, which API versions per
> project are applicable for each OpenStack release. This really needs to
> be consistent from project to project b/c at the moment everyone handles
> it differently.

See what you think of these.  They add an "apis" section to the glance
section of projects.yaml in the governance repo.

http://paste.openstack.org/show/604775/ has a complete history, where
for each release, the complete set of versions of the API that are
available in that release (and their statuses) are listed.

http://paste.openstack.org/show/604776/ has an abbreviated history,
where only the changes in available APIs are listed from version to
version, and if there's no change, the release isn't listed at all.

I don't know if this format would work for microversions, though.  (And
I don't know if it's a good idea in the first place.)


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

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Rico Lin]

 The `API Version History` links in all project seems incorrect to me (For
example, `Version v1.0 (Ocata) - LATEST RELEASE` should link to
https://releases.openstack.org/ocata/index.html#ocata-heat not
https://releases.openstack.org/ ).

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.

Agree, I suggest we can use a group `Application services` or
`Orchestration Services` for all Mistral, Heat, Senlin, etc. seems we
actually have users use OpenStack with that combinations. And we can also
consider use multi-layer grouping.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Jimmy McArthur]

Brian,

Thanks for the response. This is a tough one. Currently we're pulling 
API data manually for each project. That is no longer tenable when we're 
talking about 40+ projects. Plus, this is info is something that is 
really sought after by the community. Some thoughts below:

Brian Rosmaita 
March 28, 2017 at 10:25 PM
On 3/27/17 5:01 PM, Lauren Sell wrote:
I don't have a helpful recommendation here, but the version history 
for Glance is incorrect as well. We maintain a version history in the 
glance api-ref [0], but that's probably not much help (and, as you 
point out, is idiosyncratic to Glance anyway). At this point, though, 
my primary concern is that it's showing a deprecated API version as 
the latest release. What format would it be useful for you to get this 
data in?

What we really need is the following:

* A project history, including the date of project inception that's 
included in the TC tags.
* An API history in an easily digestible format that all projects share. 
So whether you're doing micro releases or not, just something that 
allows us to show, based on a release timeline, which API versions per 
project are applicable for each OpenStack release. This really needs to 
be consistent from project to project b/c at the moment everyone handles 
it differently.


thanks,
brian

[0]
https://developer.openstack.org/api-ref/image/versions/index.html#version-history

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Brian Rosmaita]

On 3/27/17 5:01 PM, Lauren Sell wrote:
> Hi Matt,
> 
> Thanks for the feedback. 
> 
>> On Mar 24, 2017, at 3:50 PM, Matt Riedemann  wrote:
[snip]
>> 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 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?

I don't have a helpful recommendation here, but the version history for
Glance is incorrect as well.  We maintain a version history in the
glance api-ref [0], but that's probably not much help (and, as you point
out, is idiosyncratic to Glance anyway).  At this point, though, my
primary concern is that it's showing a deprecated API version as the
latest release.  What format would it be useful for you to get this data in?

thanks,
brian

[0]
https://developer.openstack.org/api-ref/image/versions/index.html#version-history

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

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Jay S Bryant]

Lauren,

I am taking a look at the Cinder page.  All-in-all this looks nice.  
Couple of thoughts/questions:


 * The install guide doesn't go to the guide for Cinder, just to the
   docs.openstack.org website.  Is that intentional?
 * The "Find this service in the Marketplace" goes off to the devbranch
   right now and requires authentication.
 * I like the Most Active contributors section.  Would it be possible
   to get the names in the same format ( ) 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.

Let me know if you have any questions.  Looks like a good thing for 
OpenStack to have.


Thanks!

Jay




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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Alexandra Settle]

Hey Lauren,

It looks great with the new mascots :)

Is it possible to get docs and I18N represented here? I know we don’t make up a 
‘project’ of OpenStack, but we play an important part, and I would be nice to 
be represented. Especially seeing as I18n work on translating a lot of the dev 
components as well, making OpenStack available to more countries across the 
world.

Maybe we could go under a simple banner “Documentation & Translation”?

I know we are technically visible here: 
https://www.openstack.org/software/start/ but we’re kind of shunted down the 
line.

Also, OpenStack-Ansible should be edited with the hyphen if possible :)

Thanks,

Alex

From: Lauren Sell 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, March 24, 2017 at 4:57 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Michael Johnson]

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:lau...@openstack.org] 
Sent: Friday, March 24, 2017 9:58 AM
To: OpenStack Development Mailing List (not for usage questions) 

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-requ...@lists.openstack.org?subject:unsubscribe
http

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Lauren Sell]

Hi Matt,

Thanks for the feedback. 

> On Mar 24, 2017, at 3:50 PM, Matt Riedemann  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/ 
>  - 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.
> 
> 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 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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Andrea Frittoli]

On Fri, 24 Mar 2017, 5:06 p.m. 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/
>


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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Zane Bitter]

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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Matt Riedemann]

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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Lauren Sell]

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  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 mailto:lau...@openstack.org>>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
> mailto:openstack-dev@lists.openstack.org>>
> Date: Friday, 24 March 2017 at 17:57
> To: "OpenStack Development Mailing List (not for usage questions)" 
> mailto: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/ 
> <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-requ...@lists.openstack.org 
> <mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>

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

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Neil Jerram]

Thanks, Sebastian, it looks good now.

On Fri, Mar 24, 2017 at 5:12 PM Sebastian Marcet  wrote:

> Neil sorry about that, problem solved, please re test
> regards
>
> 2017-03-24 14:02 GMT-03:00 Neil Jerram :
>
> 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  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-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Sebastian Marcet]

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

2017-03-24 14:02 GMT-03:00 Neil Jerram :

> 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  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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Tim Bell]

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 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, 24 March 2017 at 17:57
To: "OpenStack Development Mailing List (not for usage questions)" 

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Project Navigator Updates - Feedback Request

[Neil Jerram]

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  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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Project Navigator Updates - Feedback Request

[Lauren Sell]

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev