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