Update Project Profile: HFLA Website
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 1/5
- Tiempo estimado
- Menos de una hora
- Aptitud para principiantes
- 62/100
- Tipo de issue
- Documentación
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- jekyll, markdown, yaml
- Área
- content
Línea de trabajo
El cambio pertenece al archivo de proyecto website.md bajo la carpeta _projects de la rama gh-pages, en la variable leadership. Lee cómo están formateadas las entradas de liderazgo existentes y luego añade un perfil para Jung Hwan Kim (Nathan) con el usuario de GitHub, el rol Merge Team y el ID de Slack indicados en el issue. Está terminado cuando la entrada coincide con el formato existente y aparece en la página del proyecto Website en hackforla.org/projects.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Overview
The Website project team needs its project leadership variable information updated, so that the current team members can be properly displayed on the Hack for LA website.
Action Items
- Review the Project Update Data below and then follow the instructions for either adding or deleting team members from the project's .md
Adding new volunteers to team page
- Create a new issue using the add new leader to project template
- Customize the title with name of project and person to add
- Customize the body
- In the ER, go to the value under the line "Project Card URL"
- Copy the file name
- On the line that starts "- [ ] In your IDE…" replace brackets with the copy (the text we are expecting is a file name with the extension .md)
- In the copy block below the line that starts, "Find the
leadershipvariable and add the following profile." add all the information from the ER for the person you are adding. - On the checkbox line below, "- [ ] Verify the changes by viewing..." replace with name of project
- to Resource 3, find the project on the https://www.hackforla.org/projects/ page
- click on its link
- copy link
- replace brackets on resource 3 with the URL
- In the ER, go to the value under the line "Project Card URL"
- Choose
Createbutton - Under Relationships, add this epic or ER as a parent to the issue you just created
- Add milestone
03.02 Onboarding flow - Review, and if ready, apply label
ready for merge team - At the bottom of this issue description, next to "Create sub-issue", click the drop-down menu arrow. Then, click "Add existing issue", search for the issue you just created, and select that issue to add as a sub-issue.
- Add the URL to a comment on this ER
- if this is the first add leader issue to be created, paste this into a comment and add the URL of the issue you just created.
### Adding Leader issues
-
### Complete
- [ ] Check this when all the Add leader issues have been made
- if the above comment already exists, just add your new issue URL to the list.
- Check off the box, if it's the last one that needed to be created.
Removing volunteers from team page
- Create a new issue using the remove leader from project template
- Customize the title with name of project and person to remove
- Customize the body
- In the epic, go to the value under the line "Project Card URL"
- Copy the file name
- On the line that starts "- [ ] In your IDE…" replace brackets with the copy (the text we are expecting is a file name with the extension .md)
- Go to https://github.com/hackforla/website/tree/gh-pages/_projects and find and click on the file
- click on code view
- copy the code block
- highlight the text on your new issue where it says
[Insert the lines of code to remove the specified leadership member]and delete it and replace with the copy block
- On the checkbox line below, "- [ ] Verify the changes by viewing..." replace with name of project
- to Resource 2, find the project on the https://www.hackforla.org/projects/ page
- click on its link
- copy link
- replace brackets on resource 2 with the URL
- In the epic, go to the value under the line "Project Card URL"
- Choose
Createbutton - Under Relationships, add this epic or ER as a parent to the issue you just created
- Add milestone
Onboarding flow - Review, and if ready, apply label
ready for merge team - At the bottom of this issue description, next to "Create sub-issue", click the drop-down menu arrow. Then, click "Add existing issue", search for the issue you just created, and select that issue to add as a sub-issue.
- Add the URL to a comment on this ER
- if this is the first remove leader issue to be created, paste this into a comment on this issue and add the URL of the issue you just created.
### Removing Leader issues
-
### Complete
- [ ] Check this when all the removal issues have been made
- if the above comment already exists, just add your new issue URL to the list.
- Check off the box, if it's the last one that needed to be created.
- When you have completed making all the add and remove issues
- move this issue into the Questions/Review column
- add the
ready for merge teamlabel
For Merge Team Members
- Check each sub-issue created for this ER/epic
- For each sub-issue that is ready, apply a
ready for prioritizationlabel
- For each sub-issue that is ready, apply a
- If all sub-issues have been created so that the request in this ER/epic has been fulfilled, apply a
ready for productlabel to this ER/epic
Project Update Data
Project Name
Hackforla.org Website
Project Card URL
website.md
Add person(s) and info to Leadership?
YES
If YES on add person(s), edit the below to provide the information required. If NO, delete the template in the field below:
Name: Jung Hwan Kim (Nathan)
GitHub Handle: nathanjkim-codes
Role: Merge Team
Slack Member ID: U0AUUE6NSJV
Project Status
Active
- Lenguaje dominante
- JavaScript
- Estrellas
- 365
- Forks
- 872
- Merge medio
- 8 d 19 h
- PR fusionados (30 d)
- 2
Preparar el entorno
- Incluye un Dockerfile o un 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 hackforla/website
-
Complexity: Small ER Feature: Refactor GHA Issue Making: Level 2 ready for merge team role: back end/devOps size: 0.25pt
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
hackforla/website#8871 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Complexity: Small ER Feature: Refactor GHA Issue Making: Level 2 ready for merge team role: back end/devOps size: 0.25pt
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
hackforla/website#8870 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Complexity: Small P-Feature: Project Info and Page ready for merge team role: back end/devOps role: front end size: 0.25pt time sensitive
Dificultad 1/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
Complexity: Small ER Feature: Refactor CSS Issue Making: Level 2 P-Feature: Projects page ready for merge team role: front end size: 0.25pt
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
hackforla/website#8860 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
Todos los issues de hackforla/website
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
documentation
Dificultad 1/5 1-3 horas Aptitud para principiantes 85/100
githubnext/gh-aw-workshop#5752 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
Add: QudsunaTV.psAbiertochannels:add check:passed
Dificultad 1/5 Menos de una hora Aptitud para principiantes 66/100
iptv-org/database#39416 · 2 comentarios ·
Los mantenedores suelen responder en 2 días
-
[TEXT] Flache Karte ist 2DAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
swisstopo/topo-swisseobrowser#48 ·
Los mantenedores suelen responder en 1 día