[Feature]: Moderation and spam filter (and re-combining forums?) on the Discord channel
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
- 5/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Área
- devtools
Línea de trabajo
This is a community and Discord-administration request, not a code change in the repository, so there is no file or test to start from. It asks for a spam filter and moderation on the Discord server, and for merging the platform-specific help channels into one. Done would be a decision by the maintainers on the moderation tooling and channel layout, which a newcomer cannot make alone.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
🚀 Feature Request
Since Debby left, and since the growth of AI coding tools, fewer (on-topic) questions are asked on the Discord channel, and many more spam messages are posted.
It would help the community if moderation would be introduced, and possibly a spam filter.
Also, since we have less traffic, consider to re-combine the platform-specific channels, so messages get more attention instead of being hidden in a sub-forum. Using tags should suffice to distinguish or filter the platforms.
Example
When someone posts something spammy or off-topic, it gets removed quickly.
When someone visits the channel, it doesn't look so dead.
Motivation
New users of Playwright, or even experienced users who visit the community the first time, will have a better first impression of the Discord community.
And community members who want to help won't get distracted and demotivated by the amount of spam.
Re-combining the forums will give new channel users also an impression of a more lively community.
Messages about other platforms are more likely to be seen when posted in the main help-playwright channel (a lot of questions are not that platform-specific anyway; Playwright is quite similar across platforms).
- Lenguaje dominante
- TypeScript
- Estrellas
- 98.5k
- Forks
- 6.7k
- Merge medio
- 17 h 15 min
- PR fusionados (30 d)
- 311
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin 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 microsoft/playwright
-
[Feature]: Node 26 Docker ImagesAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
microsoft/playwright#43759 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
microsoft/playwright#43741 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
[Bug]: --only-changed misses a test file when two ESM test files share an importPosiblemente ocupada @cpeaustriajc la tomó hoy. Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 15/100
microsoft/playwright#43824 ·
Los mantenedores suelen responder en 1 día
-
[Feature]: Let an MCP client label its own extension tab groupPosiblemente ocupada @microsoft-playwright-automation la tomó hoy. Abiertoneeds-triage
Dificultad 4/5 3-5 días Aptitud para principiantes 15/100
microsoft/playwright#43823 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[Bug]: UI mode frequently crashes at test finish with "Error: EBUSY: resource busy or locked"Abiertoneeds-triage-win
Dificultad 4/5 3-5 días Aptitud para principiantes 20/100
microsoft/playwright#43821 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de microsoft/playwright
Issues similares
-
guards: accept readonly arrays (and other array-likes) in isEmpty / hasElements / safeLengthAbiertoenhancement tech debt
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 62/100
danielmiessler/LifeOS#2533 ·
Los mantenedores suelen responder en 9 días
-
auto:producer auto:uiux
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
fritzprix/libr-agent#2447 ·
Los mantenedores suelen responder en 1 día
-
bug low priority
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100