Auto-Invite to Location Based Channels on Join
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start by locating the signup flow and any existing Slack integration in the Python bot. Map zipcode groupings to the requested channels, then clarify the NYC scope and the distance policy with the area leaders. Done means qualifying new users are automatically invited to the correct location channel, with coverage for the agreed DC and NYC cases.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Relative Priority: MEDIUM
As a user, I want to autojoin a Slack channel corresponding to my location when I join, so I know there is a local community associated with Operation Code that I can interact with.
Product Requirements
- (MVP) Users on signup who have zipcodes associated with the DC area autojoin #dc.
- (Users on signup who have zipcodes associated with the NYC area autojoin #nyc.
Technical Requirements
- Associate groupings of zipcodes with specific slack channels.
- Ex. #dc - 20001, 20002, 20003, 20004, 20005, 20006, 20007, 20008, 20009, 20010, 20011, 20012, 20015, 20016, 20017, 20018, 20019, 20020, 20024, 20032, 20036, 20037, 20045, 20052, 20053, 20057, 20064, 20202, 20204, 20228, 20230, 20240, 20245, 20260, 20307, 20317, 20319, 20373, 20390, 20405, 20418, 20427, 20506, 20510, 20520, 20535, 20540, 20551, 20553, 20560, 20565, 20566, 20593.
- Use geolocation based on the different areas and have each of those leaders determine how many miles is close enough.
- Lenguaje dominante
- Python
- Estrellas
- 33
- Forks
- 44
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
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 OperationCode/operationcode-pybot
-
general: good first issue priority: low status: accepted type: airtable modification type: code change type: feature
OperationCode/operationcode-pybot#383 · 1 asignado ·
-
priority: high project: rewrite status: accepted type: code change type: documentation type: feature
OperationCode/operationcode-pybot#365 · 1 asignado ·
-
Rate Limit on Mentor Requests Abiertofeedback: question priority: high project: rewrite status: awaiting acceptance type: code change type: documentation type: enhancement
OperationCode/operationcode-pybot#176 · 13 comentarios · 1 asignado ·
-
feedback: discussion priority: low project: rewrite status: awaiting acceptance type: code change type: documentation type: feature
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
OperationCode/operationcode-pybot#167 · 6 comentarios ·
-
feedback: discussion priority: medium status: awaiting acceptance type: code change type: documentation type: enhancement type: feature
Dificultad 4/5 3-5 días Aptitud para principiantes 30/100
OperationCode/operationcode-pybot#110 · 3 comentarios ·
Todos los issues de OperationCode/operationcode-pybot
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
🐛 Bug 🔔 Pending processing
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
jumpserver/jumpserver#17584 ·