Hi Emmanuel,

I never stated that I'll refuse to update SweetHome3DUpdates.xml for contributed plug-ins

Oh, apologies, no offense, it seems that I've got the meaning of this statement wrong:

I'll accept to edit that file only for very important udpates.

I have to admit that the intention of your first post was not really clear to me and I might have interpreted it in a wrong direction.

So lets try to make it clear:

1. How should the ID look like - esp. to prevent name clashes (in other words - what's the difference to just use the plugin name or class)?
2. How does the workflow of a new update look like esp. on which channel does a plugin developer provide a new update-element to you?
3. When will that update get promoted to your XML file?
4. If that is the official way of providing easy updates for a plugin to the end user, could you integrate it into the Plug-in developer's guide?
   [/list=1]
   
   A last word about "spamming" with the updateUrl: As soon as someone has installed a 3rd party plugin, you have already lost control [>:)].
   
   Seriously, if every plugin developer uses his own update stratgegy, because there is no official way for updates, the user might be annoyed even more by the different configuration, messages, intervals...