shift-org / shift-org/shift-docs
notice and follow-up on unpublished rides after...some specified time period
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 25
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
In https://github.com/shift-org/shift-docs/issues/304#issuecomment-1172684777 @carrythebanner suggested a cool idea: notice rides that the leader has failed to publish after "x hours" and email them a reminder.
This feels like a separate task from "updating the email to have the mosts useful info" which https://github.com/shift-org/shift-docs/issues/304 is about, so pulling that "after-hours" followup into its own issue here.
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 with issue 304 and the linked comment from @carrythebanner to understand the proposed follow-up for unpublished rides. Define the waiting period and reminder behavior, then confirm that the resulting task covers email notices after a leader fails to publish a ride.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100