From f59d20fa91d787af6ff06737324cedc3627941a3 Mon Sep 17 00:00:00 2001 From: Julia Pampus <72392527+juliapampus@users.noreply.github.com> Date: Thu, 25 Aug 2022 13:53:10 +0200 Subject: [PATCH 1/4] docs: remove contribution files and link to main repository --- .github/PULL_REQUEST_TEMPLATE.md | 2 +- CODEOWNERS | 3 - CONTRIBUTING.md | 212 ------------------------------- README.md | 6 +- pr_etiquette.md | 62 --------- styleguide.md | 63 --------- 6 files changed, 6 insertions(+), 342 deletions(-) delete mode 100644 CONTRIBUTING.md delete mode 100644 pr_etiquette.md delete mode 100644 styleguide.md diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 586111cf2..a317d8f2a 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -23,4 +23,4 @@ Closes # <-- _insert Issue number if one exists_ - [ ] documented public classes/methods? - [ ] added/updated relevant documentation? - [ ] added relevant details to the changelog? (_skip with label `no-changelog`_) -- [ ] formatted title correctly? (_take a look at the [CONTRIBUTING](https://github.com/eclipse-dataspaceconnector/identityservice/blob/main/CONTRIBUTING.md#submit-a-pull-request) and [styleguide](https://github.com/eclipse-dataspaceconnector/identityservice/blob/main/styleguide.md) for details_) +- [ ] formatted title correctly? (_take a look at the [CONTRIBUTING](https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/blob/main/CONTRIBUTING.md#submit-a-pull-request) and [styleguide](https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/blob/main/styleguide.md) for details_) diff --git a/CODEOWNERS b/CODEOWNERS index 4112fe3bf..6e03a0ecd 100644 --- a/CODEOWNERS +++ b/CODEOWNERS @@ -8,10 +8,7 @@ # The linked persons are automatically added as reviewers when a pull request is opened. -CONTRIBUTING.md @paullatzelsperger LICENSE @paullatzelsperger -pr_etiquette.md @paullatzelsperger -styleguide.md @paullatzelsperger .github/actions/ @paullatzelsperger .github/ISSUE_TEMPLATE @paullatzelsperger diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index 230a620da..000000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,212 +0,0 @@ -Contributing to the Project -=================================== - -Thank you for your interest in contributing to -the [Eclipse Dataspace Connector](https://projects.eclipse.org/projects/technology.dataspaceconnector)! - -## Table of Contents - -- [Contributing to the Project](#contributing-to-the-project) - - [Table of Contents](#table-of-contents) - - [Project Description](#project-description) - - [Code Of Conduct](#code-of-conduct) - - [Eclipse Contributor Agreement](#eclipse-contributor-agreement) - - [How to Contribute](#how-to-contribute) - - [Discuss](#discuss) - - [Create an Issue](#create-an-issue) - - [Adhere to Coding Style Guide](#adhere-to-coding-style-guide) - - [Submit a Pull Request](#submit-a-pull-request) - - [Stale issues and PRs](#stale-issues-and-prs) - - [Add Documentation](#add-documentation) - - [Report on Flaky Tests](#report-on-flaky-tests) - - [Pull Requests](#pull-requests) - - [Projects](#projects) - - [Contact Us](#contact-us) - -## Project Description - -See [README.md](README.md) for a comprehensive project description. - -## Code Of Conduct - -See the [Eclipse Code Of Conduct](https://www.eclipse.org/org/documents/Community_Code_of_Conduct.php). - -## Eclipse Contributor Agreement - -Before your contribution can be accepted by the project, you need to create and electronically sign -a [Eclipse Contributor Agreement (ECA)](http://www.eclipse.org/legal/ecafaq.php): - -1. Log in to the [Eclipse foundation website](https://accounts.eclipse.org/user/login/). You will - need to create an account within the Eclipse Foundation if you have not already done so. -2. Click on "Eclipse ECA", and complete the form. - -Be sure to use the same email address in your Eclipse Account that you intend to use when you commit -to GitHub. - -## How to Contribute - -### Discuss - -If you want to share an idea to further enhance -the project or discuss potential use cases, please feel free to create a discussion at the -[GitHub Discussions page](https://github.com/eclipse-dataspaceconnector/IdentityHub/discussions). -If you feel there is a bug or an issue, contribute to the discussions in -[existing issues](https://github.com/eclipse-dataspaceconnector/IdentityHub/issues?q=is%3Aissue+is%3Aopen), -otherwise [create a new issue](#create-an-issue). - -### Create an Issue - -If you have identified a bug or want to formulate a working item that you want to concentrate on, -feel free to create a new issue at our project's corresponding -[GitHub Issues page](https://github.com/eclipse-dataspaceconnector/IdentityHub/issues/new). - -Before doing so, please consider searching for potentially suitable -[existing issues](https://github.com/eclipse-dataspaceconnector/IdentityHub/issues?q=is%3Aissue+is%3Aopen). - -We also use [GitHub's default label set](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels) -extended by custom ones to classify issues and improve findability. - -If an issue appears to cover changes that will have a (huge) impact on the code base and needs to -first be discussed, or if you just have a question regarding the usage of the software, please -create a [discussion](https://github.com/eclipse-dataspaceconnector/IdentityHub/discussions) -before raising an issue. - -Please note that if an issue covers a topic or the response to a question that may be interesting -for other developers or contributors, or for further discussions, it should be converted to a -discussion and not be closed. - -### Adhere to Coding Style Guide - -We aim for a coherent and consistent code base, thus the coding style detailed in the -[styleguide](styleguide.md) should be followed. - -### Submit a Pull Request - -In addition to the contribution guideline made available in the -[Eclipse project handbook](https://www.eclipse.org/projects/handbook/#contributing), -we would appreciate if your pull request applies to the following points: - -* Conform to [Pull-Request Etiquette](pr_etiquette.md) - -* Always apply the following copyright header to specific files in your work replacing the fields - enclosed by curly brackets "{}" with your own identifying information. (Don't include the curly - brackets!) Enclose the text in the appropriate comment syntax for the file format. - - ```text - Copyright (c) {year} {owner}[ and others] - - This program and the accompanying materials are made available under the - terms of the Apache License, Version 2.0 which is available at - https://www.apache.org/licenses/LICENSE-2.0 - - SPDX-License-Identifier: Apache-2.0 - - Contributors: - {name} - {description} - ``` - -* The git commit messages should comply to the following format: - ``` - : - ``` - - Use the [imperative mood](https://github.com/git/git/blob/master/Documentation/SubmittingPatches) - as in "Fix bug" or "Add feature" rather than "Fixed bug" or "Added feature" and - [mention the GitHub issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) - e.g. `transfer process: improve logging, closes #3`. - - All committers, and all commits, are bound to - the [Developer Certificate of Origin.](https://www.eclipse.org/legal/DCO.php) - As such, all parties involved in a contribution must have valid ECAs. Additionally, commits can - include a ["Signed-off-by" entry](https://wiki.eclipse.org/Development_Resources/Contributing_via_Git). - -* Add meaningful tests to verify your submission acts as expected. - -* Where code is not self-explanatory, add documentation providing extra clarification. - -* Add documentation files to new modules. See [here](#add-documentation) for more details. - -* Add relevant changes (e.g., no typo fixes, updated readme files, fixes of stuck test) to the - [changelog](CHANGELOG.md). If these refer to a new feature, add this to the `Overview` section - and add your changes to the `Detailed Changes` section according to the rules documented on - . Include more information via linking to existing pull requests, - issues, or discussions. - -* If a new module has been added or a significant part of the code has been changed and you should - or want to be seen as the contact person for any further changes, please add appropriate - information to the [CODEOWNERS](https://github.com/eclipse-dataspaceconnector/IdentityHub/blob/main/CODEOWNERS) - file. You can find instructions on how to do this at . - Please note that this file does not represent all contributions to the code. What persons and organizations - actually contributed to each file can be seen on GitHub and is documented in the license headers. - -* PR descriptions should use the current [PR template](.github/PULL_REQUEST_TEMPLATE.md) - -* Submit a draft pull request at early-stage and add people previously working on the same code as - reviewer. Make sure automatic checks pass before marking it as "ready for review": - - * _Intellectual Property Validation_ verifying the [Eclipse CLA](#eclipse-contributor-agreement) - has been signed as well as commits have been signed-off and - * _Continuous Integration_ performing various test conventions. - -### Stale issues and PRs - -In order to keep our backlog clean we are using a bot that helps us label and eventually close old issues and PRs. The -following table shows the particular timings. - -| | `stale` after | closed after days `stale` | -|------------------------|---------------|---------------------------| -| Issue without assignee | 14 | 7 | -| Issue with assignee | 28 | 7 | -| PR | 7 | 7 | - -Note that updating an issue, e.g. by commenting, will remove the `stale` label again and reset the counters. However, -we ask the community **not to abuse** this feature (e.g. commenting "what's the status?" every X days would certainly -be qualified as abuse). If an issue receives no attention, there usually -are reasons for it. It is therefore advisable to clarify in advance whether any particular feature fits into EDC's -planning schedule and roadmap. For that, we recommend opening a discussion. Discussions serve us as a system of record, that -means we monitor them more closely, and do not close them automatically. - -### Add Documentation - -Every decision record, launcher, extension, or any type of module has to provide documentation that covers at least -one markdown file with necessary information. Please find appropriate templates that should -be used in [the templates directory](docs/templates). - -### Report on Flaky Tests - -If you discover a randomly failing ("flaky") test, please take the time to check whether an issue for that already -exists and if not, create an issue yourself, providing meaningful description and a link to the failing run. Please also -label it with `Bug` and `FlakyTest`. Then assign it to whoever was the original author of the relevant piece of code or -whoever worked on it last. If assigning the issue is not possible due to missing rights, please just comment and -@mention the author/last editor. - -Please do not just restart the run, as this would overwrite the results. If you need to, a better way of doing this is -to push an empty commit. This will trigger another run. - -```bash -git commit --allow-empty -m "trigger CI" && git push -``` - -If an issue labeled with `Bug` and `FlakyTest` is assigned to you, please prioritize addressing this issue as other people will be affected. -We are taking the quality of our code very serious and reporting on flaky tests is an important step toward improvement -in that area. - -#### Pull Requests - -Pull requests are not assigned to milestones as their linking to issues is sufficient to track -the relations and progresses. - -### Projects - -The [GitHub Projects page](https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/projects) -provides a general overview of the project's working items. Every new issue is automatically assigned -to the ["Dataspace Connector" project](https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/projects/1). -It can be unassigned or moved to any other project that is provided. - -In every project, an issue passes four stages: `Backlog`, `In progress`, `Review in progress`, and `Done`, -independent of their association to a specific milestone. - -### Contact Us - -If you have questions or suggestions, do not hesitate to contact the project developers via -the [project's "dev" list](https://dev.eclipse.org/mailman/listinfo/dataspaceconnector-dev). diff --git a/README.md b/README.md index bb9fa224a..9651eb008 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,10 @@ Temporary repository to get started with the Identity Hub for the MVD. +## Documentation + +Developer documentation can be found under [docs/developer](docs/developer/), where the main concepts and decisions are captured as [decision records](docs/developer/decision-records/). + ## Run and develop identity Hub locally In order to be able to develop and run this project, you need to follow the instructions below: @@ -25,4 +29,4 @@ If you change the contract of an endpoint or add a new one, you will need to re- ## Contributing -See [how to contribute](./CONTRIBUTING.md) for details. \ No newline at end of file +See [how to contribute](https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/blob/main/CONTRIBUTING.md) for details. diff --git a/pr_etiquette.md b/pr_etiquette.md deleted file mode 100644 index a117e2b6a..000000000 --- a/pr_etiquette.md +++ /dev/null @@ -1,62 +0,0 @@ -# Etiquette for pull requests - -## As an author - -Submitting pull requests in EDC should be done while adhering to a couple of simple rules. - -- Familiarize yourself with [coding style](styleguide.md), [architectural patterns](docs/architecture-principles.md) and - other contribution guidelines. -- No surprise PRs please. Before you submit a PR, open a discussion or an issue outlining your planned work and give - people time to comment. It may even be advisable to contact committers using the `@mention` feature. Unsolicited PRs - may get ignored or rejected. -- Create focused PRs: your work should be focused on one particular feature or bug. Do not create broad-scoped PRs that - solve multiple issues as reviewers may reject those PR bombs outright. -- Provide a clear description and motivation in the PR description in GitHub. This makes the reviewer's life much - easier. It is also helpful to outline the broad changes that were made, e.g. "Changes the schema of XYZ-Entity: - the `age` field changed from `long` to `String`". -- If you introduce new 3rd party dependencies, be sure to note them in the PR description and explain why they are - necessary. -- Stick to the established code style, please refer to the [styleguide document](styleguide.md). -- All tests should be green, especially when your PR is in `"Ready for review"` -- Mark PRs as `"Ready for review"` only when you're prepared to defend your work. By that time you have completed your - work and shouldn't need to push any more commits other than to incorporate review comments. -- Merge conflicts should be resolved by squashing all commits on the PR branch, rebasing onto `main` and - force-pushing. Do this when your PR is ready to review. -- If you require a reviewer's input while it's still in draft, please contact the designated reviewer using - the `@mention` feature and let them know what you'd like them to look at. -- Request a review from one of the [technical committers](pr_etiquette.md#the-technical-committers-as-of-may-13-2022). Requesting a review from anyone else is still possible, and - sometimes may be advisable, but only committers can merge PRs, so be sure to include them early on. -- Re-request reviews after all remarks have been adopted. This helps reviewers track their work in GitHub. -- If you disagree with a committer's remarks, feel free to object and argue, but if no agreement is reached, you'll have - to either accept the decision or withdraw your PR. -- Be civil and objective. No foul language, insulting or otherwise abusive language will be tolerated. - -## As a reviewer - -- Please complete reviews within two business days or delegate to another committer, removing yourself as a reviewer. -- If you have been requested as reviewer, but cannot do the review for any reason (time, lack of knowledge in particular - area, etc.) please comment that in the PR and remove yourself as a reviewer, suggesting a stand-in. The [code - owners document](CODEOWNERS) should help with that. -- Don't be overly pedantic. -- Don't argue basic principles (code style, architectural decisions, etc.) -- Use the `suggestion` feature of GitHub for small/simple changes. -- The following could serve you as a review checklist: - - no unnecessary dependencies in `build.gradle.kts` - - sensible unit tests, prefer unit tests over integration tests wherever possible (test runtime). Also check the - usage of test tags. - - code style - - simplicity and "uncluttered-ness" of the code - - overall focus of the PR -- Don't just wave through any PR. Please take the time to look at them carefully. -- Be civil and objective. No foul language, insulting or otherwise abusive language will be tolerated. The goal is to - _encourage_ contributions. - -## The technical committers (as of May 18, 2022) - -- @MoritzKeppler -- @jimmarino -- @bscholtes1A -- @ndr_brt -- @ronjaquensel -- @juliapampus -- @paullatzelsperger diff --git a/styleguide.md b/styleguide.md deleted file mode 100644 index 59eecbec9..000000000 --- a/styleguide.md +++ /dev/null @@ -1,63 +0,0 @@ -# Eclipse Dataspace Connector Code Style Guide - -In order to maintain a coherent code style throughout the project we ask every contributor to adhere to a few simple -style guidelines. We assume most developers will use at least something like `vim` and therefore have support for -automatic code formatting, we are not going to list the guidelines here. If you absolutely want to take a look, checkout -the [config written in XML](resources/edc-checkstyle-config.xml). - -## Checkstyle configuration - -Checkstyle is a [tool](https://checkstyle.sourceforge.io/) that can statically analyze your source code to check against -a set of given rules. Those rules are formulated in an [XML document](resources/edc-checkstyle-config.xml). Many modern -IDEs have a plugin available for download that runs in the background and does code analysis. - -Our checkstyle config is based off of the [Google Style](https://checkstyle.sourceforge.io/google_style.html) with a few -additional rules such as the naming of constants and Types. - -_Note: currently we do **not** enforce the generation of Javadoc comments, even though documenting code is **highly** -recommended. We might enable this in the future, such that at least interfaces and public methods are commented._ - -## Running Checkstyle - -Checkstyle can be run in different ways: implicitly we run it through the `checkstyle` Gradle Plugin -during `gradle build`. That will cause the build to fail if any violations are found. But in order to get better -usability and on-the-fly reporting, Checkstyle is also available as IDE plugins for many modern IDEs, and it can run -either on-demand or continuously in the background: - -- [IntelliJ IDEA plugin [recommended]](https://plugins.jetbrains.com/plugin/1065-checkstyle-idea) -- [Eclipse IDE [recommended]](https://checkstyle.org/eclipse-cs/#!/) - -### Checkstyle as PR validation - -Apart from running Checkstyle locally as IDE plugin, we do run it on -our [Github Actions pipeline](.github/workflows/verify.yaml). At this time, Checkstyle will only spew out warnings, but -we may tighten the rules at a future time and without notice. This will result in failing Github Action pipelines. Also, -committers might reject PRs due to Checkstyle warnings. - -It is therefore **highly** recommended running Checkstyle locally as well. - -If you **do not wish** to run Checkstyle on you local machine, that's fine, but be prepared to get your PRs rejected -simply because of a stupid naming or formatting error. - -> _Note: we do not use the Checkstyle Gradle Plugin on Github Actions because violations would cause builds to fail. For now, we only want to log warnings._ - -## [Recommended] IntelliJ Code Style Configuration - -If you are using Jetbrains IntelliJ IDEA, we have created a specific code style configuration that will automatically -format your source code according to that style guide. This should eliminate most of the potential Checkstyle violations -right from the get-go. You will need to reformat your code manually or in a pre-commit hook though. - -## [Optional] Intellij SaveActions Plugin - -If you absolutely want to make sure that no piece of ever-so-slightly misformatted code even hits your hard disk, we -advise you to use the [SaveActions plugin](https://plugins.jetbrains.com/plugin/7642-save-actions) for IntelliJ IDEA. It -takes care that your code is always correctly formatted. Unfortunately SaveActions has no export feature, so please just -copy this configuration: -![](/home/paul/dev/DataSpaceConnector/resources/save_actions_screenshot.png) - -## [Optional] Generic `.editorConfig` - -For most other editors and IDEs we've supplied an [.editorConfig](resources/edc-codestyle.editorconfig) file that can be -placed at the appropriate location. The specific location will largely depend on your editor and your OS, please refer -to the -[official documentation](https://editorconfig.org) for details. \ No newline at end of file From 5b0bb206d603c8e60572af2ac580e0b876048ac7 Mon Sep 17 00:00:00 2001 From: Julia Pampus <72392527+juliapampus@users.noreply.github.com> Date: Thu, 25 Aug 2022 13:53:48 +0200 Subject: [PATCH 2/4] chore(github): add issue templates --- .github/ISSUE_TEMPLATE/bug_report.md | 39 +++++++++++++++++++++++ .github/ISSUE_TEMPLATE/config.yml | 2 ++ .github/ISSUE_TEMPLATE/feature_request.md | 27 ++++++++++++++++ 3 files changed, 68 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md create mode 100644 .github/ISSUE_TEMPLATE/config.yml create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 000000000..cec84e48e --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,39 @@ +--- +name: Bug Report +about: Create a report to help us improve +title: '' +labels: 'bug' +assignees: '' + +--- + +# Bug Report + +## Describe the Bug +_A clear and concise description of the bug._ + +### Expected Behavior +_A clear and concise description of what you expected to happen._ + +### Observed Behavior +_A clear and concise description of what happened instead._ + +## Steps to Reproduce +Steps to reproduce the behavior: +1. Go to '...' +2. Click on '....' +3. Scroll down to '....' +4. See error + +## Context Information +_Add any other context about the problem here._ + +- Used version [e.g. IdentityHub v1.0.0] +- OS: [e.g. iOS, Windows] +- ... + +## Detailed Description +_If applicable, add screenshots and logs to help explain your problem._ + +## Possible Implementation +_You already know the root cause of the erroneous state and how to fix it? Feel free to share your thoughts._ diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 000000000..341f6afac --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,2 @@ +--- +blank_issues_enabled: true diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 000000000..6a82e5e85 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,27 @@ +--- +name: Feature Request +about: Help us with new ideas +title: '' +labels: '' +assignees: '' + +--- + +# Feature Request + +## Which Areas Would Be Affected? +_e.g., build, extension, etc._ + +## Why Is the Feature Desired? +_Are there any requirements?_ + +## Solution Proposal +_If possible, provide a (brief!) solution proposal._ + +## Type of Issue +_i.e., new feature, improvement, cleanup, etc._ + +## Checklist + +- [ ] assigned appropriate label? +- [x] **Do NOT select a milestone or an assignee!** From aa1471f9accc3b2b948826de462cea449c17c4e3 Mon Sep 17 00:00:00 2001 From: Julia Pampus <72392527+juliapampus@users.noreply.github.com> Date: Thu, 25 Aug 2022 13:54:15 +0200 Subject: [PATCH 3/4] chore(workflows): add pull request validation --- .github/workflows/pull-request.yaml | 34 +++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 .github/workflows/pull-request.yaml diff --git a/.github/workflows/pull-request.yaml b/.github/workflows/pull-request.yaml new file mode 100644 index 000000000..0ae3cdef6 --- /dev/null +++ b/.github/workflows/pull-request.yaml @@ -0,0 +1,34 @@ +name: Scan Pull Request + +on: + pull_request: + branches: [ main ] + types: [opened, edited, synchronize, reopened, labeled, unlabeled] + +concurrency: + group: ${{ github.workflow }}-${{ github.ref }} + cancel-in-progress: true + +jobs: + check-pull-request-title: + runs-on: ubuntu-latest + continue-on-error: false + steps: + - uses: actions/checkout@v3 + - uses: deepakputhraya/action-pr-title@master + with: + # Match pull request titles conventional commit syntax (https://www.conventionalcommits.org/en/v1.0.0/) + # (online tool for regex quick check: https://regex101.com/r/V5J8kh/1) + # + # Valid examples would be + # - fix: resolve minor issue + # - docs(Sample5): update docs for configuration + # - feat(management-api)!: change path to access contract agreements + # + # Invalid examples would be + # - Add cool feature + # - Feature/some cool improvement + # - fix: resolve minor issue. + regex: '^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\(\w+((,|\/|\\)?\s?\w+)+\))?!?: [\S ]{1,80}[^\.]$' + allowed_prefixes: 'build,chore,ci,docs,feat,fix,perf,refactor,revert,style,test' + prefix_case_sensitive: true From 7f541aceedc4343469687a33612bf20362410172 Mon Sep 17 00:00:00 2001 From: Julia Pampus <72392527+juliapampus@users.noreply.github.com> Date: Thu, 25 Aug 2022 13:56:35 +0200 Subject: [PATCH 4/4] docs: refactor decision records --- docs/developer/decision-records/README.md | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 docs/developer/decision-records/README.md diff --git a/docs/developer/decision-records/README.md b/docs/developer/decision-records/README.md new file mode 100644 index 000000000..e600d4504 --- /dev/null +++ b/docs/developer/decision-records/README.md @@ -0,0 +1,6 @@ +# Decision Records + +- [2022-06-08 Identity Hub](2022-06-08-identity-hub/) +- [2022-07-01 Get Claims](2022-07-01-get-claims/) +- [2022-07-29 Self-description](2022-07-29-self-description/) +- [2022-08-12 Code Quality Tooling](2022-08-12-code-quality-tooling/)