The new implementation of the like button will be excellent. I imagine users would be flattered when someone else likes their make and it would be a good idea to give them an email notification. Email notifications of activity on the site like this, also remind users to come back. We'll want to give users the option to easily adjust their notification settings on their profile, and have reasonable defaults that are kind to their inboxes. I also think it could be a good idea to be notified when somebody publishes a remix of your make, but it might be too many emails, we would want to test this.
Cade, want to extend the Liking and MakeAPI goodness to this ticket? Will require that we add preferences to this in user settings.
Assignee: nobody → cade
Yeah, I can check this out. I'm going to need to figure out how to make this NOT spammy if it's turned on. (i.e. one email per milestone)
I really wonder if we should move this out of the icebox. It's the kind of "ladder of engagement" stuff we know we need. CC'ing Amira + Matt for thoughts.
Status: ASSIGNED → NEW
* Relates to a similar request Surman just made. We need to work out our comms and email strategy more explicitly * Added it to the Webmaker Roadmap https://wiki.mozilla.org/Webmaker/Roadmap * Will work on how we need to scope this before and at work week * The work: need to think about and document how emails should get triggered by Webmaker.org behaviors. And how it maps with Engagement Ladder. https://wiki.mozilla.org/Webmaker/Get_Involved * Don't want to gate small agile steps like this on a big abstract chunk of work first. BUT: we do need to take a holistic view so that the emails and communications and meaningful. Rather than spamming users with disconnected mails.
Summary: email notifications when another user likes or remixes your make → Send email notifications when another user "likes" or remixes your make
Sorry "and" should be "are" above
Matt, if it makes sense to close this bug and file new ones after you all figure out a strategy, feel free. I just thought this sounded a lot like things we know we need to do.
This could be something that is fed by MakerMind, and it would be a useful test of what we're doing there.
Assignee: nobody → cade
Status: NEW → ASSIGNED
Once we're ready to hack on this, we can re-file in Github
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.