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