Policy-Discussion

[Drew Lehman - DigitaTech <dlehman AT digitatech.com>]

I was looking at the policy for becoming a member.  While I now know why
you require 4 eyes on each application, the process may drive away some
potential contributers.  CAcert has, essentially, an OpenSource
environment.  To grow the project, it requires a grassroots movement. 
This means giving people a reason to be a part of the project.  Most
people do not want to spend much effort, but may spread things by
word-of-mouth.  The idea of offering people "membership" makes them feel
like they are involved.  However, the sad truth is that most do not want
to do what it takes to be a member under the current definition.  And
honesty, you don't want these people in the current membership status.
I am suggesting a membership class called "associate membership" which
does not have voting rights, nor requires a fee.  This would allow for
people to feel they are tied to the project. A compromise between
members and associate members may even be to allow the associate members
to vote as a group and be counted as a small portion of the membership vote.
Just my 2 cents.

Drew Lehman
DigitaTech/ PANTUG