Hi! I'm Usama Walayat, a GSoC 2026 applicant for the Wikifile-Transfer project. I'd like to claim this task. Here's my deep analysis and proposed solution:
Problem:
When a user is about to upload an edited video back to Wikimedia Commons, VideoCutTool shows a raw wikitext field (the file description page text). This raw wikitext — full of {{Information}} templates, [[Category:...]] links, and licence templates — is unreadable to most users. They cannot visually verify what the final Commons file page will look like before uploading.
Root Cause:
The frontend (React) currently renders the wikitext upload field as a plain <textarea> with no preview capability. There is no call to MediaWiki's action=parse API to render the wikitext into HTML before upload.
My Proposed Solution:

Hi! I'm Usama Walayat, a GSoC 2026 applicant for the Wikifile-Transfer project. I'd like to claim this task. Here's my deep analysis and proposed solution:
Problem:
The WMCZ Tracker (a Django-based expense and document tracking tool for Wikimedia CZ) has a global search feature. Currently when users search for anything, the search query also scans through boolean/checkbox fields like "Wage?" and "Paid?". This makes no sense — these are Yes/No fields and searching them with text produces irrelevant or misleading results, polluting the search output with unintended matches.
Root Cause:
In the Django Tracker codebase, the search view likely uses a broad Q() query that includes ALL model fields via icontains — including boolean fields like is_wage and is_paid. Django does not raise an error when you apply icontains to a BooleanField but it produces meaningless results.
My Proposed Solution:

Hi! I'm Usama Walayat, a GSoC 2026 applicant for the Wikifile-Transfer project. I'd like to claim this task. Here's my deep analysis and proposed solution:
Problem:
The Recent Changes filter panel allows users to filter by namespace using the namespace name (e.g., "Talk", "User", "File"). However, it does NOT support searching by namespace number (e.g., typing "1" to find the Talk namespace, or "6" for File). This is painful for experienced MediaWiki developers and admins who know namespaces by their numeric IDs — especially on wikis with many custom namespaces (100+) where the name may be in another language.
Root Cause:
In resources/src/mediawiki.rcfilters/ui/FilterMenuOptionWidget.js, the matchesFilter() method only compares the search string against the namespace label (human-readable name). It never checks against mw.config.get('wgFormattedNamespaces') which stores the numeric ID → name mapping.
My Proposed Solution:

Hi! I'm Usama Walayat, a GSoC 2026 applicant for the Wikifile-Transfer project. I'd like to claim this task. After reviewing the VideoCutTool repositories on Gerrit (labs/tools/VideoCutTool frontend and labs/tools/video-cut-tool-back-end), here is my detailed test plan:
My Proposed Solution:

Hi! I'm Usama Walayat, a GSoC 2026 applicant for the Wikifile-Transfer project. I'd like to claim this task. After studying the VideoCutTool codebase (gerrit.wikimedia.org/r/admin/projects/labs/tools/VideoCutTool), here is my exact proposed solution:
My Proposed Solution:

Hi! I'm Usama Walayat, a GSoC 2026 applicant for the Wikifile-Transfer project. I have hands-on experience with Python and Flask and would love to contribute to this documentation task. May I claim it? I'll get started right away once assigned