chore: sync files

.github/ISSUE_TEMPLATE/bug.yaml

@@ -0,0 +1,71 @@
+name: Bug
+description: Report a bug
+body:
+  - type: checkboxes
+    attributes:
+      label: Checklist
+      description: Confirm the following items before proceeding. If one cannot be satisfied, create a discussion thread instead.
+      options:
+        - label: I've read the [contribution guidelines](https://github.com/autowarefoundation/autoware/blob/main/CONTRIBUTING.md).
+          required: true
+        - label: I've searched other issues and no duplicate issues were found.
+          required: true
+        - label: I'm convinced that this is not my fault but a bug.
+          required: true
+
+  - type: textarea
+    attributes:
+      label: Description
+      description: Write a brief description of the bug.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Expected behavior
+      description: Describe the expected behavior.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Actual behavior
+      description: Describe the actual behavior.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Write the steps to reproduce the bug.
+      placeholder: |-
+        1.
+        2.
+        3.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Versions
+      description: Provide the version information. You can omit this if you believe it's irrelevant.
+      placeholder: |-
+        - OS:
+        - ROS 2:
+        - Autoware:
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Possible causes
+      description: Write the possible causes if you have any ideas.
+    validations:
+      required: false
+
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add any other additional context if it exists.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,13 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Question
+    url: https://github.com/autowarefoundation/autoware/discussions/new?category=q-a
+    about: Ask a question
+
+  - name: Feature request
+    url: https://github.com/autowarefoundation/autoware/discussions/new?category=feature-requests
+    about: Send a feature request
+
+  - name: Idea
+    url: https://github.com/autowarefoundation/autoware/discussions/new?category=ideas
+    about: Post an idea

.github/ISSUE_TEMPLATE/task.yaml

@@ -0,0 +1,42 @@
+name: Task
+description: Plan a task
+body:
+  - type: checkboxes
+    attributes:
+      label: Checklist
+      description: Confirm the following items before proceeding. If one cannot be satisfied, create a discussion thread instead.
+      options:
+        - label: I've read the [contribution guidelines](https://github.com/autowarefoundation/autoware/blob/main/CONTRIBUTING.md).
+          required: true
+        - label: I've searched other issues and no duplicate issues were found.
+          required: true
+        - label: I've agreed with the maintainers that I can plan this task.
+          required: true
+
+  - type: textarea
+    attributes:
+      label: Description
+      description: Write a brief description of the task.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Purpose
+      description: Describe the purpose of the task.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Possible approaches
+      description: Describe possible approaches for the task.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Definition of done
+      description: Write the definition of done for the task.
+    validations:
+      required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,55 +1,8 @@
-## PR Type
+**Note**: Confirm the [contribution guidelines](https://autowarefoundation.github.io/autoware-documentation/main/contributing/) before submitting a pull request.
 
-<!-- Select one and remove others. If an appropriate one is not listed, please write by yourself. -->
+Click the `Preview` tab and select a PR template:
 
-- New Feature
-- Improvement
-- Bug Fix
+- [Standard change](?expand=1&template=standard-change.md)
+- [Small change](?expand=1&template=small-change.md)
 
-## Related Links
-
-<!-- Please write related links to GitHub/Jira/Slack/etc. -->
-
-## Description
-
-<!-- Describe what this PR changes. -->
-
-## Review Procedure
-
-<!-- Explain how to review this PR. -->
-
-## Remarks
-
-<!-- Write remarks as you like if you need them. -->
-
-## Pre-Review Checklist for the PR Author
-
-**PR Author should check the checkboxes below when creating the PR.**
-
-- [ ] Code follows [coding guidelines][coding-guidelines]
-- [ ] Assign PR to reviewer
-
-## Checklist for the PR Reviewer
-
-**Reviewers should check the checkboxes below before approval.**
-
-- [ ] Commits are properly organized and messages are according to the guideline
-- [ ] Code follows [coding guidelines][coding-guidelines]
-- [ ] (Optional) Unit tests have been written for new behavior
-- [ ] PR title describes the changes
-
-## Post-Review Checklist for the PR Author
-
-**PR Author should check the checkboxes below before merging.**
-
-- [ ] All open points are addressed and tracked via issues or tickets
-- [ ] Write [release notes][release-notes]
-
-## CI Checks
-
-- **Build and test for PR**: Required to pass before the merge.
-- **Check spelling**: NOT required to pass before the merge. It is up to the reviewer(s). See [here][spell-check-dict] if you want to add some words to the spell check dictionary.
-
-[coding-guidelines]: https://tier4.atlassian.net/wiki/spaces/AIP/pages/1194394777/T4
-[release-notes]: https://tier4.atlassian.net/wiki/spaces/AIP/pages/563774416
-[spell-check-dict]: https://github.com/tier4/autoware-spell-check-dict#how-to-contribute
+**Do NOT send a PR with this description.**

.github/PULL_REQUEST_TEMPLATE/standard-change.md

@@ -0,0 +1,42 @@
+## Description
+
+<!-- Write a brief description of this PR. -->
+
+## Related links
+
+<!-- Write the links related to this PR. Private links should be clearly marked as private, for example, '[FOO COMPANY INTERNAL LINK](https://example.com)'. -->
+
+## Tests performed
+
+<!-- Describe how you have tested this PR. -->
+
+## Notes for reviewers
+
+<!-- Write additional information if necessary. It should be written if there are related PRs that should be merged at the same time. -->
+
+## Pre-review checklist for the PR author
+
+The PR author **must** check the checkboxes below when creating the PR.
+
+- [ ] I've confirmed the [contribution guidelines].
+- [ ] The PR follows the [pull request guidelines].
+
+## In-review checklist for the PR reviewers
+
+The PR reviewers **must** check the checkboxes below before approval.
+
+- [ ] The PR follows the [pull request guidelines].
+- [ ] The PR has been properly tested.
+- [ ] The PR has been reviewed by the code owners.
+
+## Post-review checklist for the PR author
+
+The PR author **must** check the checkboxes below before merging.
+
+- [ ] There are no open discussions or they are tracked via tickets.
+- [ ] The PR is ready for merge.
+
+After all checkboxes are checked, anyone who has write access can merge the PR.
+
+[contribution guidelines]: https://autowarefoundation.github.io/autoware-documentation/main/contributing/
+[pull request guidelines]: https://autowarefoundation.github.io/autoware-documentation/main/contributing/pull-request-guidelines/

.github/stale.yml

@@ -0,0 +1,12 @@
+# Modified from https://github.com/probot/stale#usage
+
+# Number of days of inactivity before an Issue or Pull Request with the stale label is closed
+daysUntilClose: false
+
+# Label to use when marking as stale
+staleLabel: stale
+
+# Comment to post when marking as stale
+markComment: >
+  This pull request has been automatically marked as stale because it has not had
+  recent activity.

CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+conduct@autoware.org.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][mozilla coc].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][faq]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[mozilla coc]: https://github.com/mozilla/diversity
+[faq]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,3 @@
+# Contributing
+
+See <https://autowarefoundation.github.io/autoware-documentation/main/contributing/>.