Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#2,681 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
ruby
Área
authorization

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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).
Lenguaje dominante
Ruby
Estrellas
15
Forks
28
Merge medio
1 d 12 min
PR fusionados (30 d)
262

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de rubyforgood/awbw

Todos los issues de rubyforgood/awbw

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.