[chef] Renaming the Chef OpenStack project
In order to clean up some inconsistencies in project naming I have submitted a request to the TC to update the name of the Chef OpenStack project to "openstack-chef"[0]. The reasoning for this is twofold: a) It brings the name into line with other deployment projects like "OpenStack Ansible" and "OpenStack Charms". b) In addition there are sometimes drawbacks when there is an embedded space in the name, so I opted for the hyphenated version. Together with lowercasing everything this also has the effect to match: - The name of our central repository - The name of our IRC channel - Our project name on Launchpad Please let me know whether you agree with this change or if there are any objections. [0] https://review.openstack.org/648356
On Mon, Apr 8, 2019 at 7:58 AM Jens Harbott <frickler@offenerstapel.de> wrote:
In order to clean up some inconsistencies in project naming I have submitted a request to the TC to update the name of the Chef OpenStack project to "openstack-chef"[0]. The reasoning for this is twofold:
a) It brings the name into line with other deployment projects like "OpenStack Ansible" and "OpenStack Charms". b) In addition there are sometimes drawbacks when there is an embedded space in the name, so I opted for the hyphenated version. Together with lowercasing everything this also has the effect to match: - The name of our central repository - The name of our IRC channel - Our project name on Launchpad
Please let me know whether you agree with this change or if there are any objections.
I don't think I have too much of a problem with it but I can think of a few consumers who might want to mention if they're broken which are - openstack-map / OSF website - release team - stackalytics(?) I haven't dug into the history if we've ever done a similar rename, but perhaps one of our OpenStack historians can point to commits in the past where we've done the same and how it was dealt with in other places.
-- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com W. http://vexxhost.com
On 2019-04-12 10:56:17 -0400 (-0400), Mohammed Naser wrote: [...]
I haven't dug into the history if we've ever done a similar rename, but perhaps one of our OpenStack historians can point to commits in the past where we've done the same and how it was dealt with in other places.
2018-03-23 PowerStackers -> PowerVMStackers https://review.openstack.org/551413 2017-12-12 Shade -> OpenStackSDK https://review.openstack.org/523520 2015-12-15 Release Cycle Management -> Release Management https://review.openstack.org/255379 2014-08-20 Marconi -> Zaqar https://review.openstack.org/114770 2014-03-17 Savanna -> Sahara https://review.openstack.org/79765 2013-11-27 Ceilometer -> Telemetry https://review.openstack.org/56402 2013-07-06 Quantum -> Neutron [before openstack/governance repo existed] And there are probably a few more I'm forgetting. A number of unofficial teams also changed their names at the same as time or immediately prior to petitioning the TC for recognition as official programs or projects, mostly for legal/trademark reasons. -- Jeremy Stanley
On Fri, Apr 12, 2019 at 10:56:17AM -0400, Mohammed Naser wrote:
I don't think I have too much of a problem with it but I can think of a few consumers who might want to mention if they're broken which are
- openstack-map / OSF website - release team
The release-team is fine as Chef uses it's own external process: [tony@thor releases]$ git grep -Ei chef deliverables/ [tony@thor releases]$ cd governance [tony@thor governance]$ yq '.["Chef OpenStack"]["deliverables"][]["release-management"]' reference/projects.yaml "external" "external" "external" "external" "external" "external" "external" "external" "external" "external" "external" "external" "external" "external" "external" "external" "external" "external" "external" "none" Yours Tony.
On Fri, 2019-04-12 at 10:56 -0400, Mohammed Naser wrote:
On Mon, Apr 8, 2019 at 7:58 AM Jens Harbott <frickler@offenerstapel.d e> wrote:
In order to clean up some inconsistencies in project naming I have submitted a request to the TC to update the name of the Chef OpenStack project to "openstack-chef"[0]. The reasoning for this is twofold:
a) It brings the name into line with other deployment projects like "OpenStack Ansible" and "OpenStack Charms". b) In addition there are sometimes drawbacks when there is an embedded space in the name, so I opted for the hyphenated version. Together with lowercasing everything this also has the effect to match: - The name of our central repository - The name of our IRC channel - Our project name on Launchpad
Please let me know whether you agree with this change or if there are any objections.
I don't think I have too much of a problem with it but I can think of a few consumers who might want to mention if they're broken which are
- openstack-map / OSF website
I did a patch[1] for that, which has already been merged and the map has been updated accordingly [2].
- release team
Tony has answered this one.
- stackalytics(?)
I think our team doesn't care much about stackalytics at this point. Jens [1] https://review.openstack.org/645196 [2] https://www.openstack.org/assets/software/projectmap/openstack-map. pdf
participants (4)
-
Jens Harbott
-
Jeremy Stanley
-
Mohammed Naser
-
Tony Breeds