<strong>Press Releases and Announcements</strong><br/>
<olstyle="list-style-type: lower-alpha;">
<li>CAcert Community Members MAY communicate on their areas, but these are considered community views.
<li>CAcert Community Members may communicate on their areas, but these are considered community views.
</li>
<li>Targeted announcements MAY be sent to a minority subset of users who have opted-in to receiving information on the topic.
<li>Targeted announcements may be sent to a minority subset of users who have opted-in to receiving information on the topic.
</li>
<li>Press releases and official announcements MUST be approved by the board and issued via:<br/>
<li>Press releases and official announcements must be approved by the board and issued via:<br/>
<olstyle="list-style-type: lower-roman;">
<li>Digitally signed email to appropriate mailing list(s).
</li>
@ -72,54 +72,54 @@
<li>
<strong>Email Aliases</strong> are official email addresses within the CAcert domain(s) (eg john@cacert.org).<br/>
<olstyle="list-style-type: lower-roman;">
<li>All official CAcert communications MUST be conducted using an official address, which is typically a forwarding service.
<li>All official CAcert communications must be conducted using an official address, which is typically a forwarding service.
</li>
<li>Access to full accounts (available only to officials listed on the organisation chart) SHALL be available via web interface and standard mail protocols.
<li>Access to full accounts (available only to officials listed on the organisation chart) shall be available via web interface and standard mail protocols.
</li>
<li>Outbound mail SHOULD contain the full name and short reference to the official capacity of the user: <i>John Citizen (CAcert AO) <john@cacert.org></i>.
<li>Outbound mail should contain the full name and short reference to the official capacity of the user: <i>John Citizen (CAcert AO) <john@cacert.org></i>.
</li>
<li>Role accounts (eg support@cacert.org) SHALL be implemented as a mailing list or automated issue tracking system as appropriate.
<li>Role accounts (eg support@cacert.org) shall be implemented as a mailing list or automated issue tracking system as appropriate.
</li>
</ol>
</li>
<li>
<strong>Mailing Lists</strong> are automated distribution lists containing CAcert community members.<br/>
<olstyle="list-style-type: lower-roman;">
<li>List management (new list creation, dead list removal) SHALL be managed by the board.
<li>List management (new list creation, dead list removal) shall be managed by the board.
</li>
<li>List membership SHALL be restricted to CAcert Community members and all posts are contributions, as described in the CCA.
<li>List membership shall be restricted to CAcert Community members and all posts are contributions, as described in the CCA.
</li>
<li>Lists SHALL follow the naming convention of cacert-<listname>@lists.cacert.org, with important lists (eg support, board) aliased @cacert.org
<li>Lists shall follow the naming convention of cacert-<listname>@lists.cacert.org, with important lists (eg support, board) aliased @cacert.org
</li>
<li>List policy SHALL be set on a per-list basis (eg open/closed, searchable archives, etc.)<br/>
<li>List policy shall be set on a per-list basis (eg open/closed, searchable archives, etc.)<br/>
<ol>
<li>Open lists (eg cacert-policy) shall be accessible by anyone (including Internet search engines) and closed lists (eg cacert-board) only by list members.
</li>
<li>Posting to discussion lists (eg cacert-policy) MUST be restricted to list members and MUST NOT be restricted for role lists (eg cacert-board).
<li>Posting to discussion lists (eg cacert-policy) must be restricted to list members and must not be restricted for role lists (eg cacert-board).
</li>
<li>Messages which do not meet list policy (eg size, non-member) MUST be immediately rejected.
<li>Messages which do not meet list policy (eg size, non-member) must be immediately rejected.
</li>
</ol>
</li>
<li>Subscription requests MUST be confirmed by the requestor and subscriber lists MUST NOT be revealed..
<li>Subscription requests must be confirmed by the requestor and subscriber lists must not be revealed..
</li>
<li>Web based archives SHALL be maintained and authentication MUST reflect list policy.
<li>Web based archives shall be maintained and authentication must reflect list policy.
</li>
</ol>
</li>
<li>
<strong>Automated Email</strong> is sent by various CAcert systems automatically<br/>
<olstyle="list-style-type: lower-roman;">
<li>All new automated emails MUST be approved by the board.
<li>All new automated emails must be approved by the board.
</li>
<li>Automated emails SHOULD only be sent in response to a user action.
<li>Automated emails should only be sent in response to a user action.
</li>
</ol>
</li>
<li>
<strong>Personal Email</strong> is individual personal addresses of CAcert Community members (eg john@gmail.com).<br/>
<olstyle="list-style-type: lower-roman;">
<li>Personal email MUST NOT be used for official CAcert purposes.
<li>Personal email must not be used for official CAcert purposes.
</li>
</ol>
</li>
@ -128,7 +128,7 @@
<li>
<strong>Internet Relay Chat (IRC)</strong><br/>
<olstyle="list-style-type: lower-alpha;">
<li>An IRC service SHALL be maintained at irc.cacert.org which SHALL be available via SSL.
<li>An IRC service shall be maintained at irc.cacert.org which shall be available via SSL.
</li>
</ol>
</li>
@ -143,31 +143,31 @@
<li>
<strong>General</strong><br/>
<olstyle="list-style-type: lower-alpha;">
<li>CAcert System Administrators SHALL have discretion as to the technical implementation of this policy and SHALL report status to the board periodically.
<li>CAcert System Administrators shall have discretion as to the technical implementation of this policy and shall report status to the board periodically.
</li>
</ol>
</li>
<li>
<strong>Security</strong><br/>
<olstyle="list-style-type: lower-alpha;">
<li>Authentication (where required) MUST be done via username and password and/or CAcert certificate.
<li>Authentication (where required) must be done via username and password and/or CAcert certificate.
</li>
<li>Transport encryption MUST be used where possible.
<li>Transport encryption must be used where possible.
</li>
<li>Content encryption MAY be used where appropriate.
<li>Content encryption may be used where appropriate.
</li>
<li>All outbound mail SHOULD be digitally signed.
<li>All outbound mail should be digitally signed.
</li>
</ol>
</li>
<li>
<strong>Internet Email</strong><br/>
<olstyle="list-style-type: lower-alpha;">
<li>All mails MUST be securely archived.
<li>All mails must be securely archived.
</li>
<li>All mails MUST be subject to appropriate spam prevention mechanisms (eg SpamAssassin, greylisting).
<li>All mails must be subject to appropriate spam prevention mechanisms (eg SpamAssassin, greylisting).
</li>
<li>All mails MUST be subject to appropriate virus and content filtering (eg ClamAV, content types).
<li>All mails must be subject to appropriate virus and content filtering (eg ClamAV, content types).
Sam Johnston
16 years ago