Exemplar-ify utf_view

Author: ednolan

.devcontainer/devcontainer.json

@@ -0,0 +1,16 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+// README at: https://github.com/devcontainers/templates/tree/main/src/cpp
+
+{
+	"name": "Beman Project Generic Devcontainer",
+	"image": "ghcr.io/bemanproject/infra-containers-devcontainer-gcc:14",
+	"postCreateCommand": "pre-commit",
+	"customizations": {
+		"vscode": {
+			"extensions": [
+				"ms-vscode.cpptools",
+				"ms-vscode.cmake-tools"
+			]
+		}
+	}
+}

.gitattributes

@@ -0,0 +1,4 @@
+infra/** linguist-vendored
+*.bib -linguist-detectable
+*.tex -linguist-detectable
+papers/* linguist-documentation

.github/CODEOWNERS

@@ -1,5 +1,3 @@
 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-# Codeowners for reviews on PRs
 
 *  @ednolan @camio
-

.github/ISSUE_TEMPLATE/implementation-deficiency.md

@@ -0,0 +1,35 @@
+---
+name: Implementation Deficiency
+about: Report a bug or performance issue of our implementation
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+<!--
+Please follow our code of conduct when engaging in the Beman community:
+https://github.com/bemanproject/beman/blob/main/docs/CODE_OF_CONDUCT.md
+-->
+
+## Describe the deficiency
+
+A clear and concise description of what the deficiency is.
+Link all relevant issues.
+This could be a bug, or a performance problem.
+
+## To Reproduce
+
+```c++
+// Use case
+```
+
+## Expected Behavior
+
+A clear and concise description of what you expected to happen.
+
+## Additional Discussions
+
+Add any other context about the problem here.
+If you believe your issue is platform dependent,
+please post your compiler versions here.

.github/ISSUE_TEMPLATE/infrastructure-issues.md

@@ -0,0 +1,29 @@
+---
+name: Infrastructure Issues
+about: Report a bug or feature request with our Infrastructure
+title: ''
+labels: infra
+assignees: ''
+
+---
+
+<!--
+Please follow our code of conduct when engaging in the Beman community:
+https://github.com/bemanproject/beman/blob/main/docs/CODE_OF_CONDUCT.md
+-->
+
+## I am attempting to
+
+Describe what you were attempting to do.
+
+## Expected Behavior
+
+A clear and concise description of what you expected to happen.
+
+## Current Behavior
+
+A clear and concise description of what actually happened.
+
+## Additional Discussions
+
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/paper-discussion.md

@@ -0,0 +1,33 @@
+---
+name: Paper Discussion
+about: Provide feedback to current API
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!--
+Please follow our code of conduct when engaging in the Beman community:
+https://github.com/bemanproject/beman/blob/main/docs/CODE_OF_CONDUCT.md
+-->
+
+## Use case
+
+Describe your concerns about adding this change to the C++ Standard Library.
+
+```c++
+// example snippet
+```
+
+## What I like
+
+Let us know what you find positive about current approach / design.
+
+## What I dislike
+
+Let us know what you find negative about current approach / design.
+
+## Discussion
+
+Let us know if you have any more remarks.

.github/pull_request_template.md

@@ -0,0 +1,71 @@
+<!--
+Please follow our code of conduct when engaging in the Beman community:
+https://github.com/bemanproject/beman/blob/main/docs/CODE_OF_CONDUCT.md
+-->
+
+<!--
+Thank you for your contribution!
+
+If you are updating project structure or build configs:
+- Make sure your contribution conforms to the Beman Standard:
+  https://github.com/bemanproject/beman/blob/main/docs/BEMAN_STANDARD.md
+- For new CMake arguments / presets: please make sure you added appropriate CI tests.
+
+If you are updating documentation:
+- Make sure badges and pictures does not impact readability.
+
+If you are updating implementations:
+- Make sure you submit appropriate testing.
+
+We encourage small and incremental additions instead of large redesigns.
+They are easier and faster to review.
+They are also less likely to introduce bugs.
+
+While we do not formally adopt this guide as a standard,
+we encourage you to read and consider:
+"The CL author’s guide to getting through code review".
+https://google.github.io/eng-practices/review/developer/
+
+Regardless, feel free to open a PR on your existing changes.
+We appreciate the suggestion and will help out.
+
+Please run pre-commit against your change to comply with our linting rules.
+The command to check all files in the directory is:
+$ pre-commit run --all-files
+-->
+
+<!-- markdownlint-disable-next-line MD041 -->
+## Description
+
+Please describe your contribution in a single sentence.
+
+## Related Issues
+
+<!-- use magic keywords like "fix" to close issues linked to this PR automatically -->
+
+## Motivation and Context
+
+Explain why this change is needed.
+
+## Testing
+
+Explain how is this tested.
+
+## Meta
+
+<!--
+The convention in Beman is for the PR author to merge the PR once it's ready.
+You can check this box to indicate that you would like Beman members to merge the PR
+for you when appropriate reviews have passed.
+
+Please note that:
+1. Stale PR may still be merged by a Beman member,
+if you need significant time to work on your PR,
+leave a comment and change it's status to draft.
+2. If you are not a member of the Beman project,
+you may not have the permission necessary to merge your own PR.
+-->
+
+- [ ] If all approvals are obtained and the PR is green, any Beman member can merge the PR.
+
+<!-- make sure you run pre-commit before opening a PR -->

.github/workflows/.beman_submodule

@@ -0,0 +1,4 @@
+[beman_submodule]
+remote=https://github.com/bemanproject/infra-workflows.git
+commit_hash=d03a513d25e1251b968988bd4b28a03a220a8c5f
+allow_untracked_files=True

.github/workflows/.github/CODEOWNERS

@@ -0,0 +1 @@
+* @ednolan