Latest ABTester source to commit

[erland]

I posted this earlier in another place, but no one seems to have picked it up.

I've no problem to maintain the AB Tester plugin in my Google Code project if that would be preferred, but as I understood it was supposed to go into contrib/plugins in the SlimDevices svn repository. My own preference would be to handle it in the SlimDevices repository since this isn't my focus area at the moment and if it is in the SlimDevices repository it would allow more developers to help adjusting it to any API changes and add new functionality.

Someone also needs to build the plugin zip and par file and make it available for download for end users, is this something someone at Logitech will handle ?

So if you still want to handle this in the SlimDevices svn repository, I would appreciate if someone with svn access could commit this in the "contrib/plugins" directory.

The code is from revision 22351 which was the last before ABTester was removed, but I've made the following additions/changes:
- The code has been changed so it should now be installed in "Plugins" directory instead of "Slim/Plugin" as the built-in version was.
- Added some error handling if a downloaded testcase zips doesn't contain the correct structure (which is the case for the only available "From internet" test case at the moment).
- Generated a new id in install.xml to avoid collisions with the old built-in plugin.

[kdf]

I'm willing to add, but without a plan, I'm waiting.

Community development waits...... as always.

oh, yes, this is a statement.
-k

[dean]

Hm, that's weird, I thought it was committed in:

contrib/plugins/

But it's not. Caleb?

I see no reason it shouldn't go there...

[kdf]

great, but Dean....what happens when it is there?

as a long time third-party contributor, this question is a growing
issue.

Myself, I refrain from any effort due to crap input/random input.

-kdf

On 30-Aug-08, at 8:09 PM, dean blackketter wrote:

> Hm, that's weird, I thought it was committed in:
>
> contrib/plugins/
>
> But it's not. Caleb?
>
> I see no reason it shouldn't go there...
>
>
>
>
>

[dean]

On Aug 30, 2008, at 8:54 PM, kdf wrote:

> great, but Dean....what happens when it is there?
Sorry for not being clear. This is where it can be maintained by
folks who contribute to the code. Write access to the repository can
be granted when appropriate.

> as a long time third-party contributor, this question is a growing
> issue.
I'm not sure what question is.

The contrib section of the repository is for code that may not be
included by default in the SqueezeCenter releases, but can be
maintained in the source code repository.

[kdf]

On 30-Aug-08, at 8:09 PM, dean blackketter wrote:
>
> I see no reason it shouldn't go there...

ok it's now there.

You are welcome, erland.

Matt, et al, do what you will.
-kdf

[dean]

Great, thanks KDF!

On Aug 30, 2008, at 10:53 PM, kdf wrote:

>
> On 30-Aug-08, at 8:09 PM, dean blackketter wrote:
>>
>> I see no reason it shouldn't go there...
>
> ok it's now there.
>
> You are welcome, erland.
>
> Matt, et al, do what you will.
> -kdf
>

[Mark Miksis]

I'm not a plugin developer, but...

This discussion makes me wonder whether there's a demand for a Logitech-hosted infrastructure for 3rd party plugin developers that would support svn, auto par/zip builds, download hosting, bug tracking, etc. IMO, this would increase interest from 3rd party developers and promote more information/patch sharing between them. It would also make it easier for users to find plugins by providing a unified download location, perhaps using the forthcoming SqueezeWiki platform.

If I were a plugin developer without svn access, I would see little value in posting my plugin here in the hope that some nice person will check it into contrib/ (where I can't maintain it and most users will never find it).

[pippin]

First things first: as long as there's not even a plugin installer there's no need for a special infrastructure