Hi Greg, We haven’t yet discussed the mentioned approaches and/or chosen one, so for now I think what you can do is this:
Currently, the same API that allows setting metadata such as summaries, descriptions and icons also supports setting the license (and modifies what is currently a per-snap value), so there should be no need to point users to the store dashboard, assuming you’re OK with doing frontend work for a feature which may well change if/when it is decided to manage the license data per-revision instead of per-snap.
API documentation should be here, the required value for license is an SPDX expression (which the store validates properly prior to storing, so if it’s bogus you’ll get a nice error message).
Similarly, at the moment the single per-snap license value is what should be presented. In any case, if we go forward with the per-revision license information, the implication of having store-side heuristics is that when queried for “what’s the license of this snap?” we would still return a single value, so for presentation purposes your end shouldn’t change that much.
Let me know if this makes sense or if you need more information!
Cheers!
- Daniel