mherger wrote:
> So... what I suggest:
>
> - we create a repository file in the LMS-Community github org.
> Contributors who've somewhat tested a plugin can add what they know to
> be working to that file.
>
> - this repository file would have a community (not author) provided
> maxVersion. Again this is to have a minimum guaranteed compatibility.
>
> - LMS would have a flag to include that repository or not which would
> also be used to ignore the install.xml's maxVersion.
>
> This would give us a minimum quality check before the uninformed user
> can install a breaking/broken plugin easily. And it should make sure a
> plugin does not break LMS accidentally.
>
> At the same time this should keep LMS side changes minimal.
>
> Thoughts?
>
Sounds good to me.
Plugins that come from this repository should probably be marked somehow
in the list of available plugins that can be installed to make it clear
to the users that they install and rely on unsupported stuff that might
stop working in future LMS releases. Basically we should make it
possible to see if a plugin is maintained/supported or only have been
tested and currently seems to work.
Erland Isaksson ('My homepage' (http://erland.isaksson.info))
Developer of 'many plugins/applets'
(https://wiki.slimdevices.com/index.php/User_Erland.html)
------------------------------------------------------------------------
erland's Profile: http://forums.slimdevices.com/member.php?userid=3124
View this thread: http://forums.slimdevices.com/showthread.php?t=113403
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
