What sort of specification are you talking about here -- specs for individual plugins or a spec for how to implement a plugin? If the latter, what is the relationship of that to the official documentation about how to create a plugin (to be added to the Developer Guide)?
meg On Fri, Jan 23, 2015 at 1:43 AM, Nikolay Markov <nmar...@mirantis.com> wrote: > I also wanted to add that there is a PR already on adding plugins > repos to stackforge: https://review.openstack.org/#/c/147169/ > > There is a battle in comments right now, because some people are not > agree that so many repos are needed. > > On Fri, Jan 23, 2015 at 1:25 AM, Mike Scherbakov > <mscherba...@mirantis.com> wrote: > > Hi Fuelers, > > we've implemented pluggable architecture piece in 6.0, and got a number > of > > plugins already. Overall development process for plugins is still not > fully > > defined. > > We initially thought that having all the plugins in one repo on > stackforge > > is Ok, we also put some docs into existing fuel-docs repo, and specs to > > fuel-specs. > > > > We might need a change here. Plugins are not tight to any particular > release > > date, and they can also be separated each from other in terms of > committers > > and core reviewers. Also, it seems to be pretty natural to keep all docs > and > > design specs associated with particular plugin. > > > > With all said, following best dev practices, it is suggested to: > > > > Have a separate stackforge repo per Fuel plugin in format > > "fuel-plugin-<name>", with separate core-reviewers group which should > have > > plugin contributor initially > > Have docs folder in the plugin, and ability to build docs out of it > > > > do we want Sphinx or simple Github docs format is Ok? So people can just > go > > to github/stackforge to see docs > > > > Have specification in the plugin repo > > > > also, do we need Sphinx here? > > > > Have plugins tests in the repo > > > > Ideas / suggestions / comments? > > Thanks, > > -- > > Mike Scherbakov > > #mihgen > > > > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > -- > Best regards, > Nick Markov > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev