Changes between Version 5 and Version 6 of meetings/2011/07/28


Ignore:
Timestamp:
Oct 1, 2011, 5:44:51 PM (8 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • meetings/2011/07/28

    v5 v6  
    1414
    1515 * ~~Add tech contact as well as billing contact to the new membership form and to the control panel~~
    16  * ~~Create a second service list (in addition to service-advisories). service-advisories is a frequent announcement list of all changes happening to the technology at MF/PL. The second list (service-alerts? name to be decided) will be an in-frequent list of announcements that are particularly impactful.~~ (see [https://lists.mayfirst.org/mailman/listinfo/service-alerts service-alerts])
    17  * Auto subscribe the current billing contact of all members to both lists
     16 * ~~Create a second service list (in addition to service-advisories). service-advisories is a frequent announcement list of all changes happening to the technology at MF/PL. The second list (service-warnings) will be an in-frequent list of announcements that are particularly impactful.~~ (see [https://lists.mayfirst.org/mailman/listinfo/service-warnings service-warnings] and [wiki:email_announcement_lists wiki page on email lists])
     17 * ~~Auto subscribe the current billing contact of all members to both lists~~ (current contacts all subscribed to service-warnings list, not service-advisories list).
    1818 * Send a friendly explanation to each list about the purpose of the list
    19  * Subscribe all new member tech contacts to both lists
     19 * ~~Subscribe all new member tech contacts to both lists~~ (now all tech contacts are subscribed to both lists, and all contacts are subscribed to the service-warnings lists)
    2020 * Members other than Jamie should write future service advisories and alerts
    21  * Write templates for service advisories to ensure better non-tech readability. The templates should included more structured information (e.g. a header at the top that indicates the time range for any outage). In progress (see [wiki:templates stub]).
     21 * ~~Write templates for service advisories to ensure better non-tech readability. The templates should included more structured information (e.g. a header at the top that indicates the time range for any outage).~~ See [wiki:templates templates page]).
    2222