Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bikeshed (sorry) #6

Open
glynos opened this issue Jan 18, 2019 · 4 comments
Open

Bikeshed (sorry) #6

glynos opened this issue Jan 18, 2019 · 4 comments

Comments

@glynos
Copy link
Member

glynos commented Jan 18, 2019

The name "netlib" is already used for a very old piece of software that is still used for numerical computations:

http://www.netlib.org/

I'd like to consider a naming scheme (brand?) that we can use for the library and to identify sub-components.

@deanberris
Copy link
Member

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. :)

@deanberris
Copy link
Member

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.

@jamesjallorina
Copy link

Actually, I like it as it is the "cpp-netlib" :).

@glynos
Copy link
Member Author

glynos commented Jan 21, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants