-
Notifications
You must be signed in to change notification settings - Fork 218
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into human_readable_identifier_goal
- Loading branch information
Showing
217 changed files
with
17,745 additions
and
2,510 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,39 @@ | ||
| # For details on how this file works refer to: | ||
| # - https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file | ||
| version: 2 | ||
| updates: | ||
| # Maintain dependencies for GitHub Actions | ||
| # - Check for updates once a week | ||
| # - Group all updates into a single PR | ||
| - package-ecosystem: "github-actions" | ||
| directory: "/" | ||
| schedule: | ||
| interval: "weekly" | ||
| groups: | ||
| all-actions: | ||
| patterns: [ "*" ] | ||
|
|
||
| # Maintain dependencies for Python Packages | ||
| - package-ecosystem: "pip" | ||
| directory: "/" | ||
| schedule: | ||
| interval: "weekly" | ||
| day: "monday" | ||
| time: "04:00" | ||
| timezone: "Canada/Pacific" | ||
| ignore: | ||
| - dependency-name: "*" | ||
| update-types: ["version-update:semver-major"] | ||
|
|
||
| # Maintain dependencies for Python Packages | ||
| - package-ecosystem: "pip" | ||
| directory: "/.circleci" | ||
| schedule: | ||
| interval: "weekly" | ||
| day: "monday" | ||
| time: "04:00" | ||
| timezone: "Canada/Pacific" | ||
| ignore: | ||
| - dependency-name: "*" | ||
| update-types: ["version-update:semver-major"] | ||
|
|
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,39 @@ | ||
| name: publish-docs | ||
|
|
||
| on: | ||
| push: | ||
| # Publish `main` as latest, and when pushes are done to branches with "v-doc" prefix | ||
| branches: | ||
| - main | ||
|
|
||
| permissions: | ||
| contents: write | ||
|
|
||
| jobs: | ||
| deploy: | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| with: | ||
| fetch-depth: 0 # fetch all commits/branches | ||
| - uses: actions/setup-python@v5 | ||
| with: | ||
| python-version: 3.x | ||
| - uses: actions/cache@v4 | ||
| with: | ||
| key: ${{ github.ref }} | ||
| path: .cache | ||
| - name: Install Python dependencies | ||
| run: pip install -r ./mkdocs-requirements.txt | ||
| - name: Configure git user | ||
| run: | | ||
| git config --local user.email "github-actions[bot]@users.noreply.github.com" | ||
| git config --local user.name "github-actions[bot]" | ||
| - name: Deploy docs | ||
| run: | | ||
| python --version | ||
| # Generate the content into the docs folder | ||
| code/genSite.sh | ||
| mike deploy --push --update-aliases main latest | ||
| mike set-default latest |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,3 +5,4 @@ __pycache__ | |
| *.pyc | ||
| *.tmp | ||
| .pytest_cache | ||
| docs | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,73 @@ | ||
| # Maintainers | ||
|
|
||
| ## Active Maintainers | ||
|
|
||
| <!-- Please keep this sorted alphabetically by github --> | ||
|
|
||
| | Name | Github | LFID | | ||
| | ---------------- | ---------------- | ---------------- | | ||
| | Daniel Hardman | dhh1128 | | | ||
| | George Aristy | llorllale | | | ||
| | Nathan George | nage | | | ||
| | Stephen Curran | swcurran | | | ||
| | Drummond Reed | talltree | | | ||
| | Sam Curren | TelegramSam | | | ||
|
|
||
| ## Emeritus Maintainers | ||
|
|
||
| | Name | Github | LFID | | ||
| |--------------|---------|---------| | ||
| | | | | | ||
|
|
||
| ## Becoming a Maintainer | ||
|
|
||
| The Aries community welcomes contributions. Contributors may progress to become a | ||
| maintainer. To become a maintainer the following steps occur, roughly in order. | ||
|
|
||
| - 5 significant changes have been authored by the proposed maintainer and | ||
| accepted. | ||
| - The proposed maintainer has the sponsorship of at least one other maintainer. | ||
| - This sponsoring maintainer will create a PR modifying the list of | ||
| maintainers. | ||
| - The proposed maintainer accepts the nomination and expresses a willingness | ||
| to be a long-term (more than 6 month) committer. | ||
| - This would be a comment in the above PR. | ||
| - This PR will be communicated in all appropriate communication channels. It | ||
| should be mentioned in any maintainer/community call. It should also be | ||
| posted to the appropriate mailing list or chat channels if they exist. | ||
| - Approval by at least 3 current maintainers within two weeks of the proposal or | ||
| an absolute majority of current maintainers. | ||
| - These votes will be recorded in the PR modifying the list of maintainers. | ||
| - No veto by another maintainer within two weeks of proposal are recorded. | ||
| - All vetoes must be accompanied by a public explanation as a comment in the | ||
| PR for adding this maintainer | ||
| - The explanation of the veto must be reasonable. | ||
| - A veto can be retracted, in that case the approval/veto timeframe is reset. | ||
| - It is bad form to veto, retract, and veto again. | ||
| - The proposed maintainer becomes a maintainer | ||
| - Either two weeks have passed since the third approval, | ||
| - Or an absolute majority of maintainers approve. | ||
| - In either case, no maintainer presents a veto. | ||
|
|
||
| ## Removing Maintainers | ||
|
|
||
| Being a maintainer is not a status symbol or a title to be maintained | ||
| indefinitely. It will occasionally be necessary and appropriate to move a | ||
| maintainer to emeritus status. This can occur in the following situations: | ||
|
|
||
| - Resignation of a maintainer. | ||
| - Violation of the Code of Conduct warranting removal. | ||
| - Inactivity. | ||
| - A general measure of inactivity will be no commits or code review comments | ||
| for one reporting quarter, although this will not be strictly enforced if | ||
| the maintainer expresses a reasonable intent to continue contributing. | ||
| - Reasonable exceptions to inactivity will be granted for known long term | ||
| leave such as parental leave and medical leave. | ||
| - Other unspecified circumstances. | ||
|
|
||
| Like adding a maintainer the record and governance process for moving a | ||
| maintainer to emeritus status is recorded in the github PR making that change. | ||
|
|
||
| Returning to active status from emeritus status uses the same steps as adding a | ||
| new maintainer. Note that the emeritus maintainer already has the 5 required | ||
| significant changes as there is no contribution time horizon for those. |
Oops, something went wrong.