The m-lab/ndt GitHub repo is defined as a fork of the ndt-project/ndt repo. Are you planning on pushing your changes back upstream to ndt-project? If not, maybe you should make this repo a "canonical" one instead of a GitHub fork. The way it's set up now, GitHub users can't fork both m-lab/ndt and ndt-project/ndt because they're part of the same fork tree. Makes it a bit inconvenient to submit PRs to both.
Hi, M-Lab folks,
The m-lab/ndt GitHub repo is defined as a fork of the ndt-project/ndt repo. Are you planning on pushing your changes back upstream to ndt-project? If not, maybe you should make this repo a "canonical" one instead of a GitHub fork. The way it's set up now, GitHub users can't fork both m-lab/ndt and ndt-project/ndt because they're part of the same fork tree. Makes it a bit inconvenient to submit PRs to both.