-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We (Uniwares Ltda) are in the process of opensourceing our SPF
implementation, targeted at Windows environments. Although it should be
easily portable (no windows specific api's), we didnt test under any
non-windows OS.
Our implementation is written from scratch in C++, developed and tested
under VS2003/2005 and fully compatible with RFC 4408. Still working on
supporting the test suite. It comes without the event sink, which might be
supplied later on.
Any suggestions which license to use? BSD? GPL? LGPL?
The choice of license is really dependent on your intent. If it is
intended to have a pure OSS presence then I prefer the GPL v 2. It I want
it to be able to be used as a library, I prefer LGPL. It I want it to be
used for other things a BSD might be better. It really is a matter of
what you want. A dual licensing like MySQL I prefer the GPL and make
every one sign over/share copyright with the entity responsible for
controling the dual license.
Only the one in control can really determine what is best for them. You
can look up via google all the arguments pro and con for each license
model.
Good Luck,
- --
Boyd Gerber <gerberb(_at_)zenez(_dot_)com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/
iD8DBQFE7055VtBjDid73eYRAu9sAJ4mViczqqjxOCQvBRJ6vw2SiD5IuACdHdQz
mbztP1vLPF6YS5BaR8ljqZk=
=JS1V
-----END PGP SIGNATURE-----
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com