Update Project Profile: HackforLA Website
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 2/5
- 見積もり時間
- 1時間未満
- 初心者へのやさしさ
- 65/100
- issue の種類
- ドキュメント
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- jekyll
- 領域
- content
調査の方向性
変更は、"Project Card URL" で指定されたプロジェクトファイル website.md に加えます。このファイルは gh-pages ブランチの _projects フォルダにあります。ファイルを開き、既存のエントリを読んで leadership 変数内の形式を確認したうえで、Meghan OConnell のプロフィール(ハンドル meghan-oconnell、役割 Merge Team、Slack ID U0A6HT024Q7)を追加してください。エントリがファイルに含まれ、プロジェクトページに彼女が一覧表示される状態になれば完了です。
索引モデルが issue の本文から書いたものです。
説明
Overview
The HfLA 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: Meghan OConnell
GitHub Handle: meghan-oconnell
Role: Merge Team
Slack Member ID: U0A6HT024Q7
Project Status
Active
- 主要言語
- JavaScript
- スター
- 364
- フォーク
- 874
- 平均マージ
- 3日 7時間
- マージ済み PR(30日)
- 13
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
hackforla/website のほかの issue
-
good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
難易度 1/5 1時間未満 初心者へのやさしさ 84/100
メンテナーはふだん 1 日以内に返信
-
good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
難易度 1/5 1時間未満 初心者へのやさしさ 84/100
メンテナーはふだん 1 日以内に返信
-
good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt time sensitive
難易度 1/5 1〜3時間 初心者へのやさしさ 90/100
メンテナーはふだん 1 日以内に返信
-
Feature: Code Alerts good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
難易度 1/5 1時間未満 初心者へのやさしさ 90/100
hackforla/website#8825 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
Feature: Code Alerts good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
難易度 1/5 1〜3時間 初心者へのやさしさ 88/100
メンテナーはふだん 1 日以内に返信
hackforla/website の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
apache/rocketmq-dashboard#6896 ·
メンテナーはふだん 3 日以内に返信
-
bug engine
難易度 2/5 1〜3時間 初心者へのやさしさ 86/100
frostney/GocciaScript#1746 ·
メンテナーはふだん 1 日以内に返信
-
enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
メンテナーはふだん 1 日以内に返信
-
enhancement good first issue
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
SasanLabs/VulnerableApp#836 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
keyxmakerx/Chronicle#1469 ·
メンテナーはふだん 1 日以内に返信