Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Call for Volunteers: Help Modernize Flaredown

オープン
  • 何か問題がありますか？
#843 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
静か
技術スタック
mongodb, rails, ruby
領域
backend, databases, devops, documentation, full-stack, mobile-dev

調査の方向性

まずリポジトリとその歴史的背景を確認してください。この issue では、ファイル、テスト、または範囲が明確に限定された開始タスクが特定されていません。完了とは、ステークホルダーと MVP について合意し、移行とロールアウトのニーズを評価し、テスト、デプロイ、安定化を含む段階的な再構築を提供することです。

索引モデルが 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 はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

rubyforgood/Flaredown のほかの issue

rubyforgood/Flaredown の issue をすべて見る

似ている issue

Ruby の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。