PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Create an issue tracker for new leagues or open up Discord to the public.
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Lua
- Estrellas
- 5.4k
- Forks
- 2.4k
- Merge medio
- 1 d 12 h
- PR fusionados (30 d)
- 26
Descripción
Check for duplicates
- I've checked for duplicate issues by using the search function of the issue tracker
Is your feature request related to a problem?
I started looking at implementing some of the new patch changes when I saw random PRs being opened for the same thing already. Seems like there is a discord where people are organizing. This makes it hard for a newcomer to come and contribute as I don't know what's being worked on, or not.
Describe the solution you'd like
So I understand that it may be a lot of work to open up an issue for each new PR before that PR is being worked on, (although I would recommend it), but atleast for new leagues there should be an issue to track a master list of things to do before the new patch, or make 1 of the channels on the discord public so people can drive-by contribute.
Describe alternatives you've considered
Master issue tracker, either on Github or website or Discord.
Opening up public discord.
Requiring an issue to be written before work on a PR begins.
Creating a list of contributable issues for each new League, (although this kind of exists, it's not for bringing in new stuff from the patch, but for old issues or bugs).
Additional context
No response
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.
Línea de trabajo
Empieza revisando issue #3283 y sus tres comentarios; después compara las opciones propuestas: un GitHub master issue, un tracker en un sitio web o en Discord, un canal público de Discord, o exigir issues antes de los pull requests. Se considera terminado cuando el proyecto tenga un enfoque decidido y documentado para el seguimiento de contribuciones a nuevas ligas; en el issue no se identifican archivos de implementación ni pruebas.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- developer-experience
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100