-
Notifications
You must be signed in to change notification settings - Fork 16
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
Discussion: Change the name of this repository to a more appropriate name #106
Comments
Makes sense! I like either of the first two names. While the repo is entirely python, naming the repo with tools/utils seems the most descriptive. |
My mind went to Now, if the powers-that-be also decided to exclusively make this repo a place for Python tools, then adding the Also, fwiw, I'd be worried about just |
My first thought was ngen-toolbox, but I think ngen-tools and ngen-utils may be better/more concise but just as descriptive. Some other thoughts; ngen-pybox, ngen-pytools, ngen-utilipys, ngen-pyhelpers, ... I actually kind of like ngen-pybox. |
I'm quite ok with scrapping the
Some perhaps more apt descriptive names from an AI generator
Though as I write this, the |
Yeah, I like where your mind is wandering @hellkite500. Why not just |
I'm a lazy typer, and Other than that, no real preference between the two. |
I'm leaning toward Consider mine another vote against naming the repository with |
My biggest concern with |
We can try to hold something of a line against accepting PRs like that into this repo |
Revisiting this with some fresh thoughts. Here are a few other options:
|
@aaraney, my immediate reaction to those latest three was, "why?" And I mean that in the purest sense: they seem neither appropriate nor inappropriate at first glance, so I'm curious what was behind those.
@hellkite500, that's a valid concern, but I don't think it aligns well with what's happened in practice with the repo. I.e., where exactly is the line for what belongs here versus what doesn't? If we have to be very nuanced to unambiguously describe that line, we probably can't come up with any suggestive, concise name for the repo that doesn't risk misinterpretation. In which case, we'd either have to accept that risk or adopt a name that does not imply purpose and/or contents of the repo, forcing people to learn those things more deliberately (maybe that's what was behind those last three suggested names?). Alternatively, it may be appropriate to rethink whether the repo name is right and it is the contents that need to be changed/moved. That's not a small question, but this issue comes up because things that maybe could/should have gone somewhere else were put in this repo. At least relative to it's prior contents at the time, this seems like using the repo in a way much like what Nels was concerned about. And it might be difficult going forward to clearly define rules for what does and doesn't belong if the history of the repo is inconsistent with the general principles behind how we'd want to distinguish things now. |
Just trying to come up with names that were a bit more fun and included a play-on-words. Im certainly open to something like that. |
For better or worse, this repository has become the landing space for many NextGen related tools. Namely, tools for calibration, realization configuration, init config representation, and configuration generation. I like that this repo is operating as monorepo for a lot of our tooling around NextGen. It is so far, easy to maintain and once you've found it, you've found the majority of tooling around NextGen. However
ngen-cal
is no longer an appropriate name. For our sake and more so, the communities sake, I think we should adopt a new repo name sooner rather than later. A different name that better encapsulates the tools in this repo will help others discover these tools and hopefully drive usage of these tools.To start the discussion, below are a few suggestions. Please think about this carefully and add others that come to mind before reading my suggestions.
ngen-tools
ngen-utils
ngen-py
ngen-tooling
The text was updated successfully, but these errors were encountered: