Migrating Engineering Guides to New Repo

[JesseTheCleric]

Overview

We need to move all existing guides to the new repository for guides and templates (knowledgebase-content)

Prerequisite

You need to have

• Manager access to the following drives
  • CoP Google Drives
  • KB-content drive
• Admin access for the repos the issues are in

Action Items

Use the Guide below to migrate all guides related to Engineering from CoPs to knowledgebase-content. (e.g., there might be a research guide that is relevant to product in the Engineering community of practice).

• Do steps 1-5
• Add a comment below with the heading and add a link to each of the issues you moved for that CoP

### Guides that are ready to move for lead review
- #

• Move this issue to the Questions/Review column on project board and add the label ready for pm lead
  • Message the lead in the Guides Slack channel by sending a link to the comment with the issues
• lead will sign-off if the issues are ready to move
  • once you get sign-off, you can move the issues (step 6 in the guide)
• Check wikis/other resources for references to guides by numbers or names, so no links end up broken
• When you are done, go to Clean Up Guide Issues for Triage #174 and check off the dependency. If all other dependencies are checked off already, then move that issue into the new issue approval column and add it to the team agenda Guides: Meeting Agenda & Minutes #136

Resources/Instructions

• Epic for all CoP guides moves: CoP Templates and Guides Board Migration #169
• Repo: knowledgebase content repo
• Repo Engineering CoP Repo
  • Repo, Issue Tab: Search for guides that have not been moved to the Knowlegebase repo
    • Repo, Issue Tab, "Create a Guide" only issue Search for guides that have not been moved to the Knowlegebase repo
• Google Drive: Knowledgebase-content
• Project Board: Guides: Knowledgebase Content Tracker
• Form: Guides Migration Google Form
• Spreadsheet: New Guide Tracker (WIP)
• Guide: How to Move a Guide to a New Repo

[fchan218]

Issues that need to be checked prior to Steps 1-5 for migration into knowledgebase content repo

Check off the issues that can be migrated

• Create a Guide/Template: Using Docker knowledgebase-content#143
• Create a Guide/Template: Systems Diagram knowledgebase-content#148
• Create a Guide/Template: Engineering Interview Practice knowledgebase-content#144
• Create a Guide/Template: Documentation Technologies knowledgebase-content#145
• Create a Guide/Template: Compilation with Webpack knowledgebase-content#149
• Create a Guide/Template: Testing GitHub actions in your own repository knowledgebase-content#150
• Create a Guide/Template: Decision Records knowledgebase-content#151
• Create a Guide/Template: CI/CD with GitHub actions knowledgebase-content#152
• Create a Guide/Template: Implementing Tests with Your Code Changes knowledgebase-content#153
• Create a Guide/Template: Setting up Git knowledgebase-content#154
• Create a Guide/Template: Agile Development/Scrum/Kanban knowledgebase-content#155
• Create a Guide/Template: Professional Development knowledgebase-content#156
• Create a Guide/Template: Site Architecture Documentation knowledgebase-content#157
• Create a Guide/Template: Making a good CONTRIBUTING doc for your project's github repo knowledgebase-content#158

[ExperimentsInHonesty]

This epic has one new issue which I have moved, but it will need reformatting

• docs: How to resolve PR merge conflicts when another contributor made a previous PR knowledgebase-content#120

[JesseTheCleric]

Guides that are ready for lead review

Please check off when you have reviewed it.

• Create a Guide/Template: Engineering Interview Practice knowledgebase-content#144
• Create a Guide/Template: Documentation Technologies knowledgebase-content#145
• Create a Guide/Template: Compilation with Webpack knowledgebase-content#149
• Create a Guide/Template: Testing GitHub actions in your own repository knowledgebase-content#150
• Create a Guide/Template: Decision Records knowledgebase-content#151

[ExperimentsInHonesty]

@JesseTheCleric You have not added any other issues that you have reviewed. Please finish doing the steps for the rest of the issues by Friday.

[JesseTheCleric]

Guides that are ready for lead review

Please check off when you have reviewed it.

• Create a Guide/Template: CI/CD with GitHub actions knowledgebase-content#152
• Create a Guide/Template: Implementing Tests with Your Code Changes knowledgebase-content#153
• Create a Guide/Template: Setting up Git knowledgebase-content#154
• Create a Guide/Template: Agile Development/Scrum/Kanban knowledgebase-content#155
• Create a Guide/Template: Professional Development knowledgebase-content#156

[fchan218]

@JesseTheCleric

Guides that are ready for lead review

Please check off when you have reviewed it.

• Create a Guide/Template: CI/CD with GitHub actions engineering#25[ ] Create a Guide/Template: Implementing Tests with Your Code Changes engineering#19[x] Create a Guide/Template: Setting up Git engineering#16[ ] Create a Guide/Template: Agile Development/Scrum/Kanban engineering#15[x] Create a Guide/Template: Professional Development engineering#14

I've reviewed all 5. 3/5 are ready to move. Please check the comments for the 2 unchecked ones

[JesseTheCleric]

Guides that are ready for lead review

Please check off when you have reviewed it.

• Create a Guide/Template: Site Architecture Documentation knowledgebase-content#157
• Create a Guide/Template: Making a good CONTRIBUTING doc for your project's github repo knowledgebase-content#158

[JesseTheCleric]

1. Progress: Steps 1-5 Complete on 13/13, All 11 Steps complete on 2/13
2. Blockers: None
3. Availability: 4 Hours
4. ETA: 02-21-25
5. Pictures or links : New Guide Tracker (WIP)

[ExperimentsInHonesty]

@Aditya23soni It's been a week since you were assigned.

I spoke to France, and she indicated that the 11 issues should take about 30 min apiece to move, which would be 5.5 hours. Given that your commitment is 20 hours a week, this work should have been turned in already so that she could give you feedback, and you could fix anything needing to be fixed, in time for her to check it again before the next meeting. She has not heard from you, other than letting us know that you wouldn't make the meeting last week.

Please provide update on this issue.

Instructions

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

1. Progress:
2. Blockers:
3. Availability:
4. ETA:
5. Pictures (if necessary):

[Aditya23soni]

@ExperimentsInHonesty Hello Bonnie. I shall provide the updates for the issues to France today. I am working on those right now, as last week was a little occupied with the festival and travelling.
Apologies for the delay.

[Aditya23soni]

Issues that I migrated to KB @fchan218 @ExperimentsInHonesty
The issues that are checked off have been migrated with all 13 steps completed.

• Create a Guide/Template: Systems Diagram knowledgebase-content#148
• Create a Guide/Template: Compilation with Webpack knowledgebase-content#149
• Create a Guide/Template: Testing GitHub actions in your own repository knowledgebase-content#150
• Create a Guide/Template: Decision Records knowledgebase-content#151
• Create a Guide/Template: CI/CD with GitHub actions knowledgebase-content#152
• Create a Guide/Template: Implementing Tests with Your Code Changes knowledgebase-content#153
• Create a Guide/Template: Setting up Git knowledgebase-content#154
• Create a Guide/Template: Agile Development/Scrum/Kanban knowledgebase-content#155
• Create a Guide/Template: Professional Development knowledgebase-content#156
• Create a Guide/Template: Site Architecture Documentation knowledgebase-content#157
• Create a Guide/Template: Making a good CONTRIBUTING doc for your project's github repo knowledgebase-content#158

[Aditya23soni]

@ExperimentsInHonesty

1. Progress: Finished migrating 11/11 Guide issues to KB. All 13 Steps done
2. Blockers: Step 9 is not functional. I am unable to assign the issues to the KB Project Board
3. Availability: 20 hrs
4. ETA: 1 DAY
5. Pictures (if necessary):

[fchan218]

@Aditya23soni I am unable to add the issues to the KB Tracker Project Board also. We will discuss with Bonnie during our meeting on Friday. I have checked all the issues. One needs to be addressed: hackforla/knowledgebase-content#155 (comment)

[Aditya23soni]

@fchan218 This has been addressed.

[ExperimentsInHonesty]

@Aditya23soni I am unable to see what specifically you have completed on this issue, and what remains, because none of the check boxes at the top of this issue are checked off. Please update the top of the issue as well as giving a status report in a comment.

[Aditya23soni]

@ExperimentsInHonesty I have moved all 11 Engineering Guides Issues to KB Repo mentioned in the comment #179 (comment)
@fchan218 have validated the same.

[ExperimentsInHonesty]

@Aditya23soni please check off the checkboxes for the items that are done in the top

[Aditya23soni]

@ExperimentsInHonesty Done. And I have cleaned up the comments as well