Skip to content
This repository has been archived by the owner on Nov 8, 2022. It is now read-only.

Missing documentation for stand-alone feature #1687

Closed
katarzyna-z opened this issue Jul 14, 2017 · 4 comments
Closed

Missing documentation for stand-alone feature #1687

katarzyna-z opened this issue Jul 14, 2017 · 4 comments

Comments

@katarzyna-z
Copy link
Contributor

Missing documentation for stand-alone feature (at least I don't see it). Users should know how use stand-alone plugins.

@kjlyon
Copy link
Contributor

kjlyon commented Jul 14, 2017

Similar to plugin diagnostics is stand-alone functionality something that should go in the plugin libraries or should it go in the Snap documentation? What are your opinions?

@intelsdi-x/snap-maintainers

@katarzyna-z
Copy link
Contributor Author

katarzyna-z commented Aug 4, 2017

I think that documentation for stand-alone plugin should be in main Snap repo. New users takes a look at main repo and looks for features and stand-alone feature should work for all snap-plugin-libs.

@kjlyon
Copy link
Contributor

kjlyon commented Aug 4, 2017

I agree that information on how to use stand-alone plugins should go in Snap. Should we include information about how to write a stand-alone plugin in Snap or in the plugin-libs?

@katarzyna-z
Copy link
Contributor Author

I think that information about how to write a stand-alone could be in plugin libs because there are small differences in implementation related to the programming languages

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants