Mailman retirement to Google Groups - Revision history

Mtesauro: Redirect page to new URL per Mike

2019-02-26T21:49:46Z

Redirect page to new URL per Mike

Mtesauro: Protected "Mailman retirement to Google Groups": Relocated to another URL ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2019-02-26T21:48:10Z

Protected "Mailman retirement to Google Groups": Relocated to another URL ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Mtesauro: Added page to staff projects category

2019-02-26T21:36:19Z

Added page to staff projects category

Mtesauro: Added more stats/metrics

2019-02-26T20:34:12Z

Added more stats/metrics

Mtesauro: Added some numbers to the overview section

2019-02-26T20:30:47Z

Added some numbers to the overview section

Mtesauro: Added some status updates to milestones

2019-02-26T18:01:18Z

Added some status updates to milestones

Mtesauro: Added one milestone

2019-02-26T17:57:42Z

Added one milestone

Mtesauro: Completed the project plan for the migration from Mailman to Google Groups

2019-02-26T17:56:40Z

Completed the project plan for the migration from Mailman to Google Groups

Mtesauro: Save progress and keep editing

2019-02-26T17:04:18Z

Save progress and keep editing

Mtesauro: Saved after adding a bunch of content for CYA purposes

2019-02-26T16:16:23Z

Saved after adding a bunch of content for CYA purposes

← Older revision		Revision as of 21:49, 26 February 2019
Line 1:		Line 1:
		+	#REDIRECT [[Staff-Projects/Mailman-EOL]]
		+
	= Overview =		= Overview =

← Older revision		Revision as of 21:36, 26 February 2019
Line 100:		Line 100:
	** Harold Blankenship - staff representation for project mail lists		** Harold Blankenship - staff representation for project mail lists
	** Dawn Aitken - staff representation for chapter mail lists		** Dawn Aitken - staff representation for chapter mail lists
		+	[[Category:Staff Projects]]

@@ Line 63: / Line 63: @@
 = Milestones =
-* Review the inventory of lists to determine which are inactive - '''DONE'''
+* Review the inventory of lists to determine which are inactive - '''DONE ('''total lists = 875)
-* Use the data above to retire any inactive list - '''DONE'''
+* Use the data above to retire any inactive list - '''DONE''' (total lists = 181, 693 inactive lists removed)
 * Complete Staff Project Plan - '''DONE'''
 * Review remaining list for any that can be retired due to ownership (e.g. owned by staff and unused) or  mail in the last calendar year is SPAM - '''In Process'''

@@ Line 10: / Line 10: @@
 * The Anti-SPAM gateway service from Barracuda, which was previously donated, is ending on March 24th, 2019.
 * Due to the current climate of increased privacy and the existence of the GDPR, the migration will allow the membership in our lists to be reviewed/audited by the current user base (aka opt-in).
 In 2017, the current community manager (Tiffany Long) suggested a migration from Mailman to Discourse.  This was the original direction of efforts until it was reconsidered at the 2019 Staff Summit, a face to face meeting to plan out 2019. Instead, Mailman will be migrated to Google Groups.  The following reasons were crucial in the choice of Google Groups
 * Functionally equivalent to Mailman as a 'mail list'

@@ Line 62: / Line 62: @@
 * Use the data above to retire any inactive list - '''DONE'''
 * Complete Staff Project Plan - '''DONE'''
-* Review remaining list for any that can be retired due to ownership (e.g. owned by staff and unused) or  mail in the last calendar year is SPAM
+* Review remaining list for any that can be retired due to ownership (e.g. owned by staff and unused) or  mail in the last calendar year is SPAM - '''In Process'''
 * Review remaining lists and remove any projects or chapters which are inactive.  A new Google Group can be created for chapters that become active again
 * Send out initial communication to all lists which will be migrated,

← Older revision	Revision as of 21:48, 26 February 2019
(No difference)

@@ Line 25: / Line 25: @@
 * [https://docs.google.com/spreadsheets/d/1_Fn1t_-tcw3duCC0QMhKXEMqdKcHvqsi21e7LuiOphM/edit?usp=sharing Google Sheet of mail lists, most recent post and owner(s) of the list] (only available to Foundation Staff since it contains email addresses of list owners)
 * [https://support.google.com/groups/?hl=en#topic=9216 Google Groups Help pages]
 = Goals =
-Overall Goal: Migration of any active list from lists.owasp.org to Google Groups.
+Overall Goal: Migration of any active list from lists.owasp.org to Google Groups by March 24, 2019.
 Details:
 * Active is defined as a list which as received at least 1 non-SPAM email in the last 12 months as of 2019-01-29 when initial activity reporting was run
-* Mail lists for inactive projects and chapters will not be migrated
+** Mail lists for inactive projects and chapters will not be migrated
-* Archives on lists.owasp.org will be migrated to a static host
+** Archives on lists.owasp.org will be migrated to a static host under the same URL scheme as before
 = Milestones =
-* Review the inventory of lists to determine which are inactive - DONE
+* Review the inventory of lists to determine which are inactive - '''DONE'''
-* Use the data above to retire any inactive list - DONE
+* Use the data above to retire any inactive list - '''DONE'''
 * Review remaining list for any that can be retired due to ownership (e.g. owned by staff and unused) or  mail in the last calendar year is SPAM
 * Review remaining lists and remove any projects or chapters which are inactive.  A new Google Group can be created for chapters that become active again
 * Send out initial communication to all lists which will be migrated,
 = Communications =
@@ Line 61: / Line 89: @@
 * Board Meetings
 ** [[October 11, 2016|October 2016]] - Migration from Mailman raised by Tiffany in her [https://docs.google.com/document/d/1-4fIJfiLa8l02Hf1XBMqRYEiY2z6g4qwln-_ZLQ6GIs/edit Community Manager Report]
 = Leadership =
-* unordered list of each leader and a hyperlink to their email address.
+* This is a Foundation staff run initiative including

@@ Line 9: / Line 9: @@
 * Since the Foundation has a very small staff, administering a server takes away staff time from focusing on OWASP's mission / [https://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project#Core_Purpose core purpose].
 * The Anti-SPAM gateway service from Barracuda, which was previously donated, is ending on March 24th, 2019.
-* Due to the current climate of increased privacy and the existence of the GDPR, the migration will allow the membership in our lists to be reviewed/audited by the current user base.
+* Due to the current climate of increased privacy and the existence of the GDPR, the migration will allow the membership in our lists to be reviewed/audited by the current user base (aka opt-in).
 = Project Links =
 * [https://lists.owasp.org/mailman/listinfo Mailman legacy install]
 * [https://lists.owasp.org/pipermail/stats/ Mailman stats] - created via monthly cron job / run manually
 = Goals =
-Include top-level goals of the project in an ordered list
+Overall Goal: Migration of any active list from lists.owasp.org to Google Groups.
-Give thought to the ordering of goals. Revenue, attendance, launch date
-Make sure goals are measurable from undisputed source
+Details:
 = Milestones =
-* In an unordered list (billeted) list major milestones in chronological order
+* Review the inventory of lists to determine which are inactive - DONE
-* Use the syntax of 2019-01-19, Milestone name [Name of Owner]
+* Use the data above to retire any inactive list - DONE
-* When milestones are completed, mark them as such with ??
+* Review remaining list for any that can be retired due to ownership (e.g. owned by staff and unused) or  mail in the last calendar year is SPAM
-* A milestone isn’t everyone’s to-do list, it is the high level tasks of the project
+* Review remaining lists and remove any projects or chapters which are inactive.  A new Google Group can be created for chapters that become active again
-* If you have more than 20 milestones, you’re being too granular
+* Send out initial communication to all lists which will be migrated,
-* Posts to Leaders lists prior to creation of staff projects template
+= Communications =
 ** https://lists.owasp.org/pipermail/owasp-leaders/2019-January/019608.html
 ** https://lists.owasp.org/pipermail/owasp-leaders/2019-January/019613.html
@@ Line 42: / Line 56: @@
 ** https://owasp.blogspot.com/2019/02/owasp-community-and-chapter-reminders.html
 ** [https://mailchi.mp/90cc34fc2cdd/0rleggjjx3-222491 February Connector]

@@ Line 1: / Line 1: @@
 = Overview =
-Each project will have a 2-3 paragraph overview narrative. Keep to the key top points about the project. Visitors should be able to read this short narrative and have a good understanding of the project without having to scroll the entire document.
+Since very early in OWASP's history, Mailman has been used to facilitate communication between various members of the community.  While Mailman has served the community well for years, the decision has been made to migrate from a self-hosted Mailman installation to Google Groups.  The migration will allow the community to continue to have an email address to reach a particular segments of the community just like Mailman provides but without the administrative burden of running a server for Mailman.  The reasons for this migration were stated at length on the leaders list [https://lists.owasp.org/pipermail/owasp-leaders/2019-February/019675.html here] but are summarized below in no particular order:
 = Project Links =
+* [https://lists.owasp.org/mailman/listinfo Mailman legacy install]
-Use this section for important links for projects/events that visitors will need.
+* [https://lists.owasp.org/pipermail/stats/ Mailman stats] - created via monthly cron job / run manually
 = Goals =
@@ Line 26: / Line 32: @@
 * Posts to Leaders lists prior to creation of staff projects template