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

Choose a new name for the project and replace uses of FINESSE everywhere. #352

Open
alexdewar opened this issue Oct 13, 2023 · 5 comments
Open
Assignees
Labels
must_have Specified as "must have" in the project proposal question Further information is requested

Comments

@alexdewar
Copy link
Collaborator

As we are now entering a new project (UNIRAS), it probably makes sense to rename this project from FINESSE, which was the name of the previous project. When starting UNIRAS we considered producing two separate pieces of software for different hardware used by the FINESSE and UNIRAS rigs (albeit with shared code between the two). As we have now decided that the best way forward is to produce a single piece of software which can be configured at runtime to use whatever hardware is needed from the set provided by the FINESSE and UNIRAS rigs, it makes sense to have a name for this software that is independent of both of the projects. As this is open source, the hope would be that in future other features can be added for other use cases (esp. in terms of other hardware, but possibly in terms of visualisation capabilities etc.) both within Imperial and also possibly outside, which is another reason to give it a broader name.

The options are:

  • Leave the name as FINESSE, which is the least effort, but doesn't advertise well that the software also works with other hardware and is being developed with UNIRAS funding
  • Rename it to UNIRAS. It would be a good way of trumpeting that the software is an output of this new project
  • Rename it to something else.
@alexdewar alexdewar added the question Further information is requested label Oct 13, 2023
@alexdewar alexdewar added the must_have Specified as "must have" in the project proposal label Dec 15, 2023
@alexdewar
Copy link
Collaborator Author

This is super low priority, but it would be nice to close it before the end of the engagement.

@sophiemosselmans and @sanjpand We're looking for a new name for the software as it's being used for two projects, so it'd be nicer to not just call it FINESSE. Any name suggestions welcome!

@jonemurray
Copy link
Collaborator

jonemurray commented Nov 21, 2024 via email

@sanjpand
Copy link

As we are now entering a new project (UNIRAS), it probably makes sense to rename this project from FINESSE, which was the name of the previous project. When starting UNIRAS we considered producing two separate pieces of software for different hardware used by the FINESSE and UNIRAS rigs (albeit with shared code between the two). As we have now decided that the best way forward is to produce a single piece of software which can be configured at runtime to use whatever hardware is needed from the set provided by the FINESSE and UNIRAS rigs, it makes sense to have a name for this software that is independent of both of the projects. As this is open source, the hope would be that in future other features can be added for other use cases (esp. in terms of other hardware, but possibly in terms of visualisation capabilities etc.) both within Imperial and also possibly outside, which is another reason to give it a broader name.

The options are:

  • Leave the name as FINESSE, which is the least effort, but doesn't advertise well that the software also works with other hardware and is being developed with UNIRAS funding
  • Rename it to UNIRAS. It would be a good way of trumpeting that the software is an output of this new project
  • Rename it to something else.

How about the Far-infraRed Observation Gui (FROG) Software!

@alexdewar
Copy link
Collaborator Author

I like it! ❤️

@jonemurray
Copy link
Collaborator

jonemurray commented Nov 21, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
must_have Specified as "must have" in the project proposal question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants