Its the commons problem again. Either we encourage folks to contribute a little bit to the commons (review a few other peoples noncompute cli thingies. in doing so, you learn how to better do the cli in the generic/user friendly ways), to further their own project goals (get easier access to contribute to the cli of the compute stuff), or we do what we've always done. Let each project maintain their own cli and have no uniformity at all. Why are the walls in OpenStack so high?
Kevin ________________________________________ From: Matt Riedemann [mriede...@gmail.com] Sent: Thursday, September 27, 2018 12:35 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series On 9/27/2018 2:33 PM, Fox, Kevin M wrote: > If the project plugins were maintained by the OSC project still, maybe there > would be incentive for the various other projects to join the OSC project, > scaling things up? Sure, I don't really care about governance. But I also don't really care about all of the non-compute API things in OSC either. -- 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 __________________________________________________________________________ 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
