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

Remove OpenPype and avalon references #11

Open
5 tasks
iLLiCiTiT opened this issue Sep 11, 2024 · 0 comments
Open
5 tasks

Remove OpenPype and avalon references #11

iLLiCiTiT opened this issue Sep 11, 2024 · 0 comments
Labels
type: maintenance Changes to the code that don't affect product functionality (Technical debt, refactors etc.))

Comments

@iLLiCiTiT
Copy link
Member

iLLiCiTiT commented Sep 11, 2024

Description

Make AYON and ayon naming as first class citizen for all functionality and metadata naming in repository.

Ideal goal is that openpype, pype and avalon are not mentioned anywhere in codebase. But that probably won't be possible because of backwards compatibility.

Codebase requirements

  • Instances and containers do use AYON_INSTANCE_ID and AYON_CONTAINER_ID instead of AVALON_INSTANCE_ID and AVALON_CONTAINER_ID (constants from ayon-core).
  • If there are metadata stored to scene, we're referring to them as "ayon" metadata and not "openpype", "pype" or "avalon".
  • If there are metadata related to folder, it is not referred to it as "asset" (OpenPype term) - Use correct folder path or folder name based on functionality.
  • If there are metadata related to product, it is not referred to it as "subset" (OpenPype term)
  • If there are metadata related to product type, it is not referred to it as "family", except for publishing (OpenPype term)

And codebase need to change any of that, we must make sure it can be backwards compatible (read older scenes).

Create separate issues if it should be split to multiple PRs, and close the issue if all conditions are met.

@iLLiCiTiT iLLiCiTiT added the type: enhancement Improvement of existing functionality or minor addition label Sep 11, 2024
@jakubjezek001 jakubjezek001 added type: maintenance Changes to the code that don't affect product functionality (Technical debt, refactors etc.)) and removed type: enhancement Improvement of existing functionality or minor addition labels Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: maintenance Changes to the code that don't affect product functionality (Technical debt, refactors etc.))
Projects
None yet
Development

No branches or pull requests

2 participants