@noskill I merged this, because it seems reasonable. Note however, that this repo is wildly out of date compared to work being done by @kasimebrahim and @ngeiswei who have made literally something like 1000 commits over the last year and a half that have not been merged into this repo.
I once again strongly and sharply encourage @kasimebrahim and @ngeiswei to merge all of their code so that we can have once single unique and obvious master branch for working code.
I strongly and sharply encourage pull requests and merges to be made every 5-50 commits, or after 1-7 days worth of work -- whenever some distinct working change/improvement/update/enhancement has been (mostly) completed. Waiting a year and a half to merge thousands of commits is not a wise development process. It endangers the project, and can lead to failures and breakdowns. It's a dangerous way to code.
@noskill I merged this, because it seems reasonable. Note however, that this repo is wildly out of date compared to work being done by @kasimebrahim and @ngeiswei who have made literally something like 1000 commits over the last year and a half that have not been merged into this repo.
I once again strongly and sharply encourage @kasimebrahim and @ngeiswei to merge all of their code so that we can have once single unique and obvious master branch for working code.
I strongly and sharply encourage pull requests and merges to be made every 5-50 commits, or after 1-7 days worth of work -- whenever some distinct working change/improvement/update/enhancement has been (mostly) completed. Waiting a year and a half to merge thousands of commits is not a wise development process. It endangers the project, and can lead to failures and breakdowns. It's a dangerous way to code.