>
> you spent a year developing a muscle plugin system. So you spend a year
> studying math, anatomy and any other useful resources to finally write your
> plugin from scratch. Would you not consider that intellectual property?

This definitely constitutes an IP.

Not talking about the implementation here, I suggest using some sort of
licensing. The Maya node/nodes should be licensed. Licensing term depends
on you but from what I understand, in your case, the node is to be used in
a rig. The clients should get a license for the node. How they use it
depends on them, maybe they use it on the rig you provided or maybe they
make their own rigs using the node. You can restrict activation of the node
based on the mac address of the machine. This ensures that the node is
licensed for 'a' machine. The clients can have as many rigs as they want
running on a machine. This will create a problem with rendering on the farm
if the client does not use any sort of caching (Alembic or something else)
where the mac address is not known beforehand. Either you have to supply
license for each rendering machine or you can give an unlimited number of
nodes for a reasonable discounted price. Usually, this is not a problem
because most modern pipelines use Alembic cache for rendering. So for
caching pipelines, you can supply a license for a number of seats. You can
even benefit from the floating license schemes, for that, you have to look
into license servers. Either way, this simply means that a license is used
per machine per Maya session.

I encourage you to start looking at the licensing workflows, understand
them and implement them in your code.

- Alok

-- 
You received this message because you are subscribed to the Google Groups 
"Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/python_inside_maya/CAPaTLMQXBAaEGLVij-k%3DKakCqULX4sVpvN-2q8mfUM4M2V6eCQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to