rubyforgood / rubyforgood/awbw
Rename organization_status → program_status in code
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 15
- Forks
- 26
- Avg merge
- 12h 42m
- Merged PRs (30d)
- 242
Description
🤖 From Claude: Follow-up from #1993.
The org-wide "status" column is really a program status (Active / Formerly active / Never active buckets derived from facilitator affiliations, with the stored OrganizationStatus as fallback). The code still calls it organization_status throughout — model association, column (organization_status_id), scopes, decorator methods, params.
Rename to program_status for clarity once #1993 settles, so the code name matches the domain concept. Straightforward but wide (association, FK column + migration, scopes, decorator, views, specs), so it's worth its own PR rather than bundling into #1993.
Longer term (separate, gated on legacy data cleanup): move to a fully computed, non-overridable status and drop the stored fallback.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
First check the outcome of #1993, then search the codebase for organization_status, organization_status_id, scopes, decorator methods, params, views, and specs. Update the association, foreign-key migration, and every named reference to program_status. Done means the rename is consistent and the affected specs pass without leaving the legacy code name in use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100