Add Creative Commons license to Learn page or footer

[scottveirs]

Feature request related to a problem? Please describe.

It's great that we enable the download of the "greatest hits" examples of calls, whistles, and clicks from the v3 learn page at https://live.orcasound.net/learn, but ideally we'd convey the Creative Commons licensing (BY-SA-NC) along with any download options. In the longer run, since ripping any audio stream is easy these days, it may be optimal to generally post the license within the web app.

Describe the solution you'd like

Short term: Add a discrete CC-BY-NC-SA icon below the sound clips?

Long term: Add a CC-BY-SA-NC icon in the footer of the entire web app so that it is always visible, and link it to the same sort of guidance that is currently in the footer of the Wordpress site (at orcasound.net) --

Here is the attribution text from that footer:

Please attribute with a hypertext link (text should be "Orcasound" and URL should be orcasound.net) and ask for permission before any commercial use via info@orcasound.net

Describe alternatives you've considered

1. Create a general licensing page within the new Orcasound web site (via orcahome repo) and then just link to it discretely from the web app. The page could have details about attribution for audio data, and maybe add links to Orcasound Github with some context for how we chose/choose to license software vs labeled data vs algorithms (Responsible AI Licenses)...

Additional context We might want to revisit licensing in next MOA for Orcasound and as a community, perhaps becoming more permissive over time?

For example, Orcasound currently uses CC-BY-NC-SA for audio data (and by proxy audio data products like labels), but we are poised to post human and machine detections into the Acartia data cooperative which itself only carries a CC-BY license...

[Filadora]

Overall Orcasite's buttons get a bit darker when hovering. Should we have that as a rule?

[paulcretu]

Draft looks good! BTW I'm pretty comfortable working with Figma so happy to drop comments directly if that's easier.

Overall Orcasite's buttons get a bit darker when hovering. Should we have that as a rule?

Short answer: for now, probably yes

Long answer: this is great to bring up, it touches on a really important topic—design systems and constraints.

We're using MUI as our UI library so a lot of what you're seeing is default behavior from MUI components. It's possible to make adjustments, but in general the less one-off customization, the faster we can build things. So it's important to choose wisely where we want to allocate resources (definitely something we should discuss next time we sync).

[scottveirs]

@Filadora I like the proposed designs for a record and share feature (e.g. within the v3 player) and the download/progress within an MUI or HTML audio element player... however, I think they should be provided via separate issues.

I say this because the features you've presented don't directly address the primary concern I was trying to express when I created this issue: the need for displaying our Creative Commons license within v3 of the web app. Any proposed designs regarding how to show the license -- at least on the Learn page, but ideally app-wide because folks do sometimes record the audio stream (using various tools to "rip" whatever is currently being played by their computer or through a particular browser window).

[Filadora]

@scottveirs I agree, these should not be here, my mistake.

[Filadora]

I removed the comments that didn't belong here to avoid any further confusion