Page MenuHomePhabricator

Update text in Terms of Service
Closed, ResolvedPublic

Description

In the Terms of Service and Privacy Policy page we need to make some changes to reflect a small change to the way library eligibility is handled (T285557). There are also a couple of areas we want to tidy up and clarify as part of the same change.

This task must not be merged to production until T286897 is also ready to send.

The following sentences need updating:

Old New
This website allows users to apply simultaneously for access to multiple publishers’ materials, and makes the administration of and access to Wikipedia Library accounts easy and efficient.This website allows Wikipedia editors to search and access these resources.
To that end, in order to be eligible for the Wikipedia Library program, we require that you be registered for a user account on the projects. We give preference to users with at least 500 edits and six (6) months of activityTo that end, in order to be eligible for The Wikipedia Library, we require that you be registered for a user account on the projects, with at least 500 edits, six (6) months of activity, and 10+ edits in the last month.
, but these are not strict requirements[Delete]
We ask that you do not request access to any publishers whose resources you can already access for freeWe ask that you do not request access to any publishers with a limited number of available accounts whose resources you can already access for free
Wikipedia Library Card accounts do not expire. However, access to an individual publisher’s resources will generally lapse after one year, after which you will either need to apply for renewal or your account will automatically be renewed.Your eligibility to access The Wikipedia Library is assessed at each login. While more than half of the library's content is provided via this automated eligibility check, access to other publisher's content may be time limited, typically lapsing after one year, after which you will usually need to apply for renewal.
If you obtain a Wikipedia Library account, but a long-term block or ban is subsequently instituted against you on one of the projects, you may lose access to your Wikipedia Library account[remove "long-term"]
The following limited information that you provide is public to all users by default: 1) when you created a Wikipedia Library Card account; 2) which publishers’ resources you have applied to access; 3) your rationale for accessing the resources of each partner to which you apply. Editors who do not wish to make points 2 and 3 public may opt out using a checkbox when filing an application.[Delete]
Sharing your usernames, passwords, or any access codes for publisher resources with others;Sharing your Wikipedia account, usernames, passwords, or any access codes for publisher resources with others;
You can browse the Wikipedia Library site without logging in, but will need to log inSome Wikipedia Library pages are visible without logging in, but you will need to log in

We will also need to update the 'Last updated' date to the relevant date this change is made.

This task should not be merged to production until all subtasks of T285929 are ready to deploy.

Event Timeline

Samwalton9-WMF updated the task description. (Show Details)
Samwalton9-WMF updated the task description. (Show Details)

Something that I've noticed in the terms is that we refer to The Wikipedia Library as The Wikipedia Library, Wikipedia Library Card, and Wikipedia Library Card Platform. Should we just change everything to The Wikipedia Library?

jsn.sherman subscribed.

I came here to move this to "done", but seeing this question, I'll stick it back in review for now. I think streamlining/normalizing the language in this way sounds great, but I'm curious about what @Samwalton9 has to say.

...Also, I realized that I shouldn't have merged this in until all T285929 subtasks were done. I went ahead and paused the deployment cron task on production for now

This wasn't merged into the master branch, but the eligibility-update branch so you don't have to pause the deployment cron task :)

Oh, whew! that's right, I'm getting a bit loopy at the end of the day here. I'll unpause that cron task and step away from the keyboard!

A thought does occur to me:
What about translations for the updated terms?
We'll send folks localized emails telling them to go read the terms, but if we're not merging the changes until just before sending, there won't be time for translation, so the terms will be English only.

Something that I've noticed in the terms is that we refer to The Wikipedia Library as The Wikipedia Library, Wikipedia Library Card, and Wikipedia Library Card Platform

This is a good point, but I don't think I quite care enough to worry that much about it. We only use 'Library Card' a couple of times, and I don't think it affects how the terms read.

What about translations for the updated terms?

If we did want to get translations what would the solution be? Duplicating the terms to a hidden page so that the new wording is available for translation?

Yeah, I suppose the best way to handle this kind of thing (perhaps moving forward if not starting now) would be to create new terms templates (like terms_20210812.html) when we need to update and then point the the /terms route to that and drop the old template when it's ready.

That makes sense. I think in this case it's OK - we're not making a massively substantial change.