Skip to content

Bikeshed (sorry) #6

Open
Open
@glynos

Description

@glynos
Member

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.

Activity

deanberris

deanberris commented on Jan 21, 2019

@deanberris
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

deanberris commented on Jan 21, 2019

@deanberris
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

jamesjallorina commented on Jan 21, 2019

@jamesjallorina

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

glynos

glynos commented on Jan 21, 2019

@glynos
MemberAuthor

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @glynos@deanberris@jamesjallorina

        Issue actions

          Bikeshed (sorry) · Issue #6 · cpp-netlib/netlib