I'll add it to the bug report in Phabricator.

Question: It's important that customers easily can reach the extension developers for questions and feedback. Should the author email in config.xml work as a default communication point?

Or, rather the authorUrl web page.

If we state that we are service oriented, why not adding it to the XML file without the information being mandatory?
A link to a support website (which could e.g. hold an FAQ page for a certain plugin/heme) would be useful as well but should not be mandatory.

Mazi wrote: A link to a support website (which could e.g. hold an FAQ page for a certain plugin/heme) would be useful as well but should not be mandatory.

homeUrl + supportUrl + contactUrl

ollehar wrote: Or, rather the authorUrl web page.

I already say : authorUrl != service/tool URL.

Sample of the reason : i hire a dev bill@homeofbill.example.org

authorUrl = homeofbill.example.org
supportUrl = gitlab issue (for example)
homeUrl = extensions.sondages.pro/homeOfBillPlugin
contactUrl = extensions.sondages.pro/about/contact.html

And about support : i'm for a separation between free/community support and professionnal support (but understand LimeSurvey GMBH is OK with only one URL)

Mazi wrote: If we state that we are service oriented, why not adding it to the XML file without the information being mandatory?
A link to a support website (which could e.g. hold an FAQ page for a certain plugin/heme) would be useful as well but should not be mandatory.

If you sell an extension, I think support details should be absolutely mandatory.

Something else that can be interesting: Share extension details page on social media (Facebook, Twitter, ...)? (Only if it's possible without sharing visitor data automatically with those platforms.)

ollehar wrote: Something else that can be interesting: Share extension details page on social media (Facebook, Twitter, ...)? (Only if it's possible without sharing visitor data automatically with those platforms.)

I don't thing that's needed. It doesn't add much value and if you can link to a homepage that should be sufficient.

You might invest a few minutes and check established description standards for software.
Use them as a check list for what might be useful for the LimeStore.
E.g. pad.asp-software.org/spec/spec.php

jelo wrote: You might invest a few minutes and check established description standards for software.
Use them as a check list for what might be useful for the LimeStore.
E.g. pad.asp-software.org/spec/spec.php

I don'tb understand your link ? You ean definition of the xml ?

Else i already give link to drupal : www.drupal.org/project/project_module

But my prefered system is contrib.spip.net/

See screenshot :


Samples of paquet.xml zone.spip.net/trac/spip-zone/browser/spi...aquet.xml?rev=113432
detail on paquet in french : plugins.spip.net/redaction-du-paquet-xml.html?lang=en

LimeStore beta will be delayed, probably two weeks or so. We had a meeting with suggested improvements that I will implement first, and also some internal maintenance that has priority. Thank you for your patience.

Hi @ollehar,

I see you add supportUrl (as mandatory), what other meta you add in config.xml ?

And about zip file : currently : to do the zip file, i add the directory : because it's more easy for user's to understand to move whole directory than to create a directory with same name and miove file inside.

Maybe LimeStore (and lime plugin manager) can accept :
- zipfile without directory
- zipfile with one directory

I think we can allow only zipfilename === directory.

I report the same feature for theme in some minutes.

PS : the best is to have a API to send new zip when updating/fixing a theme/template