Topics

Email reminders going out!


David A. Wheeler
 

We now have email reminders set to automatically start going out, beginning Sep 8 23:00 UTC.  They’ll only go to projects where there’s been no update for at least 30 days, and either no reminders or the last reminder was at least 60 days (we can configure this later).  I made sure there’s a rate limit, to prevent horrors others have had with email reminder systems.   I’ve currently set the rate limit to only send 2 reminders a day; if it continues to work fine we will increase the rate limit.

 

Below is the latest draft of the reminder.  Comments welcome. I just added this text to help people understand this isn’t something that will fill their inbox: “We don't send reminders if you continue to update your badge entry, and we only send reminders approximately every 30-60 days.”

 

We have a lot of people who start & don’t finish.  Hopefully this will get more people over the finish line.

 

--- David A. Wheeler

 

===============================

 

This is an automated reminder that your project

"<%= @project.name %>"

does not currently have a "best practices" badge,

and its badge entry has not been updated in a while.

 

Your best practices badge entry is at

<%= @project_info_url %>

and was last updated on <%= @project.updated_at %>.

It is currently at <%= @project.badge_percentage %>% (out of 100%).

 

We encourage you to keep making progress.

Please visit your badge entry at

<%= @project_info_url %>

to complete the information and get your badge!

 

If you have questions, or need help, please contact

cii-badges-questions-owner@...

or file an issue at

https://github.com/linuxfoundation/cii-best-practices-badge/issues

(click on "new issue").

 

We don't send reminders if you continue to update your badge entry,

and we only send reminders approximately every 30-60 days.  However,

if you want to disable these reminder messages, edit your badge entry at

<%= @project_info_url %>

to turn on "disable inactivity reminder".

We hope you'll instead keep working at it

and eventually earn the badge.

 

Thank you for your time.


Nicko van Someren <nicko@...>
 

Hi David,

That sounds great. Will we be able to track how many people respond to the reminders directly or will we need to manually compare logs for the reminders and the web site? If you put some benign tracking tag into the URL that goes out in the email then I guess we would be able to just grep for that to get the data directly.

Cheers,
Nicko


On Thu, Sep 8, 2016 at 9:03 AM, Wheeler, David A <dwheeler@...> wrote:

We now have email reminders set to automatically start going out, beginning Sep 8 23:00 UTC.  They’ll only go to projects where there’s been no update for at least 30 days, and either no reminders or the last reminder was at least 60 days (we can configure this later).  I made sure there’s a rate limit, to prevent horrors others have had with email reminder systems.   I’ve currently set the rate limit to only send 2 reminders a day; if it continues to work fine we will increase the rate limit.

 

Below is the latest draft of the reminder.  Comments welcome. I just added this text to help people understand this isn’t something that will fill their inbox: “We don't send reminders if you continue to update your badge entry, and we only send reminders approximately every 30-60 days.”

 

We have a lot of people who start & don’t finish.  Hopefully this will get more people over the finish line.

 

--- David A. Wheeler

 

===============================

 

This is an automated reminder that your project

"<%= @project.name %>"

does not currently have a "best practices" badge,

and its badge entry has not been updated in a while.

 

Your best practices badge entry is at

<%= @project_info_url %>

and was last updated on <%= @project.updated_at %>.

It is currently at <%= @project.badge_percentage %>% (out of 100%).

 

We encourage you to keep making progress.

Please visit your badge entry at

<%= @project_info_url %>

to complete the information and get your badge!

 

If you have questions, or need help, please contact

cii-badges-questions-owner@lists.coreinfrastructure.org

or file an issue at

https://github.com/linuxfoundation/cii-best-practices-badge/issues

(click on "new issue").

 

We don't send reminders if you continue to update your badge entry,

and we only send reminders approximately every 30-60 days.  However,

if you want to disable these reminder messages, edit your badge entry at

<%= @project_info_url %>

to turn on "disable inactivity reminder".

We hope you'll instead keep working at it

and eventually earn the badge.

 

Thank you for your time.




--
Nicko van Someren
CTO, Linux Foundation
+1 (978) 821-0391


David A. Wheeler
 

Nicko:
That sounds great. Will we be able to track how many people respond to the reminders directly or will we need to manually compare logs for the reminders and the web site? If you put some benign tracking tag into the URL that goes out in the email then I guess we would be able to just grep for that to get the data directly.
I'd rather not use tracking tags in emails, that brings its own issues. In any case, what really matters is if they start making changes - not if they viewed the page.

We currently record, for each project, when the reminder was sent (to limit when we send them - we don't want to badge anyone). We could do a query to ask "how many were sent reminders in the last X days, and had a project modification since that reminder date"? It's possible that the update was trivial, but it would at least show that "someone is home". We could omit projects that disable reminders (since the modification could simply be to "turn off reminders").

We could record that number daily, as well as the number of reminders sent, as additional project_stats. Or just report it on demand ("over the last 30 days, X reminders were sent, and Y reminded projects have made updates since then").

--- David A. Wheeler


David A. Wheeler
 

We currently record, for each project, when the reminder was sent (to limit
when we send them - we don't want to badge anyone).
s/badge/badger/. Of course we *do* want to badge people if they earn it :-).

--- David A. Wheeler


David A. Wheeler
 

That sounds great. Will we be able to track how many people respond to the reminders directly or will we need to manually compare logs for the reminders and the web site? If you put some benign tracking tag into the URL that goes out in the email then I guess we would be able to just grep for that to get the data directly.
How about this: As part of the daily recording, we can record the # of reminders sent that day, and the # of projects that have been updated after being sent a reminder within the past 14 days. A project may have chosen to update their project regardless of being sent a reminder - computers are not perfect gauges of motives - but that would provide some insight.

We could also record the number of projects that are <100% (in progress) and have been updated in the last 30 days. I'd call these "active" projects. This is imperfect, since we can't tell about the projects that are working on it but do it through separate systems (such as Xen or MediaWiki). But again, it'd provide some insight.

--- David A. Wheeler


David A. Wheeler
 

I earlier said:
How about this: As part of the daily recording, we can record the # of
reminders sent that day, and the # of projects that have been updated after
being sent a reminder within the past 14 days. A project may have chosen to
update their project regardless of being sent a reminder - computers are not
perfect gauges of motives - but that would provide some insight.

We could also record the number of projects that are <100% (in progress) and
have been updated in the last 30 days. I'd call these "active" projects. This is
imperfect, since we can't tell about the projects that are working on it but do
it through separate systems (such as Xen or MediaWiki). But again, it'd
provide some insight.
It's much easier to log data while it's being generated, as opposed to figuring it out later, so I'll hurry to get this added. Shouldn't take long. My intent is to show all this on /project_stats.

--- David A. Wheeler


Nicko van Someren <nicko@...>
 

That sounds like a good plan. Thank you.

Cheers,
Nicko


On Thu, Sep 8, 2016 at 2:29 PM, Wheeler, David A <dwheeler@...> wrote:
I earlier said:
> How about this: As part of the daily recording, we can record the # of
> reminders sent that day, and the # of projects that have been updated after
> being sent a reminder within the past 14 days.  A project may have chosen to
> update their project regardless of being sent a reminder - computers are not
> perfect gauges of motives - but that would provide some insight.
>
> We could also record the number of projects that are <100% (in progress) and
> have been updated in the last 30 days.  I'd call these "active" projects.  This is
> imperfect, since we can't tell about the projects that are working on it but do
> it through separate systems (such as Xen or MediaWiki).  But again, it'd
> provide some insight.

It's much easier to log data while it's being generated, as opposed to figuring it out later, so I'll hurry to get this added.  Shouldn't take long.  My intent is to show all this on /project_stats.

--- David A. Wheeler




--
Nicko van Someren
CTO, Linux Foundation
+1 (978) 821-0391


David A. Wheeler
 

The code for recording & viewing metrics is in place, and the tests run, but we're cutting it too close for my comfort.

I'm going to delay sending emails out for 1 day, and plan to start sending reminders tomorrow (Friday night). I like the idea of collecting metrics, but it's better to collect the metrics on something while you're doing it. But it's also better to only put something in production once it's gone through its paces. One day delay won't hurt.

--- David A. Wheeler