Hi!
About shoutcast and UTF-8: I sadly can't tell; I believe it just outputs the content from the shoutcast server; I don'T know if they serve ISO or UTF...
Obviously people would need FTP access to upload new plugins before they can be submitted to SPARTACUS.
Why do they need that? Spartacus plugins are committed to CVS; people I know are 'worthy' get CVS access, all other plugins are first shown to me and then I commit those. Spartacus plugin can only be maintained via CVS, not via FTP.
Instead of a Wiki maybe some bug reporting software would be in order? that way developers would get automatic e-mails and such?
Sure, you could also use the
http://www.sf.net/projects/php-blog bug tracker.
Thanks a lot for offering your help! The project can definitely need that help!
Also (and once again: this is not a personal attack) I think the fact that mgroeninger admits that he has less experience with the front-end side (i.e. the HTML/XHTML output) actually proves my point that there should be some kind of check/approvement for plugins
If we have people that volunteer to check it, I am sure no developer would refuse it. Even I am making bugs and troubles. Having other people check it is always a plus.
But we can only establish such an "approvement" mechanism, if people can constantly dedicate their time to this.
I think I would like to have my S9y test server behind a user-name password (after that full access)...
I must admit I don'T really see the need for a test server? Every person that would like to check plugins could also try them on his own blog? If you give write privilege to a central test installation, you would have to moderate it, and reset it from time to time. Also people would need admin privileges and thus could intrude your server.
Developers need to have their own blog for developing a plugin, so for those people it would also not be really needed?
On the other hand, having a test-server would not hurt either.
Best regards,
Garvin