# Beman Infra

**URL:** https://discourse.bemanproject.org/c/beman-infra/11.md

[Latest](https://discourse.bemanproject.org/latest.md) · [Categories](https://discourse.bemanproject.org/categories.md) · [Tags](https://discourse.bemanproject.org/tags.md)

---

## [About the Beman Infra category](https://discourse.bemanproject.org/t/about-the-beman-infra-category/443)

<div class="topic-metadata">

**Author:** [@Jeff-Garland](https://discourse.bemanproject.org/u/Jeff-Garland)\
**Replies:** 0\
**Last updated:** [June 15, 2025, 6:29am UTC](https://discourse.bemanproject.org/t/about-the-beman-infra-category/443 "2025-06-15T06:29:01Z")

</div>

This category is devoted to infrastructure related development discussions

---

## [Beman-tidy - Allowing pre-wg21.link links](https://discourse.bemanproject.org/t/beman-tidy-allowing-pre-wg21-link-links/595)

<div class="topic-metadata">

**Author:** [@TedLyngmo](https://discourse.bemanproject.org/u/TedLyngmo)\
**Replies:** 3\
**Last updated:** [July 16, 2026, 12:28am UTC](https://discourse.bemanproject.org/t/beman-tidy-allowing-pre-wg21-link-links/595 "2026-07-16T00:28:00Z")

</div>

I wrote \[readme.implements\] requires a \`wg21.link\` · Issue #327 · bemanproject/beman-tidy · GitHub about this last weak. The current pre commit hook prevents us from linking to revisions of papers that have not gotten a …

---

## [Dealing with breaking infra changes](https://discourse.bemanproject.org/t/dealing-with-breaking-infra-changes/578)

<div class="topic-metadata">

**Author:** [@TedLyngmo](https://discourse.bemanproject.org/u/TedLyngmo)\
**Replies:** 1\
**Last updated:** [April 27, 2026, 3:14pm UTC](https://discourse.bemanproject.org/t/dealing-with-breaking-infra-changes/578 "2026-04-27T15:14:41Z")

</div>

It’s hard for me to know if I need to act on changes that breaks CI that are submitted to GitHub - bemanproject/timed\_lock\_alg: Timed lock algorithms for multiple lockables (P3832) and std::multi\_lock (P3833) · GitHub wh…

---

## [Possible source for boilerplate github actions:](https://discourse.bemanproject.org/t/possible-source-for-boilerplate-github-actions/535)

<div class="topic-metadata">

**Author:** [@Sdowney](https://discourse.bemanproject.org/u/Sdowney)\
**Replies:** 5\
**Last updated:** [January 31, 2026, 12:52am UTC](https://discourse.bemanproject.org/t/possible-source-for-boilerplate-github-actions/535 "2026-01-31T00:52:22Z")

</div>

Bloomberg just put this out on our public github for use by our teams publishing open source, and it includes, apparently, a bunch of housekeeping actions. It was generated from GitHub - cisco-ospo/oss-template: Open …

---

## [MSVC compiler flags incorrect in CI?](https://discourse.bemanproject.org/t/msvc-compiler-flags-incorrect-in-ci/550)

<div class="topic-metadata">

**Author:** [@Jeff-Garland](https://discourse.bemanproject.org/u/Jeff-Garland)\
**Replies:** 1\
**Last updated:** [December 26, 2025, 12:22am UTC](https://discourse.bemanproject.org/t/msvc-compiler-flags-incorrect-in-ci/550 "2025-12-26T00:22:59Z")

</div>

C:\\PROGRA~1\\MICROS~2\\2022\\ENTERP~1\\VC\\Tools\\MSVC\\1444~1.352\\bin\\Hostx64\\x64\\cl.exe /nologo /TP -ID:\\a\\take\_before\\take\_before\\include /DWIN32 /D\_WINDOWS /EHsc /EHsc /permissive- /fsanitize=address /Zi /Zi /Ob0 /Od /RTC1…

---

## [We’ll start implementing "Remove MIT as a supported license"](https://discourse.bemanproject.org/t/we-ll-start-implementing-remove-mit-as-a-supported-license/548)

<div class="topic-metadata">

**Author:** [@neatudarius](https://discourse.bemanproject.org/u/neatudarius)\
**Replies:** 0\
**Last updated:** [December 19, 2025, 3:54pm UTC](https://discourse.bemanproject.org/t/we-ll-start-implementing-remove-mit-as-a-supported-license/548 "2025-12-19T15:54:46Z")

</div>

Hey, We’ll start implementing \[Remove MIT as a supported license\](https://github.com/bemanproject/beman-tidy/issues/211). @pysojic (https://github.com/pysojic) will help me! Darius

---

## [How to handle infra status checks after pre-commit autoupdate?](https://discourse.bemanproject.org/t/how-to-handle-infra-status-checks-after-pre-commit-autoupdate/541)

<div class="topic-metadata">

**Author:** [@ClausKlein](https://discourse.bemanproject.org/u/ClausKlein)\
**Replies:** 5\
**Last updated:** [December 8, 2025, 3:22pm UTC](https://discourse.bemanproject.org/t/how-to-handle-infra-status-checks-after-pre-commit-autoupdate/541 "2025-12-08T15:22:15Z")

</div>

After pre-commit autoupdate, files from infra may be new formatted. What is to do now? see Feat: apply precommit autoupdate by ClausKlein · Pull Request #1 · ClausKlein/scope · GitHub

---

## [Why not share more files via infra submodule?](https://discourse.bemanproject.org/t/why-not-share-more-files-via-infra-submodule/536)

<div class="topic-metadata">

**Author:** [@ClausKlein](https://discourse.bemanproject.org/u/ClausKlein)\
**Replies:** 6\
**Last updated:** [December 3, 2025, 1:23pm UTC](https://discourse.bemanproject.org/t/why-not-share-more-files-via-infra-submodule/536 "2025-12-03T13:23:08Z")

</div>

Would it not better to share the gitlab/workflow files and the CMakePrests files for the projects via the infra repo too?

---

## [Use this template + Cookiecutter](https://discourse.bemanproject.org/t/use-this-template-cookiecutter/520)

<div class="topic-metadata">

**Author:** [@Jason5480](https://discourse.bemanproject.org/u/Jason5480)\
**Replies:** 2\
**Last updated:** [August 15, 2025, 12:07pm UTC](https://discourse.bemanproject.org/t/use-this-template-cookiecutter/520 "2025-08-15T12:07:37Z")

</div>

I was looking how other template github projects function and here a template-janitor job is triggered to replace the placeholder variables after the user clicks on “Create a new repository” from the “Use this template” …

---

## [Why do we think we need to release beman-tidy as a Python package?](https://discourse.bemanproject.org/t/why-do-we-think-we-need-to-release-beman-tidy-as-a-python-package/511)

<div class="topic-metadata">

**Author:** [@neatudarius](https://discourse.bemanproject.org/u/neatudarius)\
**Replies:** 3\
**Last updated:** [August 11, 2025, 4:08pm UTC](https://discourse.bemanproject.org/t/why-do-we-think-we-need-to-release-beman-tidy-as-a-python-package/511 "2025-08-11T16:08:05Z")

</div>

Why do we think we need to release beman-tidy as a Python package? It was suggested we can release beman-tidy 1.0 as a Python package. We already have uv support to build and install the tool. Approaches: v1: We don’t…

---

## [Can someone explain the magic CI is using to get lowest compiler versions?](https://discourse.bemanproject.org/t/can-someone-explain-the-magic-ci-is-using-to-get-lowest-compiler-versions/463)

<div class="topic-metadata">

**Author:** [@Jeff-Garland](https://discourse.bemanproject.org/u/Jeff-Garland)\
**Replies:** 6\
**Last updated:** [July 13, 2025, 3:33pm UTC](https://discourse.bemanproject.org/t/can-someone-explain-the-magic-ci-is-using-to-get-lowest-compiler-versions/463 "2025-07-13T15:33:43Z")

</div>

So over in this PR I’m trying to scope down the compiler set bc the library needs c++23 – which means gcc12, gcc13, and llvm17 are out. I thought I’d removed all the ci hooks that would be picking that up, but it’s st…

---

## [Containers for GitHub CI actions](https://discourse.bemanproject.org/t/containers-for-github-ci-actions/453)

<div class="topic-metadata">

**Author:** [@mkretz](https://discourse.bemanproject.org/u/mkretz)\
**Replies:** 8\
**Last updated:** [July 5, 2025, 9:53pm UTC](https://discourse.bemanproject.org/t/containers-for-github-ci-actions/453 "2025-07-05T21:53:42Z")

</div>

CI on bleeding-edge compilers was mentioned in the Beman evening session. I have solved that problem for myself and I am very happy with how it turned out. I’m happy to collaborate / migrate if this is a fit for Beman. S…

---

## [Considering spack for platform management](https://discourse.bemanproject.org/t/considering-spack-for-platform-management/448)

<div class="topic-metadata">

**Author:** [@Jeff-Garland](https://discourse.bemanproject.org/u/Jeff-Garland)\
**Replies:** 2\
**Last updated:** [June 18, 2025, 4:58pm UTC](https://discourse.bemanproject.org/t/considering-spack-for-platform-management/448 "2025-06-18T16:58:24Z")

</div>

In late night conversation last night Darius and I were made aware of this tool which some national labs are using to deal the platform configuration issue: The tooling has a ‘simple’ json config file for establishing…

---

## [CForge: New Dev Tool to Investigate](https://discourse.bemanproject.org/t/cforge-new-dev-tool-to-investigate/385)

<div class="topic-metadata">

**Author:** [@bretbrownjr](https://discourse.bemanproject.org/u/bretbrownjr)\
**Replies:** 2\
**Last updated:** [March 31, 2025, 12:51pm UTC](https://discourse.bemanproject.org/t/cforge-new-dev-tool-to-investigate/385 "2025-03-31T12:51:46Z")

</div>

It seems to be a meta build system, written in Rust built from cargo. It has an interesting feature list that looks like it could simplify Beman project workflows if it proves to be useful and popular for our community…