-------- Forwarded Message -------- Subject: Re: [DISCUSS - NuttX Workflow] Date: Wed, 18 Dec 2019 11:55:46 -0500 From: Nathan Hartman <hartman.nat...@gmail.com> Reply-To: dev@nuttx.apache.org To: dev@nuttx.apache.org
On Wed, Dec 18, 2019 at 11:18 AM Gregory Nutt <spudan...@gmail.com> wrote:
Requirements specification is a top-down activity. It is only driven by end users needs and project objects. NOT by implementation. That is the nature of System Engineering: top-down
Just throwing some thoughts out here as a starting point for that top-down discussion: Users of NuttX can: * Use NuttX with our Apps * Use NuttX by itself and provide their own Apps For the toolchain, they can: * Use the toolchains we provide with buildroot * Use their own toolchains They can get NuttX and/or apps: * From Git * From source release tarballs If getting from Git, they can: * Live on the bleeding edge with Master * Work from a branch or tag for more stability When they wish to contribute, they can do so: * Via a pull request * Via a patch transmitted to us by some method Regardless of the method, we would convert the pull request and/or patch into a form that is useful for us. For example, if we work with pull requests and we are given a patch, we convert the patch into a pull request. Contributions may be based on: * Master. * Or the latest release. When contributions are based on the latest release, we should rebase them onto master.
