Skip to content
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

Open
kelson42 opened this issue Feb 8, 2020 · 8 comments
Open

Introduce Arabic WP1 evaluations gathering #141

kelson42 opened this issue Feb 8, 2020 · 8 comments

Comments

@kelson42
Copy link
Collaborator

kelson42 commented Feb 8, 2020

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

@kelson42
Copy link
Collaborator Author

kelson42 commented Dec 2, 2020

@alanajjar would be the arabic speaking Wikipedianer partner here on this.
@alanajjar This tools do basically three things:
1- gathering evaluations
2- writting stats tables/logs on Wikipedia
3- Providing a web interface (at https://wp1.openzim.org)

Bases on 1- we can then make article selection (like for wikimed).

Would you agree to want the 3 different points for WPAR?

@alanajjar
Copy link

Thanks

@alanajjar would be the arabic speaking Wikipedianer partner here on this.
@alanajjar This tools do basically three things:
1- gathering evaluations
2- writting stats tables/logs on Wikipedia
3- Providing a web interface (at https://wp1.openzim.org)

Bases on 1- we can then make article selection (like for wikimed).

Would you agree to want the 3 different points for WPAR?

Thanks @kelson42. Yes of course, and I'll help as much as I can, also Arabic Wikipedia community will be very thankful to you!

@kelson42
Copy link
Collaborator Author

kelson42 commented Dec 2, 2020

@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?

@audiodude
Copy link
Member

Nice to meet you @alanajjar !
@kelson42

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 arwiki_p, the Arabic Wikipedia replica database.

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 ar directory in /data/code/ on the production server (and similar ar/ and en/ directories in /data/wp1bot/).

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 wp1-frontend. I'm not entirely sure how this is done, as I've never localized a web project outside of Google where the tools are very baked in and mature. As part of localization of both the templates and the frontend, we would have to have some way of specifying the language setting in either the Docker file or somewhere else.

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.

@audiodude
Copy link
Member

Created a milestone for this work.

@audiodude audiodude added this to the Arabic Evaluations milestone Dec 6, 2020
@audiodude
Copy link
Member

Also I know we have #122. Does it make sense to do French first before taking on Arabic, @kelson42 ?

@alanajjar
Copy link

Hello @audiodude. Thank you, nice to meet you too!

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?

Yes, we've around 80 Wikiprojects on Arabic Wikipedia.

@kelson42
Copy link
Collaborator Author

Also I know we have #122. Does it make sense to do French first before taking on Arabic, @kelson42 ?

Yes, definitly. Let do #122 first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants