Orb publishers grant CircleCI a broad license to orbs published in the registry under our Code Sharing Terms of Service

Going through the _Using Orbs_ documentation, it became pretty obvious that accepting the _Code Sharing Terms of Service_ was a prerequisite for publishing an Orb. It was a pretty big oversight on my part.

In that case, from a legal standpoint, I have no concerns with the publishing process.

It would still be nice to highlight the terms on the Orb page for regular users (for regular CI users who aren't admins of an Org, and therefore, would not have gone through the workflow that allows you to enable third-party Orbs if you accept the _Code Sharing Terms of Service_)

Also, as you noted, how to handle licensing for on-premise installations would also still remain a concern of mine.

This is definitely on our list to add. Worth noting in this context, CircleCI plans to provide a single license for all orbs in the registry (Orb publishers grant CircleCI a broad license to orbs published in the registry under our Code Sharing Terms of Service). We also need to build in ways to deal with licensing in our server installs where the currently plan is for each install to have its own registry.