A perfect solution is to put the project up on Github or SourceForge so other devs can take up the project. But than again, this is also something only Julian can do.<br><br><div class="gmail_quote">On 1 February 2012 14:54, Jeremy McSpadden <span dir="ltr"><<a href="mailto:jeremy@fluxlabs.net">jeremy@fluxlabs.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Not necessarily. If the project is feature complete, yet takes manual work-arounds to work properly on every distro, doesn't mean it's solid. Given that MS is dependent on Perl, and the newer versions of perl break MS; a patch is in order.<br>
<br>
The room for concern is no one other than Julian has access to patch. There aren't other devs on this project. Sure someone could submit the patch, but looking at the lack of responses from Julian, it could take months to have the patches applied.<br>
<font color="#888888"><br>
<br>
--<br>
Jeremy McSpadden<br>
</font><div class="im"><br>
On Feb 1, 2012, at 7:24 AM, "Mikael Syska" <<a href="mailto:mikael@syska.dk">mikael@syska.dk</a>> wrote:<br>
<br>
> If its feature complete ... is it then a dying projekt? Then alot of<br>
> projekts are dying. We only need to see new usages of MS since its so<br>
> plugable and open source.<br>
<br>
--<br>
</div><div><div></div><div class="h5">MailScanner mailing list<br>
<a href="mailto:mailscanner@lists.mailscanner.info">mailscanner@lists.mailscanner.info</a><br>
<a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" target="_blank">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br>
<br>
Before posting, read <a href="http://wiki.mailscanner.info/posting" target="_blank">http://wiki.mailscanner.info/posting</a><br>
<br>
Support MailScanner development - buy the book off the website!<br>
</div></div></blockquote></div><br>