In doing this I realised there are a fair few plugins in our plugins directory that are not really ready for release and would, perhaps, be better housed in the whiteboard area.
I propose that we only have plugins that are officially released in the plugins directory and all in-development plugins are housed in whiteboard/plugins. My reasoning is twofold:
Firstly, in the near future I hope to make Forrest run with the plugins on the local disk, i.e. not requiring download if you have the source and not requiring a local-deploy if you are developing. Keeping all the released plugins in a single location will make it easy for us to release a bundle of released plugins and another bundle of unreleased plugins as a separate download from forrest core.
Secondly, it gives a clear indication of what is considered complete functionality by the Forrest Team. That is I would suggest that the plugins in the released section (i.e not in the whiteboard) will attempt to maintain backward compatability, whilst those in the whiteboard are experimental and therefore may change without any attempt at backward compatability.
Note that we can still have a separate plugins.xml for the whiteboard plugins so that users can see what other plugins are available.
So, unless there is a -1 before by the end of the weekend I will move the following plugins to whiteboard/plugins next week.
o.a.f.p.input.Daisy (actually this one is still on my hard drive) o.a.f.p.output.htmlArea o.a.f.p.input.logs o.a.f.p.internal.views o.a.f.p.output.ViewHelper
Ross
