You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Activity
deanberris commentedon Jan 21, 2019
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 commentedon Jan 21, 2019
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 commentedon Jan 21, 2019
Actually, I like it as it is the "cpp-netlib" :).
glynos commentedon 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.