Skip to main content

Code of Conduct

How we expect people to work together at Arrow — a permissionless, open-source community building the future of air travel.

Arrow wants to make air travel affordable, accessible, and ubiquitous — and we think infrastructure this important should be built in the open, by the people who use it. That's why Arrow is permissionless: anyone with a good idea and the will to act can show up and contribute.

That freedom comes with responsibility. Everyone here can speak, build, and publish freely, and everyone is accountable for what they do with that. Here's what we expect.

Own your work​

Arrow has no managers and no approval chains. Nothing gets done unless people take it on themselves. If you commit to something, do it. If you start something, finish it or hand it off clearly.

Ownership doesn't stop at your own tasks. If you see something broken, fix it or flag it. If a project is drifting because nobody's paying attention, that's on all of us. We expect people to care about the health of the whole community, not just their corner of it.

Bias for action​

The fastest way to find out if something works is to try it. We don't require consensus or permission to take initiative — we expect it. If you're in a discussion that could be resolved by just doing the thing, do the thing. If you're waiting for approval that hasn't come, ask yourself whether you actually need it.

Some work will get thrown away. That's fine. Moving fast and occasionally being wrong is cheaper than moving slowly and waiting for certainty.

This doesn't mean skipping coordination. It means not using coordination as a substitute for action.

Default to transparency​

Everything that can be public, should be — your work, your reasoning, your decisions, your mistakes. Arrow is open source for exactly this reason.

Write things down. If you made a decision, explain why. If you changed direction, note what changed. Prefer public channels over DMs. Prefer GitHub issues and PRs over private conversations. If a useful discussion happened in private, summarize it somewhere the community can see.

Don't create noise; create context.

Communicate directly​

Say what you think. If someone's work isn't good enough, tell them. If you disagree with a direction, say so clearly. Vague feedback helps no one.

Direct doesn't mean harsh. Critique the work, not the person. Be specific about what isn't working and what would be better. The goal is to help the project and the people in it improve, not to score points.

When reading someone else's actions or words, assume positive intent. Most people are trying hard with limited time and context. If something falls short, missing information is the more likely explanation than bad faith.

Be a good collaborator​

Arrow is a global community. People from different backgrounds, time zones, and skill levels work here. That only works if people treat each other with respect.

Be kind, professional, and welcoming — especially to people who are new. A contributor who asks a basic question probably just doesn't have the context yet. Give it to them.

We do not tolerate:

  • Harassment, discrimination, or personal attacks of any kind
  • Bigotry or hate speech of any kind
  • Dismissing or talking over people based on their background, experience level, or identity
  • Bad-faith participation — derailing discussions, ignoring settled decisions, or relitigating outcomes without new information

These apply everywhere Arrow contributors interact: Discord, GitHub, the DAO Forum, community calls, and any other Arrow-affiliated space.

Work asynchronously​

Most Arrow contributors are spread across time zones and work irregular schedules. Don't design your work around synchronous availability.

Write clearly enough that someone reading your PR, issue, or forum post 48 hours later has everything they need. Don't leave decisions dangling in Discord threads that will scroll away. If something needs a response, put it somewhere permanent.

You're not expected to respond immediately. You are expected to respond.

Disagree well​

You will disagree with decisions here. That's healthy. Make your case clearly — once, with reasoning — and then accept the outcome or escalate through the proper process: an AIP, a conflict resolution request, or a formal objection.

Passive resistance isn't acceptable: ignoring a decision, quietly building around it, or relitigating it indefinitely. If you think something is wrong, say so and explain why. If the argument doesn't carry, respect the outcome and move on.

Conflict resolution​

When conflict between contributors or Pods can't be resolved directly, Arrow has formal processes:

  • Pod-to-pod conflicts are facilitated by the Growth/Ops Pod and documented publicly.
  • Conflicts within a Pod are handled by the Pod Facilitator. A running log of internal conflicts and outcomes is maintained and available to all members.
  • Individual conflicts are handled by the relevant Pod Facilitators, or — if neither party is in a Pod — by the Community Pod.

Unresolved conflicts can be escalated to the Growth/Ops Pod.

Grievances about toxic culture, bad-faith behavior, or a hostile environment within a Pod are grounds for that Pod's termination.

Enforcement​

Violations can be reported in the DAO Forum or directly to a core contributor. Serious or repeated violations may result in removal from Arrow spaces and, in extreme cases, revocation of membership by DAO vote.

This Code of Conduct applies across all Arrow community spaces. It complements the Arrow Constitution, which governs formal DAO operations.