New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce Arabic WP1 evaluations gathering #141
Comments
@alanajjar would be the arabic speaking Wikipedianer partner here on this. Bases on 1- we can then make article selection (like for wikimed). Would you agree to want the 3 different points for WPAR? |
Thanks
Thanks @kelson42. Yes of course, and I'll help as much as I can, also Arabic Wikipedia community will be very thankful to you! |
@audiodude Supporting wiki is one of the strategic move I would like to see happening. WPAR is a good first candidate. How complex would that be? |
Nice to meet you @alanajjar ! So I've thought about this, and the prerequisite is, of course, that there are WikiProjects on Arabic Wikipedia that are doing evaluations. Can you confirm @alanajjar? Assuming that is the case, the wp1 bot software already theoretically supports using variables for the names of categories and classes. So in en, we have "Military History articles by quality" and "FA-Class, A-Class, B-Class", and we would simply have to provide an Arabic conf.json with the equivalent labels in Arabic. We would also need to edit the Docker files so that this conf.json file is variable and provided by each language version of the project rather than being statically checked into the repo of course. In fact, this is more of a systems/devops project than a software one. We would need a new database for Arabic, which we would have to decide if we provision on Toolforge or as part of the WP1 system. If the latter, we would need database backups, which I'm almost certain Toolforge gives us for free. If the former we would create a new Toolforge account, which would give us a new set of credentials for what I assume is In terms of deployment, we would need to provide the new conf.json and credentials.py to the new Arabic installation, but this wouldn't be much more difficult than creating an We would have to localize the templates that create the log files on WIkipedia, because currently they have English hardcoded: " was renamed to " and " had it's quality changed from to " (The foo/bar labels would come automatically from conf.json). We would then have to localize the frontend in All in all, there are probably a lot of steps involved in this, and we should make a Milestone for it, with each of the steps being listed in it. However, luckily, none of the steps are particularly complex. |
Created a milestone for this work. |
Hello @audiodude. Thank you, nice to meet you too!
Yes, we've around 80 Wikiprojects on Arabic Wikipedia. |
See https://ar.wikipedia.org/wiki/%D9%88%D9%8A%D9%83%D9%8A%D8%A8%D9%8A%D8%AF%D9%8A%D8%A7:%D9%85%D8%B4%D8%B1%D9%88%D8%B9_%D9%88%D9%8A%D9%83%D9%8A_%D8%B7%D8%A8. That would allow us to get native Wikimed selection
The text was updated successfully, but these errors were encountered: