Skip to main content

Lists

Unordered list​

  • Project Quiver is an open source quadcopter platform
  • Designed for autonomous aerial mobility
  • Built and maintained by the Arrow community
  • Hardware designs are fully open source
  • Anyone can contribute, fork, or manufacture

Unordered — 2 levels​

  • Project Quiver
    • Open source quadcopter
    • Carbon fibre frame
    • Custom flight controller PCB
  • Project Spearhead
    • Fixed-wing VTOL
    • Long range autonomous flight
    • Designed for cargo and delivery

Unordered — 3 levels​

  • Hardware
    • Airframe
      • Carbon fibre arms
      • Injection moulded body panels
      • Aluminium motor mounts
    • Electronics
      • Flight controller
      • ESC stack
      • Power distribution board
  • Software
    • Flight stack
      • ArrowOS firmware
      • MAVLink telemetry
      • Failsafe routines
    • Ground control
      • Mission planner
      • Real-time telemetry

Ordered list​

  1. Fork the repository on GitHub
  2. Clone your fork locally
  3. Create a new feature branch
  4. Make your changes and commit
  5. Open a pull request against staging
  6. Wait for review and CI to pass
  7. Merge after approval

Ordered — 2 levels​

  1. Set up your environment
    1. Install Rust via rustup
    2. Install Node.js 18 or later
    3. Install the Arrow CLI
  2. Build the firmware
    1. Clone the ArrowOS repo
    2. Run cargo build --release
    3. Flash to the flight controller
  3. Run tests
    1. Unit tests with cargo test
    2. Integration tests with npm test

Ordered — 3 levels​

  1. Hardware assembly
    1. Airframe
      1. Attach motor mounts to arms
      2. Secure arms to centre plate
      3. Install landing gear
    2. Electronics
      1. Solder ESC pads
      2. Connect motors to ESCs
      3. Install flight controller
  2. Software setup
    1. Firmware
      1. Flash ArrowOS
      2. Configure parameters
      3. Calibrate sensors

Mixed — unordered inside ordered​

  1. Choose your contribution area
    • Hardware design
    • Firmware development
    • Documentation
  2. Read the relevant guide
    • Dev guide for firmware contributors
    • CAD guide for hardware contributors
  3. Join the Discord and introduce yourself
    • #hardware for mechanical and electrical
    • #firmware for ArrowOS and flight stack
    • #docs for documentation

Mixed — ordered inside unordered​

  • Before your first PR
    1. Sign the CLA
    2. Read the code of conduct
    3. Set up your local environment
  • During review
    1. Respond to all comments
    2. Keep commits clean and atomic
    3. Don't force-push to shared branches
  • After merge
    1. Delete your feature branch
    2. Update any linked issues
    3. Announce in Discord if it's a notable change

With inline code​

  • Run npm start to start the dev server
  • Run npm run build to build for production
  • Run npm run typecheck for TypeScript checks
  • Run npm run clear to clear the Docusaurus cache
  • Edit docusaurus.config.js to change site config
  • Edit sidebars.js to update the sidebar structure

With bold and emphasis​

  • Hardware — physical components including airframe, motors, and electronics
  • Firmware — the ArrowOS flight stack running on the flight controller
  • Ground control — mission planning and real-time telemetry software
  • Open source — all designs, code, and decisions are public
  • Decentralized — no single company owns Arrow

Long list items (wrapping)​

  • The Arrow project was founded on the belief that private air travel should be accessible to everyone, not just the wealthy, and that the technology to make this possible should be open and community-owned.
  • Project Quiver is our first platform — a quadcopter designed for repeatability and ease of assembly, using off-the-shelf components wherever possible to lower the barrier to participation.
  • The Arrow DAO governs all major decisions through on-chain proposals using the ARROW token, ensuring that no single entity can unilaterally change the direction of the project.

Checklist (task list)​

  • Set up local development environment
  • Sign the contributor licence agreement
  • Read the code of conduct
  • Open your first pull request
  • Get your first PR merged
  • Receive your first bounty payout
  • Become a named contributor

Checklist — nested​

  • Hardware
    • Order components from BOM
    • Assemble airframe
    • Install and configure flight controller
    • First hover test
  • Software
    • Flash ArrowOS firmware
    • Configure parameters
    • Run integration tests

Definition-style (bold term + description)​

  • CLA — Contributor Licence Agreement. Required before your first pull request is merged.
  • AIP — Arrow Improvement Proposal. The formal process for proposing significant changes.
  • GBC — Governance & Budget Council. The team responsible for stewarding the DAO treasury.
  • BOM — Bill of Materials. The full list of components needed to build a Quiver.
  • ESC — Electronic Speed Controller. Converts flight controller signals into motor power.

Very deeply nested (stress test)​

  • Level 1
    • Level 2
      • Level 3
        • Level 4
          • Level 5
            • Level 6
  1. Level 1
    1. Level 2
      1. Level 3
        1. Level 4
          1. Level 5
            1. Level 6