[Free-RTC] standards / principles for secure, free RTC software?

[Daniel Pocock]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



I've had a look at the FSF info about the campaign for a Skype replacement

http://www.fsf.org/campaigns/priority-projects/priority-projects/highpriorityprojects#Replaceskype

While it specifies that existing solutions have shortcomings, it
doesn't specify what the final solution should look like.  In other
words, a developer aiming to build such a solution won't know when
they cross the finish line.

Has anybody done any policy work, possibly similar to the Debian Free
Software Guidelines, to define the essential attributes of a solution?

Looking at it from another angle, Debian also provides a set of tests
to determine if a license is really free:

http://people.debian.org/~bap/dfsg-faq.html#testing

and it may be useful to define a similar set of tests for evaluating a
communications application.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJRpkO7AAoJEOm1uwJp1aqDCRQQAMbztWtR/FBIYGR5qJ6L/U6Z
MmF5W5S5uNjQ2ZTjd1uCil+CSH5PTQGXaMCyTgUFunGLNf7FwDw7PVrUWfx3/gYh
On2pMjeH3ZGxDUcMcQzeZMImJJyKIQAAP0Hd4D7g5z5K0G4erRY7UUq3Ze+7MByc
LyJlvaT8fr20CYUhwDmDg1LA6dR66NZzf+rg6K/kMz29ZXPi/4d+UJVpN4piErrs
+FvL/y90qzVnqLbftmvePx70ZmifBH865jTP4Eb2KRTOGCAj75cP5JpYwuLR7u6p
jKu22zECQlqC66NVp6VGETrILE0TPfr/vn5l+2/+DPb3q3+MZyyrfBGAd0hr+e6b
aU4TPrUyUL6MUYD/QPsv9Uy3NYKrH4ZQtqZBzF3HIrIKJgxYtlp9F6WKxcD+k+7r
alepkyKBXURfiDCWeSGmHjAnVNn6iByr6A0JP/MfY6DH5JpoNo0gZYtVL8TqaZc3
lHaddWkGb9o1isiV7fvPKKuejjK8r4+ssV8JM94Vo/IoXU9P71OgCxRVr0kGhdVT
rUbXDey/JmYOgcEhR9dGF5nm758xw/RKQrz0j/i0Uupn+/erkY4s4yUDzZrAZiBx
c/3KDgBc+8WTu+XRb+Lry58pI+73PzdZOVvUdMFEXfGhcBebAGAfvqEIdZKAsRaK
xhxG3PZvpLdoUTUXbC0B
=6++g
-----END PGP SIGNATURE-----