Policy-Discussion

[Daniel Black <daniel AT cacert.org>]

One person asked for the role and the response below was given.
It applies to anyone interested in the position:

----------

The policy officer is responsible for all the trivial editing of current 
policy.
https://wiki.cacert.org/PolicyDecisions#p20100306

Most policies are in SVN. Please check them out and go ahead in doing all the 
trivial edits allows by the policy.
http://svn.cacert.org/CAcert/Policies/

The cacert-policy email list can be used if any edits you consider are 
bordering on oversteping their mandate. 
https://lists.cacert.org/wws/arc/cacert-policy

If you'd like to help please get a large set of svn diffs against the 
policies. This is one way we as a board can evaluate your work before any 
appointment is made. If you can present these in a way to the policy list to 
show them what your are doing without  flooding the list that would be good 
also.

Ultimately this editor position will be in a good position to know policy 
weaknesses, conflicts and other aspects that require resolution. I'd hope 
anyone given this position will use this knowledge to seek assistance from 
appropriate people to get these deficiencies fixed.

The board is still deciding how to appoint a policy officer.

Their general comments from the last board meeting (end of log):
are:
          * we also try to find more people for this role
          * we'll consider appointing more that one person
          * we will give the role to anyone with the right skills 

http://wiki.cacert.org/Brain/CAcertInc/Committee/MeetingAgendasAndMinutes/20100321

Board appointment isn't a requisite to contributions in this field.

----

As community member I'm keen on calling this position a Policy Editor as its 
more inline with the IETF policy process that goes on here (aka RFC editor in 
IETF speak). It also avoids cultural implications that this person is somehow 
the boss and therefore more conducive to a community organisation like ours.


-- 
Daniel Black
Vice President / Infrastructure Team Lead
CAcert

Attachment: smime.p7s
Description: S/MIME cryptographic signature