We are committed to making participation in the AgML Community respectful, constructive, and welcoming to people across disciplines, career stages, geographies, institutions, and levels of technical experience.
Agricultural machine learning depends on collaboration among people with different forms of expertise. Domain knowledge, field experience, data stewardship, software development, modeling, evaluation, and critical questions should all be treated as meaningful contributions.
Community members should:
- Be respectful, curious, and constructive
- Welcome questions and explain specialized terminology
- Critique ideas and evidence rather than people
- Give appropriate credit to data creators, contributors, and prior work
- Distinguish validated findings from preliminary results or proposals
- Respect licensing, privacy, consent, data sovereignty, and usage restrictions
- Disclose relevant limitations, conflicts, and uncertainties
- Help make discussions accessible across agricultural and technical disciplines
The following are not acceptable:
- Harassment, intimidation, discrimination, or personal attacks
- Demeaning comments about experience, discipline, identity, geography, institution, or technical ability
- Publishing private or sensitive information without permission
- Sharing restricted data or materials that contributors do not have the right to distribute
- Plagiarism, deliberate misrepresentation, or removal of appropriate attribution
- Repeated disruption, spam, or bad-faith participation
- Presenting unsafe, unvalidated, or misleading agricultural recommendations as established guidance
This Code of Conduct applies in Project-AgML repositories, Discussions, issues, pull requests, community calls, and other spaces where someone is representing the AgML Community.
If you experience or observe unacceptable behavior, contact a Project-AgML organization owner or maintainer privately. You may also use GitHub's reporting and blocking tools when appropriate.
Maintainers may edit or hide content, close discussions, restrict participation, or take other proportionate action to protect the community. Reports should be handled as confidentially as practical, with attention to the safety and privacy of those involved.
A healthy community is not created only through enforcement. Members are encouraged to welcome newcomers, redirect conversations constructively, acknowledge mistakes, and help translate between technical and agricultural perspectives.