Some brief history, in case there are developers who weren't working on
Spambayes 5 years ago ;-):
I wrote the first crummy integration between Outlook and Spambayes, which
worked really well (thanks to Tim), and was so ugly that Mark was inspired
to replace it with something cool. After letting Mark do the heavy lifting,
I eventually built a commercial product (InBoxer Antispam) which used
Spambayes at the core, 'specially Marks integration code.
Fast forward, oh, several years. InBoxer has customers who insist on using
the product even though we've tried to kill it. Twice. And Outlook 2010
incompatibility is driving them nuts. I can't even tell them to go try
Spambayes, because the same issues exist there.
I have the following propositions, just to see if anyone is excited, err
interested, or even unemployed.
1) We could contract with someone with experience to do the 2010 changes to
the common code base, and then port those
changes in our product. Payment to be negotiated, common code base changes
freely usable in Spambayes. BTW, Mark H. is oversubscribed. Tried that.
2) We can offer a 1K prize to the developer submitting a patch/rev to the
common code base that solves the problem to the satisfaction of the
development lead (?Skip?)
2a) We could offer the the equivalent cash as a donation to the PSF if there
is more interest.
If there is any interest, please contact me directly as well as the list.
-- Sean
Sean True
seant(a)inboxer.com
CTO
Inboxer @ Safecore, Inc
**<https://clients4.google.com/voice/embed/webCallButton?id=0470b068193dc53601…>
Can someone give me a quick summary of how SourceForge website updates have
changed? We currently try rsync'ing files to shell1.sourceforge.net but
that fails now.
It looks like I want something like
rsync files montanaro,spambayes(a)web.sourceforge.net
but that's not clear from the documentation I found so far.
Thx,
Skip
(No, this is not an April Fools' Day prank.)
I think I have most of the stuff done for the 1.1a6 release (md5 checksums,
ascii armor GPG sigs, file sizes, etc). I also reworded the index.html and
download.html pages slightly to nudge people in the direction of using the
1.1a6 release in preference to 1.0.4 or 1.1a4.
I haven't the slightest idea how to verify the integrity of the
distributions using the GPG sigs. Could someone please give that a go? The
sigs are all in
http://spambayes.sourceforge.net/sigs/
(which you currently can't read - I'll work on getting a directory listing
going, hopefully tomorrow). The files are the name of the distribution file
with ".asc" tacked onto the end. For example, for the 1.1a6 version of the
Outlook installer:
http://spambayes.sourceforge.net/sigs/spambayes-1.1a6.exe.asc
I'm sure I've missed some things. If you see something please open a help
ticket here:
https://sourceforge.net/tracker/?group_id=61702&atid=498103
(Project admins should of course feel free to just correct my mistakes
themselves!)
I hereby decree that the next version which goes out will be version 1.1b1.
At the current rate of releases that should occur around June 2013.
--
Skip Montanaro - skip(a)pobox.com - http://www.smontanaro.net/
I created a 1.1a6 source release for SpamBayes to match Mark's Windows
installer. It is available here:
https://sourceforge.net/projects/spambayes/files/
Click the 1.1a6 folder to get at the files.
Mark, can you put your Windows installer there (or point me at it and I'll
stick it in place)?
I moved the 1.1a2 and 1.1a3 folders into the OldFiles folder (not visible
except to the project admins). I left 1.0.4 and 1.1a4 in place, but people
should generally be using the 1.1a6 release unless it's demonstrated to have
significant problems.
Skip
