As long as you stick to git only features you can have everyone work
on it, so branch bases workflow would be best. You can still use
GitHub only features but just don’t make them compulsory.
WRONG!
Not also that some more advanced features or options for GItHub that
have been discussed here e.g admin access, adding bots may or may not
be possible under the ASF. Infra is the admin of all repo and they
need to ensure that we know who has contributed code (which generally
means bots can’t have write access)and that git history can not be
altered.
The majority of users do not use GIT at all. NuttX distributions are
SCM neutral (all GIT information has been used). People on this list
have indicated that they use NuttX released with Apache SVN. I am are
of corporation that use proprietary SCMs with NuttX releases.
So the whole assumption is wrong. Assume that the NuttX user does not
use GIT, does not have GIT, and does not keep NuttX released under GIT
control. Nothing in the workflow must ever make that decision or we
screw a major part of the NuttX user base. Most companies will not
user Code due Jour from the GIT repositiies, they use the SCM-independ
NuttX releases.
Users get get release versions from the repository by checkout out or
branching from the Release tag. But the the release tarballs are SCM
agnostic.
Greg
