openstack/election
Code Issues Proposed changes

Add Dean Troyer as a candidate for OpenStackClient PTL

Browse Source 
Change-Id: I73719b30a7d664f29a68227cbe8a9bbf4a1cfb20
This commit is contained in:
Dean Troyer 2017-01-26 13:49:25 -06:00
parent 9a32414cfc
commit e4578e3a41
1 changed files with 39 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
candidates/pike/OpenStackClient/dtroyer.txt Normal file
View File

@ -0,0 +1,39 @@
Dean Troyer (dtroyer)
I am running for re-election as the OpenStackClient PTL.
We accomplished some major milestones in the last term:
* Continued working toward parity with the cinder and neutron CLIs
* Participated in a UX study in Barcelona focused on patterns
around volume commands.
In the coming releases we hope to:
* Volume v3 support
* Revise the plugin interface to allow plugins to hook in to common
commands, such as quota set/show
* Add support for higher-layer value-add commands, such as a project
purge command that can remove all resources owned by a project across
all APIs (this also requires the revised plugin interface)
* Move more command implementations to utilise the OpenStack SDK once it
reaches a 1.0 release. (This also reduces dependencies.)
* Continue to migrate useful common code into osc-lib for use by
plugins and stand-alone CLIs. This includes basic command support
code that is not API-specific.
The os-client-config library is also included in the OpenStackClient
project. Our plans for it in the near future are:
* Refactor the primary configuration functionality to allow flexibility
to support different needs in calling applications, such as the order
of operations and plugin loading.
* Collect all of the 'magic' configuration bits used in multiple apps
in one place so we can converge support for common user expectations.
Most of all, I want to see us continue our mission of providing a
(wait for it...) consistent interface to OpenStack via the CLI.
Sometimes this means changing how we think about certain operations
in individual projects, sometimes it means providing direction for new
operations, and mostly it means finding the common ground that makes
our users lives simpler.
I thank you and am honored by your support.