Bikeshed (sorry)
glynos opened this issue · 4 comments
The name "netlib" is already used for a very old piece of software that is still used for numerical computations:
I'd like to consider a naming scheme (brand?) that we can use for the library and to identify sub-components.
Indeed -- the repository name is sufficient I think, and we should keep calling it cpp-netlib as a project.
I would still like to call the project "cpp-netlib" just the "netlib" repository. In my head (and notebooks) I've been calling it "v2" even though we've never gotten v1 out the door. :)
Although I think you might be raising a larger point, which I definitely value feedback on -- should we even still be calling the project "cpp-netlib" or should we be calling it something else? Definitely happy to discuss this further.
Actually, I like it as it is the "cpp-netlib" :).
I am only worried about the naming conflict with another project. If no-one else is concerned by this, then we'll continue with the same name.