Add a native license package attribute about rez HOT 1 OPEN

This is a great question. I'd like to think about it a bit longer, but offhand, I'm not sure my studio currently has a need to track licenses in a way that's tightly coupled to the rez package. I recognize you're probably thinking further ahead, and I'd love to discuss it at an upcoming meeting.

We definitely check licenses and are careful about any use restrictions, but our overall tracking is more associated with regular checks of the source code, bringing OSS into the studio, and specific handoffs. Our rez packages are only consumed within our studio and the licensing has already been managed at that point.

We don't use rez-pip due to limitations in the original, and are interested in the new version but haven't had a chance to try it out. The pip install domain certainly makes this more exciting, when dozens of dependencies are brought in automatically. We perform some checks of those dependencies.

It's absolutely valuable when licenses are clearly defined. There's too much ambiguity in the OSS world with how licenses are associated with code.

from rez.