User Details
- User Since
- Oct 8 2025, 6:51 PM (5 w, 4 d)
- Availability
- Available
- LDAP User
- System625
- MediaWiki User
- System625 [ Global Accounts ]
Thu, Nov 13
Wed, Nov 12
Apologies for not seeing that, I have made a fix: https://codeberg.org/ph4ni/wsindex/pulls/8
Please kindly review, let me know if it works well
Mon, Nov 10
Hi! Can I take this task?
Sat, Nov 8
Oh alright then. I’ll check out other issues if available
Thank you for the clarification
Tue, Nov 4
Alright thank you! Here is my implementation proposal for the book update feature
Hello @Pepe_piton @Nat_WDU
I made a PR for this issue: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/165
Please kindly review
Hello @Saiphani02 I'm aware the contribution period has ended but can I work on this?
Sun, Nov 2
Hello @Saiphani02 , I have fixed and pushed the fix. The problem was I was using book.title instead of book.titleNativeLanguage
Here is a screenshot of books downloaded during testing.
Fri, Oct 31
Hi @Saiphani02 , here is the PR: https://github.com/cis-india/Wikisource-Reader/pull/57
Please kindly review
Oh okay no problem, I’ll make the changes soon
Hello @Saiphani02 , I have made a PR in the Wsindex repo: https://codeberg.org/ph4ni/wsindex/pulls/7
Please kindly review
Thu, Oct 30
Hello! Can I take this task?
Hello @Bodhisattwa @Saiphani02 , Wanted to remind you about the PR I made, thank you!
Tue, Oct 28
Hi @Saiphani02 I made a PR: https://github.com/cis-india/Wikisource-Reader/pull/56
Please kindly review
Alright then!
Hello @Saiphani02 , Can I pick this up?
Oh alright then! I see that T407462 is already for vertical scrolling, What is the next step?
Hi @Bodhisattwa @Saiphani02 , I've investigated implementing vertical paginated scrolling (discrete up/down page turns) for the app and wanted to share my findings:
Current Situation
Readium Kotlin Toolkit v3.1.2 does NOT support vertical pagination for reflowable EPUB publications. This is a technical limitation of the library.
@System625 I really like your solution! A very interesting feature is that the interface displays the Q ID of the chosen option.
One question: Is there a reason why you created the /api/autocomplete-work-type API proxy? Was it necessary to solve a particular problem? What advantages did you see over calling the Action API directly from JavaScript?
Sun, Oct 26
Hello @Saiphani02 , I will be starting afresh and I will close the previous PR. If I understand correctly, I should add vertical swipe(not scroll) for pages, similar to existing horizontal swipe right?
You’re welcome!
I’ll be starting afresh on task T406912 if that’s okay, I noticed the contributor who claimed it has dropped it
Sat, Oct 25
Hi @Saiphani02 , I've made a PR: https://github.com/cis-india/Wikisource-Reader/pull/53
Please kindly review
@Saiphoni02 yes you are correct
I’ll test it out soon
Fri, Oct 24
Hi @Saiphani02 @Bodhisattwa , I've implemented the sort functionality in the Android app UI and it's passing the correct sort parameters to the API (verified via logs). However, the API seems to be returning the same books in the same order regardless of the sort parameter. Test URLs:
https://wsindex.toolforge.org/books?page=1&sort=title_asc
https://wsindex.toolforge.org/books?page=1&sort=title_desc
https://wsindex.toolforge.org/books?page=1&sort=popularity_asc
All return: "Constitution of the United States of America", "Jibanananda Dasher Shrestha Kabita", "The Osteology of the Reptiles" as the first 3 books. Has the API been deployed to production? The UI implementation is complete and ready for testing once the API sort is working.
Thu, Oct 23
I made a merge request concerning this task: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/146
Please kindly review
Hello @Saiphani02 , I've created a PR concerning the logic update: https://codeberg.org/ph4ni/wsindex/pulls/6
please kindly review
@System625, pagination logic looks solid. Can you give a few details about the workaround to keep the "in-public-domain" filter?
I did find the pagination buttons on the bottom instead of on top a bit harder to find but UX is not my field. Just a comment in case you want to mention if it was an explicit choice.
Tue, Oct 21
Sun, Oct 19
@Pepe_piton
Thank you for the feedback!
Sat, Oct 18
Hi @Saiphani02 @Bodhisattwa
I have made a PR in the API repo: https://codeberg.org/ph4ni/wsindex/pulls/4
Please kindly review
Oct 17 2025
Hello @Pepe_piton @Nat_WDU
I've created a merge request: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/116
Please kindly review
Hi @Pepe_piton @Nat_WDU
I've made a merge request for this task: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/115
@System625 Thanks for your contribution! The only problem I see, at least on my local environment, is that the "Choose a field" box is already shown before the user clicks on the "Add information" button, so the button has no real use.
@Saiphani02 I have noted this, thank you. So I have to first made changes in the API repo right?
Oct 15 2025
Hello @Bodhisattwa , I would like to take this issue
Good job, @System625 . I appreciate that you are using the language selected by the user for the query, and that you've updated i18n files.
Thank you very much for the feedback, it means a lot :)
My bad @Nat_WDU ,
I have fixed it! I've moved the requests import to the top of the file. There was no specific reason for the inline import, I just didn't notice it before pushing. Thanks for the review!
Oct 14 2025
Hello @Nat_WDU
I made a merge request concerning this issue: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/81
Please kindly review, thank you!
Hello @Nat_WDU
I have made a merge request concerning this issue: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/79
Please kindly review
Oct 13 2025
Hello @Bodhisattwa . I have linked a PR: https://github.com/cis-india/Wikisource-Reader/pull/37
Please kindly review
@System625
I like that you listed the changes and added a test plan
you paid attention to the h1 category hierarchy
Hello! My name is Olamiposi, I'm an outreachy contributor and I would love to contribute to this great project. Is this issue still available, I would like to work on it
Oct 12 2025
Hello @Zache , I've create a PR: https://github.com/Wikimedia-Suomi/PendingChangesBot-ng/pull/72
Please kindly review
Alright, I have created the ticket: https://github.com/Wikimedia-Suomi/PendingChangesBot-ng/issues/71
I will commence work now
Yes I can. Should I open an issue on Github first commencing work or I should start working and create a PR when I'm done?
Oct 11 2025
Hello @Zache , I made my research and came up with a proposal but I can't paste it directly due to it's length so I attached in a google docs. Here is the link: https://docs.google.com/document/d/1Y1fHYUDenIiSmQQtC7ZErrcmqlTgr9npDnLx6K5cE2o/edit?usp=sharing
@Zache I've accepted the invitation, thank you!
@Zache That is my email but it is not the one I used to sign up for the wikimedia accounts. This is it: tunde-ajayi.olaoluwasijibomi@lmu.edu.ng
Apologies for the confusion
Hello @Zache
I still haven't gotten an update concerning the slack invitation. Please kindly assist me at your convenience, thank you :)
Oct 10 2025
Hi @Pepe_piton
I've submitted a merge request implementing the UI proof-of-concept for the "Add information" feature: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/41
Hi Every one!
My name is Olamiposi and I plan to contribute to this project for Outreachy. I sent a mail info@wikimedia.fi (I saw it on the thread) to be added to the slack channel.
I've completed this task and created a merge request: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/30
Oct 9 2025
Hello @Pepe_piton , I made a merge request concerning this issue: https://gitlab.wikimedia.org/toolforge-repos/paulina/-/merge_requests/20

