How to Contribute to Open Source
Conservation Technology

You do not need a PhD in ecology. You do not need to live near a rainforest. If you can code, design, write, translate, or test software, there is a conservation project that needs you — today. Not after a training programme. Not after a career change. Now.

The open source conservation technology ecosystem is larger, more welcoming, and more desperate for contributors than most developers realise. Projects tracking endangered species, detecting poachers via AI, mapping deforestation in near-real-time, and giving rangers offline data collection tools that work on $50 phones — all of these are open source. All of them need help. And almost none of them require you to understand ecology before you can contribute.

This is a guide to exactly where to start. Not a think piece. A directory of projects, skills, and contribution pathways that are open right now. If you have ever wanted your skills to matter for the planet, here is where you begin.

Why Open Source Matters in Conservation

Conservation runs on five-year grant cycles. An NGO gets funded by a foundation, buys software licences, trains their staff, and integrates the tool into their workflow. The grant ends. The vendor raises prices or pivots to a different market. The tool becomes abandonware. The rangers who depend on it are left with unsupported software that gradually stops working on newer devices. This is not hypothetical. It has happened to field teams on every continent.

Open source breaks this cycle. When the code is public, the tool outlives its original funding. When CyberTracker’s original developer moved on, the community kept it running for 28 years. When SMART’s founders needed to guarantee longevity, they built an 8-organization partnership and merged operations with EarthRanger under the SERCA alliance. These projects survive because no single entity has to carry them alone. If you build something useful, and the code is open, it does not die when you move on.

There is a second reason: auditability. Conservation data increasingly ends up in court — poaching prosecutions, land rights disputes, environmental impact lawsuits. A closed-source app is a black box to a judge. You cannot prove the software did not alter the GPS coordinates. You cannot verify the timestamp chain. With open source tools, you can. The code is public. The data pipeline is inspectable. The chain of custody is verifiable from the moment a ranger taps “record” to the moment a prosecutor presents it as evidence. When species protection laws depend on data integrity, open source is not a preference — it is a requirement.

The third reason is community ownership. Conservation data collected with public funds — government grants, university budgets, NGO donations — should be held by public infrastructure. An open source tool that anyone can deploy, audit, and fork means the data stays with the community that collected it. No vendor lock-in. No proprietary formats. No “your subscription has expired, export your data in the next 30 days.” This is why ODK, used by the WHO for disease surveillance across 1.4 billion people, is open source. This is why EarthRanger, monitoring 900+ conservation sites, is free. This is why we built FieldLog under a permissive licence. The tools that protect what remains must belong to everyone.

What Skills Are Needed

Conservation technology is not one thing. It is a stack of interdependent problems — data collection, AI processing, hardware deployment, user interface, documentation, translation — and each layer needs different skills. Here is what is needed right now.

If you are unsure which path fits, start with documentation or translation. These are the highest-leverage, lowest-barrier contributions in open source, and conservation projects are critically under-resourced in both. A translated UI can unlock a tool for millions of people. A well-written setup guide prevents days of frustration for a field team that has no IT support.

Where to Start — Specific Projects

Here are the projects with open issues, contribution guides, and community channels that are welcoming contributors right now. Each one has a direct path from “I want to help” to “I shipped something.”

Microsoft MegaDetector / PyTorch-Wildlife

GitHub: microsoft/MegaDetector — Camera-trap animal detection AI used by 80+ conservation organisations.

Discord: discord.gg/TeEVxzaYtm

Contribute: Microsoft Biodiversity Contribution Guidelines

Needs: Python developers, ML engineers, documentation writers.

Start: Browse the PyTorch-Wildlife project board, pick a task from the “Ready” column, comment to claim it.

ODK (Open Data Kit)

GitHub: github.com/getodk — Offline data collection used by 2M+ people. 250M submissions annually.

Forum: forum.getodk.org — 17,000 members.

Contribute: docs.getodk.org/contributing

Open issues tagged “help wanted”: 5 on Central, 10 on Collect, 6 on Docs.

Needs: Kotlin (Android), JavaScript (Node.js/Vue.js), TypeScript, Python, technical writers.

iNaturalist / Seek

GitHub: github.com/inaturalist — 300M+ observations, 400K active users, the world’s largest biodiversity social network.

“Good first issue” tagged: Seek React Native (TypeScript).

“Help wanted” tagged: iNaturalist API (JavaScript).

Needs: TypeScript, React Native, JavaScript, Ruby on Rails, Java, Swift, Objective-C, translators, designers.

EarthRanger / SERCA

Website: earthranger.com — Real-time protected area monitoring. 900+ sites, 23K+ animals tracked. Now part of the SMART-EarthRanger Conservation Alliance (SERCA).

Community: community.earthranger.com

Beta programme: earthranger.com/beta

Needs: Beta testers, field testers, integration developers, documentation writers.

Zooniverse

GitHub: github.com/zooniverse — The world’s largest citizen science platform. 374 repos, 70+ active projects.

Active conservation projects: European Camera Trap Project, Cameras for Conservation, Snapshot Safari.

Code: JavaScript, Ruby, Python, React Native. No-code: Classify images directly on the platform.

SMART Conservation Software

Website: smartconservationtools.org — Patrol monitoring at 1,100+ sites in 95 countries.

Partners: WWF, WCS, Panthera, Frankfurt Zoological Society, ZSL, Re:wild, North Carolina Zoo.

Community forum: SMART Community Forum

Needs: Field testers, trainers, documentation translators (English → Spanish, French, Swahili, Portuguese).

SPARROW (Microsoft)

GitHub: microsoft/SPARROW — Solar-powered AI edge device. Full open-source BOM (bill of materials), assembly guide at aka.ms/sparrowassembly.

Needs: Hardware engineers, embedded systems developers, field deployers, Python developers, Docker tinkerers.

The Field Company / FieldLog

We are building a better CyberTracker — offline-first, AI-powered, free forever. Data collection for field researchers, designed for $50 phones and zero signal.

GitHub: github.com/thefieldcompany

Needs: React Native developers, Python/FastAPI developers, designers (icon sets, accessible mobile UI), translators (Zulu, Xhosa, Afrikaans, Swahili), field testers in Southern Africa. See the Join Us section below for specifics.

No-Code Ways to Help

You do not need to write code to contribute to conservation technology. Here is what you can do from your phone or laptop, right now, with zero setup.

iNaturalist — Photograph and Identify Species

Download the app, photograph a plant or animal, upload it. The community and AI will help identify it. Every verified observation trains species classification models and feeds the GBIF global biodiversity database. If you are a subject expert, spend 10 minutes a day verifying other people’s observations. The AI needs ground truth data to improve. You provide it.

eBird — Submit Bird Checklists

Every time you notice birds — a walk in the park, your back garden, anywhere — record what you saw in eBird. Millions of these casual observations power the models that track bird populations, migration patterns, and climate-driven range shifts globally. No expertise required. Start with the birds you can identify and learn more over time.

Zooniverse — Classify Camera Trap Images

Open European Camera Trap Project and start identifying animals. Or Snapshot Safari — African wildlife from camera traps across the continent. Or Savanna Spy: Sound — verify AI-classified bird calls from Texas savanna. Each classification is a training data point. Do a hundred, and you have meaningfully improved an AI model that researchers deploy at scale.

Translate — Unlock Tools for Millions

Most conservation tools are built in English, then need translation into Swahili, Portuguese, French, and dozens of local languages before field teams can use them. This is one of the highest-impact, lowest- barrier contributions in open source. ODK, iNaturalist, and FieldLog all need translators. You do not need to be a developer. You need to be fluent in a language used in a conservation area and willing to spend 30 minutes a week translating strings.

Share What You Find

Open source conservation projects suffer from a visibility gap. Most developers have never heard of MegaDetector or ODK. If you try a project and it works, tell people. Write a blog post. Post on LinkedIn. Send it to your team. The single biggest barrier to contribution is that people do not know these projects exist.

The People Who Do This

You do not need a conservation background to make conservation impact. Here are three profiles of people who contributed without one.

The Translator Who Unlocked East Africa

A university student in Nairobi, fluent in Swahili, English, and Kikuyu, started contributing Swahili translations to ODK Collect. Within six months, their translations were deployed to thousands of community health workers and conservation rangers across Tanzania, Kenya, and Uganda. They never wrote a line of code. They simply made an existing tool accessible to people who could not read English. If you speak a language used in conservation areas, your translation work has a direct line to impact that most code contributions will never match.

The Retired Teacher Who Trained AI

A retired teacher in the American Midwest spent 30 minutes a day identifying animals in Snapshot Safari camera trap images on Zooniverse. Over two years, their 20,000+ classifications became training data for species detection models deployed across African national parks. They were not a biologist. They were not a coder. They looked at photos of animals and clicked the right button. Consistent, careful work, repeated over time, directly improved AI that saves researchers months of manual image review.

The UX Designer Who Fixed Accessibility for 400,000 People

A designer tired of building corporate dashboards found iNaturalist Seek’s “good first issue” tag. They contributed accessibility improvements — larger touch targets, better colour contrast, clearer icon labels — that made the app usable for children, elderly users, and people with vision impairments. Their design work is now in the pockets of over 400,000 citizen scientists worldwide. They did not need to understand ecology, machine learning, or mobile development. They needed to understand users.

Join Us

We are The Field Company. We are building FieldLog — an open source, offline-first data collection platform for conservation. It works on $50 phones. It works without signal. It is free forever.

We need help. Specifically:

Developers: Python (FastAPI), React Native, offline sync architecture. Our stack is SQLite on device, PostgreSQL on server, delta-based sync protocol. github.com/thefieldcompany

Designers: Icon sets for African wildlife (mammals, birds, reptiles, insects, plants). Accessible mobile UI patterns for bright sunlight, gloved hands, low-literacy users. Low-bandwidth sync indicators that are impossible to miss.

Field Testers: Conservation researchers and rangers in Southern Africa. We need people running real expeditions with FieldLog and telling us everything that breaks. You are the most important contributor we have.

Translators: Zulu, Xhosa, Afrikaans, Swahili. These languages are spoken by millions of people in conservation areas. Our app is in English. This is a barrier we need to remove.

Writers: User guides. Developer docs. Tutorial videos. Field manuals. If you can write clearly about software, we have an endless supply of things that need explaining.

The code is open source. The roadmap is public. The community is growing. If you want your skills to matter for the planet, here is exactly where to start.

GitHub: github.com/thefieldcompany

Join the Discord (link coming — or email us through the site).

Community Hubs

These are the places where conservation technologists find each other, share work, and coordinate across projects.

The planet is under pressure. Species are disappearing. The people doing the work — rangers, researchers, community members — need tools that work, and they need them to be free and open. If you can write code, design interfaces, translate strings, test apps, or label images, you are already qualified to help. Pick a project from this post. Open a GitHub issue. Join a Discord. Make your first contribution. The tools that protect what remains need you.