<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Mike,</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class="">I also wanted to add that there is a PR already on adding plugins<br class="">repos to stackforge: <a href="https://review.openstack.org/#/c/147169/" class="">https://review.openstack.org/#/c/147169/</a></blockquote></div><div class="">All this looks good, but it’s not clear when this patch will be merged and repos are created.</div><div class="">So the question is what should we do with the current spec made in fuel-specs[1,2] which are targeted for plugins?</div><div class="">And how will look development process for plugins added to 6.1 roadmap? </div><div class="">Especially for plugins came not from external vendors and partners. Will we create separate projects on the Launchpad and duplicate our </div><div class="">For now I’m not sure if we need to wait for new infrastructure created in stackforge/launchpad for each plugin and follow the common </div><div class="">procedure to land current plugins to existing repos during 6.1 milestone.</div><div class=""><br class=""></div><div class="">[1] <a href="https://review.openstack.org/#/c/129586/" class="">https://review.openstack.org/#/c/129586/</a></div><div class="">[2] <a href="https://review.openstack.org/#/c/148475/4" class="">https://review.openstack.org/#/c/148475/4</a></div><br class=""><div class="">
<div class="">Regards,</div><div class="">Alexander Ignatov</div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 23 Jan 2015, at 12:43, Nikolay Markov <<a href="mailto:nmarkov@mirantis.com" class="">nmarkov@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">I also wanted to add that there is a PR already on adding plugins<br class="">repos to stackforge: <a href="https://review.openstack.org/#/c/147169/" class="">https://review.openstack.org/#/c/147169/</a><br class=""><br class="">There is a battle in comments right now, because some people are not<br class="">agree that so many repos are needed.<br class=""><br class="">On Fri, Jan 23, 2015 at 1:25 AM, Mike Scherbakov<br class=""><<a href="mailto:mscherbakov@mirantis.com" class="">mscherbakov@mirantis.com</a>> wrote:<br class=""><blockquote type="cite" class="">Hi Fuelers,<br class="">we've implemented pluggable architecture piece in 6.0, and got a number of<br class="">plugins already. Overall development process for plugins is still not fully<br class="">defined.<br class="">We initially thought that having all the plugins in one repo on stackforge<br class="">is Ok, we also put some docs into existing fuel-docs repo, and specs to<br class="">fuel-specs.<br class=""><br class="">We might need a change here. Plugins are not tight to any particular release<br class="">date, and they can also be separated each from other in terms of committers<br class="">and core reviewers. Also, it seems to be pretty natural to keep all docs and<br class="">design specs associated with particular plugin.<br class=""><br class="">With all said, following best dev practices, it is suggested to:<br class=""><br class="">Have a separate stackforge repo per Fuel plugin in format<br class="">"fuel-plugin-<name>", with separate core-reviewers group which should have<br class="">plugin contributor initially<br class="">Have docs folder in the plugin, and ability to build docs out of it<br class=""><br class="">do we want Sphinx or simple Github docs format is Ok? So people can just go<br class="">to github/stackforge to see docs<br class=""><br class="">Have specification in the plugin repo<br class=""><br class="">also, do we need Sphinx here?<br class=""><br class="">Have plugins tests in the repo<br class=""><br class="">Ideas / suggestions / comments?<br class="">Thanks,<br class="">--<br class="">Mike Scherbakov<br class="">#mihgen<br class=""><br class=""><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""><br class=""></blockquote><br class=""><br class=""><br class="">-- <br class="">Best regards,<br class="">Nick Markov<br class=""><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></body></html>