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

Implementation Plan: Copy updates mature -> sensitive #1965

Closed
Tracked by #383
sarayourfriend opened this issue May 2, 2023 · 0 comments · Fixed by #2126
Closed
Tracked by #383

Implementation Plan: Copy updates mature -> sensitive #1965

sarayourfriend opened this issue May 2, 2023 · 0 comments · Fixed by #2126
Assignees
@AetherUnbound
Labels
📄 aspect: text Concerns the textual material in the repository 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧭 project: implementation plan An implementation plan for a project 🧱 stack: mgmt Related to repo management and automations
Milestone
Sensitive content...

Comments

@sarayourfriend
Copy link
Collaborator

Description

Project proposal: https://docs.openverse.org/projects/proposals/trust_and_safety/content_report_moderation/20230411-project_proposal_content_report_moderation.html#update-copy-to-use-the-more-general-sensitive-language-requirement-1

Write an implementation plan to update copy from mature to sensitive in the frontend and Django API. To reiterate what is said in the project proposal, there should be no design changes or new features as part of this plan, only changes to copy. Field and model names should also be updated when possible, but without the need for database migrations (i.e., use Django's built in tools for specifying different underlying names for fields and tables).
@sarayourfriend sarayourfriend added 🟨 priority: medium Not blocking but should be addressed soon 🌟 goal: addition Addition of new feature 📄 aspect: text Concerns the textual material in the repository 🧱 stack: mgmt Related to repo management and automations labels May 2, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Openverse Backlog May 2, 2023
@sarayourfriend sarayourfriend added the 🧭 project: implementation plan An implementation plan for a project label May 2, 2023
@obulat obulat mentioned this issue May 3, 2023
Open
12 tasks
@AetherUnbound AetherUnbound moved this from 📋 Backlog to 📅 To do in Openverse Backlog May 16, 2023
@AetherUnbound AetherUnbound mentioned this issue May 18, 2023
Merged
2 tasks
@zackkrida zackkrida moved this from 📅 To do to 🏗 In progress in Openverse Backlog Jun 20, 2023
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in Openverse Backlog Jun 26, 2023
@sarayourfriend sarayourfriend mentioned this issue Dec 19, 2023
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AetherUnbound AetherUnbound

Labels
📄 aspect: text Concerns the textual material in the repository 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧭 project: implementation plan An implementation plan for a project 🧱 stack: mgmt Related to repo management and automations
Projects
Openverse Backlog
Archived in project
Milestone
Sensitive content moderation implemen...
Development

Successfully merging a pull request may close this issue.

Implementation Plan: Copy updates mature -> sensitive WordPress/openverse
2 participants
@AetherUnbound @sarayourfriend