AcademySoftwareFoundation / AcademySoftwareFoundation/rez
Questions about package organisation and names
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 369
- Avg merge
- 12d 3h
- Merged PRs (30d)
- 5
Description
We're starting to get some more traction with Rez at Imageworks, and discussions around how to structure our package locations and their naming have been popping up frequently. I am curious about how other studios handle the questions below.
- Do you have one single, flat location where you put all of your packages? Or do you split them up by department, and/or application (Maya, Houdini), and/or by some other scheme? Are there clear advantages/disadvantages to one approach over others?
- What kind of package naming scheme do you use? For example, how do you distinguish between a package called, say, `mathTools` for Houdini vs `mathTools` for Maya? We were thinking of using prefixes (like `mayaMathTools`, `houMathTools`) for easy sorting and browsing, but I am wondering if there are best practices for this.
Both of these seem like the kinds of things that reveal gotchas only after you've tried them out for real. If anyone can share their experiences I would love to hear them :) Thanks!
Contributor guide
Research direction
No files, tests, or entry points are identified. Review the discussion first and establish whether the outcome should be documented guidance or a concrete package-organisation change; done requires an agreed, actionable scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100