00 / 08HOME
11 OCTOBER / INDEX

ELEVEN OCTOBER

SCROLL TO EXPLORE

The orbit

CONTINUE

Engineering begins by listening.

We don’t invent community problems. We begin with a need already raised by people, communities, maintainers, and organizations.

We investigate them, build practical solutions, test them, and share what we learn.

01 / PROBLEMS

Every problem
has an origin.

We don’t turn internal ideas into community requests. Each accepted problem keeps a link to the person, group, or public source it came from.

Requesters are named only with permission. A submission is reviewed before it is accepted.

Sources can include

  • Individuals and communities
  • Open-source maintainers
  • NGOs and organizations
  • Labs and universities
  • Public challenge platforms

1 PROBLEM PUBLISHED

Only verified, externally sourced problems appear here.
02 / METHOD

Understand
before building.

The work follows the evidence. The record includes the parts that did not work.

  1. 01

    Verify the problem

    Confirm the source, context, and people affected.

  2. 02

    Understand the system

    Study existing tools, constraints, and assumptions.

  3. 03

    Build the smallest useful solution

    Keep the first prototype focused on the need.

  4. 04

    Test it

    Measure results against stated success criteria.

  5. 05

    Document what failed

    Keep failed approaches and remaining limits visible.

  6. 06

    Open everything

    Publish the build, results, sources, and license.

03 / SOLUTIONS

Results are
earned in testing.

A project becomes part of the public record after its prototype, validation, limitations, repository, and contributors are documented.

1 project is in the public record. New orbits will be drawn from published project data, not placeholders.

Explore solutions
RECEIVEDINVESTIGATINGTESTINGPUBLISHED
04 / OPEN ARTICLES

Work leaves a trace.

Every published project becomes an open engineering article: what we learned, built, tested, and got wrong.

Articles link back to their source problem, project repository, contributors, references, and revision history.

Open the index
READ THE OPEN ENGINEERING INDEX
05 / GITHUB ISSUES

Have a problem
worth solving?

Open a GitHub issue with what is happening, who it affects, and what has already been tried.

Issues are public. Opening one starts a review; it does not mean the problem has been accepted.

Open a GitHub issue
  • What is happening?
  • Who experiences it?
  • What has already been tried?
  • What would a useful outcome look like?
  • Links or evidence that help explain it
06 / JOIN

Build with us.

Contribute to an active problem where your skills are useful.

ElectronicsEmbedded systemsFirmwareSoftwarePCB designMechanical designTechnical writingResearchTestingStudentsCurious builders