Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability for Users to sign up to receive updates #19

Open
cnorm35 opened this issue Mar 1, 2023 · 9 comments
Open

Add ability for Users to sign up to receive updates #19

cnorm35 opened this issue Mar 1, 2023 · 9 comments

Comments

@cnorm35
Copy link

cnorm35 commented Mar 1, 2023

No idea if this is something you think would be useful but was thinking of something very simple to start.

Something bare-bones like allowing a user to opt-in to weekly updates where new issues created in the past week are still open are emailed out once a week as a gentle nudge to keep people coming back and looking for new issues.

If this is too soon or out of scope from what you all have planned, feel free to close!

@excid3
Copy link
Owner

excid3 commented Mar 1, 2023

That is a great idea. I would love that.

I would imagine a semi-plaintext email (in the Rails Weekly style) with links to the bounties, their description and the amount.

We can probably just email out only the open bounties. Might want to limit to like 15 most recent bounties or so and link to the homepage if there are more available?

@cnorm35
Copy link
Author

cnorm35 commented Mar 1, 2023

I think that's perfect. Keep it simple and go from there.

I don't know if I would call this a "Jr" task but think if there's a clear description and someone to help things along, I think it'd be reasonable for a newer dev to tackle.

@excid3
Copy link
Owner

excid3 commented Mar 1, 2023

Definitely a more challenging one, but a good one none the less. Background job + mailer shouldn't be too hard.

@cnorm35
Copy link
Author

cnorm35 commented Mar 1, 2023

Here's what I'm thinking for the acceptance criteria, let me know what you think

  • Create a Background Job to find open bounties created in the last 7 days and email to Users

  • Display Bounties with links to the bounty, the description and the amount in a very basic HTML email

Should probably allow the users a way to opt out of those emails, but maybe that can be a separate task? In the meantime maybe something like 'email [email protected] to be removed' ?

Trying to keep the task manageable but also don't want to rope you all into a bunch of manual work

Did you have any ideas on how you'd like to run the job?

Maybe just plan on running manually for now in the console inline or with a rake task?

@clair13
Copy link

clair13 commented Mar 2, 2023

Hey I think,I'll be able to solve the above tasks

Create a Background Job to find open bounties created in the last 7 days and email to Users

Display Bounties with links to the bounty, the description and the amount in a very basic HTML email

If it is ok , can I have like 3-4 days for this?
If I have any questions I will ask them on discord. It is amazing what you are doing.
Let me know. Thank you for your time.

@cnorm35
Copy link
Author

cnorm35 commented Mar 2, 2023

@clair13 that works for me. I'll be sure to create a bounty for this one and assign to you so you can get paid for your time. I'm available in the GoRails Discord if you have any questions.

@clair13
Copy link

clair13 commented Mar 2, 2023

Ok thank you, I'll join Discord tomorrow(it is pretty late here ), and I'll ask for directions like if you would like a specific adapter and maybe to have a more clear understanding of the task.

@cnorm35
Copy link
Author

cnorm35 commented Mar 2, 2023

Sounds good. For now, instead of worrying about bringing in sidekiq right now, maybe just use ActiveJob. Here's some helpful info on ActiveJob to get you started https://guides.rubyonrails.org/active_job_basics.html

@clair13
Copy link

clair13 commented Mar 2, 2023

Thanks for this ,it will be simpler. I was thinking about Rescue adapter :) . I'll give you a message on discord. Thanks again for your time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants