Skip to content

AO3-7451 Add technical integrity TOS FAQ link to Terms of Service#5819

Open
annieyx-cpu wants to merge 2 commits into
otwcode:masterfrom
annieyx-cpu:AO3-7451
Open

AO3-7451 Add technical integrity TOS FAQ link to Terms of Service#5819
annieyx-cpu wants to merge 2 commits into
otwcode:masterfrom
annieyx-cpu:AO3-7451

Conversation

@annieyx-cpu
Copy link
Copy Markdown

Pull Request Checklist

Issue

https://otwarchive.atlassian.net/browse/AO3-7451

Purpose

What does this PR do?
Links the technical integrity TOS FAQ to the Terms of Services (I.F.6) under the text “interrupt, destroy, or limit the functionality”.

Testing Instructions

How can the Archive's QA team verify that this is working as you intended?
Checkout this change and open localhost to this link https://test.archiveofourown.org/tos#I.F and click on the text "interrupt, destroy, or limit the functionality" to ensure it opens to this link https://test.archiveofourown.org/tos_faq#technical_integrity_faq

Screen recording of the link working as expected:
https://github.com/user-attachments/assets/5e547400-f1ef-4771-810a-33425dc084f2

Credit

What name and pronouns should we use to credit you in the Archive of Our Own's Release Notes?
AnnieX she/her/hers

If you have a Jira account, please include the same name in the "Full name"
field on your Jira profile, so we can assign you the issues you're working on.

@sarken sarken changed the title AO3 7451 Add technical integrity TOS FAQ link to Terms of Service AO3-7451 Add technical integrity TOS FAQ link to Terms of Service May 16, 2026
@sarken
Copy link
Copy Markdown
Collaborator

sarken commented May 16, 2026

Hi, AnnieX!

Thank you so much for this pull request. Someone will be along to review it soon.

For now, we've set the Jira issue status to In Review so no one mistakenly creates a duplicate pull request. If you'd like the ability to comment on, assign, and transition issues in the future, you're welcome to create a Jira account! It makes things a bit easier for us on the organizational side if the Full Name on your Jira account either closely matches the name you'd like us to credit in the release notes or includes it in parentheses, e.g. "Nickname (CREDIT NAME)."

Once you've done that (or if you've already done it -- Jira has been unreliable about showing us new accounts in the admin panel lately), you can either reply here or send an email to otw-coders@transformativeworks.org with your account name and email address and we'll set up the permissions for you.

Thanks again for contributing! If you have any questions, you can contact us at the same email address listed above.

position_on_fanwork_legality: position on fanwork legality
resident_embargo_country_html: to create an account if you are a resident or national of any country with which the U.S. has prohibited transactions by mandating a %{comprehensive_trade_embargo_link}, as detailed by the Office of Foreign Assets Control; or
software_viruses: to make available any material that contains software viruses or other computer code, files, or programs designed to interrupt, destroy, or limit the functionality of any computer, hardware, or telecommunications equipment;
software_viruses_html: to make available any material that contains software viruses or other computer code, files, or programs designed to %{technical_integrity_link}, as detailed by the Office of Foreign Assets Control; or
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like the text after the link got a bit mixed up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants