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

Terminology Alignment - Artifact vs Artefact #519

Open
fdegir opened this issue Aug 5, 2024 · 1 comment
Open

Terminology Alignment - Artifact vs Artefact #519

fdegir opened this issue Aug 5, 2024 · 1 comment
Labels
enhancement New feature or request triaged The team has reviewed the issue

Comments

@fdegir
Copy link
Contributor

fdegir commented Aug 5, 2024

The terms, artifact and artefact, are used interchangeably both in the codebase and the documentation which makes it a bit challenging to read the codebase and the documentation and could perhaps cause issues during the development as well.

It would be beneficial to align the terminology and use either artifact or artefact.

Please note that similar issue exists in other repositories under suse-edge org as well, such as the end user documentation. (artifact vs artefact)

@jdob jdob added enhancement New feature or request triaged The team has reviewed the issue labels Aug 16, 2024
@jdob jdob changed the title [RFE] Terminology Alignment - Artifact vs Artefact Terminology Alignment - Artifact vs Artefact Aug 16, 2024
@hardys
Copy link
Contributor

hardys commented Aug 23, 2024

Ref this conversation from a docs perspective we should align with the US English variant e.g "Artifact" - to avoid making a backwards incompatible change I suspect that means we'll have to support both directory names in EIB?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triaged The team has reviewed the issue
Projects
None yet
Development

No branches or pull requests

3 participants