https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7727
--- Comment #6 from John Mertz <john.me...@mailcleaner.net> --- (In reply to Henrik Krohns from comment #3) > I feel I have to clarify this comment from the SpamAssassin projects > point of view: > > - Plugins should not be committed to SA to just get some plugin "out > there", they should be committed to be developed by SpamAssassin > project and preferably widely used. > - Committed plugins are maintained by the SpamAssassin project. As > such, if the intent is to also use and develop them internally by > some other entity (corporate or not), it might be wiser to just leave > maintaining and publishing to that entity. There are many third party > plugins that are not part of SpamAssassin: > https://wiki.apache.org/spamassassin/CustomPlugins Certainly, if that is the point of view of the project, I'm not here to push back against any of that. I initially introduced the idea to Kevin McGrail because I was interested in using CPAN as a distribution platform. There are several plugins there which appear to be authored and presumably maintained by entities outside of the project itself, so trying to do the same seemed like the most logical coarse of action and that is why I'm here. The module varies from many on the Custom Plugins page in that it is simply used to interface between SA and the OCR engine available within all major distribution repositories. Aside from those dependencies, it is self-contained and does not rely on any technology, data-feed, licensing, or infrastructure provided by myself or the company. Any development that I/we do is expected to only be granted by approval of the project to ensure that it is useful and properly implemented for everyone. -- You are receiving this mail because: You are the assignee for the bug.
