codebar / codebar/planner

Add ability for organisers to contact chapter members directly from the admin section of the codebar website

Open
#2,310 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
104
Forks
205
Avg merge
1d 5h
Merged PRs (30d)
63

Description

There have been a number of requests recently from organisers wanting to contact their chapter members by email. Organisers have access to chapter member emails and the only way for them to contact members is for them to use these email addresses manually. This has a couple of problems:

  • Organisers have access to email addresses. It would be good to minimise this.
  • There is a risk of accidentally using cc rather than bcc and thereby exposing the email addresses.
  • They have to use their personal email accounts for "official" emails which might end up in spam.
  • Only three levels of granularity: all coaches/students in the chapter, everyone that attended a specific workshop, individual member.

It would be good to have the ability to email members from within the codebar web interface without having to manually deal with email addresses. It's unclear what the minimum functionality should be for this, given the differences in chapter sizes and varying needs. Based on my own personal experience, the types of email I have sent the most are to attendees of a specific workshop to give them last minute updates.

Meetup has an interface for sending emails that might be useful for inspiration. It allows sending emails to varying subsets of a group.

Screenshot of some mailing options from the meetup.com group admin interface. Some of the options are 'all members', 'the leadership team', 'a custom list', 'members active with the last:', 'members inactive for:' with a dropdown showing 'month' and lastly 'members based on RSVP status to a given event'

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the admin section of the codebar website and review how chapter members, workshops, and organisers are represented. Clarify the minimum recipient-selection and email requirements with maintainers before implementation. Done should be a defined, reviewed way for organisers to contact the intended members without manually handling addresses.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.