User talk:Zamkorus

Join us for “Many Tongues, One Movement: Voices Across Languages”!

Hello Zamkorus,

We’re excited to invite you to an inspiring global virtual gathering: the first Capacity Exchange Translat-a-thon.

Together with Language Diversity Hub, the Capacity Exchange (CapX) team will host its first Translation Marathon dedicated to ensuring linguistic equity in access to this amazing tool aimed to connect Wikimedians.
If you enjoy contributing to Wikimedia projects through translating and adapting content into different languages, this event is for you! Join us in the celebration of the multilingual spirit of the Wikimedia Movement at an event where communities that contribute in diverse languages will be able to share local knowledge and collaborate across borders.
Many Tongues, One Movement: Voices Across Languages

• Date: December 6, 2025
• Time: 12 PM (UTC) - Check the event page for your local timezone
• Location: Online (Meta-Wiki + live session links)

Register for the Event here

If you can’t join the live event, you can still contribute to the translations! Edits will be counted for two weeks, until December 20th. And everyone who participates will receive a special badge to display on their CapX profiles.

Strengthen your collaboration through CapX

We invite you and your community to join the Capacity Exchange (CapX), a Wikimedia community-built platform for connecting, collaborating, and exchanging skills with peers across the movement.

CapX helps Wikimedians and organizations find each other, share expertise, and build stronger, more connected communities.

Whether you’re an individual contributor, a user group, a community initiative or an affiliate, CapX helps you grow through knowledge exchange.

Sign up to CapX

More information

→ Explore the CapX platform: capx.toolforge.org
→ Read: User Guide & FAQ
→ Watch: Meet the Capacity Exchange video
→ Join our Telegram community chat: CapX Telegram Group

If your community, usergroup or affiliate would like to have a CapX organization profile, please reach out at capx@wmnobrasil.org, and we’d be delighted to support you.

With warm regards,
Joris Darlington Quarshie
Outreach Facilitator,
Capacity Exchange Project – Wikimedia Brasil

MediaWiki message delivery (talk) 14:55, 13 November 2025 (UTC)

Script Publisher - Community Wishlist 2022 implementation update

Hello Zamkorus,

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:38, 7 February 2026 (UTC)