Opened 5 years ago

Closed 4 years ago

#4058 closed enhancement (reported-upstream)

Auto-notifier of new local WordCamp site to old local WordCamp site subscribers

Reported by: camikaos's profile camikaos Owned by:
Milestone: Priority: low
Component: WordCamp Site & Plugins Keywords: needs-patch


create a way to auto-notify subscribers from a past WordCamp site that a new WordCamp is happening and they should subscribe to the new site for news. Example 500 people subscribe to WordCamp NYC 2018. It’s safe to assume that those local folks very well may want to know when another local WordCamp happens but the organizers may not have access to post from the site. So when the 2019 site goes live is there a way for the system to tell the 2018 site to send out an update to subscribers linking them to subscribe to the new site? Thanks to Drew Jaynes for the suggestion

Change History (4)

#1 @garrett-eclipse
5 years ago

  • Type changed from defect to enhancement

In Canada due to the CASL regulations it would have to be the old site that sent the notification prompting them to subscribe to the new site/list. I'm not a lawyer but my understanding is it would be prohibited to just export/import that list to the new site and sent the notification from there. I think it's a great way to gain exposure for the new site, I mainly wanted to flag the liability to make sure the notification is sent by the original site/list and not from the new one.

This ticket was mentioned in Slack in #meta-wordcamp by ryelle. View the logs.

4 years ago

#3 @casiepa
4 years ago

Adding some privacy thoughts here:

  • If you did not CLEARLY ask for permission in the old WordCamp for it, you cannot contact them from the new WordCamp (opt-in)
  • You probably have to indicate in the old WordCamp how long you want to keep the email addresses (until the next WordCamp? If this is not done, not sure you can 're-use' the emails.

But! It's a big yes from me to have a system where people can opt-in to know about future WordCamps!

#4 @dd32
4 years ago

  • Resolution set to reported-upstream
  • Status changed from new to closed

This ticket has been moved to GitHub

Note: See TracTickets for help on using tickets.