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.

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

mature -> sensitive code changes for the API #3723

Closed
AetherUnbound opened this issue Jan 30, 2024 · 1 comment · Fixed by #3769
Closed

mature -> sensitive code changes for the API #3723

AetherUnbound opened this issue Jan 30, 2024 · 1 comment · Fixed by #3769
Assignees
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API

Comments

@AetherUnbound
Copy link
Collaborator

Description

Change code references of the term "mature" to "sensitive". This work is described in the implementation plan here: https://docs.openverse.org/projects/proposals/trust_and_safety/content_report_moderation/20230517-implementation_plan_mature_copy_change.html#code

Additional context

Part of #383

@AetherUnbound
Copy link
Collaborator Author

Note to myself: We may need to do this in two parts:

  1. Explicitly define the table name on the existing model (results in a no-op)
  2. Rename the table and all references while leaving the defined table name untouched (also a no-op)

@openverse-bot openverse-bot moved this from 📅 To Do to 🏗 In Progress in Openverse Backlog Feb 8, 2024
@openverse-bot openverse-bot moved this from 🏗 In Progress to ✅ Done in Openverse Backlog Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant