Excerpts from Matt Riedemann's message of 2018-06-04 18:46:15 -0500: > On 6/4/2018 4:20 PM, Doug Hellmann wrote: > > See my comments on the other part of the thread, but I think this is too > > optimistic until we add a couple of people to the review team on OSC. > > > > Others from the OSC team who have a better perspective on how much work > > is actually left may have a different opinion though? > > Yeah that is definitely something I was thinking about in Vancouver. > > Would a more realistic goal be to decentralize the OSC code, like the > previous goal about how tempest plugins were done? Or similar to the > docs being decentralized? That would spread the review load onto the > projects that are actually writing CLIs for their resources - which they > are already doing in their per-project clients, e.g. python-novaclient > and python-cinderclient. >
In the past we've tried to avoid that because we wanted some consistency in the UI design. I don't know if it's time to give up on that and reconsider dividing the commands into multiple repos, or just ask that people participate in building this tool for our users. I don't think it would be any more complicated to do the work in the OSC repo and gain some minimal experience that could let folks become cores than it would be to do the same work in a repo where they are already core. The plugin APIs are relatively stable so it's basically the same code. Doug __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
