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

Display emails to organizers #2549

Closed
wants to merge 5 commits into from
Closed

Conversation

rahul2240
Copy link
Member

@rahul2240 rahul2240 commented Jul 11, 2019

Checklist

  • I have read the Contribution & Best practices Guide.
  • My branch is up-to-date with the upstream master branch.
  • The tests pass locally with my changes.
  • I have added tests that prove my fix is effective or that my feature works(if appropriate).
  • I have added necessary documentation (if appropriate).

NEED

If organizers want to contact a user, they can get the user's email from user's profile and can contact through mail. This is okay if they want to contact 1 or 2 users.
But what if they want to contact a group of people associated with the conference. For such scenario,
the only option available to them is to find emails of all users and then contact them.

With this PR, Organizers will get the emails of the group of people they want to contact say (subscribers, booth responsibles etc.). They just have to select the group and proceed with the link which will open their default mail service with email already entered for them. Now they just have to enter subject and body.

This way organizers can save a lot of time in finding people to contact.

WORKFLOW

  1. Organizers will go to send emails link available in sidebar.
  2. Select the right group or enter email ids if they want to in the text field.
  3. Press the send email button.
  4. User will be redirected to the default mail with emails in bcc.

sidebar link
main2

form
main1

options
options

selecting options
main3

redirected to mail
main4

@codecov
Copy link

codecov bot commented Jul 11, 2019

Codecov Report

Merging #2549 into master will decrease coverage by 0.21%.
The diff coverage is 20%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2549      +/-   ##
==========================================
- Coverage   76.46%   76.25%   -0.22%     
==========================================
  Files         146      146              
  Lines        4810     4830      +20     
==========================================
+ Hits         3678     3683       +5     
- Misses       1132     1147      +15
Impacted Files Coverage Δ
app/controllers/admin/emails_controller.rb 40.62% <16.66%> (-30.81%) ⬇️
app/mailers/mailbot.rb 48.93% <50%> (+0.04%) ⬆️
app/helpers/format_helper.rb 58.33% <0%> (+0.92%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9b12830...6c70de9. Read the comment docs.

@codecov
Copy link

codecov bot commented Jul 11, 2019

Codecov Report

Merging #2549 into master will decrease coverage by 0.48%.
The diff coverage is 3.22%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2549      +/-   ##
==========================================
- Coverage   82.21%   81.72%   -0.49%     
==========================================
  Files         146      146              
  Lines        4773     4804      +31     
==========================================
+ Hits         3924     3926       +2     
- Misses        849      878      +29
Impacted Files Coverage Δ
app/controllers/admin/emails_controller.rb 31.11% <3.22%> (-61.75%) ⬇️
app/controllers/commercials_controller.rb 96.42% <0%> (+3.57%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c5ad952...e572428. Read the comment docs.

@rahul2240 rahul2240 added the GSoC GSoC 19 related issues/PR label Jul 13, 2019
@rahul2240 rahul2240 force-pushed the custom_email branch 2 times, most recently from ea778df to ebf7972 Compare July 14, 2019 11:46
@hennevogel
Copy link
Member

Hm this might sound a bit harsh as I don't have any idea about your GSoC plans but why are we implementing mail functionality in our web app? There are plenty of ways people can send email.

@rahul2240
Copy link
Member Author

@hennevogel Thanks for the comment 😄 .Yes, you are right. But I proposed this so that organizers can inform people about some sudden changes or with an update about the conference.
It has its own advantage i.e organizers can contact the right group of people instantly.
There are plenty of ways to send email but my purpose for this feature is to provide a custom template to organizers for a given audience in regard to the particular conference.

@hennevogel
Copy link
Member

It has its own advantage i.e organizers can contact the right group of people instantly.

That's as simple as

<a href="mailto:onecooldude@gmail.com?subject=Hey+Dude.+You're+Cool.&cc=anotherdude@gmail.com,thirddude@gmail.com,fourthdude@gmail.com&bcc=invisibledude@gmail.com,ghost@gmail.com">Contact Organizers</a>

and we don't have to worry about all the follow up features your mail interface will not support, like different formats (text/plain vs. html), BCC or other custom headers, special formatting of the text. The list of MUA features is endless.

@rahul2240
Copy link
Member Author

@hennevogel thank you 😄 . That's indeed very simple, didn't think of this approach 😓 . I will update the PR. Thanks.

@rahul2240 rahul2240 force-pushed the custom_email branch 2 times, most recently from d08d19d to e2410f8 Compare July 18, 2019 17:10
@rahul2240 rahul2240 changed the title Custom email for admins [WIP] display emails to organizers [WIP] Jul 18, 2019
@rahul2240 rahul2240 force-pushed the custom_email branch 3 times, most recently from 303601b to ef7001f Compare July 19, 2019 09:33
@rahul2240 rahul2240 changed the title display emails to organizers [WIP] Display emails to organizers Jul 19, 2019
@rahul2240 rahul2240 force-pushed the custom_email branch 3 times, most recently from cc832c5 to e572428 Compare July 20, 2019 15:04
@codecov-io
Copy link

codecov-io commented Jul 20, 2019

Codecov Report

Merging #2549 into GSoC19 will decrease coverage by 0.3%.
The diff coverage is 5.26%.

Impacted file tree graph

@@            Coverage Diff             @@
##           GSoC19    #2549      +/-   ##
==========================================
- Coverage   82.26%   81.96%   -0.31%     
==========================================
  Files         147      147              
  Lines        4799     4818      +19     
==========================================
+ Hits         3948     3949       +1     
- Misses        851      869      +18
Impacted Files Coverage Δ
app/controllers/admin/emails_controller.rb 42.42% <5.26%> (-50.44%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b2f2b5...234defc. Read the comment docs.

@rahul2240 rahul2240 force-pushed the custom_email branch 2 times, most recently from 65b33b3 to da75406 Compare July 20, 2019 15:14
@rahul2240 rahul2240 changed the base branch from master to GSoC19 July 21, 2019 09:30
@differentreality
Copy link
Contributor

I like the fact that we are able to further add/deselect emails from the list!

What we aim to do here is to automatically send an email to all accepted booths (we already have an Email template for that). The scenario is the following:

  • Evaluate Booth proposals
  • Start accepting booths (for some you are certain, for some others not), some booths are already marked as accepted
  • Some booth proposals are to_accept (meaning we think about accepting them, but let's see if we can fit them all)
  • After the deadline (and after we have finalized our selections) we want to send out an email to everyone to let them know if their proposal was accepted or rejected

@keys['Registered Users'] = @conference.participants.pluck(:email) if @conference.participants.present?
@keys['Confirmed Tracks'] = User.find(confirmed_track_ids.uniq).pluck(:email) if confirmed_track_ids.present?
@keys['Supporters'] = @conference.supporters.pluck(:email) if @conference.supporters.present?
@keys['Organizers'] = roles_ids['organizer']
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That should be Conference Organizers, right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes.

@rahul2240
Copy link
Member Author

rahul2240 commented Aug 16, 2019

@differentreality Sending email to everyone after the deadline can be implemented in separate PR.
The purpose of this PR is that organizers can contact a group of people and inform them about anything i.e either updating them with some news or important announcement or something. I think its an important feature for improving communication between organizers and people.

@codecov
Copy link

codecov bot commented Aug 16, 2019

Codecov Report

Merging #2549 into GSoC19 will decrease coverage by 0.3%.
The diff coverage is 5.26%.

Impacted file tree graph

@@            Coverage Diff             @@
##           GSoC19    #2549      +/-   ##
==========================================
- Coverage   82.26%   81.96%   -0.31%     
==========================================
  Files         147      147              
  Lines        4799     4818      +19     
==========================================
+ Hits         3948     3949       +1     
- Misses        851      869      +18
Impacted Files Coverage Δ
app/controllers/admin/emails_controller.rb 42.42% <5.26%> (-50.44%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b2f2b5...234defc. Read the comment docs.

@differentreality differentreality self-assigned this Jan 6, 2020
@hennevogel
Copy link
Member

Closing this for lack of activity...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GSoC GSoC 19 related issues/PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants