---
# System prepended metadata

title: NIST DevOps Community of Interest 20221129

---

# NIST DevOps Community of Interest 20221129

**NOTE**: This is a snapshot in time copy. These meeting notes and follow-on work, per agreement in this meeting, can be found in the commit in the NIST Gitlab repo below.

https://gitlab.nist.gov/gitlab/devops-coi/awesome-devops/-/merge_requests/2

https://gitlab.nist.gov/gitlab/devops-coi/awesome-devops/-/commit/e856b4882eeb2180edb85645cb1f6d03040e6173

## Agenda

1. Is this worth doing again? If so, how often do we want to gather and how?
2. Let's get to know each other: what have you done at NIST and/or elsewhere thanks to good DevOps practice?
3. What works about DevOps practice at NIST?
4. What doesn't work about DevOps practice at NIST?
5. How can we as a group make DevOps practice and culture at NIST better?
6. With synchronous meetings or async discussions, how can we keep the ideas and conversations going? Email/Slack/Teams?

## 1. Are COI meetings worth it?

Many were interested in continuing interactions and knowledge sharing.

## 2. Get to know each other!

All attendees introduced themselves, their ongoing work and how they applied DevOps practices, and interests for future collaboration.

## 3. What works about DevOps NIST?

Deferred for a future meeting, many achievements were presented as workarounds or solutions to what is not working well with DevOps in NIST.

## 4. What doesn't work about DevOps at NIST?

- GitHub Actions and GitLab runners is often a problem.
  - Lots of feedback about frustrations with Gitlab runners: stability, consistency, etc.
  - Some people have solutions, maybe they are willing to share!
- The constraints and limitations of how AWS accounts are provisioned and provided to NIST technical staff.
- JIRA migration is unclear, especially how it is integrated with code repository services.

## 5. What can we do better through DevOps at NIST?

Deferred for a future meeting, almost everyone summarized long-term intent or short-term gains from practices and tools they developed or are currently developing.

## 6. How can we communicate/share after this?

All attendees agreed lowest common denominator is good: we should use [the NIST Gitlab instance available all staff](https://gitlab.nist.gov/) for code, docs, and knowledge sharing. Ad-hoc async communication should occur via Teams.
