We are committed to providing a welcoming and inclusive environment for all contributors and users of JIT-Optimization-Engine, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
Examples of behavior that contributes to creating a positive environment include:
- Using welcoming and inclusive language
- Being respectful of differing opinions, viewpoints, and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members
- Crediting and attributing contributions fairly
- Respecting data privacy and confidentiality
Examples of unacceptable behavior include:
- Harassment of any kind (sexual, discriminatory, etc.)
- Insulting or derogatory comments
- Personal or political attacks
- Public or private harassment
- Publishing others' private information (data, credentials, infrastructure details)
- Submitting real customer/production data to the project
- Circumventing security or privacy safeguards
- Other conduct which could reasonably be considered inappropriate
If you witness or experience behavior that violates this Code of Conduct:
- Do not engage with the person exhibiting concerning behavior
- Report directly to the project maintainers at the contact email in the repository
- Provide context including what happened, who was involved, and any evidence
- Your report will be treated confidentially
This project is about sharing FinOps methodologies and tools — not customer data. This means:
✅ Do:
- Share your learnings about cost optimization
- Discuss FinOps strategies and best practices
- Provide synthetic examples and case studies
- Publish results from analyzing YOUR OWN infrastructure (with consent)
❌ Don't:
- Share real customer billing data (even partially or anonymized)
- Upload production logs or telemetry
- Expose infrastructure metrics of any company
- Publish credentials, API keys, or secrets
- Use this project to bypass security or expose sensitive data
Red flags: Any PR/issue with:
- Real company billing CSV/JSON
- Actual AWS/GCP/Azure account IDs
- Production resource names or configurations
- Customer-specific metrics or costs
- Credentials in any form
→ These will be rejected immediately and marked as confidentiality violation.
If you discover confidential information committed to this repository, report it immediately as a security issue.
Project maintainers are responsible for clarifying standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Possible consequences of violation include:
- Request to remove/modify content
- Temporary or permanent ban from repository
- Escalation to GitHub support for serious violations
- Report to legal authorities if data/credentials were exposed
This Code of Conduct applies within all project spaces (GitHub issues, pull requests, discussions, documentation) and also applies when an individual is representing the project or its community in external spaces (conferences, blogs, social media, etc.).
- Transparency: Open-source done right, with clear boundaries
- Community: Shared knowledge benefits everyone
- Ethics: Building tools for good, with respect for privacy
- Inclusivity: Everyone can contribute and learn
Thank you for helping keep this a safe, welcoming community for all. 🙏