microsoft / microsoft/ntttcp-for-linux
A new name to this tool?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 426
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
I know it is not a good practice to rename a tool, especially when there are lots of users are using it everyday.
Many people asked me questions that, ntttcp-for-linux actually is so different from the Windows version of ntttcp, why we still follow the name? Example of the difference is the tool options/usage. Keep such name (ntttcp-for-linux) would be confusing to some of us.
To be frankly, those are good questions. I am seriously considering to give a new name to this tool. For example, nspeed, or netspeed?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the tool's current name, usage, and differences from the Windows ntttcp version; done would require an agreed replacement name and a defined renaming scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100