Hi Matej, mato konecny a écrit : > Hi everyone, > > I think this question has been solved at this mailing list, but I am > unable to find the answer in the archive, so I'm just posting it again: > What are the steps needed to package and publish a plugin so other users > are able to see/test it? Maybe this a good thing to post to Wiki (or I > am completely blind and it's already there, who knows...:)
We now have a tutorial for plugin developers on our wiki: https://elisa.fluendo.com/wiki/Docs/PluginTutorial. It is still a beta version and will evolve but forms already a good basis. @Jesús: The section dedicated to publication of the plugin is pretty short, maybe we can improve it. > How is it then with plugin updates? Do they have to be re-released > through someone from the core-team? You can publish updates to your plugins in the form of eggs hosted anywhere whenever you want. However if you want a new plugin or an update to be published in our plugin repository you'll need to ask us to review it first. This, of course, to ensure quality for all users. We are also able to publish some plugins as unstable, either because they are not tested enough or because they are still in development and the features already implemented may interest early adopters. If you think your work may fall in this category just let us know! > Cheers > Matej Cheers, Olivier
