Skip to content

Projects

Type Started by Approval
Personal Any member None, just register it
Community Any member A lead and a short charter
Official OASA Builder+ proposal or Core Founder (later the Core council)
Contract The company Company and client

Projects can graduate from personal to community to official.

Level Who can work on it
Open to members Any member can start
Apply or invite Members the lead approves
Contract Members hired through OASA Engineering

One page: name and goal, tech tree nodes, lead and team, access level, first milestone, help needed.

Projects post what they need: skills, parts, money. Members jump in and get credited.

Personal projects can keep their work private, but every project has a public listing (name, goal, who’s on it, tech tree link) so others can find it and offer help.

Idea → Registered → Active → Milestone → Released → Maintained → Archived

Post an update when you hit a milestone or get blocked. Blockers can become new project opportunities on the tech tree.

A project with no progress for 90 days is archived. Anyone can pick it up and fork it. For private projects, the creator chooses at registration whether the work opens on archive or stays private. The public listing always stays available.

A project is released when it has a working build, docs someone else can follow, a bill of materials (for hardware), test results, a security review (for anything that communicates) and a training guide.

Funding, makerspace time, partner parts, mentors and promotion.

Have an idea but no project yet? Post it on the idea board.