-
-
Notifications
You must be signed in to change notification settings - Fork 846
Open
0 / 10 of 1 issue completedOpen
0 / 10 of 1 issue completed
Copy link
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueTake this type of issues after the successful merge of your second good first issueIssue Making: Level 2Make issue(s) from an ER or EpicMake issue(s) from an ER or EpicP-Feature: Communities of Practicehttps://www.hackforla.org/communities-of-practicehttps://www.hackforla.org/communities-of-practiceReady for Prioritizationepicrole: productProduct ManagementProduct Managementsize: 0.25ptCan be done in 0.5 to 1.5 hoursCan be done in 0.5 to 1.5 hourstime sensitiveNeeds to be worked on by a particular timeframeNeeds to be worked on by a particular timeframe
Milestone
Description
Overview
The community of practice UI/UX 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 community of practice's update request below and then follow the instructions for deleting team members from the community of practice's .yml file.
Removing volunteers from a community of practice
- Create a new issue using the remove leader from community of practice issue template
- Customize the title with name of project and person to remove
- Go to https://github.com/hackforla/website/tree/gh-pages/_data/internal/communities and find the yml file for the specific community of practice and click on the file.
- Customize the body
- In the issue template, on the line that starts with "- [ ] In your IDE…" replace
[Insert filename]with the community of practice filename (the text we are expecting is a filename with the extension .yml) - In the yml file on GitHub,
- Click on
Codeview - 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 copied code block
- Click on
- In the issue template, on the line that starts with "- [ ] In your IDE…" replace
- Choose
Createbutton - Under "Relationships", add this epic 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
- Add the URL to a comment on this epic
- 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 remove issues
- move this issue into the Questions/Review column
- add the
ready for productlabel
Community of Practice Update Request
Change Leadership Type
NO
Leadership Type
N/A
Remove person(s) and info from CoP file?
YES
If YES on remove person(s) edit the below to provide the information required. If NO, delete the template in the field below:
- Name: Julia Gab
- Name: Leo Peng
Add person(s) and info to CoP file?
NO
If YES on add person(s), edit the below to provide the information required. If NO, delete the template in the field below:
Sub-issues
Metadata
Metadata
Assignees
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueTake this type of issues after the successful merge of your second good first issueIssue Making: Level 2Make issue(s) from an ER or EpicMake issue(s) from an ER or EpicP-Feature: Communities of Practicehttps://www.hackforla.org/communities-of-practicehttps://www.hackforla.org/communities-of-practiceReady for Prioritizationepicrole: productProduct ManagementProduct Managementsize: 0.25ptCan be done in 0.5 to 1.5 hoursCan be done in 0.5 to 1.5 hourstime sensitiveNeeds to be worked on by a particular timeframeNeeds to be worked on by a particular timeframe
Type
Projects
Status
Ready for Prioritization