Hi Nathan, Great list!
I can +1 on most of them, but isn't correct that the PPMC will need to all agree on these? > When they wish to contribute, they can do so: > * Via a pull request > * Via a patch transmitted to us by some method Is this an ASF edict? > 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. Where is the ability to have group a review? How is it done? > Contributions may be based on: > * Master. > * Or the latest release. When contributions are based on the latest > release, we should rebase them onto master. What If the fix on master? Would it need to be backported to the release? How do you see the decision made on backports and who does this? David -----Original Message----- From: Nathan Hartman [mailto:hartman.nat...@gmail.com] Sent: Wednesday, December 18, 2019 8:56 AM To: dev@nuttx.apache.org Subject: Re: [DISCUSS - NuttX Workflow] 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.
