@vfarcic/dot-ai 0.119.0 → 0.124.0

package/assets/project-setup/templates/ADOPTERS.md.hbs

@@ -0,0 +1,119 @@
+# Adopters
+
+This page lists organizations and users who are officially using {{projectName}} in production or development environments.
+
+{{#if projectDescription}}
+{{projectDescription}} is being used by organizations worldwide for various use cases, from development workflows to production deployments.
+{{/if}}
+
+## Organizations Using {{projectName}}
+
+{{#if includeUseCase}}
+| Organization | Use Case | Website |
+|--------------|----------|---------|
+{{#if maintainerOrganization}}
+| {{maintainerOrganization}} | {{maintainerUseCase}} | [{{maintainerWebsite}}]({{maintainerWebsite}}) |
+{{else}}
+| *Add your organization here* | *Describe your use case* | *Your website* |
+{{/if}}
+
+{{else}}
+{{#if maintainerOrganization}}
+1. [{{maintainerOrganization}}]({{maintainerWebsite}})
+{{else}}
+1. *Add your organization here*
+{{/if}}
+
+{{/if}}
+## Adding Your Organization
+
+We'd love to hear from organizations using {{projectName}}! Adding your organization helps:
+
+- Build confidence for other organizations evaluating {{projectName}}
+- Show the diversity of use cases and industries
+- Recognize your support for the project
+- Connect with other users in your industry
+
+### How to Add Yourself
+
+1. **Fork this repository**
+2. **Edit this file** (`ADOPTERS.md`)
+3. **Add your organization** {{#if includeUseCase}}to the table above{{else}}to the list above{{/if}} in **alphabetical order**
+4. **Submit a Pull Request**
+
+{{#if includeUseCase}}
+#### Information to Include
+
+- **Organization**: Your company or organization name
+- **Use Case**: Brief description of how you use {{projectName}} (1-2 sentences)
+- **Website**: Link to your organization's website or public project
+
+#### Example Entry
+
+```markdown
+| Acme Corporation | Using {{projectName}} to automate infrastructure deployment across 50+ Kubernetes clusters | [acme.com](https://acme.com) |
+```
+
+{{else}}
+#### Information to Include
+
+- **Organization name**
+- **Website URL** (optional but recommended)
+
+#### Example Entry
+
+```markdown
+2. [Acme Corporation](https://acme.com)
+```
+
+Please maintain **alphabetical ordering** when adding your organization.
+
+{{/if}}
+{{#if requiresDco}}
+### DCO Sign-off Required
+
+All commits must be signed off (`git commit --signoff`) to comply with the [Developer Certificate of Origin](https://developercertificate.org/).
+
+{{/if}}
+## Verification
+
+{{#if requiresVerification}}
+Organizations listed here have been verified by maintainers. When submitting your PR:
+- Include a link to your deployment or public usage
+- Or request verification from a maintainer via email
+
+{{else}}
+Organizations self-report their usage through pull requests. While we don't formally verify each entry, we may reach out for clarification or examples.
+
+{{/if}}
+## Support and Recognition
+
+{{#if recognitionProgram}}
+Organizations listed here are eligible for:
+- Recognition on our website and documentation
+- Early access to new features (optional program)
+- Direct communication channel with maintainers
+- Featured case studies (upon request)
+
+Contact {{maintainerEmail}} to learn more about our adopter recognition program.
+
+{{else}}
+Thank you to all organizations using {{projectName}}! Your adoption and feedback help drive the project forward.
+
+If you'd like to be featured in a case study or share your story, contact {{maintainerEmail}}.
+
+{{/if}}
+## Why Share Your Adoption?
+
+Publicly sharing your usage:
+- **Helps the project**: Demonstrates real-world validation and builds community trust
+- **Helps others**: Provides proof points for organizations evaluating {{projectName}}
+- **Helps you**: Connects you with other users and increases visibility for your organization
+
+---
+
+**Thank you for using {{projectName}}!** We appreciate your support and willingness to share your experience with the community.
+
+{{#if questionsContact}}
+Questions about the adopters list? Contact {{questionsContact}}
+{{/if}}

package/assets/project-setup/templates/CODE_OF_CONDUCT.md.hbs

@@ -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
+{{enforcementEmail}}. 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

package/assets/project-setup/templates/CONTRIBUTING.md.hbs

@@ -0,0 +1,159 @@
+# Contributing to {{projectName}}
+
+Thank you for your interest in contributing to {{projectName}}! We welcome contributions from the community.
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Ways to Contribute](#ways-to-contribute)
+- [Getting Started](#getting-started)
+- [Development Workflow](#development-workflow)
+- [Pull Request Process](#pull-request-process)
+- [Coding Standards](#coding-standards)
+{{#if requiresDco}}
+- [Commit Sign-off](#commit-sign-off)
+{{/if}}
+- [Communication](#communication)
+
+## Code of Conduct
+
+This project adheres to a [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+
+## Ways to Contribute
+
+There are many ways to contribute:
+
+- **Report bugs** - File detailed bug reports with reproduction steps
+- **Suggest features** - Propose new features or improvements
+- **Write code** - Submit bug fixes or new features
+- **Improve documentation** - Fix typos, clarify content, add examples
+- **Review pull requests** - Provide feedback on proposed changes
+- **Answer questions** - Help other users in issues or discussions
+- **Write tests** - Improve test coverage
+
+## Getting Started
+
+1. **Fork the repository** on GitHub
+2. **Clone your fork** locally:
+   ```bash
+   git clone https://github.com/YOUR_USERNAME/{{repoName}}.git
+   cd {{repoName}}
+   ```
+3. **Add upstream remote**:
+   ```bash
+   git remote add upstream {{repositoryUrl}}
+   ```
+{{#if setupCommand}}
+4. **Install dependencies**:
+   ```bash
+   {{setupCommand}}
+   ```
+{{else}}
+4. **Install dependencies** - See [README.md](README.md) for setup instructions
+{{/if}}
+
+## Development Workflow
+
+1. **Create a branch** for your changes:
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+
+2. **Make your changes** - Write code, add tests, update docs
+
+3. **Test your changes**{{#if testCommand}} - Run `{{testCommand}}`{{/if}}
+
+4. **Commit your changes**:
+   ```bash
+   git commit -m "Description of your changes"
+   ```
+{{#if requiresDco}}
+   Use `git commit -s` to sign off your commits (required)
+{{/if}}
+
+5. **Push to your fork**:
+   ```bash
+   git push origin feature/your-feature-name
+   ```
+
+6. **Open a Pull Request** on GitHub
+
+## Pull Request Process
+
+### Before Submitting
+
+- Ensure your code follows the project's coding standards
+{{#if testCommand}}
+- Add or update tests for your changes
+- Verify all tests pass: `{{testCommand}}`
+{{/if}}
+{{#if lintCommand}}
+- Run linters: `{{lintCommand}}`
+{{/if}}
+- Update documentation as needed
+- Keep pull requests focused on a single concern
+
+### PR Description
+
+Include in your pull request description:
+
+- **What** - Summary of changes
+- **Why** - Motivation and context
+- **How** - Implementation approach
+- **Testing** - How you tested the changes
+- **Related Issues** - Link any related issues (e.g., "Fixes #123")
+
+### Review Process
+
+1. Automated checks will run on your PR
+2. Maintainers will review your changes
+3. Address any feedback or requested changes
+4. Once approved, a maintainer will merge your PR
+
+## Coding Standards
+
+{{#if lintCommand}}
+Follow the project's coding style enforced by `{{lintCommand}}`.
+{{else}}
+- Write clear, readable code
+- Use meaningful names for variables and functions
+- Add comments for complex logic
+- Follow language-specific best practices
+{{/if}}
+
+{{#if requiresDco}}
+## Commit Sign-off
+
+All commits must be signed off to certify that you have the right to submit the code under the project's license.
+
+Add the `-s` flag when committing:
+
+```bash
+git commit -s -m "Your commit message"
+```
+
+This adds a "Signed-off-by" line:
+
+```
+Signed-off-by: Your Name <your.email@example.com>
+```
+
+Learn more at [https://developercertificate.org/](https://developercertificate.org/)
+{{/if}}
+
+## Communication
+
+- **Issues** - Report bugs and request features via [GitHub Issues]({{repositoryUrl}}/issues)
+{{#if discussionsUrl}}
+- **Discussions** - Ask questions in [GitHub Discussions]({{discussionsUrl}})
+{{/if}}
+{{#if slackChannel}}
+- **Slack** - Join our community: {{slackChannel}}
+{{/if}}
+{{#if discordUrl}}
+- **Discord** - Chat with the community: {{discordUrl}}
+{{/if}}
+
+---
+
+Thank you for contributing to {{projectName}}!