Hello,
I pretty much agree with Evgeniya here. Keeping everything (code, docs,
specs and tests) in the same repo is essential to keep up-to-date
information. Otherwise chances are that it will diverge eventually.
See other comments inline.
BR,
Simon
On Fri, Jan 23, 2015 at 4:50 PM, Evgeniya
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
Hi Fuelers and Mike,
I'd like to provide some ideas/comments for the issues Mike has put into
discussion.
Yesterday we had a nice discussion for plugins SDK.
According to this discussion, we should create an internal document for
plugins certification ASAP (I mean, steps to perform on the
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,
Hi Mike,
All of the items look nice. I have a small comment regarding to the docs.
I don't think that we should force plugin developer to write the docs in
Sphinx compatible format, I vote for Github compatible docs format,
and in case if we want to show this information somewhere else,
we can
Mike,
I also wanted to add that there is a PR already on adding plugins
repos to stackforge: https://review.openstack.org/#/c/147169/
All this looks good, but it’s not clear when this patch will be merged and
repos are created.
So the question is what should we do with the current spec made
Folks -
I support the idea to keep plugins' code and other artifacts, e.g. design
specs, installation and user guides, test scripts, test plan, test report,
etc, in one repo, just to create dedicated folders for that.
My argument here is pretty simple, i consider a Fuel plugin as a separate
and
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
