We’ve digressed a bit on this thread. Let’s see if we can reboot DavidS’ Workflow thread and keep the thread on topic.
Let me start by stating a few [obvious] objectives: Keep things simple for those NuttX users who prefer to work with a zip’d release. provide best-practice tools and workflow to maximize productivity of developers living on the bleeding edge. define a disciplined process that insures the continued quality of the project. As we fill in the details, this discussion will naturally blend in specifics of implementation and tools — I expect “git” might come up in the discussions ;) Cheers, -david > On Dec 17, 2019, at 1:36 AM, david.sidr...@gmail.com wrote: > > [DISCUSS - NuttX Workflow] > > I am creating this thread to discuss what we as a community would like to > have as NuttX Workflow. I have also created [REQUIREMENTS- NuttX Workflow] > I am asking us to not add discussion to [REQUIREMENTS- NuttX Workflow]. > Please do that here. > > As this discussion evolves we shall create requirements and add them > to the [REQUIREMENTS- > NuttX Workflow] thread. > > Please use [DISCUSS - NuttX Workflow] to propose and discuss the ideas > and experiences > you have to offer. > > Be detailed; give examples, list pros and cons, why you like it and why you > don't. > > Then after the requirements are gathered in one place and discussed here > then can vote on them. > > Thank you. > > David
