Talk:Plugin shop

--DenisChenu (talk) 15:51, 16 March 2018 (CET) About plugin update : need to have a compatibility system , then , before i think we must have a compatibility system for plugin itself (inside LS).

• compatible => [3.5,3.*] : compatible since 3.5.1, and current 3.X release surely next (but can not be sure)
• compatible => [3.0,3.99]  : compatible for 3.0 branh
• compatible => [3.0,4.99]  : compatible for 3 and 4 branch
• compatible => [3.0,4.*]  : compatible for 3 and current 4 version

And maybe more :

• tested => [3.5.2,3.6.1] (with a [3.5,3.*])

Another idea is 'state'=> '(stable|test|dev)'

And the 'update url'

Can't we assume that if the plugin is compatible with 3.5, the it will also be compatible with 3.6, 3.7, etc, for all coming 3.x versions? Olle (talk) 16:11, 16 March 2018 (CET)

We can assume, but you know it can be false … A lot of plugin use model function or limesurvey global function etc … I just see a plugin call another view (not mine), and this view was updated between 2.6 and 2.7. --DenisChenu (talk) 16:53, 16 March 2018 (CET)

We can include 'state', but it's not relevant for LimeSurvey GmbH and the plugin shop, because if it's on the shop it should always be stable. Olle (talk) 16:18, 16 March 2018 (CET)

You mean shop like 'Pay to have plugin' ? --DenisChenu (talk) 16:53, 16 March 2018 (CET)

Else : maybe included limeservice “shop” include only stable, but have a config.php setting to allow test ?

And repo url updatable only via config url (then i can add my 'testing and debug' repo url on a mssql dev instance for example And Tammo or other team can easily test new beta plugin --DenisChenu (talk) 16:56, 16 March 2018 (CET)

Yes, update URL also in config.json, but it's very important that this system supports a purchased update key, like for ComfortUpdate, so maybe we also need an URL that points to limesurvey.org, which can check the current order status of the user. And of course it's important that the user can't just switch the url to get to the free version. In that case, the repo has to be private (I guess). We want the plugin shop to work on both LS CE and Pro hosted. You can compare how it works for Joomla, that you can buy an extension, get a ZIP file and an update key. Olle (talk) 17:20, 16 March 2018 (CET)

About repo : in config.php : repoUrlUpdatable (boolean) : allow or not to add other repo. In LS ce : this was set to NO and you have only the official fixed repo allowed. Question about update key : you don't offer freely some little plugin ?

If user can't add new repo url on LimeSurvey CE edition : i make my own update plugin and don't work on this project.

Well, of course it should be fully possible for the plugin author to offer his/her plugin for free! But I also have to take into account the opposite position, when it's a commercial product. Olle (talk) 17:35, 16 March 2018 (CET)

For LimeSurvey repo : you can ask a micro-payment for updating, it's not the question :). But for other place : allow to add 'extra repo' url if you disable some plugin. I have a new contact where plugin in 2.X was made by someone with an email adress in .gov.it for example. GPL plugin , but not published. Maybe they need/want .gov.it repo :)

Denis, what would you prefer - upload a zip file with your plugin to limesurvey.org, OR give a link to your git repo (possible including a username/password or ssh key if the repo is private)? Olle (talk) 13:41, 26 April 2018 (CEST)

Git repo url for me. But can prpvide zip files if needed. https://gitlab.com/SondagesPro . Let me check those (maybe) 4.0 ready