Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#2,310 0 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
rails, ruby
领域
full-stack

调研方向

从 codebar 网站的管理部分开始，检查 chapter 成员、workshop 和组织者是如何表示的。在实现之前，与维护者明确收件人选择和电子邮件的最低要求。Done 应该是一种定义明确且经过审查的方式，使组织者能够联系目标成员，而无需手动处理地址。

由索引模型根据 Issue 内容生成。

描述

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'
主要语言
Ruby
星标
104
派生
205
平均合并
1 天 8 小时
30 天内合并 PR
67

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

codebar/planner 的其他 Issue

查看 codebar/planner 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。