Update Project Profile: HFLA Website
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 1/5
- Tempo stimato
- Meno di un'ora
- Idoneità per principianti
- 62/100
- Tipo di issue
- Documentazione
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- jekyll, markdown, yaml
- Ambito
- content
Direzione di ricerca
La modifica va nel file di progetto website.md nella cartella _projects del branch gh-pages, nella variabile leadership. Leggi come sono formattate le voci di leadership esistenti, poi aggiungi un profilo per Jung Hwan Kim (Nathan) con l'handle GitHub, il ruolo Merge Team e l'ID Slack indicati nell'issue. È completato quando la voce rispetta il formato esistente e compare nella pagina del progetto Website su hackforla.org/projects.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- Lingua principale
- JavaScript
- Stelle
- 365
- Fork
- 872
- Merge medio
- 8g 19h
- PR unite (30g)
- 2
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di hackforla/website
-
Complexity: Small ER Feature: Refactor GHA Issue Making: Level 2 ready for merge team role: back end/devOps size: 0.25pt
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
hackforla/website#8871 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Complexity: Small ER Feature: Refactor GHA Issue Making: Level 2 ready for merge team role: back end/devOps size: 0.25pt
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
hackforla/website#8870 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Complexity: Small P-Feature: Project Info and Page ready for merge team role: back end/devOps role: front end size: 0.25pt time sensitive
Difficoltà 1/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno
-
Complexity: Small ER Feature: Refactor CSS Issue Making: Level 2 P-Feature: Projects page ready for merge team role: front end size: 0.25pt
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
hackforla/website#8860 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di hackforla/website
Issue simili
-
Add: QudsunaTV.psApertachannels:add check:passed
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 66/100
iptv-org/database#39416 · 2 commenti ·
I maintainer di solito rispondono entro 2 giorni
-
[TEXT] Flache Karte ist 2DAperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
swisstopo/topo-swisseobrowser#48 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno