Add issue templates, community docs, and OSS-ready documentation

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug Report
+about: Report a bug to help us improve SubmitQueue
+title: "[Bug] "
+labels: bug
+---
+
+## Description
+
+A clear and concise description of the bug.
+
+## Steps to Reproduce
+
+1.
+2.
+3.
+
+## Expected Behavior
+
+What you expected to happen.
+
+## Actual Behavior
+
+What actually happened.
+
+## Environment
+
+- **Go version**:
+- **OS**:
+- **Bazel version**:
+
+## Logs / Screenshots
+
+If applicable, add logs or screenshots to help explain the problem.
+
+## Additional Context
+
+Any other context about the problem.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,22 @@
+---
+name: Feature Request
+about: Suggest a new feature or improvement for SubmitQueue
+title: "[Feature] "
+labels: enhancement
+---
+
+## Problem Statement
+
+A clear and concise description of the problem this feature would solve.
+
+## Proposed Solution
+
+Describe the solution you'd like.
+
+## Alternatives Considered
+
+Describe any alternative solutions or features you've considered.
+
+## Additional Context
+
+Any other context, mockups, or examples about the feature request.

CODE_OF_CONDUCT.md

@@ -0,0 +1,75 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age,
+body size, disability, ethnicity, gender identity and expression, level of
+experience, nationality, personal appearance, race, religion, or sexual
+identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an
+appointed representative at an online or offline event. Representation of a
+project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at oss-conduct@uber.com. The project
+team will review and investigate all complaints, and will respond in a way
+that it deems appropriate to the circumstances. The project team is obligated
+to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at
+[http://contributor-covenant.org/version/1/4][version].
+
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,59 @@
+# Contributing to SubmitQueue
+
+Thank you for your interest in contributing to SubmitQueue! Whether you are reporting a bug, suggesting a feature, improving documentation, or writing code, your contribution is welcome.
+
+## Getting Started
+
+1. Read the [Development Setup](doc/howto/DEVELOPMENT.md) guide for prerequisites, building, and running tests.
+2. Review the [Architecture Guide](CLAUDE.md) to understand project layout, conventions, and code style.
+3. Check the [Testing Guide](doc/howto/TESTING.md) for testing patterns and requirements.
+
+## Development Workflow
+
+1. Fork the repository and clone your fork.
+2. Create a feature branch from `main`:
+   ```bash
+   git checkout -b yourname/short-description
+   ```
+   Use branch naming like `yourname/short-description` or `fix/issue-123`.
+3. Make your changes, following the project conventions.
+4. Add or update tests as appropriate.
+5. Run `make gazelle` if you added or removed Go files.
+6. Run `make test` to ensure unit tests pass.
+7. Commit with a clear, descriptive message.
+8. Push to your fork:
+   ```bash
+   git push origin yourname/short-description
+   ```
+9. Open a pull request against `main`.
+
+## Pull Request Guidelines
+
+- Keep PRs focused on a single change.
+- Reference related issues: use `Closes #123` for fixes or `Part of #123` for incremental work.
+- Include tests for new functionality.
+- Ensure all existing tests pass (`make test`).
+- Ensure CI passes before requesting review.
+- Follow the existing code style and patterns described in the [Architecture Guide](CLAUDE.md).
+- Fill out the PR template with a description, motivation, and test plan.
+
+## Code Review
+
+All submissions require review before merging. We use GitHub pull requests for this purpose. A maintainer will review your PR and may request changes.
+
+## Reporting Issues
+
+Use [GitHub Issues](https://github.com/uber/submitqueue/issues) to report bugs or request features. Please use the provided [issue templates](.github/ISSUE_TEMPLATE/) and check existing issues before creating a new one.
+
+## Communication
+
+- **Bug reports and feature requests** — [GitHub Issues](https://github.com/uber/submitqueue/issues)
+- **Questions and discussions** — open an issue with the `question` label
+
+## Code of Conduct
+
+This project adheres to the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+
+## License
+
+By contributing to SubmitQueue, you agree that your contributions will be licensed under the [Apache License 2.0](LICENSE).