Jump to content

User talk:Addshore

Add topic
From Meta, a Wikimedia project coordination wiki

Wikimedia Foundation Bulletin 2026 Issue 2

[edit]


MediaWiki message delivery 02:06, 4 February 2026 (UTC)Reply

Script Publisher - Community Wishlist 2022 implementation update

[edit]

Hello Addshore,

I hope you are doing well. I am reaching out regarding the Community Wishlist Survey 2022 proposal you supported: “A bot or gadget to publish public Git repo to a gadget or user script”

Over the past few months, I have been working on implementing this as a Toolforge-based OAuth application called Script Publisher. The goal is to provide a web-based interface that allows users to publish JS/CSS files from a public Git repository (e.g., GitHub) directly to user scripts or gadget pages, with explicit preview and confirmation before publishing.

Current project links:

  1. Toolforge deployment (work-in-progress MVP): https://script-publisher.toolforge.org/
  2. Source code (public repository): https://gitlab.wikimedia.org/toolforge-repos/script-publisher/
  3. Initial demo prototype: https://wikipublisher.vercel.app/

The tool currently supports:

  • Public repository fetching
  • File selection (JS/CSS)
  • Mapping files to target wiki pages
  • Preview before publish
  • Manual publish flow (no background automation)

The main blocker now is OAuth approval for JS-editing permissions. WMF security has raised valid concerns around applications that can edit JavaScript pages, especially site-wide JS. The discussion is ongoing here:

  1. User_talk:Dev_Jadiya#Script_Publisher
  2. https://meta.wikimedia.org/wiki/Steward_requests/Miscellaneous#OAuth_permissions

Since you originally supported this wishlist proposal, your technical input and perspective would be extremely valuable. In particular:

  • Does the current MVP align with what you expected from this wishlist?
  • Are there safeguards you believe are necessary for responsible deployment?
  • Would you be willing to share your view in the ongoing Meta discussion?

My intention is not to bypass any security expectations, but to implement this in a way that is aligned with community review standards (similar to bots or interface editors), while keeping the tool transparent, auditable, and limited to user-authorized edits.

Thank you again for supporting the original idea. I would truly appreciate your feedback. Regards, Dev Jadiya (talk) 14:40, 7 February 2026 (UTC)Reply