spam-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Spam-discuss] bad news, spamassassin future


From: Mathieu Roy
Subject: [Spam-discuss] bad news, spamassassin future
Date: 11 Jan 2003 18:26:12 +0100
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

Please, take a look at

http://www.mcafeeb2b.com/other/jump/deersoft-faq.asp

"Q. What is Network Associates position on open source technology?

    * Network Associates strongly supports the commercial software
    * model, and prefers to work with proprietary source
    * code. However, where there is clear customer need, we will work
    * with open source solutions if those solutions are the best
    * technology to address the need. 
    * Open source is a term that encompasses a large variety of
    * licensing schemes. 
    * Network Associates recognizes that some open source projects
    * such as Linux are very successful and highly desired by our
    * customers. 
    * We will work with customers in the operating systems that they
    * choose. 

Q. What will be the status of the open source product following the
acquisition?   

The SpamAssassin open source project will continue and will be
maintained by its current authors including Justin Mason and Craig
Hughes. Mason and Hughes will be employees of Network Associates and
will devote their energies to the development of the proprietary
McAfee product."

It's bad news. Even if there's no need to fork, future of spamassassin
as free software, independant from full-proprietary companies, is
pretty unclear.

As far I understood, the policy from proprietary companies buying free
software company is frequently to maintain availability of the free
version in a degraded status, to incitate people to distrust free
software and to buy their proprietary stuff. 

Regards,

-- 
Mathieu Roy
 
 << Profile  << http://savannah.gnu.org/users/yeupou <<
 >> Homepage >> http://yeupou.coleumes.org           >>
 << GPG Key  << http://stock.coleumes.org/gpg        <<




reply via email to

[Prev in Thread] Current Thread [Next in Thread]