Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
As a way of connecting with the nearly million users on Drupal.org - and perhaps prompting a login / update - we could send an email to everyone on their Drupalversary. People often remark on this informally on twitter / IRC etc...
I think it would be nice to recognise people this way. It may even be a "community development initiative" :)
Proposed resolution
Send email to d.o users on their drupalversary.
Contents
- nice short message
- link to social media share
- reminder can/how opt in to newsletters
Consider
avoid EU spam rules, ... details needed
Remaining tasks
- draft message
- evaluate if we can even do this, terms of service, laws, opt in, opt out, etc.
User interface changes
none? opt in? account setting?
API changes
none?
Data model changes
none?
Comment | File | Size | Author |
---|---|---|---|
#9 | Screen Shot 2015-11-24 at 10.52.00.png | 17.35 KB | Anonymous (not verified) |
Comments
Comment #1
mgiffordWell, this would have been nice. Sadly we missed it for 2014.
On the plus side though, we've got months to organize it for next year.
I do think having semi-regular reasons to send out alerts to people who signed up to Drupal is a good thing.
If we were sending emails every year (or maybe even more than that), we'd have a much better sense of how many of those 1 million users are really there.
I do think it is a good reason to celebrate and also great way to get folks to say answer a survey or remind people to tweet "Happy Birthday Drupal!" to their friends.
Comment #2
kattekrab CreditAttribution: kattekrab at Creative Contingencies commentedHey thanks Mike!
We had the upgrade to get through when I first posted this - but that's done now, so perhaps we could ask for this to be implemented now?
Let's try to get a few more eyeballs and thoughts?
cheers
Donna
Comment #3
mgiffordSo do we send regular updates from DrupalCons to this list? Is the next big mailing going to be the next DrupalVersary?
I'd like to have more regular means to reach out to the membership and let them know that things are changing (for the better).
Anyways, totally good to have more eyeballs on this. Do we have a communications plan which outlines how often the DA communicates to the drupal.org users via email or twitter?
I haven't noticed a pattern thus far.
Comment #4
holly.ross.drupal CreditAttribution: holly.ross.drupal commentedHi all! I love this idea! Unfortunately, it's my understanding that we're still stuck in a situation where we can't email anyone anything other than required system messages because we do not have any email/opt-in process/policy. However - I think we could easily post a message on their profile on that day with a little "tweet your drupalversary" social media icon. Would that be a sufficient implementation?
Comment #5
mgifford0) That's great! Glad you like @kattekrab's idea too.
1) Is there an issue to set up a email/opt-in process/policy for drupal.org? I'd probably prefer for it to be opt-out vs opt-in, but
2) I don't know if posting something in their profile is sufficient. I don't know that I went to my profile page around then and may not have seen it. I think we could be using something like this though to convey regular messages to users #2193871: Create an Action Block for Short Messages for Users & Visitors. If this were StackOverflow they could just send a message to all of their users and have it on their in-site mailbox. I'd like something a bit more noticeable than just a block on a page most users rarely check though.
Comment #6
kattekrab CreditAttribution: kattekrab at Creative Contingencies commentedI wonder if we could pick this up again now?
Comment #7
mlhess CreditAttribution: mlhess as a volunteer commented@Holly
I wonder if we could combine this message with a happy Drupal anniversary and a please change your password as it has been a year.
Comment #8
mgiffordThat's a good call @mlhess - might even give them a relative score for the complexity of their password.
Comment #9
Anonymous (not verified) CreditAttribution: Anonymous as a volunteer commentedCan we actually see when the day is? I'm getting this comical display which I presume I could/should create an issue for somewhere ;)
Comment #10
kattekrab CreditAttribution: kattekrab at Creative Contingencies commentedYes - that would be kinda useful, ey? :)
I wonder if we could use that time toggle feature that displays in comments?
Comment #11
Wim LeersIt'd be nice if we'd also finally fix that
strangeness, as adorable as it may be :)Comment #12
Steven Jones CreditAttribution: Steven Jones at ComputerMinds commentedNote that you can use the drupal.org rest API to get the exact timestamp your created your account, for example: https://www.drupal.org/api-d7/user/99644.json
Comment #13
mlhess CreditAttribution: mlhess as a volunteer commented@CWG, is something you feel that should be done. This is in your queue but does touch on security.
I would think we would want some rules around it.
1) You must have logged in sometime in the last year and posted something in the last year.
2) If you have an elevated role and have not logged in, in the last year, the message should go to the sec team to remove the role.
3) I would want someone from the cwg to write the text of the message. It should end with a message about changing your password
4) The message should include a link to share to facebook/twitter (I think??)
5) Anything else?
Comment #14
Wim Leers#12 OOOHHHH! Thanks!
Comment #15
gdemetSo awesome to see this issue is getting some attention!
kattekrab may have more context, but my understanding is that this is an idea that came out of a community summit at DrupalCon a couple of years ago as a way to build community pride and engagement, and that the issue got moved to our queue when the CWG was chartered because there wasn't another obvious place for it to go.
I don't think that the CWG has strong opinions on how this gets implemented or the specific wording of the emails that get sent out, but if there are specific questions or text that you'd like us to review, we can do so at our next meeting in early January. In the meantime, we're more than happy to let the community run with this.
Comment #16
giorgio79 CreditAttribution: giorgio79 commentedIt would also require prior consent in the EU to avoid spam rules.
Comment #17
kattekrab CreditAttribution: kattekrab at Creative Contingencies commentedI missed my 10 year DrupalDay by a month. :(
We should do this.
Comment #18
rachel_norfolkHi,
As we are looking to place more issues describing the governance of the CWG here (as opposed to the actual activity of the CWG), I’d like to do some “tidying up”.
Can you please describe what actions are needed to close this issue for you?
Thanks
Rachel, CWG
Comment #19
mlhess CreditAttribution: mlhess as a volunteer commentedMoving...
Comment #20
rachel_norfolkTa!
Comment #21
drummMoving to maybe a better project.
The security tag is for tracking public security issues on projects that do not fall under the security advisory coverage policy, and security hardening issues.
Comment #22
kattekrab CreditAttribution: kattekrab at Creative Contingencies commentedThat seems a sensible move @drumm - thanks!
What's necessary to move this forward?
Comment #23
drummProbably an issue summary update with the specific rules. Is this a transactional mailing we don’t need more opt-in for, or should we send it via MailChimp and respect subscription to any of the lists? Do we mail people who haven’t logged in for years?
Personally, I don't think I’d want this email if I weren’t subscribed to a list, but I wouldn’t be too annoyed if I got it anyway.
Comment #24
YesCT CreditAttribution: YesCT commentedComment #25
YesCT CreditAttribution: YesCT commentedthis is a good idea
updated issue summary
re #13
1) You must have logged in sometime in the last year and posted something in the last year.
- nah.
2) If you have an elevated role and have not logged in, in the last year, the message should go to the sec team to remove the role.
- out of scope
3) I would want someone from the cwg to write the text of the message. It should end with a message about changing your password
- anyone can draft it. let's get a few people to review. not required to be cwg people, but could be.
4) The message should include a link to share to facebook/twitter (I think??)
- good idea
Comment #26
lizzjoyI'd like to see this happen. I think we should send to anyone who has logged in during the year (since last anniversary date) but keep the message short and sweet.
Here's a draft that I started to keep this moving. If I leave this open for editing until April 27 (2 weeks from now), and we finalize the message, then we can take next steps. https://docs.google.com/document/d/15BlQivggdkViTbukmYpibqLe_sscRTvoekfc...
Comment #27
dwwSounds fun and like a nice touch.
However, we'll have to finally resolve the leap year problem in format_interval() in D7 or d.o will send these emails on the wrong days. #109878: format_interval should support leap-year calculation was the original issue. Marked as duplicate with #2456521: Add DateFormatter::formatDiff() as a non-buggy alternative to DateFormatter::formatInterval() when the start and end of the interval are known but that was never backported. I don't think there's a good way in D7 to accurately do what you're talking about here. As someone with 2 or 3 leap years between when I opened my d.o account and today, I see this bug every year near my "Drupalversary" d.o is confused about when to display "12 years and 0 days". Beware. ;)
Cheers,
-Derek
Comment #28
dwwp.s. Oh, the D7 backport issue is here: #2744597: Add format_time_diff() as a non-buggy alternative to format_interval() when the start and end of the interval are known ...
Comment #29
kattekrab CreditAttribution: kattekrab at Creative Contingencies commentedOooh!
So pleased to see movement here.
Let's get this done!
Comment #30
Gábor HojtsyMatt Grill created https://drupalbirthday.fun/ (append your username to the URL). This of course only works if you actively look for your drupalversary.
Comment #31
lizzjoyIf the leap year issue can't be resolved, the alternative I see is sending this message via the mailchimp list. This would mean that anyone who isn't receiving messages from https://drupal.us2.list-manage.com/subscribe?u=618af7a460cf93cf211231139... will not receive the message.
Comment #32
kattekrab CreditAttribution: kattekrab at Creative Contingencies commentedWould a simpler thing be... to just display the date someone first joined Drupal.org, and email them on that date?
The years ago... is nice, but not necessary.
Given I made this ticket 5 years ago - it would be great to find ways to make it happen faster, rather than more reasons not to do it.
Comment #33
Steven Jones CreditAttribution: Steven Jones as a volunteer commentedPresumably once a day we could email everyone who joined 'today' in any year, mention the year they joined and a nice message etc.
However, that would mean that people who joined on 29th Feb would only get an email every 4 years, but maybe we could acknowledge that with a super special email :)
Comment #34
drummSending by date is not too hard:
Risking sending duplicate emails due to time math or cron outages/etc isn’t something we want to do, so we keep track of what was sent and use that to keep track. Or if we go with MailChimp, I think this is a straightforward drip campaign.
Implementation aside, how is the important part, the content of the emails, doing?
Comment #35
kattekrab CreditAttribution: kattekrab at Creative Contingencies commentedOk here's a start (let the real bikeshedding begin)
Hello [name]
Happy Drupal Day!
You first logged in to Drupal.org on [date] and we'd like to acknowledge that, by thanking you for your participation and contribution to the Drupal project and community.
So thank you!
You might like to take a moment to update your profile, or change your password.
Happy Drupalling!
- (who / how) sign off.
Comment #36
lizzjoyThis is launched for the Drupal Email list. We can revisit it anytime if it seems like the audience to receive the message should be larger. To avoid the issues mentioned in comments here (leap year making date of send tricky, not emailing to those who haven't opted in....) I set the message up to run on the Drupal email list via automation. The language is here https://docs.google.com/document/d/15BlQivggdkViTbukmYpibqLe_sscRTvoekfc... and to make sure you get your message, double check you are subscribed to https://drupal.us2.list-manage.com/subscribe?u=618af7a460cf93cf211231139... and select Email under Marketing Preferences.