Page MenuHomePhabricator

GSoC-2024 : Improve searchability and filtering of PageTriage feed (WIP)
Closed, InvalidPublic

Description

Profile Information

Name: Pratiksha Sankhe
IRC nickname on libera.chat IRC: Pratiksha
Web Profile: Linkedin, Github
Resume (optional): Link
Location (country or state): India, Maharashtra, Mumbai
Typical working hours (include your timezone): IST (Indian Standard Time) (UTC + 5.30)

Synopsis

Short summary describing your project and how it will benefit Wikimedia projects

  • PageTriage is a MediaWiki extension for English Wikipedia designed to streamline the review process for new articles. It provides various features to assist patrollers, including tracking, categorizing, and addressing problematic new pages. These tools enable patrollers to effectively manage the constant flow of new content and uphold the quality standards of the encyclopedia.
  • The extension currently offers satisfactory performance, but there's potential for improvement in its filtering and search functionalities. Enhancements could include integrating AI-based topic prediction through the ORES API, implementing keyword searches within articles, filtering articles based on pageview metrics, and enabling searches for similarities between a given page and other deleted pages.

Possible Mentor(s)
@Soda @TheresNoTime

Have you contacted your mentors already?
Yes

Deliverables

  • (T218132) Add ORES topic prediction to the NewPagesFeed and allow filtering by the same
  • (T207238) Special:NewPageFeed - add option to filter by pageviews
  • (T207761) Keyword Search for New Pages Feed
  • (T327955) See and filter with percent similarity to top deleted revision

Timeline

Timeline

Community Bonding Period:

PeriodTimeline
May 02 - May 27Get in touch with the mentors and familiarize myself with the community and codebase of PageTriage extensions. I'll discuss potential ideas to solve the issues and improve the extension. Understand the architecture and identify relevant parts of the codebase for the issues. I'll also familiarise myself with how various components of it work together.

Coding Period :

PeriodWeek NoTimeline
May 27 - June 03Week 1Look into the initial features to be implemented and start work on deliverables.
June 03 - June 10Week 2Write bi-weekly report.
June 10 - June 17Week 3Resolve code reviews promptly and provide punctual check-ins. I also documented the changed code patches and my progress on the project.
June 17 - June 24Week 4
June 24- July 01Week 5
July 01 - July 8Week 6Discuss new ideas and features for improving the extension with the mentor, prepare for mid-evaluation, and receive feedback from the mentors. Write bi-weekly report.

Mid-evaluation

July 08- July 15Week 7
July 15 - July 22Week 8
July 22 - July 29Week 9
July 29 - August 05Week 10Write bi-weekly report.
August 05 - August 12Week 11Work on the feedback received from mentors , if completed early , work on implementing more ideas and features discussed with the mentors.
August 12 - August 19Week 12Work on pending or last-minute issues and prepare for final evaluation.

Final Evaluation
Fixing unforeseen bugs, waiting around for final evaluation and working on community feedback.

Pre GSoC Work

  • WikiFind
    • WikiFind is a online platform designed to provide users with efficient access to a vast repository of articles sourced from the MediaWiki API.
    • WikiFind is a website comprising two primary sections: the "Home" and "About" pages. The "Home" section features a search bar where users can input topics of interest. Additionally, users can specify the number of articles they wish to view, with a default setting of 20. Upon submission, WikiFind retrieves related articles and presents brief descriptions accompanied by links to the corresponding Wikipedia pages. The "About" page provides an overview of WikiFind's functionality and purpose.
    • While building the website, I familiarized myself with Vue.js, Vue Router, and how to utilize the Wikimedia API and Codex Library.
    • GitHub
    • Deployed Link
  • The setup of the PageTriage extension, alongside MediaWiki-Docker, was done locally using WSL.

Participation

  • I am active on Email, Zulip, and Slack. I will use Phabricator and Gerrit for issue discussions and code reviews.
  • I can dedicate 30+ hours a week.
  • I'll be committing my progress to the master branch of the PageTriage extension via Gerrit.
  • If I encounter questions regarding the implementation of a specific feature, I will seek guidance from my mentor through Zulip, within the Phabricator task, or on Discord.
  • I’m reachable at all times (within ~8:00 AM to ~1:00 AM IST) on Phabricator, via my email (sankhepratiksha3@gmail.com).
  • I'll post bi-weekly updates regarding my progress on my MediaWiki user page.

Post-GSOC
I am learning a lot by contributing to Wikimedia and learning about its codebase. Even after the GSoC period ends, I plan on contributing to this organization. The familiarity I've gained with the technical stack and the ongoing challenges it presents make it an ideal environment for growth. With the skills I've acquired, I aim to contribute to the growth of both the project and the community. Additionally, I'm keen on assisting others in embarking on their own open-source journeys, guiding them through the process of contribution and fostering community growth.

Future Goals

  • Suggest more changes and features during the GSOC period.

About Me

Tell us about a few:

Your education (completed or in progress)
I'm in my last year of studying for a Bachelor's Degree in Computer Science and Engineering at Veermata Jijabai Technological Institute. I have a solid grasp of fundamental coding concepts, including data structures and algorithms, as well as proficiency in web development technologies.

Skills

  • Proficient in frontend technologies including JavaScript, HTML, CSS, Tailwind CSS, and Bootstrap.
  • Skilled in backend development with Node.js, Express, and PHP for creating various applications.
  • Experienced in full-stack development using frameworks like React.js, Next.js, and Vue.js for frontend development.
  • Proficient in mobile app development with Flutter and React Native, using Android Studio as the development environment.
  • Familiar with Docker.

How did you hear about this program?
I was first introduced to Google Summer of Code at an event in my college during my second year where seniors who had already participated in the program talked about their experiences.

Will you have any other time commitments, such as school work, another job, planned vacation, etc, during the duration of the program?
Until the end of May, I have academic commitments, and I will be joining BNY Mellon as an SDE in August. Besides these, I have no other commitments and can fully devote my attention to the project. Throughout my summer break, I am committed to investing 3 to 4 hours daily, summing up to 25-30 hours per week. Despite these commitments, I can readily allocate my time effectively.

We advise all candidates eligible for Google Summer of Code and Outreachy to apply for both programs. Are you planning to apply to both programs and, if so, with what organization(s)?
No.

What does making this project happen mean to you?

I've always found great excitement in the idea of transforming concepts into tangible products with meaningful impacts. I'm excited about the Wikimedia Foundation's mission to create free and open-source applications that educate millions worldwide. I'm incredibly keen on this project, and my involvement with Wikimedia has been an enriching journey, thanks to the support of all the mentors involved. Engaging in this project will not only provide me with insights into production-level code structures but also significantly enhance my learning experience. My background in Vue.js and PHP will be valuable, and I'm committed to contributing to Wikimedia regardless of the outcome of the Google Summer of Code proposal.

Past Experience

Please add links to any feature or bug fix you have written for a Wikimedia project during the application phase.

TitleLinkStatus
'Email Instructors' feature should have 'BCC to Salesforce' option just like Ticket replieshttps://github.com/WikiEducationFoundation/WikiEduDashboard/pull/5708Under Review

Describe any relevant projects that you've worked on previously and what knowledge you gained from working on them.

Hospital Management System
The Hospital Management System, developed using PHP, offered a user-friendly interface for managing patient records, appointments, and prescriptions. Leveraging PHP's robust backend capabilities, along with HTML, CSS, and JavaScript for frontend development, this project enabled efficient patient management for healthcare providers. For me, it provided a valuable learning opportunity to hone my PHP skills and understand the complexities of building such websites.

Describe any open source projects you have contributed to as a user and contributor (include links).
Since last year, I've been actively engaged in open-source projects. Notably, I was selected as one of the 103 participants for Code4Gov Tech, India's first open-source program. Moreover, I've contributed to various organizations such as Sunbird UCI, OpenFoodFacts, CaMicroscope, and Elixir-Cloud-Aai. Additionally, I took part in Script Winter of Code.

Some of my merged PR links:

Event Timeline

Prati28 renamed this task from Gsoc-2024 : Improve searchability and filtering of PageTriage feed (WIP) to GSoC-2024 : Improve searchability and filtering of PageTriage feed (WIP).Mar 20 2024, 9:56 AM

@Prati28 What project size are you aiming for ? I would suggest spacing out your timelines to account for delays and back-and-forth. Also, note that for large projects, you should be able to plan out your timeline early November (In case you need more time).