Standardize CoP name across org as DevOps

[chelseybeck]

Overview

Currently, the DevOps Community of Practice (CoP) is referred to by both DevOps and Ops in a lot of documentation (code repo, website, and Google drive). We need to make it DevOps across the org.

Resources

Search the GitHub repo for every instance of "ops" and provide a link so that we can change it

Action Items

• [x] Create a checklist w/ links to all of the places where the name Ops is mentioned so that we can change it to DevOps

List of locations

• [x] website - both Ops and Dev-ops are listed on the CoP page
• [x] code repository
  • [x] https://github.com/hackforla/ops/blob/c15c6c96290ab0fb5069b1cd7d805a3a643b77a7/README.md#ops-community-of-practice
  • [x] https://github.com/hackforla/ops/wiki

[freaky4wrld]

Here's a checklist of instances with Ops/ops that's going to be changes to DevOps :

• [ ] DevOps Readme.md

• [ ] DevOps 2020 agenda maybe we can ignore this, or make changes if we are using it for recording history

• [ ] Issue Template onboard-ops-cop-lead.md

• [ ] Issue Template offboard-ops-cop-lead.md

• [ ] ssue Template recruit-new-lead.md

• [ ] @danielridgebot ops wiki

• [ ] Community Leads Roles wiki

• [ ] Home wiki

• [ ] Community wiki

• [ ] CoP Meetings wiki

• [ ] AWS User Management wiki

      - just noticed a spelling error `utulized` at `bullet point number 8 Note`

• [ ] CoP Page

       - the title can be changed to DevOps
       - the introductory line `This group covers all areas of dev-ops` can be changed to `This group covers all areas of DevOps`

• [ ] DevOps Drive link

[freaky4wrld]

@chelseybeck as the requirement, provided the links to where the changes are to be made....... just a suggestion we should use spellchecker-extension to avoid spelling-errors......... please review the links in the comment and suggest changes, thanks

[chelseybeck]

This is great, @freaky4wrld. Thank you! I think one more place to look is the Google Drive. We may need to change the drive name, etc.

[ExperimentsInHonesty]

We need to create new issues from this list to have two different PRs. One that can be merged that just changes working and another that changes links. The wording one, we can merge anytime, the one that changes any links to repos, will need to be held and merged directly after the URL has been change.

[ExperimentsInHonesty]

@freaky4wrld Should we unassign you from this before we decompose it?