Hi folks,
I've lately taken the task of packaging more activities to get us a reasonably user experience for the next iteration of SoaS. The normal review process requires an application to be properly and clearly licensed. I'd like to encourage activity authors to work on getting these clarifications, if needed, committed into GIT.
For example, if your activity doesn't contain a license file that states unambiguously the licenses of the *whole* activity and all of its bundled libraries, a kind of per-file licensing would be good, as some files would be otherwise without a license specification.
I'm not trying to make things up here, but am rather just realistic, as such things are simply blockers. I'll try to follow up with people...
Thanks, --Sebastian