Wed, Jan 25
Dec 1 2022
IPBE has been granted.
Nov 28 2022
Nov 19 2022
@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.
Nov 15 2022
Thank you, @taavi .
Nov 9 2022
Oct 27 2022
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 ?
Aug 1 2022
Thanks. I've added answers to the FAQ and moved the page to [[m:WikiLearn/Translation]].
Jul 22 2022
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?
Jul 15 2022
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?
Aug 30 2021
Never mind, opened a new task with updated request.
Aug 27 2021
Aug 25 2021
Aug 24 2021
Aug 19 2021
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).
Aug 13 2021
Jan 6 2021
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
Jan 5 2021
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:
Which now gets me to an actual OAuth error, 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.
Jan 3 2021
Nov 11 2020
Some more weeks on, I repeat the request to make progress, or at least offer an ETA for this. Thank you.