{"id":7048,"date":"2015-07-30T11:52:24","date_gmt":"2015-07-30T16:52:24","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=7048"},"modified":"2015-07-31T10:03:46","modified_gmt":"2015-07-31T15:03:46","slug":"technical-committee-highlights-july-24-2015","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/technical-committee-highlights-july-24-2015\/","title":{"rendered":"Technical Committee Highlights July 24, 2015"},"content":{"rendered":"

Welcoming a common project for improving OpenStack user experience<\/h2>\n

We accepted a proposal for a new UX Program whose mission is to support and facilitate cross-project efforts to improve the overall user experience of OpenStack. I personally find this as exciting an effort and innovative as cross-project documentation in open source. Congratulations to this team and welcome! We look forward to great collaborative and open efforts across multiple projects.<\/p>\n

Starter kit suggestions change<\/h2>\n

With much discussion the TC decided to change the compute starter kit tag applications slightly by adding the neutron project as the networking solution and removing the cinder project as a block storage solution since starter clouds could have ephemeral storage and then add block storage later.<\/p>\n

New team for RPM packaging<\/h2>\n

A new team has been approved to manage all packaging git repos for RPM-based distributions in the \/openstack git namespace. This team will enable gate testing and reviewing of changes
\nto the packaging close to the actual OpenStack development. The co-Project Team Leads are Dirk Mueller and Haikel Guemar. This team offers packaging for SUSE, openSUSE, Fedora Linux, Red Hat Enterprise Linux, or CentOS.<\/span><\/p>\n

Stackforge resolution<\/h2>\n

Proceeding from our discussions about retiring Stackforge, we have continued to revise the resolution while still wanting to find a way to alleviate the extra work of organization renaming. The current proposal is instead of retiring the Stackforge project, we simply move all Stackforge projects into the “openstack\/” namespace and create new projects there as well. Then as projects become official OpenStack projects, no repository renames are necessary.\u00a0 Essentially, this means the “openstack\/” namespace will no longer hold only official OpenStack projects, but also any project being developed in our community-driven shared development environment.\u00a0 This should be a lot less disruptive to developers, users, and system administrators.<\/p>\n

M naming quest resolved<\/h2>\n

The M release is Mitaka, say it three times fast! Mitaka, mitaka, mitaka. And if you can write\u00a0the second character\u00a0in the name, \u4e09\u9df9, color me impressed!<\/p>\n

Service names and project names<\/h2>\n

In an insane quest for consistency and ability to write about each service in a sensible way, TC member and documentarian Anne Gentle has proposed a set of guidelines for projects and services names, even for those services that have been around a few years. After consulting with the legal team and technical editors alike, please review the proposed guidelines<\/a> and take a look at examples of possible new names<\/a> with the new guidelines applied:<\/p>\n