Sure, if you see that as out of scope for this ticket, I'm happy to create a new one.

I think this is an easy lift -- to deliver this task I just need to conduct a short subject-matter expert interview with a developer who's in the know on how to do this. Can also be async -- I just need to know what a user should do beyond `docker compose down --volumes```.

On the release announcement/community comms side I think we need the announcement to contain:

Possibly relevant: https://phabricator.wikimedia.org/T272472

Checked and marked up (by me)!

Is this technically fixed?: https://github.com/wikimedia/mediawiki-extensions-Wikibase/commit/c4ec3483e77bc9981ddfa8ded0ea93570cb76f7c

In T344689#9226273, @dang wrote:

@danshick-wmde Hi Dan! I noticed one little thing about the email that there's no mentioning of which wiki is empty. One user can have up to 6 wikis running so it's best to mention it somewhere before the user decided to delete it.
And it's totally doable in the code. Do you think it's a viable option?

Dear Wikibase.cloud user,

Given the "placeholder" comment, I'll send feedback via email and copy all participants.

In T345083#9146899, @Manuel wrote:

Hi @danshick-wmde, I've conducted some user testing, and it's clear that our current copy could benefit from some enhancements. Given my close involvement with this project, I'd greatly appreciate your fresh perspective. Would you kindly take a moment to review it?

Thanks @GreenReaper ! I'm glad to know it's the prefixes. This works for me:

Added a note about the bot flag.

Yesterday Silvan pointed out that this issue is actually about users getting 403 "rest-write-denied" errors when lacking bot permissions. Some context apparently at T321318 . I have a subject-matter-expert interview tomorrow with @WMDE-leszek , will try to get to the bottom of this behavior then.

In T326948#8596607, @danshick-wmde wrote:

I had a chat with Ollie scheduled for yesterday which got cancelled since he's at a conference. I still need to formalize on the wiki page the stuff he & others said on Mattermost about error states (documented in Swagger) and rate limiting (fundamentally the same as ActionAPI, but I need to note how they're implemented on Wikidata). I'll attempt to finish this today, tomorrow at the latest.

Leszek is correct, I have an SME interview on these topics pending. (was scheduled for yesterday but it was deferred)

I had a chat with Ollie scheduled for yesterday which got cancelled since he's at a conference. I still need to formalize on the wiki page the stuff he & others said on Mattermost about error states (documented in Swagger) and rate limiting (fundamentally the same as ActionAPI, but I need to note how they're implemented on Wikidata). I'll attempt to finish this today, tomorrow at the latest.

Todo: error states & rate limiting

A preliminary authentication doc can be found here: https://www.wikidata.org/wiki/Wikidata:REST_API/Authentication

Okay, I'll treat this as extremely urgent.

I see this as my task working with subject-matter experts. Feel free to reassign if you see this task as fundamentally belonging to the SMEs with my edits to come after.

I'll need to speak with a subject-matter expert on this one. Who's the right person?

I've been hoping against hope that this is something I'm doing wrong. However I think those prefixes are universal to Wikibase despite the choice of letters, for two reasons:

I see the same behavior on a fresh Docker install. I checked out wikibase-release-pipeline commit 6f7f418d1434229142650ae1e19db391857fcad9, copied the contents of examples/ to another directory, created an .env file, and ran COMPOSE_HTTP_TIMEOUT=3000 docker-compose -f docker-compose.yml -f docker-compose.extra.yml up -d.

@Kris_Litson_WMDE or someone with similar powers will need to hand this off to the team that admins wikiba.se .

This documentation exists: https://www.mediawiki.org/wiki/Wikibase/Installation/Advanced_configuration#Enabling_sitelinks

As noted above, so long as the ontology file is linked via the domain wikiba.se, updates to the file need to be given to those who manage that site, currently MOR working for KOM.

Red link (to pending page) removed -- thanks for the heads-up!

In T316083#8180785, @danshick-wmde wrote:

Welcome to Wikibase.cloud!

You can create and manage wikis from this central dashboard.

Check out our cloud service documentation as well as general documentation on Wikibase.

Welcome to Wikibase.cloud!

In T310899#8148074, @Addshore wrote:

Resolving as this already works.

Ping @danshick-wmde @Evelien_WMDE to see if we want to document this in any way

Note that as far as I know there is currently no process for propagating changes to this file. Due to historical decisions the ontology file is now managed by those who manage wikiba.se (COM and the external agency MOR).

In T55974#8086214, @Tacsipacsi wrote:

No, there’s another “minor” caveat the blog post doesn’t mention: you can’t add new markup. The content can be edited, they can be deleted, even copied and pasted, but if there’s no <translate> or <tvar> tag on the page you edit, there’s no way to create them.

I'll try to answer some of the questions, stated and implied, in this comment. Keep in mind that much of the documentation for Wikidata has been created by and is actively owned and maintained by the WD community, to the extent that I have to write drafts of revisions of important pages and invite public comment on them before publishing. (Case in point: https://www.wikidata.org/wiki/Wikidata:Data_access )

The Wikibase landing page has been updated.

Native speaker has already spoken -- do whatever you like.

Does anyone know why this task (adding a link) is taking multiple weeks? @Evelien_WMDE

In T308664#7975981, @danshick-wmde wrote:

I suggest the following:

"Lemma field cannot be empty."
"Lemma field cannot exceed X characters."
"Lexeme language field cannot be empty."
"Spelling variant field cannot be empty."
"Lexical category field cannot be empty."

I suggest the following:

In T308538#7934128, @Jan_Dittrich wrote:

Thanks for tagging me in this ticket. @Aklapper is right, wikiba.se is no longer a docs landing page for Wikibase. As part of my plans to revamp Wikibase docs I will review https://www.mediawiki.org/wiki/Documentation/Review_template .

We're straddling Asana and Phabricator here -- let's say that we've fully gathered the list of cookies when I've reviewed the doc as mentioned in https://app.asana.com/0/1201480856350195/1201480856350215/f . This will happen by EOB 2022-02-25 (CET).

Thanks, clarified the docs.

Doc page updated.

Potential duplicate of T272472 .

I have my eyes on this because I'm very invested in seeing/building consensus that all formal issues should be tracked in Phabricator.

I've had this in my task list for a while; what's the release date?

Documentation should be treated as living and changing. To the extent that tickets have meaning, we need to have some definition of done for this one.

As always, feel free to add topics to the meeting document!

This task probably needs to be rescoped or subtasks created:

https://www.mediawiki.org/wiki/Wikibase/Extending

Import is an upcoming meeting topic; I'd like to frame this task in the context of this page:

I take it back; I don't think it belongs on the Advanced config page after all.

I'll add a link to the mediawiki.org page(s) to the Wikibase FAQ and advanced config pages.

Met with @toan and have a set of instructions I will develop into improvements to this document:

Original: Thank you for your assistance! We have noted your request to not receive a donation receipt. If you change your mind, you can notify us at any time by sending an email to spenden@wikimedia.de
Suggestion: Thank you for your assistance! You have asked not to receive a donation receipt. Should you change your mind, you can notify us by emailing spenden@wikimedia.de.

Original: Would you like to enter your contact details? Private individual; Company; Without address details
Suggestion: Would you like to enter your contact details? Yes, as a private individual; Yes, as a representative of an organization; No

In T293075#7423289, @karapayneWMDE wrote:

Original: Which amount would you like to donate?
Suggestion: How much would you like to donate?

I have this down as a Q4 task for technical writing. To complete it I'll need to work with a subject-matter expert who understands the upgrade process, ideally someone who has tested it and made some kind of notes I can turn into a user-facing document. If I'm asked to I can test it as well.

If you name the script config-migrate-1.36.php or equivalent and include instructions, it should be clear when to use it. In my opinion, all code we offer for use should be included in the repo.

What is the rationale not to distribute the script in the repo? Offering it via phabricator is a very strange and unhelpful way to offer it to the users.

Is there any reason we provide this script in phabricator and not in the code itself?

In T285653#7291583, @toan wrote:

@danshick-wmde Does this look like useful information to you?

In T97577#7216825, @danshick-wmde wrote:

In T97577#7207515, @Billinghurst wrote:

We also should be looking to add it to mw:Help:Magic words when it goes live.

In T277027#7186119, @Addshore wrote:

Tagging @danshick-wmde as I am sure we should make some docs changes etc after working through this!

Updated per our discussion.

There's no "Wikibase" tag any more so I don't know how to tag this properly...

I unintentionally left this task hanging. I have the info I need to complete this task thanks to @LucasWerkmeister and will finish revamping the page in the coming days.

https://www.mediawiki.org/wiki/Wikibase/Permissions

Well sheesh, @ItamarWMDE , you didn't leave me much to do, did you? :) Thank you for this super-thorough piece of documentation. I will copy it to MediaWiki shortly.