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

Detect Mentions to Links/People/Events/Topics/Talks

Abierto
#1,863 1 comentario 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
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
ruby
Área
full-stack

Línea de trabajo

Start by reading #1862 and the published mentions branch, then compare the mockup with the current talk and transcript experience. Define how transcript mentions become potential references, how they are reviewed or edited, and how clicks behave for linked and unlinked people, events, topics, talks, and URLs.

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

Descripción

enhancement

Looking at what we did in #1862, I had the idea that we could try to analyze the transcript to "parse" out mentions and then show them specially in a tab on the talk. This helps with connecting even more data as part of the RubyEvents dataset.

If we aren't 100% certain we could mark them as a "potential reference" and either have admins (or the community) decide if they are accurate, or fix-up/fill-in the "mentionable" in a nice UI.

Clicking on the event/talk/topic/link will either bring you to the page on RubyEvents, open the link in a new tab, or just show the information if we can't link anywhere (like if a known person is mentioned that doesn't have a RubyEvents profile).

Idea/Mockup:

Image

I published the dummy UI code in this branch: https://github.com/rubyevents/rubyevents/tree/mentions

Lenguaje dominante
Ruby
Estrellas
567
Forks
232
Merge medio
23 h 53 min
PR fusionados (30 d)
44

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

Todos los issues de rubyevents/rubyevents

Issues similares

Más issues de Ruby

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.