# Community guidelines The Health AI Developer Foundations (HAI-DEF) user community is an open source developer community, and we believe that it can only thrive based on the spirit of collaboration, transparency, and mutual respect. These guidelines are for all HAI-DEF projects and are designed to help foster a positive environment where developers can work together, share ideas, and grow professionally. Whether you're a seasoned open source contributor or just starting out in the Healthcare + AI space, help the community be more successful by following these guidelines. This page aims to provide clear expectations, consistency, and predictability in how *HAI-DEF and the community at large* conduct ourselves. ## Code of conduct The HAI-DEF community recognizes that open source communities are diverse, consisting of individuals from various backgrounds, skill levels, and cultures. It's important for all users that we maintain an environment where everyone feels welcome, safe, and valued. We follow the [Google Open Source Community Guidelines](https://opensource.google/conduct), which are fundamentally about respecting each other and resolving any conflicts peacefully. Report any violations by emailing `hai-def@google.com`. In practice, we think that the following are concrete ways that the Community Guidelines apply to everyday interactions: 1. **Be Respectful and Considerate:** Treat everyone with kindness and respect. Value diverse perspectives and experiences. Embrace different viewpoints and approaches. Assume good intentions, approach discussions with a positive attitude, and seek clarification before jumping to conclusions. 2. **Contribute Constructively:** Provide helpful and informative contributions. When submitting code, opening issues, or participating in discussions, ensure that your input is clear, concise, and relevant. Keep it professional. Maintain a respectful tone in all interactions, even when disagreeing. Be mindful of your language, and avoid jargon or slang that might exclude others. 3. **Follow Project Guidelines:** Familiarize yourself with each of the HAI-DEF project's guidelines, because each project can have specific nuances in the API and usage. Respect the HAI-DEF [Terms of use](https://developers.google.com/health-ai-developer-foundations/terms), and ensure that your contributions comply with them. 4. **Foster Collaboration:** Be responsive and helpful. Work together with other contributors to find the best solutions. Be willing to compromise and consider alternative perspectives. Acknowledge contributions, and give credit wherever needed. 5. **Maintain a Positive Environment:** Help create a welcoming space. Encourage and support new contributors. ## Contributing HAI-DEF values and welcomes contributions by everyone in the community. Each GitHub repository includes a `CONTRIBUTING.md` file that outlines any special considerations. Code contributions must be accompanied by a [Contributor License Agreement](https://cla.developers.google.com/about) (CLA), which you can look up and sign at . In addition to code contributions, there are other ways to contribute and help the community, and we encourage everyone to consider: - Answering questions on HAI-DEF project discussions forums, including sharing your insights or experiences in using HAI-DEF projects. - Filing feature requests or bugs, or commenting on existing issues with your opinions. - Adding or improving documentation, through pull requests or by creating issue or discussion threads with the changes you'd like made. - Providing feedback on what a model is doing well and what it could do better. ### Contribution guidelines - *Adhere to legal and ethical standards:* Follow the HAI-DEF [Terms of use](https://developers.google.com/health-ai-developer-foundations/terms). Ensure that you are adhering to the terms of any open source licenses your project uses. This includes respecting copyright, attribution, and distribution requirements. - *Respect privacy:* Be mindful of privacy concerns when dealing with sensitive information. Never expose private data or information that could compromise someone's security or privacy. - *Avoid malicious code:* Open source software is built on trust. Ensure that your contributions are free of malicious code, backdoors, or security vulnerabilities that could harm users. - \*Make proper attributions: Follow the Organizataion for Ethical Source [Contributor Covenant](https://www.contributor-covenant.org/) to make proper attributions. Recognize contributions by publicly acknowledging and thanking other contributors for their work, helping the HAI-DEF community foster goodwill and motivate continued collaboration. ### Code review process and guidelines Following are the review process and requirements for HAI-DEF open source contributions: - For external contributions we use GitHub pull requests. Consult [GitHub Help](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) for more information about using pull requests. - All submissions require review. To help ensure timely acceptance of your changes, before requesting a review, ensure that your code follows all the standard [Contribution guidelines](https://developers.google.com/health-ai-developer-foundations/community-guidelines#contribution-guidelines) as well as any project-specific guidelines in their GitHub `CONTRIBUTING.md` file. - All tests must pass. If you find that a test is broken and the issue is not related to your build environment or your changes, please contact the maintainers (such as filing a new GitHub Issue). - Avoid scope creep during the review process. This is the responsibility of both the submitter and the reviewer. If a change starts to get too large, consider breaking it into multiple changes. Before a change is merged, it will undergo internal testing. This can potentially add extra steps to the review process if there are failures on internal tests. Your reviewer will communicate any internal test failures and describe what needs to be fixed. ## Summary A thriving open source community is built on respect, collaboration, and shared goals. By following these community guidelines, we can promote a welcoming, supportive, and productive environment for all developers. Together we can build a great community and ecosystem together that benefits everyone. Open source is more than just writing code - it's about creating an environment where people can learn, share, contribute, and grow together.