On Fri, 24 Mar 2017, 5:06 p.m. Lauren Sell, <lau...@openstack.org> wrote:
> Hi everyone, > > We’ve been talking for some time about updating the project navigator, and > we have a draft ready to share for community feedback before we launch and > publicize it. One of the big goals coming out of the joint TC/UC/Board > meeting a few weeks ago[1] was to help better communicate ‘what is > openstack?’ and this is one step in that direction. > > A few goals in mind for the redesign: > - Represent all official, user-facing projects and deployment services in > the navigator > - Better categorize the projects by function in a way that makes sense to > prospective users (this may evolve over time as we work on mapping the > OpenStack landscape) > - Help users understand which projects are mature and stable vs emerging > - Highlight popular project sets and sample configurations based on > different use cases to help users get started > > For a bit of context, we’re working to give each OpenStack official > project a stronger platform as we think of OpenStack as a framework of > composable infrastructure services that can be used individually or > together as a powerful system. This includes the project mascots (so we in > effect have logos to promote each component separately), updates to the > project navigator, and bringing back the “project updates” track at the > Summit to give each PTL/core team a chance to provide an update on their > project roadmap (to be recorded and promoted in the project navigator among > other places!). > > We want your feedback on the project navigator v2 before it launches. > Please take a look at the current version on the staging site and provide > feedback on this thread. > > http://devbranch.openstack.org/software/project-navigator/ > I've tried the site on a mobile phone, overall it looks fine, but after clicking on a project, the text in the project details table is not readable. > > > Please review the overall concept and the data and description for your > project specifically. The data is primarily pulled from TC tags[2] and Ops > tags[3]. You’ll notice some projects have more information available than > others for various reasons. That’s one reason we decided to downplay the > maturity metric for now and the data on some pages is hidden. If you think > your project is missing data, please check out the repositories and submit > changes or again respond to this thread. > Should Tempest / QA be in the list? > Also know this will continue to evolve and we are open to feedback. As I > mentioned, a team that formed at the joint strategy session a few weeks ago > is tackling how we map OpenStack projects, which may be reflected in the > categories. And I suspect we’ll continue to build out additional tags and > better data sources to be incorporated. > > Thanks for your feedback and help. > > Best, > Lauren > > [1] > http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/ > [2] https://governance.openstack.org/tc/reference/tags/ > [3] https://wiki.openstack.org/wiki/Operations/Tags > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-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