What should org profiles show for workshop logs and monthly reports, and can individuals opt out?

Open
#2,681 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
ruby
Domain
authorization

Research direction

This is a policy question for maintainers, not a code task yet. Read the org profile's "Associated records" card and the organizations.profile_show_workshop_logs toggle, then the unused people.profile_show_workshop_logs and people.profile_show_monthly_reports columns, and check issue #2676 for the person-profile context. Done means the admins have chosen answers to the three questions; the follow-up work (wiring or dropping the toggle, dropping the columns) comes after that.

Written by the indexing model from the issue text.

Description

stakeholder-question

🤖 From Claude:

Question for admins: what should an organization's profile show for workshop logs and monthly reports, and should individuals be able to keep their own logs and reports from showing at the org level?

How it works today

  • Org profile: an "Associated records" card links to the org's workshop logs and monthly reports. Only admins and people affiliated with the org can see it.
  • Affiliated members see everyone's records, not just their own. That's every workshop log and monthly report filed under the org, including other facilitators'.
    • Members can also delete those workshop logs, and edit or delete those monthly reports.
  • The org "Show workshop logs" toggle does nothing. It's on the org edit form (organizations.profile_show_workshop_logs), but no page reads it. There's no monthly reports toggle.
  • Person profile: a person's own logs and reports are private (the person and admins only) with no toggle (#2676). The leftover people.profile_show_workshop_logs / profile_show_monthly_reports columns are unused.

Questions

  1. Who should see an org's workshop logs and monthly reports from its profile?
    • Keep it to members and admins (as now)?
    • Admins only?
    • Show the public something lighter, like counts?
  2. What should the org "Show workshop logs" toggle do?
    • Hide the card from members?
    • Hide it from the public?
    • Or remove the toggle?
    • Should monthly reports get a toggle too, or none since they're deprecated?
  3. Should individuals control whether their own logs and reports show at the org level?
    • Options: (a) no, anything filed under the org is visible to its members; (b) a per-person opt-out; (c) a per-record "private" flag.
    • Should members' ability to edit or delete other people's records change too?

Follow-up once decided

  • Drop or wire up the org toggle.
  • Drop the unused people columns (or reuse them for the opt-out in 3b).
Dominant language
Ruby
Stars
15
Forks
28
Avg merge
14h 29m
Merged PRs (30d)
292

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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/awbw

All issues in rubyforgood/awbw

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.