Merge branch 'trs/groups-migration-complete'

nextstrain · Jun 22, 2023 · c0e1eb9 · c0e1eb9
2 parents e844e6e + 4d79f7b
commit c0e1eb9
Show file tree

Hide file tree

Showing 3 changed files with 23 additions and 9 deletions.
diff --git a/src/guides/share/groups/index.rst b/src/guides/share/groups/index.rst
@@ -6,7 +6,6 @@ Share via Nextstrain Groups
     :hidden:
 
     Customize your page <customize>
-    Migrate from S3 <migrate-from-s3>
 
 .. hint::
     This how-to guide assumes familiarity with the :doc:`Nextstrain Groups

diff --git a/src/guides/share/groups/migrate-from-s3.rst b/src/guides/share/groups/migrate-from-s3.rst
@@ -1,11 +1,22 @@
+:orphan:
+
+..
+    This page is no longer linked from within our docs, but I'm keeping it
+    around so as not to break direct links we've previously distributed and to
+    provide a record of the migration.
+        -trs, 22 June 2023
+
 ========================================================================
 Migrate data management for a Nextstrain Group from S3 to nextstrain.org
 ========================================================================
 
 .. hint::
-    This guide only applies to :doc:`Nextstrain Groups </learn/groups/index>`
+    This guide only applied to :doc:`Nextstrain Groups </learn/groups/index>`
     created **before March 2022**.
 
+    As of June 2023, all such groups have been migrated.  This guide is
+    preserved only as a record.
+
 What
 ====
 
@@ -175,6 +186,8 @@ Timeline
 
 :end of February 2023: Nextstrain team's desired deadline for migrating all groups.
 
+:June 2023: All affected groups have been migrated.
+
 
 Notification
 ============
@@ -239,3 +252,9 @@ migrated.
     <https://discussions.nextstrain.org>`__.
 
     —the Nextstrain team
+
+On 15 February 2023, a `final reminder email <https://github.com/nextstrain/email/tree/19ad4396b2559b9b2dcf03e3c903b1164a4ad2f5/sent/2023-02-15-groups-migration-reminder-final>`__
+was sent to the contacts of several remaining groups.
+
+On 10 March 2023, the bulk of the several remaining groups were migrated
+without the involvement of their contacts, and they were `notified via email <https://github.com/nextstrain/email/tree/19ad4396b2559b9b2dcf03e3c903b1164a4ad2f5/sent/2023-03-10-groups-migration-performed>`__.
diff --git a/src/learn/groups/index.rst b/src/learn/groups/index.rst
@@ -123,13 +123,9 @@ determines the permissions they have within the group.
         Owners have full control over the group.
 
         This includes the same permissions as :term:`editors` plus the ability
-        to manage the group's description and logo [#owners1]_, invite and
-        remove group members, change the roles of group members, and even
-        delete the group entirely [#owners2]_.
+        to manage the group's description and logo, invite and remove group
+        members, change the roles of group members, and even delete the group
+        entirely [#owners2]_.
 
 
-.. [#owners1] Self-service for groups using their own S3 buckets; currently
-              requires contacting the Nextstrain team for groups which have
-              :doc:`migrated from S3 </guides/share/groups/migrate-from-s3>`.
-
 .. [#owners2] Currently requires contacting the Nextstrain team.