The Open Inverter Community

Open Inverter exists because a handful of people decided to reverse engineer expensive proprietary hardware and release the results as open source. That's not a small thing. It's the foundation everything else here is built on, and it's worth understanding before you start participating, because the social contract isn't always obvious from the outside.

This page is the orientation that most communities don't bother writing down. Read it before you post.

Open source is not a free service

The most common misunderstanding here is treating open source like a product with support included. It isn't. Open source means the work is shared so others can use it, modify it, and build on it. It does not mean the people who did the work owe you their time when you have questions about your specific build.

The developers, contributors, harness makers, video documenters, and forum regulars are not staff. There is no help desk. There is no ticket queue. There are people, doing this in their spare time, sometimes answering questions because they want to, sometimes not, on their schedule, not yours.

If you need guaranteed support, paid application support exists. That's the right channel for someone who needs an answer on a timeline. Everything else is a favor when it happens.

What a community actually is

A community is a group of people who give and take with each other. Help and be helped. Teach and learn. Build and use what others built. Everyone takes from it sometimes and everyone contributes to it sometimes. The balance doesn't have to be even on any given day, or even any given year, but over time it has to roughly work out, or there's no community left.

Someone has to give for someone to take. Every hour of help received is an hour someone else gave up to provide it. Every answered question, every documented build, every reverse engineered protocol, every wiki page, all of it is time someone chose to spend on the community instead of on themselves.

The problem starts when someone only ever takes, never gives, and doesn't notice the other side exists. People who do that consistently use up more than they replace, and over time there's less of the community left for everyone else. If you've been around a while and can't think of anything you've contributed back, that's worth noticing. (Why this matters mathematically, for the curious.)

What Patreon and buying a board actually fund

Patreon supports the work. It funds a developer's time to keep reverse engineering, keep documenting, keep releasing firmware updates. It is not a retainer for personal technical support. Some money a month, whatever the amount, does not buy a private help line.

Buying a turnkey board funds the development that made the board possible, plus the cost of building it. It is not a support contract. The board comes with a working design and the right to ask questions in the public forum like everyone else.

Both of these keep the project alive. Neither obligates a specific person to answer your specific question on your specific schedule.

Worth noting: a small number of buyers have abused refund systems on payment platforms, which is part of why some sales have moved to non-refundable methods. The honest majority pays the friction cost for the dishonest few. It's worth being aware of.

What contribution looks like

Contribution isn't only writing firmware or reverse engineering inverters. The range is wider than most people realize:

Building something interesting and posting your journey, including the failures
Documenting the answer to your own question after you figured it out, so the next person finds it
Writing wiki pages, adding to existing ones, fixing broken links
Making harnesses, adapter plates, or other parts the community needs
Recording video walkthroughs as you learn, which captures beginner questions experts forget to answer
Pulling scattered information into organized learning resources
Translating documentation
Answering forum questions you happen to know the answer to
Donating to people whose work you've used

Use what your skills and time allow. Anything that reduces the load on the next person counts.

How to ask for help well

Needing help is normal. Everyone here needed help at some point. The difference between an easy question to answer and a hard one is usually not the technical difficulty, it's how the question is asked.

If you're going to ask, ask in a way that respects the people who might answer:

Search first. Forum, wiki, github issues, youtube. Most questions have been answered already.
Document what you tried. "It doesn't work" is not a question. "I did X, expected Y, got Z, here's the relevant log" is a question.
Post in the forum, not in DMs. Forum posts get searched and help future readers. DMs help one person and disappear. Developers especially are buried in private messages and email.
Share specifics. Hardware version, firmware version, what you're trying to do, what's actually happening, photos or scope traces if relevant.
Accept that an answer may take time, or may not come. No one is paid to answer you. Nudging once after a few days is fine. Bumping every hour is not.
When you figure it out, post the answer. This is the single highest leverage thing a help receiver can do. It gives back to the community and helps the next person.

Keeping the project alive

Open hardware projects don't die because the technology fails. They die because the contributors and maintainers walk away. Every major one that has shut down, shut down because the people doing the work got tired of carrying the social load on top of the technical load and decided they were done. A contributor who documents stops documenting. A maintainer who reviews changes stops reviewing. The work doesn't get picked up by someone else, it just stops.

The best thing any community member can do is be the kind of participant who makes the work sustainable instead of draining. That doesn't require special skills. It mostly comes down to asking well, contributing what you can, and noticing when the people who give a lot are starting to look tired.

Quick reference

The rest of this page covered the why. Here's the practical summary.

If you're new here:

Read the wiki before posting
Search the forum before posting
Ask in the forum, not in DMs
Share what you tried and what specifically failed
Post the answer when you find it

If you've been here a while:

Notice when you're consuming more than you're giving back
Find a contribution that matches your skills, even a small one
Consider supporting the developers whose work you've used

For the people behind this work, see Who we are.

The Open Inverter Community

Contents