...

• Submit a PR on GitHub against master if it is approved by one commiter (that did not propose it) it can be merged.  The approval is done via the GitHub approval system.

• A commiter may create a PR on behalf of a patch submitted to the mailing list.

• Commiters can ask for others to review or approve.  But at the end of the day they are the ones who approve and merge. 

Overview

Purpose

The purpose is simple: We'd like to help everyone participate in the future of NuttX by providing clear and open documentation on how to contribute.

This document can be declared a success if newbies and veteran NuttX developers alike find it valuable as both a how-to and a reference. We hope you'll find it easy to read and that it eliminates the need to hunt, memorize, or guess about parts of the workflow.

Enthusiastic Contributors Welcome!

NuttX is a free open-source project. If you'd like to participate, whether it's to enhance documentation (even this workflow document) or dive into the nitty gritty of some low-level drivers, please read on!

Also, join the conversation at our dev mailing list by emailing dev-subscribe@nuttx.apache.org. The mailing list is open to the public and archived. You can browse older messages at http://mail-archives.apache.org/mod_mbox/nuttx-dev/.

Where is The Code?

Document the GitHub repositories where all work takes place.

...