Metacat 3.0.0 Announcement Email & list cleanup
-
[x] Finalize email body template in Google Docs
-
[x] Finalize the recipients list - in the same gdoc
-
[x] Send the email
See original outreach list (created from list of registered D1 nodes), for orgs using old skins-based deployments. Only 2 orgs needed action from this list:
- [x] Japan LTER - Have included in the recipients list
- [x] Office of Tropical Studies (OTS) - cannot find evidence of a metacat installation.
- Matt suggested looking for old tickets mentioning OST, either in GH issues in the MN tracking board, or older versions of that in redmine.dataone.org
June 7, 2019 - Per Oscar:
I am writing to let you know that, we had a problem with our server. For this reason, OTS has decided to withdraw our member node from the DataONE network indefinitely, because in this moment we have another pressing issues which prevent us from attending to this situation immediately.
This, coupled with not being able to find their server at the registered URL, and seeing a last harvested date in 2018, leads me to believe they no longer use Metacat.
Finalized Lists
from 5/14/24 backend dev meeting (notes made in google doc):
-
- Active. keep
-
- Active. keep
-
[email protected]: Don’t use for announcements - too broad
-
ESS-DIVE
- [x] [email protected] (MB double-checked with Val which is best list for her team, 5/14/24)
-
[email protected]: Don’t send to this - unmaintained. ~~Keep list but make read-only~~ List contains only 3 postings, all metacat announcements form Jing). The real archives (Pre-April 2015) are not in this list - they are located at http://lists.nceas.ucsb.edu/ecoinformatics/pipermail/ecoinfo/.
- [x] Delete list (confirmed by Matt 5/15/24)
- [x] Give Nick the backup of 800+ members to add to archive server
-
[email protected]: old list for d1 devs on payroll. Obsolete list. Don’t send to this
- [x] Delete list
- [x] Give Nick the backup of messages and members, to add to archive server
-
[email protected]: Original OS list.
- [x] add a GH Issue for 3.1.0 release, to update readme & documentation guide to use
[email protected]instead of[email protected]- see #1926 - [x] Send an announcement saying shutting down, and suggest members join
[email protected] - [x] Move people actively running dataONE metacat nodes to the new list
- [x] PISCO
- [x] Ppbio
- [x] Sanparks
- [x] TFRI
- [x] @taojing2002 will identify who else
- https://groups.google.com/my-groups
- Click on the list
- Click members
- [x] Ask Nick to set up an email alias from
[email protected]->[email protected]until #1926 is completed - [x] ~~Keep list but make read-only~~ Delete list, since conversation history was not enabled, so list is empty
- [x] give a list of members to Nick for archiving
- [x] add a GH Issue for 3.1.0 release, to update readme & documentation guide to use
-
[email protected]: old list
- [x] Send metacat release email this last time
- [x] Send an email announcing list closure, then
- [x] ~~Keep list but make read-only~~ delete list, since conversation history was not enabled, so list is empty
- [x] give a list of members to Nick for archiving
-
instead of sending individually, check these recipients are on developers@d1 instead, before we send out the 3.1.0 email:
- [x] Rani Gaddam [email protected]
- [ ] ~~Japan LTER site admin [email protected]~~
- [ ] ~~JaLTER Secretariat [email protected]~~
- Tried multiple times to get in touch with both of the above, to no avail
So final recipients list for this 3.0.0 email is as follows:
- [x] (@taojing2002 did these) [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
slack (@artntek did these)
- [x] Dataone dev-general
- [x] ESIP - council of data facilities (CDF)
Final recipients' list for future announcements is
[email protected], [email protected], [email protected]
slack
- Dataone dev-general
- ESIP - council of data facilities (CDF)
For "read only" groups - Nick said:
we don’t have a set config for read-only, but you can follow our other configs listed at https://github.nceas.ucsb.edu/NCEAS/Computing/blob/master/google_groups.md to get close to read-only. Mainly, change settings for
Posting,Subscribing, and the listArchives
Google Group/List Cleanup Summary
All the archives listed below can be found in zipfiles on the host:
optimal-squirrel.nceas.ucsb.edu`
...in the directory:
/backups/archive/services-archive/google_groups/
# i.e:
outin@optimal-squirrel:/backups/archive/services-archive/google_groups$ ls -lh
total 3.1M
-rw-r--r-- 1 outin outin 3.0M May 15 20:40 [email protected]
-rw-r--r-- 1 outin outin 156K May 15 20:40 [email protected]
-rw-r--r-- 1 outin outin 2.3K May 16 17:10 [email protected]
-rw-r--r-- 1 outin outin 2.2K May 16 17:10 [email protected]
[email protected] list backup
- Google Group Archive name: [email protected]
- Contains:
- messages .mbox file (contains only 3 release announcements by Jing)
- member list (800+ members)
- Pre-April-2015 Archives: http://lists.nceas.ucsb.edu/ecoinformatics/pipermail/ecoinfo/
[email protected] list backup
- Google Group Archive name: [email protected]
- Contains:
- messages .mbox file
- member list (15 members)
- Pre-April-2015 Archives: N/A
[email protected] list backup
- Google Group Archive name: [email protected]
- Contains:
- no messages .mbox file (Conversation history not enabled)
- member list (48 members)
- Pre-April-2015 Archives: http://lists.nceas.ucsb.edu/ecoinformatics/pipermail/morpho-dev/
[email protected] list backup
- Google Group Archive name: [email protected]
- Contains:
- messages .mbox file
- member list (50 members)
- Pre-April-2015 Archives: http://lists.nceas.ucsb.edu/ecoinformatics/pipermail/metacat-dev/