rubyforgood / rubyforgood/casa
Improved Email Understanding
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 381
- Forks
- 542
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 47
Description
Show all old emails for user on user page
Show un/confirmed status of current email on user page
When changing a volunteer email address, send the confirm email to both old and new addresses ? (yes this is a security issue but casa volunteers sometimes have email literacy issues)
Contributor guide
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 at the user page and the volunteer email-change flow described in the issue, then trace the existing email confirmation behavior. Define how historical addresses, current confirmation status, and notifications to old and new addresses should appear and behave, including the security implications; done means the agreed behavior is implemented and covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- authentication, full-stack, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100