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

Call for Volunteers: Help Modernize Flaredown

未关闭
  • 哪里不对？
#843 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

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

调研方向

首先审查仓库及其历史背景；该 issue 未指明文件、测试或范围明确的起始任务。完成意味着与利益相关者就 MVP 达成一致，评估迁移和 rollout 需求，并交付分阶段重建，同时完成测试、部署和稳定化。

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

描述

Team Request - Open

About Flaredown

Flaredown is a symptom tracker for individuals with chronic conditions — Crohn's Disease, Fibromyalgia, Lupus, and many more. It gives users a tangible way to record their symptoms and provides real, structured information their healthcare providers can use to support diagnosis and treatment. Flaredown is used by individuals in over a hundred countries and has helped many treat, manage, and identify their conditions.

Flaredown was originally built in 2015 and is now showing its age. It has served its users well but needs to be updated, streamlined, and improved.

Current State

  • Application: Mobile app with a Ruby on Rails backend
  • Preferred stack for the rebuild: Ruby on Rails with Hotwire Native for mobile
  • Code, license, and history: Available in this repository

The Work

The team will partner with Flaredown stakeholders to:

  1. Understand the problem. Regular syncs with stakeholders to scope what needs to change and why.
  2. Produce research artifacts. Personas, journey maps, mocks, and design documentation once the problem is well understood.
  3. Plan data migration. An engineering assessment of what current user data exists and how it will be migrated to the new application.
  4. Build iteratively. Develop the new application with user testing along the way to validate decisions.
  5. Roll out to all users. Coordinate the cutover from the legacy app to the new one.
  6. Fix bugs and stabilize. Address issues that surface post-launch.

Beyond building the app, the team will also navigate the rest of the project lifecycle like documentation, deployment to the Apple App Store and Google Play Store, and general project hygiene.

Team Composition

We're looking for 5–6 volunteers:

  • 2 designers
  • 1 product manager
  • 3 software engineers

This isn't strict. We're happy to consider other team compositions if you want to suggestion one.

What We Provide

  • A regular sync with someone from our side
  • Availability in a Slack channel for asynchronous questions
  • Introductions to Flaredown stakeholders
  • Access to the codebase and historical context via this repository

Time Commitment

3–6 months, with each team member contributing a few hours per week. Software estimates are exactly that, estimates, and we'll work with the team to scope an MVP that fits the available time and iterate from there.

Restrictions

Because Flaredown stores health information that users share with their medical professionals as part of their care, this project is open primarily to teams with experienced members who have shipped production software before. We'd be glad to include some students or early-career folks as a learning and mentorship opportunity, but the core of the team should be experienced.

How to Apply

You can comment on the issue and we'll get in touch. We're volunteers too so don't panic if we don't respond instantly!

主要语言
Ruby
星标
50
派生
21
30 天内没有已合并 PR

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

rubyforgood/Flaredown 的其他 Issue

查看 rubyforgood/Flaredown 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

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