On 2/26/2014 6:25 PM, Ivo Truxa wrote:
Hello everybody,
I just subscribed to the dev list, so all of you, please accept my greetings,
and also my thanks for the continuing work on
SpamAssassin! Also please bear with my ignorance. I wrote a new plugin module
for SA, but since I did not know anything about the SA
internals, and am not a Perl coder, it was not easy for me to get grip of it.
Anyway, the plugin starts to look and work as
intended, but before I can publish it, I'd like to know some details that I
didn't manage to find in list archives or on the web
(though I am certain it must have been asked already before, so most likely I
did not search with the right terms).
Thanks. Happy to try and help.
1) Is there a way to parse locally the markdown in the Perl module into HTML,
so that I can verify whether it displays nicely and as
intended?
Do you mean the perldoc aka perl POD documentation?
If so, you could do a pod2html command on the code and redir to an html
file and check in a browser.
2) What is the procedure for proposing the module? Should I simply make a pull
request through the GitHub repository? Or should I
rather first publish it as an independent extension externally? Or is there
another way?
There is no set procedure. I suggest you start by attaching it to an
email to dev for discussion and others to test.
The next step would be a bugzilla issue to track it and see about adding
it to the codebase which may require a licensing agreement (ICLA).
regards,
KAM
