shift-org / shift-org/shift-docs
consider adding extra email for "fully published" rides with some guidance for leaders
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 25
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
We could link to stuff like the ride leader comic, and also ask them to input fields that might be missing like distance and other details that we've heard discourage folks from going on rides from Meghan. This would be an additional email, not the "you just submitted a ride and must now publish it" one we already send.
Fool's thinking on this is that we could do something like a cron job to send them in batch every day based on new rides listed in past 24h, to keep more email data and other stuff we don't use pho for, out of the php codebase...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing “you just submitted a ride and must now publish it” email and the data available once a ride is fully published. Clarify the separate message’s guidance, including the ride leader comic and missing distance or other details, then determine how a daily batch for rides from the prior 24 hours should run outside the PHP codebase. Done means the scope, schedule, recipient criteria, and message content are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100