==PROFILE INFORMATION==
**Name :** Sushrith Bogi
**IRC nickname :** sushrith
**Email :** bogisushrith@gmail.com
**Web Profile :** [[ https://phabricator.wikimedia.org/p/Sushrith_Bogi/ | Phabricator ]],[[ https://github.com/bogisushrith | Github ]]
**Timezone :** IST (Indian Standard Time) (UTC + 05.30)
**Location (country or state) :** Telangana, India
**Typical working hours (include your timezone) : **18:00 IST to 01:00 IST (5.5 hours on weekdays), 10:00 IST to 22:00 IST (10 - 10.5 hours on Sundays)
==SYNOPSIS==
This project aims to significantly augment the filtering and searching functionalities of the New Pages Feed within PageTriage, an essential component of the MediaWiki extension. It serves as a critical tool for English Wikipedia patrollers, facilitating the management of newly created content. However, the current filtering options are deemed insufficient by the community, prompting the need for enhancements. This initiative empowers patrollers with improved tools for content management.
- Implement AI-based topic prediction leveraging the ORES API to enable patrollers to swiftly identify pages of thematic relevance.
- Introduce keyword-based search functionality, allowing patrollers to locate articles containing specific terms or phrases efficiently.
- Enhance filtering options based on the number of pageviews an article receives, providing insights into the popularity and relevance of newly created pages.
- Introduce a feature enabling patrollers to search for pages similar to previously deleted content, aiding in the identification and management of potentially problematic material.
**Possible Mentor(s) :** @Soda, @TheresNoTime
**Have you contacted your mentors already?**
Yes
==TIMELINE==
| Period | Task
| ------ | ----
|May 1 - May 26 | **Community bonding period : ** Acquaint myself with the ORES web services and API for AI-based topic prediction, I plan to gain more familiarity with the existing codebase of the PageTriage extension, analyzing its architecture and implementation details to better comprehend potential challenges and opportunities for enhancement. I would explore the sorting mechanisms based on the pageview count. I intend to analyze the keyword search techniques for articles based on themes or content. I plan to gain a comprehensive understanding of how to add or create an API that could calculate the visitors of the article.Will have college exams for a week.
|May 27 - June 2|Work on implementing integration of articletopic into Special:NewPagesFeed filters menu.Fetch topic predictions from ORES API and display them in filters menu.Address any bugs or issues encountered during implementation process.
|June 3 - June 9|Integrate articletopic into Page Curation toolbar's "Page info" flyout.Modify toolbar's functionality to include topic predictions for currently viewed page.Conduct testing to verify seamless integration into both filters menu and toolbar.
|June 10 - June 16|Conduct thorough testing of both filters menu and toolbar integrations.Verify accurate retrieval and display of topic predictions in both components.Address any remaining bugs or issues identified during testing.
|June 17 - June 23|Would work on integrating functionality to sort the NewPageFeed by pageview count and would start by examining the existing codebase and identifying integration points for this feature.
|June 24 - June 30|Would address any bugs or issues arising from initial testing and make necessary refinements to the sorting feature. This may involve debugging and troubleshooting to resolve inconsistencies. Once the code is stable, would conduct comprehensive testing to validate performance and usability.
|July 1 - July 7|Would focus on implementing the keyword search functionality for the New Pages Feed. This involves ensuring that search results accurately display articles containing the specified keyword in their text.
|July 8 - July 14|During the midterm evaluation phase, I will focus on reviewing and addressing the feedback provided by my mentors. Additionally, I will dedicate effort towards enhancing any remaining tasks outlined in the timeline.
|July 15 - July 21|I would work on resolving any bugs that might have emerged and conduct thorough testing to ensure the functionality and stability of the keyword search feature.
|July 22 - July 28|I would work on designing and implementing the API for PageTriage to pull the top deleted revision and compare it to the current top revision of an article. This involves carefully considering the architecture and functionality needed to efficiently perform this comparison.
|July 29 - August 11|I would work on integrating the API into the PageTriage frontend. This could involve adding a button to manually trigger the comparison or implementing automatic calculation when visiting the article. Additionally, I would explore options for automatically calculating this comparison for all articles and displaying it as a red tag in Special:NewPagesFeed.
|August 12 - August 18|I would address any remaining tasks, such as adding support for detecting previous AFDs and deciding on the best approach for implementation. I would thoroughly test the functionality to ensure accurate detection and comparison of deleted revisions, making any necessary refinements based on testing feedback
|August 19 - August 26|I aim to set aside the final week as a buffer to accommodate any unforeseen issues or delays that may occur throughout the project timeline. If everything proceeds as expected, I would work on unassigned Phabricator tasks.
**Deliverables:**
- Add ORES topic prediction to the NewPagesFeed and allow filtering by the same - T218132
- Special:NewPageFeed - add option to filter by pageviews - T207238
- Keyword Search for New Pages Feed - T207761
- See and filter with percent similarity to top deleted revision - T327955
==PARTICIPATION==
I maintain an active presence across various communication platforms, including Zulip, Slack and Email. For discussing issues and conducting code reviews, I will utilize Phabricator and Gerrit.With no other commitments, I am capable of dedicating more than 40 hours per week to this project.
==ABOUT ME==
> - Your education (completed or in progress)
I am a third year student currently pursuing my Engineering in depatment of Information Technology
> - How did you hear about this program?
I heard about Google Summer of Code in my freshman year from my seniors, they discussed about contributing to an open-source organization and benefit of it. The very idea of working collaboratively on a real-world project with people from diverse background and skill sets and opportunity to learn and grow as a developer fascinated me.
> - Will you have any other time commitments, such as school work, another job, planned vacation, etc, during the duration of the program?
I will have some exams during the May 14 - May 21 week which may lead to me being engaged during that period. I'll be in touch with my mentors and inform them of my progress.
> - Are you planning to apply to both programs and, if so, with what organization(s)?
I am applying only for Google Summer of Code.
> - What does making this project happen mean to you?
Actualizing this project holds profound significance for me as it represents a commitment to advancing the accessibility and integrity of information on Wikipedia. By enhancing the filtering and search capabilities of the New pages feed, we empower volunteers to effectively manage and curate content, ultimately enriching the user experience and furthering the mission of free knowledge sharing.
==PAST EXPERIENCE==
Microtask
> - Create a small independent tool/web app that iteracts with any Wikimedia API and displays some information about an article. The tool must have a frontend built using VueJS and the Wikimedia Codex UI library. Include a link to the source code in your proposal
**Source code for the proposal:** [[ https://github.com/bogisushrith/Wiki_Article_Viewer/ | Code ]]
Technologies used
- Vue.js
- Wikimedia Codex UI library
- Wikimedia API
>- Setup the #pagetriage extension (using [these draft instructions](https://www.mediawiki.org/wiki/MediaWiki-Docker/Extension/PageTriage)) along with [MediaWiki-Docker](https://mediawiki.org/wiki/MediaWiki-Docker).
PageTriage setup has successfully completed
{F43214932}
**I have been a part of the Wikimedia community since November 2022.Given Below are some of my contributions to Wikimedia Projects :**
| Patch | DESCRIPTION | STATUS
| ----- | --------------- | ------
|https://gerrit.wikimedia.org/r/c/mediawiki/extensions/PageTriage/+/1012741|Fix weird count when switching between feeds|Merged
|https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ProofreadPage/+/879899|Animation should take left pane when "preview" is clicked|Merged
|https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikiLambda/+/879892|Fix to open link in same tab|Merged
|https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikiLambda/+/887954|Testers on Implementations should be links|Merged
|https://gerrit.wikimedia.org/r/c/mediawiki/extensions/PushAll/+/888355|Exchange the word for a different one|Merged
|https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/890360|Visual change in the article toolbar|Merged
|https://gerrit.wikimedia.org/r/c/wikimedia/developer-portal/+/927717|Replace the link|Merged
|https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/912401|Eliminate unnecessary spacing in the username/create account link|Merged
|https://gerrit.wikimedia.org/r/c/mediawiki/extensions/PageTriage/+/1011156|Fix copyvio prop type validation error|In-Review
|https://gerrit.wikimedia.org/r/c/mediawiki/extensions/PageTriage/+/1010248|Maintain consistency across NPP and AFC|In-Review
===== Image Search [[ https://github.com/bogisushrith/Image-Search | (Github link) ]]
- Developed by using Vue.js.
- Generates an image that corresponds to the user provided input.
- Utilizes Unsplash API to fetch the image.