Ask Bjørn Hansen wrote:
It'd be nice if it could be structured in a way so it's easy to enable the plugins in contribs/ and also support things that are not plugins.
The plugin loader code assumes everything lives in plugins/, so unless you are suggesting that contribs/ lives under plugins/, we'd need to change that. I don't view it as a terrible hardship for the site admin to move anything out of contrib/ into plugins/ in order to use is (since that is exactly what happens today).
For the record, my proposal was a contribs/ folder at the top level of the qpsmtpd directory, with individual folders for each contributed item. This might seem overkill for a single plugin submission, but we could easily switch that to a separate folder for each author (which would also make the auth much easier to manage on your end). Additionally, if you are talking about supporting contributions other than plugins (examples please?), then having multiple folders make so much more sense.
Once you make up your mind on how to structure, I can start loading stuff up.
John
