Continuing the discussion from Porting a Daz3D Avatar?: Because, the discussion on licensing was derailing the thread.
This Monetization is discussed at
Now, branching off to your post earlier:
If content is placed in HiFI’s Github, that is then by default it is Apache License. And you tend to get compensated for the work if you do it via Worklist.
If you are hosting the assets them selves, High Fidelity acts as “browser” to display the content. Practically speaking you can apply your own licenses on them. Enforcing these Licenses, however is up to you, which practically applies for -all- of the content you place and host on the web, and it usually is presumed you have the right to do so, unless otherwise told not to host them.
However, After thinking this over, this will going to change once the new Asset Transfer Protocol gets implemented. Now we know this system will then be linkable through the marketplace. But what will the License be in this case? because technically the content can then be propagated in the cloud of domains, so one doesnt really have control of the asset if it gets shared (by choice)
With this, should there be an TOS for connecting one’s Domain to the cloud?
These are the questions we should ask next. And its a Legalese mess with parmesan cheese.