Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Capture contact info?

Open
#134 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with issue #107 and the paper “About you” form described here. Clarify whether contact details belong in a separate system or the app’s onboarding flow, then document the chosen placement and scope; no implementation entry point or test is named.

Written by the indexing model from the issue text.

Description

Extracted out from #107 .

The 'About you' paper form (see issue above) includes address and phone information.

We weren't sure that including these details in the 'about you' form itself made sense, so omitted it for now and created this issue to think through some open questions:

  • Sounds like this info is captured in a separate system?
  • While it probably made sense in a paper-centric flow to capture both contact and narrative details at the same time, is that still the best flow on the app?
  • Where might contact info fit in a well thought through onboarding flow?
Dominant language
Ruby
Stars
12
Forks
1
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No 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.

More from rubyforgood/community_foundation

All issues in rubyforgood/community_foundation

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.