Show mapping-project activity on profile timelines, only to people who can see the project

Abierto
#2,982 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo

Línea de trabajo

Start with the linked OpenConceptLab/ocl_online#418 for context on how mapping projects and their visibility are modelled. Then find where the API records activity events and where each feed — profile timelines, dashboards, the community feed — filters them, since the visibility rule must be applied in all of them. Finish on TBv3's Overview timeline, where each event must render and link to its project in the Mapper. Done means project-creation events are recorded and visible only to the owner, owning-org members and staff across every feed.

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

Descripción

component/api component/mapper component/web decision/human-review signal/high-risk signal/large-scope signal/needs-human stage/triaged type/feature

Summary

A profile's Overview timeline shows activity on organizations and repositories, but nothing from the Mapper: the API records no events for mapping projects. Events are public today. They appear on profile timelines, on followers' dashboards and in the community feed. Mapping projects are private, so their events need a visibility rule before any are recorded.

Acceptance criteria

  • The API records an event when a mapping project is created, plus any other project milestones we agree on.
  • A mapping-project event is returned only to people who can see the project (its owner, members of the owning organization and staff), in every feed: profile timelines, dashboards and the community feed.
  • TBv3's Overview timeline shows these events and links each to its project in the Mapper.

Related: OpenConceptLab/ocl_online#418

Lenguaje dominante
Sin datos de lenguaje
Estrellas
4
Forks
2
Merge medio
2 h 12 min
PR fusionados (30 d)
1

Preparar el entorno

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 OpenConceptLab/ocl_issues

Todos los issues de OpenConceptLab/ocl_issues

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.