Something I’ve been wanting to do for a long time here is to write a plugin, we’ll call it ninja for now 'cause this is gonna get confusing, that serves as an extension to the plugin system. What ninja would do is provide an interface for configuring what plugin repositories that the openfire administrator wanted to pull from. I would define some sort of .xml file that the repositories would provide that describes what they have, and all ninja would do is go to the repositories it knows about /whatever.xml and routinely pull an updated list of available plugins. After that it would behave similarly to how the built-in plugin mechanism does. (though it would probably not tie -directly- into it, it would act on it’s own accord, and probably create a new “3rd Party Plugins” tab)
Now… this has been on my list for a while and I want to make it happen sometime soonish. My question for you all is, shall I go forth with my plugin concept or do you feel that I should mess with Openfire itself and allow 3rd party repository support.