hackforla/devops

Epic - Standardize CoP name across org as DevOps

Open

#108 opened on Jan 31, 2024

View on GitHub
 (7 comments) (0 reactions) (0 assignees)JavaScript (9 forks)auto 404
Complexity: Smallfeature: administrativegood first issueready for CoP Leadrole: PMsize: 0.5pt

Repository metrics

Stars
 (8 stars)
PR merge metrics
 (PR metrics pending)

Description

Dependency

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.

Contributor guide

Research direction
Search for instances of 'Ops' in the repository's code and documentation files, and replace them with 'DevOps' as appropriate. Be careful to distinguish between 'Ops' as part of 'DevOps' and standalone 'Ops'.
Tech stack
None
Domain
documentationdevops
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85