Week 1: May 25 - May 31
Summary of the work:
This week’s work focused on understanding the Wikimedia Foundation, the sister projects it supports, and how Wikimedia content is written, discussed, and reviewed. The sessions covered the foundational policies of Wikipedia, the basics of content and code licensing, the role of Wikimedia Commons, and the technical context behind the WikiFileTransfer project. Alongside the session discussions, I also explored the MediaWiki Action API and studied several Commons and Wikipedia file pages to better understand how licensing is represented on-wiki.
Tasks completed:
Reviewed the history and role of the Wikimedia Foundation and how Wikimedia pages are built using wiki markup and wikitext, including the use of DiscussionTools in the Talk namespace.
Analyzed how content correctness is maintained through volunteer review, reliable sourcing, public page history, and IP tracking to issue warnings or blocks for wrong information.
Categorized the sister projects by purpose and audience: the reference group (Wikipedia, Wiktionary, Wikiquote, Wikibooks), the collections group (Commons, Wikisource, Wikiversity, Wikispecies), and the technology/coordination projects (Wikidata, Wikifunctions, MediaWiki, Wikivoyage, Meta-Wiki).
Reviewed Wikipedia’s Five Pillars and core policies including WP:NOR, WP:V, WP:NPOV, WP:BIO, WP:COI, and WP:NOT.
Studied copyright, content licensing models used on Wikipedia (CC BY-SA 4.0, GFDL 1.3, Public Domain/CC0, Fair use/EDP), and the four Creative Commons components (BY, SA, NC, ND).
Discussed software licenses commonly used in Wikimedia-related projects (MIT, GPL v2/v3, Apache 2.0).
Analyzed Wikimedia Commons policies and the workflow of the WikiFileTransfer project, mapping out its Python-based stack (Flask, Celery, templatelist.py) and MediaWiki API integration.
Explored the MediaWiki Action API operations (action=query, action=parse, action=upload), JSON output format, and the use of tokens.
Completed homework analyzing five files with different licensing situations: a CC BY-SA 4.0 image, a CC BY 4.0 image, a CC0 1.0 image, a Public Domain historical portrait (PD), and a Fair Use non-free film poster of Sholay.
Challenges faced:
Understanding the strict rules for non-free files (such as film posters or company logos). Because they cannot be hosted on Commons, they remain on local wikis under strict Exemption Doctrine Policy (EDP) rules. Understanding that non-free rationales may need to be rewritten per wiki makes cross-wiki transfers conceptually complex.
Recognizing the limitations of the current WikiFileTransfer project: it does not automatically verify EDP compliance and assumes the file being transferred is already valid, which is a challenge but also an area for future contribution.
Learnings and skills gained:
Ecosystem structure: Learned why each project stays independent. MediaWiki is designed for collaboration without defined content owners, making it flexible enough to support different content models, rules, and community expectations.
Accessibility and safety: Learned about Wikimedia's commitment to digital accessibility, low-bandwidth access, the Wikimedia sound logo, and resources for volunteer safety, human-rights, and privacy.
Licensing rules: Gained a clear understanding of what “free” means in the Wikimedia context. Commons accepts freely licensed files but strictly rejects non-free content, NC-licensed files, ND-licensed files, and fair-use material.
Technical architecture: Understood how WikiFileTransfer works to automate tedious cross-wiki file migrations by fetching wikitext, checking for non-free templates, and re-uploading files while preserving metadata and source information.
API fundamentals: Learned how to interact programmatically with Wikimedia sites using the MediaWiki API, connecting the session discussions to actual development work.
Additional comments as needed:
Next Steps: In the coming week, I will set up my local development environment, make my first MediaWiki API calls, and take look at the WikiFileTransfer codebase properly. I also plan to understand more deeply how file pages are structured on-wiki using wikitext and templates for understanding further project details.

Yes, I have submitted my proposal on the GSoC platform as well. I really appreciate the support and am looking forward to contributing to Wikimedia!

@Aklapper can you add this as a subtask in the wikifile transfer enhancement project so that mentors can see accordingly

@LGoto can you try contacting the mentors for clarifications as to how do I proceed I have submitted the proposal and PR for the minitasks but want to get it reviewed from the mentors, what shall I do?

@ParasharSarthak @Jnanaranjan_sahu could you please take a look at PR #61 for T415715 and T415717. It covers the backend error-handling improvements and temp-file cleanup work. I have also completed my GSoC proposal, do you want me to share it over here so that we can discuss accordingly

@ParasharSarthak @Jnanaranjan_sahu I have opened PR #61 for T415715 and T415717. It covers the backend error-handling improvements and temp-file cleanup work: standardized JSON error responses, removal of silent/broad exception handling, structured logging, and deterministic cleanup for uploaded temporary files. I have explained the details in the PR; please review it and share your feedback.

Hi @ParasharSarthak, for this task I want to discuss how I plan to implement the task and the work I have done.
I have worked on:

• Custom Exceptions: Created exceptions.py with specific error classes like MediaWikiAPIError, UploadError, and ValidationError (inheriting from a base AppError).
• Structured Rotating File-Based Logging: Added logging_config.py to set up a RotatingFileHandler for both the Flask app and Celery workers, so logs are saved to a file without growing too large.
• Removed Broad Exceptions: Updated tasks.py and utils.py to catch specific errors (like requests.exceptions.RequestException) instead of using bare except Exception: blocks, which were hiding the real errors.

How I plan to implement the remaining parts:

@LGoto can you answer to the above comment, also I think it is fine if we start before the contributing period but still please clarify it.

Hello @ParasharSarthak, I have completed local setup using Docker and have worked for an initial PR for the part structured, rotating file-based logging.
Implemented it with these details

• Added a new logging_config.py module with a RotatingFileHandler (10MB max, 5 backups)
• Updated app.py to call setup_logging(app) for Flask/Gunicorn logging
• Updated celeryWorker.py to call setup_logging() for consistent Celery task logging
• Mounted host ./logs/ to /app/logs/ in docker-compose.yml for log persistence across restarts

I'm ready to proceed with the next parts once you've had a chance to review.