Sounds good, thanks!

That sounds like a workable solution for now, thanks. Can you connect with Edly to ensure they understand this solution and what it would require on their end?

Recording here that the WikiLearn vendor is waiting on LangEng for this. Thanks.

What is the status of this work? Does its inclusion in "LPL Essential 2024 Jul-Sep" mean it was worked on?

Thank you. We will look into setting up email on learn.wiki with our vendor, and update the ticket when we learn if that's feasible.

In that case, I apologize for the confusion I created. We do want to send from [email protected], so please amend the patch to the original CNAMEs requested.

Our vendor tells me they did in fact mean wikimedia.org, in order to be able to use our team email ([email protected]) as the sender in WikiLearn emails. Is there a concern with registering the CNAMEs as originally requested?

Yes, agreed. Our vendor made a mistake, and I pasted it verbatim. 😅

Migration complete, with many thanks to @dcaro .

Thanks for the analysis! That is indeed what it would take, but I can't put in the time in the foreseeable future.

Oh, that was indeed the default! Now unprotected the branch, thanks.

In T349976#9329187, @abi_ wrote:

@Asaf I see that the l10n-bot has been granted developer access to the repository. Is the master branch protected? Will "developers" be able to push changes to the master branch directly?

1. done
2. done.

IPBE has been granted.

@Aklapper -- yes and no: WikiLearn is mostly developed by an external vendor (Edly.io), and they have their own internal planning/management processes. But this project tag is useful for managing the (smaller) WMF side of the work, which is primarily around the course content translation feature using Meta.

Thank you, @taavi .

Oh, do you mean the GitHub user @translatwiki? I've granted that user write access to the repo now.

@abi_ -- I'm not clear on what you're asking. Are you asking to add the bot's source code to the repo? If so, I have not seen the bot code myself; I believe Edly has the code and can add it to the repo. Correct, @Ali-Salman29 ?

Thanks. I've added answers to the FAQ and moved the page to [[m:WikiLearn/Translation]].

I apologize if I missed something, but if we do end up separating into different *lexemes*, how do we retain the value of all the descriptive work done on one lexeme (presumably the more common or standard form) that equally-well describes the form in the other lexeme? Do we rely on some sameAs property and then on applications and re-users to consider that property and auto-merge/import statements from the other lexeme?

Thank you for making this list. What does "creating an API user" mean, in this context? And how do I go about doing that, and specifying the 'editcontentmodel' right? The API I know is the MW API. Do you mean a 'user' needs to be created for the translation system to use in making MW API calls to meta.wikimedia.org? If so, wouldn't it make sense for you to create that user and keep its credentials, since your code would need to use that account?

Never mind, opened a new task with updated request.

And also:

Thank you very much for the quick response!

The instances I have right now are part of the 6 we need, yes. Their current sizes are not fitting the needs, just calculated to max out the allowance (per your instructions, to first use up our quota before requesting an increase).

Exciting update: Turns out that I never properly tested the "mwoauth-authonlyprivate" option, because of that silent clearing of the custom endpoints config. I have now done that, and seem to have gotten a proper OAuth handshake completed!

Confusing indeed! Turns out that the custom endpoints definitions were silently deleted (reset to empty) when I made changes to the scopes field. I have now re-populated the custom endpoints, and we're back to the "The requested scope is invalid, unknown, or malformed" error.

No luck with authonlyprivate either.

Thank you. The scope parameter is not optional on the Moodle side, so I'm forced to put some value in there. Trying both "mwoauth-authonlyprivate" and "openid mwoauth-authonlyprivate", I did not even get as far as Meta's error message (instead getting an apparently spurious 403 Forbidden on the Moodle server itself, like the one described in https://phabricator.wikimedia.org/T271078#6723663

Thank you! Using the correct manual endpoints seems to have taken me a step further. I now get a Moodle error "The requested scope is invalid, unknown, or malformed", presumably referring to one or more of the three "scopes" in the config field shown above, viz. "openid profile email".

Progress(?) -- I have defined endpoints by some wild guessing and peeking at some client code, as follows:

Thank you, @Reedy. I did indeed peruse the [[OAuth/For_Developers]] page, which is how I got as far as registering my OAuth client and receiving my credentials. However, I am probably still missing something.

Some more weeks on, I repeat the request to make progress, or at least offer an ETA for this. Thank you.

E.g. https://office.wikimedia.org/wiki/User:Abartov/nonce