Add feedback to rejection emails
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
The issue names no files, tests, or entry points; begin by locating the rejection-email workflow in the Rails application and reviewing how proposal outcomes are represented. Done would require an agreed feedback model and supportive rejection emails that close the loop, but the issue does not define the implementation or acceptance tests.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Having been on the review committee for RailsConf 2016, and been a submitter for many before it, I think constructive feedback in the rejection email would alleviate the anxiety of the unknown and could encourage speakers to submit again in the future.
I spoke with an individual last year at RailsConf 2016 that didn't know why his proposal was rejected; He didn't know if it was totally off or close. I logged in, and told him he was close, but it just didn't make it for the year. Due to that he resubmitted the talk this year and was accepted. He told me that he might not have, had he not known it was close.
I can speak from experience: I've been rejected, but not sure if it was due to something I could address in the future, or it simply didn't win out over other talks. You're left "in the dark."
Whatever solution is found, I feel it needs to:
- Have little impact on the review committee's process
- Provide constructive and direct feedback
- Be encouraging and supportive and not callus and blunt
- Close the loop on the process and not leave a vague sense that the door is still open for the current event
After speaking with @mghaught it appears that many/most talks fall into one of a few buckets:
- Talk lacks clear attendee value
- Talk is vague or too broad
- Talk topic is overdone
- Talk topic was out of alignment with the goals of the event
- Talk was a runner up, but another talk won out
- (likely a few more)
As we all know, putting a talk together can be time consuming and scary. Given feedback can make the experience encouraging and empowering. That's the ultimate goal.
(I'll include implementation thoughts below)
- Lenguaje dominante
- Ruby
- Estrellas
- 237
- Forks
- 162
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la 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 rubycentral/cfp-app
-
Dificultad 3/5 1-2 días Aptitud para principiantes 50/100
rubycentral/cfp-app#1140 ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
rubycentral/cfp-app#311 · 3 comentarios ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 45/100
rubycentral/cfp-app#225 ·
-
Withdrawn Talk StatusAbiertoenhancement
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
rubycentral/cfp-app#183 · 1 comentario ·
-
Custom Filters Are LostAbiertobug
Dificultad 3/5 1-2 días Aptitud para principiantes 40/100
rubycentral/cfp-app#145 · 3 comentarios ·
Todos los issues de rubycentral/cfp-app
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Homebrew/homebrew-core#317477 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
area/web interface
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
mastodon/mastodon#41009 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
yegor256/ellipsized#131 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100