On 06/13/2017 04:45 PM, Tiago Machado wrote:
Hi all,
we are currently using Cockpit (a lot) and we love it ! But there's one thing
we miss about cockpit: modules from the community.
I think it would be great if we had a standard procedure to publish modules for
cockpit on GitHub.
If everybody use, for example, a predefined name, like
cockpit-module-contrib-MODULE_NAME it would be easier to create a repository of
cockpit modules and then we could even add an interface for managing the
installed modules, where you can download/remove modules.
I'm thinking about something similar to what we have on Node-RED (
https://github.com/node-red/node-red). There we have a standard name for
external modules (node-red-contrib-NODE_NAME) and they could create a repo of
node (https://flows.nodered.org/ ) where we already have more than 1500 modules
(and counting). There's even an UI inside Node-RED where it's possible to
manage and download new modules.
I agree that we need some way to make community modules easier to
discover and use. I'm ok with setting a naming convention, though I
think initially it might be good to start small. Maybe just a wiki page
on our repo that people can add their modules to.
Another issue to consider is that a big part of what makes cockpit
workable is the CI. So I think that part of having a good library of
modules to chose from is going to be figuring out how to allow out of
tree modules to best leverage what cockpit has for testing. If you have
a module you'd be interested in working with us on to see how doable
this is let us know.
_______________________________________________
cockpit-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
