Changes between Version 1 and Version 2 of meetings/2011/07/28
- Timestamp:
- Sep 16, 2011, 5:30:27 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
meetings/2011/07/28
v1 v2 13 13 == Action steps == 14 14 15 * Add tech contact as well as billing contact to the new membership form and to the control panel16 * 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.15 * ~~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 17 * Auto subscribe the current billing contact of all members to both lists 18 18 * Send a friendly explanation to each list about the purpose of the list 19 19 * Subscribe all new member tech contacts to both lists 20 20 * 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) 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]. 22 22