Check Feed Official Status
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 45/100
Línea de trabajo
Find the feed submission handler in the web-app where feed_info is processed and GitHub issues are created for new feed submissions. Look for where the official/unofficial classification currently happens and where feed_publisher_name, feed_publisher_url, and feed_contact_email are available. Implement the three automatic checks (domain similarity, allow list, schedule/realtime cross-reference) to run upon submission and include the result in the GitHub issue.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the problem
In the feed submission form, contributors are given the chance to declare a feed as official or unofficial. Before we import or update the feed, we want to be able to confirm feeds either as official or unofficial.
Currently, this is done manually by:
- examining the feed email and the publisher URL to detect likelihood that it is official
- checking for known vendors/producers like trillium, swiftly, passio which indicate that it is official
- reaching out directly at the feed email asking if the feed is official in cases where it is ambiguous
Proposed solution
There are several checks that can be performed to determine a signal of whether a feed is official or not:
- Cross reference the feed_info's feed_publisher_name, feed_publisher_url and feed_contact_email to verify domain similarity with the publisher name. In the following two examples, the domains of the feed_publisher_url and feed_contact_email both match, which indicates a likelihood of officialness.
- Create an allow list to automatically classify feeds as official
allow list: passio, swiftly, trillium, 511
- Cross reference the schedule feed with realtime feed and vice-versa. If the schedule feed being imported has an existing official realtime feed with a similar URL domain, we can strongly assume that the schedule feed is official as well. The opposite can also be assumed.
We can consider including this in the web-app as something that is executed immediately upon submission. Then the URL validity can be directly included in the Github issue that is created.
Alternatives you've considered
No response
Additional context
No response
- Lenguaje dominante
- Python
- Estrellas
- 34
- Forks
- 7
- Merge medio
- 2 d 4 h
- PR fusionados (30 d)
- 8
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de MobilityData/mobility-feed-api
-
fix(notifications): dispatcher ignores a subscription's feeds and sends every feed.url_updated eventAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
MobilityData/mobility-feed-api#1875 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
MobilityData/mobility-feed-api#1846 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
MobilityData/mobility-feed-api#1755 · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
MobilityData/mobility-feed-api#1647 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
MobilityData/mobility-feed-api#836 ·
Los mantenedores suelen responder en 1 día
Todos los issues de MobilityData/mobility-feed-api
Issues similares
-
push_gh-pages fails on master branch on forksPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertogood first issue infrastructure
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
kuznia-rdzeni/coreblocks#1135 ·
-
good first issue server
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
documentation priority: high
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
a-lex-s/mealie-telegram-bot#54 ·
Los mantenedores suelen responder en 1 día
-
type/test
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
SaltedTan/virgil-language-server#218 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
btclib-org/btclib-wallet#541 ·
Los mantenedores suelen responder en 1 día