With two people working on WoT-based plugins apart from Freetalk, and one of them being at a late stage and hopefully integrating Freetalk-related functionality soon, and with Freetalk mostly working, we need to seriously consider how to get wider testing. IMHO it should be on the drop-down list on the plugins page, but marked as ALPHA or BETA or WARNING or something.
p0s has said that he is okay with this once he has implemented some warning code - but that warning code will have to just look for a key and then say "this build is completely broken, please wait for the next Fred build so you can fetch the next version of Freetalk". It can't say get it from X URI, because that would break the rest of the plugin updating system, would need a revocation system and would end up with p0s implementing his own freetalk-specific updating code. We thus need to fix the plugin updating so that plugins can be released, and possibly disabled, mid-build. The main worry is that plugins may be deployed which require new node versions, so we will need to tag plugin jars' manifest.mf's with the version of the node they need, just like we tag freenet jars with the freenet-ext.jar versions they need. After that it should mostly be similar to the current system for updating fred and therefore involve mostly refactoring. I propose to implement this soon. Thoughts? Objections? Details? Some folk have been advocating that we use a lightweight OSGi implementation for plugin dependancies, plugin interfaces etc... IMHO that is a longer term issue?
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list [email protected] http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
