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

API endpoint for licenses #732

Open
lenasterg opened this issue Feb 11, 2022 · 2 comments
Open

API endpoint for licenses #732

lenasterg opened this issue Feb 11, 2022 · 2 comments
Assignees
@dhruvkb
Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: api Related to the Django API 🔧 tech: django Involves Django

Comments

@lenasterg
Copy link

Problem

Currently, there is no Openverse API endpoint for the available/deprecated licenses.

Description

An API endpoint for the licenses which it could contain for each license also info data ex:

  • shortname ex: BY-SA
  • Full name ex: Attribution-ShareAlike 4.0 International
  • icon url: ex: The black color icon URL
  • description: A short description
  • Use: ex: Commercially or Not
  • more info url: The URL of the license info ex: https://creativecommons.org/licenses/by-sa/

Ideally, there should be language-based endpoints URL so the above info can be changed by the localization teams.
@lenasterg lenasterg added ✨ goal: improvement Improvement to an existing user-facing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Feb 11, 2022
@dhruvkb dhruvkb self-assigned this Feb 11, 2022
@dhruvkb dhruvkb added 🔧 tech: django Involves Django 🌟 goal: addition Addition of new feature and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing user-facing feature labels Feb 11, 2022
@lenasterg lenasterg mentioned this issue Feb 11, 2022
Open
@krysal
Copy link
Member

krysal commented Feb 11, 2022

Related to #749.

@sarayourfriend
Copy link
Contributor

@krysal Is this a duplicate of the issue you linked? Maybe we can merge them into a single issue. If we parse the full list of issues from the license spec sheet as suggested in the other issue we wouldn't need to maintain internationalisation stuff as suggested by this issue. There might not be anything specifically in this issue that wouldn't be covered by the other. What do you think?

@obulat obulat transferred this issue from WordPress/openverse-api Feb 22, 2023
@obulat obulat added 🧱 stack: api Related to the Django API and removed 🧱 stack: backend labels Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dhruvkb dhruvkb

Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: api Related to the Django API 🔧 tech: django Involves Django
Projects
Openverse Backlog
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
5 participants
@lenasterg @krysal @obulat @dhruvkb @sarayourfriend