Mailing list migration
Mailing list migration:
For the reasons:
"sourceforge doesn't give us access to the subscriptions"
migration is better done soonish, then later.
Solution 1: Creating new lists and announcing them. Letting the old lists run for 1 year or something and regular invite folks to join the new lists.
Solution 2: There is access to subscribers email pre-2017. They can be migrated to new service and sending them an email asking for confirmation. Sending announcement via sourceforge to all, that there's a new email list. There is no option that pre-2017 subscribers won't receive that same email, even if they're already part of the new list. Potential legal issue: Do you have the consent, that allows you to switch the pre-2017 subscribers to new service?
Solution 3: ?
- discussion in devel list will be split between 2 lists until everyone participating switched to the new one, or if this issue is mitigated by bridging the lists (could be as simple as coping the digest of the daily mails into the other list with a link to read them in the browser)