Open Stack

On Sun, Mar 1, 2015 at 8:45 AM, Clint Byrum <clint at fewbar.com> wrote:
> Excerpts from Gary Kotton's message of 2015-03-01 02:32:37 -0800:
>> Hi,
>> I am just relaying pain-points that we encountered in neutron. As I have
>> said below it makes the development process a lot quicker for people
>> working on external drivers. I personally believe that it fragments the
>> community and feel that the external drivers loose the community
>> contributions and inputs.
>
> I think you're right that this does change the dynamic in the
> community. One way to lower the barrier is to go ahead and define the
> plugin API very strongly, but then delegate control of drivers in-tree
> to active maintainers, rather than in external repositories. If a driver
> falls below the line in terms of maintenance, then it can be deprecated.
> And if a maintainer feels strongly that they cannot include the driver
> with Ironic for whatever reason, the plugin API being strongly defined
> will allow them to do so.
>


++ on all counts.

Even with delegation of existing drivers to an active driver
maintainer(s), there is still a cost to the core review team: new
driver submissions have generally not come from existing core
reviewers. That could be mitigated if we were to encourage new drivers
to be developed and proven out of tree while the author becomes active
in the "parent" project, then when the core team feels ready, allow
the driver in-tree and delegate its maintenance.

-D