There are three different concepts being discussed here that I think we should separate. I know that I get confused about which is which. 1. Two repositories apps/ and nuttx/ -- GOOD 2. One respository with apps/ and nuttx/ as folders -- VERY, VERY BAD 3. Three repositories, apps/, nuttx/ and, say, testing/. Where testing has the apps/and nuttx/ as submodules -- WORTH CONSIDERINGThanks for summing this up. I think this correctly summarizes what was said before. I agree that #2 is very very bad.
#3 should be thought of an implementation strategy. In this thread, we are trying to summarize and agree to the high level, logical steps of the workflow. I don't think that implementation details should even be a part of the conversation. Mixing discussions of implementation into a description of functional requirements is bad engineering and cannot lead to a successful definition of the functional requirements.
My preference is that we forget about github altogether for now for the purpose of communicating functional requirements clearly. Let's forget want what is the cleanest and easiest implementation for now. Let's specify the behavior that we want, the nicest thing in the show window, not the lowest cost thing in the bargain bin.
Greg
