[openstack-dev] [Fuel][Plugins] Rules for Fuel Plugins: short-term perspective action plan

Irina Povolotskaya ipovolotskaya at mirantis.com
Wed Feb 24 14:32:01 UTC 2016

Hi Dmitry,

I wanted to follow-up on the 'let's have some rules' email.
For now, there are many requests on repo creation for Fuel Plugins and we
need to think
on the best way to proceed here.

In the long-term perspective;
the theme of the rules for Fuel Plugins and transition manner between
stages is more for a discussion on the OpenStack summit - would you agree?

As for the short-term perspective, we will speak about new and already
existing plugins.

For new plugins, there needs to be the following flow from Fuel core team
(on creating a repo):
1) make sure the plugin has several maintainers and is intended for further
maintenance (i.e. is not for the one and only Fuel release).
2) once repo is created,  request adding the plugin entry to DriverLog to
have very specific personas in charge of this plugins' future
3) provide baseline information into README file to let everyone now about
the plugin's functionality and add someone from Fuel core team to review

For already existing plugins:
there needs to be a survey on already existing plugins that aren't updated
any longer; their repos can be moved back into private ones or might be
owned by new maintainers (if those willing to take up this regular task are

Similar exercise was so far done when stackforge NS was becoming obsolete
and the corresponding repo owners were asked to update the wiki page and
add the repo entry into the corresponding list if they were willing to get
their repo be moved to openstack NS (=if they were willing to continue
working on specific project).

If the current plugin maintainers are not willing to work on their plugin
any longer, they should post the corresponding request in openstack-dev ML
and ask if any volunteers are present.

If no volunteers are in place, then the code should live in the private
repo of the current maintainers, with README/DriverLog updated accordingly.

I would appreciate any extra ideas in terms of things to do right now.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160224/bce43419/attachment.html>

More information about the OpenStack-dev mailing list