initial release (#1)

.editorconfig

@@ -0,0 +1,12 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.{md,mdx}]
+trim_trailing_whitespace = false

.eslintrc.js

@@ -0,0 +1,34 @@
+module.exports = {
+  root: true,
+  parser: '@typescript-eslint/parser',
+  parserOptions: {
+    tsconfigRootDir: __dirname,
+    project: ['./tsconfig.json']
+  },
+  plugins: ['simple-import-sort', '@typescript-eslint'],
+  env: {
+    jest: true
+  },
+  extends: ['eslint:recommended', 'plugin:@typescript-eslint/recommended', 'prettier'],
+  globals: {
+    customElements: true
+  },
+  rules: {
+    // Enforce consistent brace style for all control statements.
+    curly: ['error', 'all'],
+    // Require `default` cases in `switch` statements.
+    'default-case': 'error',
+    // Require the use of `===` and `!==`.
+    eqeqeq: ['error', 'smart'],
+    // Disallow duplicate module imports.
+    'no-duplicate-imports': 'warn',
+    // Disallow empty functions.
+    'no-empty-function': 'error',
+    // Disallow template literal placeholder syntax in regular strings.
+    'no-template-curly-in-string': 'warn',
+    // Disallow loops with a body that allows only one iteration.
+    'no-unreachable-loop': 'error',
+    // Enforce sorted import declarations within modules.
+    'simple-import-sort/imports': 'error'
+  }
+};

.github/ISSUE_TEMPLATE/intake-request.md

@@ -0,0 +1,26 @@
+---
+name: Stratum Intake Request
+about: Propose a change to Stratum (enhancement, bug, etc.)
+title: ''
+labels: needs triage
+assignees: ''
+
+---
+
+**What's the problem you are facing?**
+A clear and concise description of what you're looking to solve. If proposing a new feature, please outline your use case.
+
+**Describe the solution you're proposing**
+Provide a general description of your solution including expected changes and final outcome.
+
+**Additional context**
+Add any other context or screenshots about the request here.
+
+-----
+
+Note that any Stratum enhancements should add general functionality that applies to a broad range of users. If you're looking to add custom functionality to your specific application, we recommend creating or extending existing plugins when possible.
+
+**Next steps**
+- A maintainer will look over your request, and we'll help you flesh it and provide additional context/requirements as necessary.
+- We welcome contributions from the community! If you're looking to contribute to this request, open a PR and connect it to the Github issue. 
+- Once your PR is approved and merged, we will close this issue and mark it as complete.

.gitignore

@@ -0,0 +1,8 @@
+.idea
+.DS_Store
+.vscode
+.rollup.cache
+coverage
+node_modules
+dist
+temp

.husky/pre-commit

@@ -0,0 +1 @@
+npm run pre-commit

.lintstagedrc.json

@@ -0,0 +1,4 @@
+{
+  "**/*.{js,ts,json}": ["npm run prettier"],
+  "src/**/*.{js,ts}": ["npm run lint"]
+}

.npmignore

@@ -0,0 +1,2 @@
+/*
+!/dist

.nvmrc

@@ -0,0 +1 @@
+20.16.0

.prettierignore

@@ -0,0 +1,5 @@
+node_modules
+coverage
+dist
+.rollup.cache
+package-lock.json

.prettierrc.js

@@ -0,0 +1,7 @@
+module.exports = {
+  embeddedLanguageFormatting: 'off',
+  htmlWhitespaceSensitivity: 'strict',
+  printWidth: 120,
+  singleQuote: true,
+  trailingComma: 'none'
+};

CODEOWNERS

@@ -0,0 +1 @@
+* @capitalone/stratum-admin-team

CONTRIBUTING.md

@@ -0,0 +1,122 @@
+# Contributions
+We love to hear feedback from the community and encourage developers to contribute back to Stratum with bugfixes, feature requests, and new plugins whenever possible.
+
+If you are looking to contribute a new feature, we recommend first implementing it as a custom plugin if possible. If you think your plugin is useful to others, let us know! We'd love to learn more and help you make it available.
+
+## Intake
+
+In order to maintain Stratum, we require that all contributions (feature requests or bugs) go through an intake process via GitHub issues so that maintainers can evaluate the impacts of changes and provide guidance on the implementation.
+
+### Any contributions you make will be under the Apache License 2.0
+In short, when you submit code changes, your submissions are understood to be under the same [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0) that covers the project. Feel free to contact the maintainers if that's a concern.
+
+### We develop with GitHub
+We use github to host code, to track issues and feature requests, as well as accept pull requests.
+
+### Process 
+
+#### Submit a GitHub issue in the Stratum repository
+
+[Stratum GitHub issues page.](https://github.com/capitalone/Stratum-Observability/issues/new/choose) Fill out the "Stratum Intake Request" issue template for both bugs and enhancements, providing as much detail as possible for your request.
+
+#### Intake approval process
+
+Once an issue is created, a maintainer will review the issue and provide feedback.
+
+The intake approval process is relatively informal. We will
+ * Go over your request and use cases
+ * Provide any feedback, questions, technical considerations, or complications that we notice
+ * Let you know if any specific updates would be required with your changes 
+
+If we require additional information from you, we'll label the issue with *"engaged"* to indicate that it's mid-process and also add the correct request category: *"bug"*, *"enhancement"*, *"documentation"*, etc.
+
+Once we've looked over the issue, we'll label your PR as one of the following:
+* *"ready for contribution"* - your intake is approved and awaiting contributions
+* *"duplicate"* - the issue outlines a request that's already been decided on
+* *"wontfix"* - your intake is not something we plan to incorporate within Stratum. This may be because your enhancement is better suited as custom plugin instead
+
+## Local development
+
+### 1. Install dependencies
+
+```
+nvm use && npm ci
+```
+
+### 2. Build
+This command will build out the compiled code within the repository's `dist/` folder.
+
+```
+npm run build
+```
+
+#### build:watch
+
+To continuously build the application as you make changes, run
+```
+npm run build:watch
+```
+
+#### build:analyze
+
+Since Stratum is a build-time integration, bundle size is definitely one of our priorities. Run
+```
+npm run build:analyze
+```
+to get an estimate of the gzipped size of the library.
+
+#### Watching for changes
+For continuous building on changes, use the `build:watch` script instead.
+```
+npm run build:watch
+```
+
+### 3. Code quality & maintenance
+#### lint
+Run code quality checks and attempt to fix any violations. This script is automatically run as part of a pre-commit hook. You will not likely need to run this manually.
+
+```
+npm run lint
+```
+
+#### prettier
+Update code to conform to repository code style rules. This script is automatically run as part of a pre-commit hook. You will not likely need to run this manually.
+
+```
+npm run prettier
+```
+
+### 4. Unit tests
+Unit tests are run via Jest.
+
+#### test
+Run full unit test suite.
+```
+npm run test
+```
+
+#### test:coverage
+Run full unit test suite and calculate code coverage reports.
+```
+npm run test:coverage
+```
+
+## Pull requests
+
+Once you are ready to merge your changes, open PR(s) in the repository and fill out the provided template.
+
+The template will prompt you for the following information:
+* A link to the connected Stratum intake request GitHub issue (include the "Fixes" prefix so that your issue will auto-close on PR merge)
+* Testing steps so that we can test your changes locally
+* A pre-release checklist to document the scope of your changes
+
+Once your PR is submitted, all Stratum maintainers will be automatically be requested for review. PRs require at least one maintainer to approve before it can be merged.
+
+## Release process
+
+After a maintainer approves your PR, they will merge it to the base branch and handle any release activities.
+
+* Add a *"complete"* label to your intake request.
+* If your changes require a new release, we will verify that the new version is available for download and create a new release tag in GitHub crediting you!
+
+We absolutely love and welcome any and all contributions. Thanks for being a part of the community!