Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add dedicated page about the licenses #644

Closed
1 task
zackkrida opened this issue Aug 12, 2021 · 2 comments
Closed
1 task

Add dedicated page about the licenses #644

zackkrida opened this issue Aug 12, 2021 · 2 comments
Labels
🕹 aspect: interface Concerns end-users' experience with the software design: needed Needs a designer's touch before implementation can begin 🌟 goal: addition Addition of new feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: frontend Related to the Nuxt frontend 🔒 staff only Restricted to staff members

Comments

@zackkrida
Copy link
Member

Problem

In the future we may support licenses other than CC licenses, only for content types, like software and fonts, where CC licenses are not commonly used. In doing so we would want a dedicated content page to discuss the licenses used on Openverse.

Additionally, having rich content about the CC licenses and others would be beneficial for SEO regarding searches for those licenses.

Description

Create a new 'licenses' page with some copy about the various licenses in Openverse and their features. We can and should continue to link to 3rd party references like cc.org.

Alternatives

Additional context

Implementation

  • 🙋 I would be interested in implementing this feature.
@zackkrida zackkrida added 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing user-facing feature 💻 aspect: code Concerns the software code in the repository labels Aug 12, 2021
@zackkrida zackkrida added good first issue New-contributor friendly help wanted Open to participation from the community 🌟 goal: addition Addition of new feature 🕹 aspect: interface Concerns end-users' experience with the software and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing user-facing feature 💻 aspect: code Concerns the software code in the repository labels Sep 14, 2021
@AndreWillomitzer
Copy link

Hi there @zackkrida hope you are well. Do you mind if I ask what still needs to be done on this issue? I am looking for a repo to contribute to.

I noticed you already went ahead and created the License.vue page and I see the license.js file where you import the logo names/images from.

I would be interested in helping once I know a little more!!!

Thanks,

Andre :)

@zackkrida zackkrida changed the title [Feature] Add dedicated page about the licenses Add dedicated page about the licenses Dec 18, 2021
@krysal krysal added the design: needed Needs a designer's touch before implementation can begin label Feb 14, 2022
@sarayourfriend sarayourfriend added 🕹 aspect: interface Concerns end-users' experience with the software and removed 🕹 aspect: interface Concerns end-users' experience with the software labels Apr 22, 2022
@fcoveram fcoveram mentioned this issue May 13, 2022
Closed
@obulat obulat added 🔒 staff only Restricted to staff members and removed good first issue New-contributor friendly help wanted Open to participation from the community labels Nov 19, 2022
@obulat
Copy link
Contributor

obulat commented Nov 19, 2022

I added the 'staff only' label because this issue requires writing and approving a new copy for the page.

@obulat obulat transferred this issue from WordPress/openverse-frontend Feb 22, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Openverse Backlog Feb 23, 2023
@obulat obulat added the 🧱 stack: frontend Related to the Nuxt frontend label Feb 24, 2023
dhruvkb pushed a commit that referenced this issue Apr 14, 2023
@stacimc @zackkrida
Use Airflow variable to omit DAGs from any Slack notification (#644)
cec6893 
* Add DAG to check for DAGs that need alerts reenabled

* Add tests

* Add test that send_alert skips

* Update message format to prevent links unfurling

* Rename files and small refactor to make it easier to add silenced notifications as well as alerts

* Update send_message to conditionally omit dags from slack notifications

* Update reporting to pass dag_id to send_message

* Update tests

* Add notifications configuration check to DAG

* Make dag_id required argument to ensure all Slack messages are skipped

* Make single variable for silencing notifs of all types, allow different issues

* Update record reporting

* Only allow one predicate per github issue

* Add types for clarity

* Update check_silenced_dags DAG

* Change order of functions

* Correct default for slack_message_override

* Consolidate DAG to one file, update docstring, fix send_alert

* Quote predicate in slack message

* Update dag docs

* Fix typo

Co-authored-by: Zack Krida <[email protected]>

* Update DAG docs with fixed typo

Co-authored-by: Zack Krida <[email protected]>
@stacimc stacimc mentioned this issue Apr 17, 2023
Open
1 task
@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in Openverse Backlog Aug 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🕹 aspect: interface Concerns end-users' experience with the software design: needed Needs a designer's touch before implementation can begin 🌟 goal: addition Addition of new feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: frontend Related to the Nuxt frontend 🔒 staff only Restricted to staff members
Projects
Openverse Backlog
Archived in project
Milestone
No milestone
Development

No branches or pull requests
6 participants
@fcoveram @zackkrida @krysal @obulat @sarayourfriend @AndreWillomitzer