WordPress / five-for-the-future

Plugins and themes for the Five for the Future subsite
https://wordpress.org/five-for-the-future/
55 stars 25 forks source link

Regularly email contributors to prompt for updates #27

Closed ryelle closed 2 years ago

ryelle commented 5 years ago

[moving from code comment to github issue]

setup cron to automatically email once per quarter "here's all the info we have: x, y, z" is that still accurate? if not, click here to update it

Two emails, one for pledge owner and one for contributors?


Update: rough implementation idea, based on the accepted proposal

Setup a cron job to:

iandunn commented 5 years ago

I like that idea, yeah.

For contributors, it'd be especially good to include the # of hours and teams that they marked on the profile, since many people haven't filled that out. If they haven't filled either of those out, it'd be good to ask them specifically to do that.

ryelle commented 4 years ago

How frequently should "regularly" be? Every 6 months? more often? It should offset from the date they confirmed the pledge (publish date).

For pledge owners, since we're already sending them an email, can we generate the manage token and give them a direct link to the Manage Pledge form?

For contributors, it should link them to the profiles.wp.org page where they can edit the teams/hours (unless we do end up adding that in #89/#93)

cc-ing @andreamiddleton for copy advice 🙂

iandunn commented 4 years ago

Every 6 months seems reasonable to me.

andreamiddleton commented 4 years ago

I think 6 months is the shortest time we can set this, and not have it marked as spam. @ryelle do you need copy for the whole email? If so, something like this maybe:

Howdy! This is an email reminder to check and update your WordPress Five for the Future pledge. This reminder is sent every 6 months, to help organizations remember to keep their pledge up to date! Here's the link to manage your pledge:

Things to check:

Thanks for participating in the WordPress Five for the Future program! Your support helps the open source WordPress project, and everyone who uses WordPress.

Have a great day!

iandunn commented 4 years ago

Are the hours your employees have pledged still accurate? Are they still contributing to the same teams?

It doesn't seem like there's a convenient way for the pledge admin to check that; they'd have to visit each of their contributor's profiles individually. There's also no way for them to edit it, they'd have to email the contributor and ask them to update it.

I wonder if it'd be better to send the email to individual contributors, rather than the pledge admin?

I can see how that'd be kind of annoying for people, though 🤔

iandunn commented 4 years ago

What do y'all think about volunteer contributors?

They're also entering teams/hours data into their profiles, which will become outdated over time. We're planning to track and report on those hours in #124, so outdated data would significantly decrease the reliability/usefulness of those stats.

What do you think about a progressive approach like this:

That would minimize the intrusive emails, and also catch cases where people stop contributing and never respond.

andreamiddleton commented 4 years ago

I don't think it's an undue burden on an organization to check over the hours/teams for their linked contributors, twice a year. They can manage it however they want to, by emailing everyone on their end and asking for an update, or by checking through one by one and reaching out directly. Also, that seems like the best way to ask organizations to stay current while still keeping a low email volume.

If we're going to email everyone who fills out a pledge on their profile every 6 months, I think we need to tell them about that when they fill the pledge out, or at the very least let them know in the first email that the way to "turn these emails off" is to un-pledge.

iandunn commented 4 years ago

I don't think it's an undue burden on an organization... They can manage it however they want to

👍

I'm still concerned about the stats for volunteer contributors becoming out of date. What do y'all think about doing these for them:

If we're not going to do that, then maybe we shouldn't do #124 in the first place, since the data won't be reliable.

iandunn commented 2 years ago

I've updated the issue description w/ a rough implementation idea, based on the accepted proposal

iandunn commented 2 years ago

Fixed in #206