farmOS
farmOS is a web-based application for farm management, planning, and record keeping.
Website: https://farmOS.org
Type of Digital Public Good
- Open content
- Open data
- ✅ Open software
- Open standard
- Open AI model
1. Is it relevant to one of the Sustainable Development Goals?
- 3. Good Health and Well-being
Evidence: farmOS is used to track lab results that test food quality and compare against soil health practices.
Link to Evidence: https://proofingfuture.eu/2022/02/09/bionutrient-food-association/
- 6. Clean Water and Sanitation
Evidence: A farmOS Produce Safety module was developed by the University of Vermont, which includes recordkeeping for on-farm water quality testing and worker hygience requirements.
Link to Evidence: https://blog.uvm.edu/cwcallah/produce-tracking-and-traceability/
- 9. Industry, Innovation and Infrastructure
Evidence: farmOS provides record keeping and planning tools for farmers to monitor their operations.
Link to Evidence: https://opensensing.com/open-source-agtech-iot-ecosystem/
- 12. Responsible Consumption and Production
Evidence: farmOS can be used for traceability, tracking food production from seed to sale.
Link to Evidence: http://blog.uvm.edu/cwcallah/produce-tracking-and-traceability
- 13. Climate Action
Evidence: farmOS is being used to measure on farm carbon capture.
Link to Evidence: https://www.dell.com/en-us/perspectives/keeping-cows-happy-and-soil-healthy-with-ai-and-open-source-data-management/
2. Does it use an appropriate open license?
Yes, this project is licensed under the following license(s):
3. Is ownership clearly defined?
Is the ownership of the project and everything that the project produces clearly defined and documented?
Yes
If yes - please link to the relevant copyright, trademarks, or ownership documentation for the project.
4. Does the license of libraries/dependencies undermine the openess of the project?
Does this open project have mandatory dependencies (i.e. libraries, hardware) that create more restrictions than the original license?
No
If yes - are the open source components able to demonstrate independence from the closed component(s) and/or are there functional, open alternatives?
Not Applicable
If yes - please describe how the open source components are independent and/or list the open alternatives for the closed component:
Not Applicable
5. Is there documentation?
Does some documentation exist of the source code, use cases, and/or functional requirements. For software projects, this should be present as technical documentation that would allow a technical person unfamiliar with the project to launch and run the software. For datasets and data projects, this should be present as documentation that describes all the fields in the set, and provides context on how the data was collected and how it should be interpreted. For content collections, this should indicate any relevant compatible apps, software, hardware required to access the content and any instructions about how to use it.
Yes
If yes - please link to the relevant documentation:
6. Is non PII data and/or content accessible?
Does this project collect or use non-personally identifiable information (non-PII) data and/or content?
Yes
If yes - is there a mechanism for extracting or importing non-personally identifiable information (non-PII) from the system in a non-proprietary format?
Yes
If yes - describe the mechanism for extracting or importing non-personally identifiable information from the system in a non-proprietary format:
farmOS provides an API (that adheres to JSON) that other applications/systems can use to read and write records via HTTP requests - https://farmos.org/development/api/
7. Does the project adhere to privacy and other applicable international and domestic laws?
Has this project taken steps to ensure adherence with relevant privacy, domestic, and international laws? For example, the General Data Protection Regulation (GDPR) in the European Union or the Supplementary Act A/SA.1/01/10 on Personal Data Protection for the Economic Community of West African States (ECOWAS) (yes/no)
Yes
If yes, please list some of relevant laws that the project complies with:
- farmOS is an open source project that can be self-hosted by farmers, so that all of their data is directly under their control. There is no requirement for data to be stored in a central database of any company or organization. It is true data sovereignty. As such, laws such as GDPR do not apply, because a third-party is not involved in data storage.
If yes, please describe the steps this project has taken to ensure adherence (include links to terms of service, privacy policy, or other relevant documentation):
- farmOS is an open source project that can be self-hosted by farmers, so that all of their data is directly under their control. There is no requirement for data to be stored in a central database of any company or organization. It is true data sovereignty. As such, laws such as GDPR do not apply, because a third-party is not involved in data storage.
8. Does the project adhere to standards and best practices?
Does this project support standards? (i.e. Web Content Accessibility Guidelines (WCAG) 2.1 or other standards such as those listed on W3C)
Yes
Which standards does this project support (please list)
- HTTPS
- SSL
- OAuth2
- OIDC
- JWT
- UTF-8
- HTML
- CSS
- REST (Representational State Transfer)
- OpenAPI
- JSON
Can you point to evidence of your support? (i.e. please link to your validator, open test suite, etc.)
Was this project built and developed according to or in adherence with any design, technical and/or sector best practices or principles? i.e. the Principles for Digital Development?
Yes
Which principles and best practices does this project support (please list)
- Coding standards - farmOS follows Drupal coding standards (https://farmos.org/development/environment/code/)
- Automated tests - https://farmos.org/development/environment/tests/
9. Does the project do no harm by design?
Has this project taken steps to anticipate, prevent and do no harm by design?
On the whole, does this project take steps to ensure that it anticipates, prevents and does no harm by design?
Unknown
Is there any additional information you would like to share about the mechanisms, processes or policies that this project uses to avoid doing harm by design?
The farmOS community has adopted the Contributor's Covenant as its Code of Conduct - https://www.contributor-covenant.org/
9.a. Data Privacy & Security
Does this project collect or store personally identifiable information (PII) data and/or content?
Yes
If yes - please list the types of data and/or content collected and/or stored by the project:
- Farm records and field geometries
If yes - does this project share this data and/or content with third parties?
No
Please describe the circumstances with which this project shares data and/or content with third parties. Please add links as relevant.
Not Applicable
If yes - does the project ensure the privacy, security and integrity of this data and/or content collection and has it taken steps to prevent adverse impacts resulting from its collection, storage and distribution.
Yes
If yes - please describe the steps, and include a link to the privacy policy and/or terms of service:
farmOS is an open source project that can be self-hosted by farmers, so that all of their data is directly under their control. There is no requirement for data to be stored in a central database of any company or organization. It is true data sovereignty.
9.b. Inappropriate & Illegal Content
Does this project collect, store or distribute content?
No
If yes - what kinds of content does this project, collect, store or distribute? (i.e. childrens books)
Not Applicable
If yes - does this project have policies that describe what is considered innappropriate content? (i.e. child sexual abuse materials)
Not Applicable
If yes - please link to the relevant policy/guidelines/documentation.
Not Applicable
If yes - does this project have policies and processes for detecting and moderating innappropriate/illegal content?
Not Applicable
If yes - please describe the policies and processes for detecting, reporting and removing innapropriate/illegal content (Please include the average response time for assessment and/or action. Link to any policies or descriptions of how inappropriate content is handled):
Not Applicable
9.c. Protection from harassment
Does this project facilitate interactions with or between users or contributors?
Yes
If yes - does the project take steps to address the safety and security of underage users?
Yes
If yes - please describe the steps this project takes to address risk or prevent access by underage users:
- The farmOS community has adopted the Contributor's Covenant as its Code of Conduct, which is used to enforce positive conduct in our community spaces such as the forum and issue queues. The software itself can be self-hosted and therefore the users of it are dictated by the person running the software.
If yes - does the project help users and contributors protect themselves against grief, abuse, and harassment?
Yes
If yes - please describe the steps taken to help users protect themselves.
- Contributor Covenant Code of Conduct - https://farmos.org/community/conduct/
Development & deployment countries
List of countries this project was developed in.
- United States of America
List of countries this project is actively deployed in.
- United Kingdom
- Ireland
- Spain
- Germany
- Norway
- Sweden
- Uganda
- Australia
- New Zealand
- Malaysia
- India
- United States of America