@sbassett it's not related with the extension.

Hey @MaryMunyoki, I don't yet have a formal future plan, with several patches awaiting review and merge I paused further changes, and once they land I will draft and share the concrete next steps.

This proposal addresses a very niche need, and while I understand the motivation behind it, I’m not in favor of changing the long-standing interface editing restrictions. Those restrictions exist to protect against vandalism and unintended security issues, and introducing a special exception for sandboxes would add complexity without bringing much value to the broader community.

The hang happens on CLI too, not just in IDEs. v42 works fine, but v43 hangs unless the <arg name="parallel" value="64"/> line is removed.

Hey @CBID2, I actually already replied to your question on the talk page. :) I'm the author of Adiutor (the gadget too), and I have not quit maintaining it. I believe you were misinformed. I stepped away from maintaining the extension, not the gadget. Since we are all volunteers and the gadget needs some care, I added the "unmaintained" template because it needs to be ported to ES6 and updated to follow Wikimedia ESLint rules.

Could you please specify your operating system and Java version? It works fine on macOS for me using:

See: https://packagist.org/packages/wikimedia/message

Hey @DTorsani-WMF, Thanks for reaching out! Unfortunately, I’m currently tied up and won’t be able to work on this immediately.

I've addressed the issues you raised regarding the Table component and Checkbox label handling in Codex PHP:

IMO, once the pending patches are merged, version 0.3.0 will be ready for release. They’re currently awaiting code review.

In T381327#10379053, @SLyngshede-WMF wrote:

@Dogu is it the wrong password :-)

It should be the same password you use for https://idp.wikimedia.org

Maybe something else went wrong with the hashing.

One workaround is to sign out on https://idm.wikimedia.org and then sign out of SSO as well, from https://idp.wikimedia.org/logout and then go to https://idm.wikimedia.org and pretend that you forgot your password. Or perhaps just a easy, use Toolforge: https://toolsadmin.wikimedia.org/profile/settings/change_password/ that will work as well.

I'll do a bit more digging, but I can understand if you just need to change your password. I'll work out the issue separately.

In T381327#10378573, @SLyngshede-WMF wrote:

@Dogu We've updated idm.wikimedia.org with the fix. If you still have a need to update your password, please give it a go and let me know how it goes.

In T361745#10358083, @DTorsani-WMF wrote:

Hi @Dogu thanks for the heads up. We have updated the permissions for the Figma file so you should be able to view it now. Let me know if you have any issues.

@DTorsani-WMF, @Sneha, I currently don't have access to the linked spec files. I've requested access, and I would appreciate it if someone could approve my request. Thank you!

I am planning to start the librarization of libs/message by focusing on its core functionality. Here’s a brief outline of the approach:

The issue is that libs/message does not currently support essential i18n features like {{PLURAL}} and {{GENDER}}. This limitation can make it challenging to provide the same robust internationalization capabilities expected from MediaWiki-style i18n in non-MediaWiki environments.

@CCiufo-WMF, sure thing!

@egardner I'll start coding this component according to the provided design specs. Once my patch is ready for review, I'll let you know. Let me know if there's anything else I should keep in mind while working on this. Thanks!

@CCiufo-WMF I’d love to work on T361745. I noticed @egardner is listed as the developer for this task—would it be possible for me to collaborate on the development or assist in any way?

@CCiufo-WMF If no one is planning to continue working on this task, I’d be happy to volunteer and take it forward.

In the task specifications for the ImageContainer component, there is no explicit mention of how the container’s width and height should be handled. While implementing the component, I used container-specific width (380px) and height (230px) to define the dimensions.

@Reedy The Codex PHP library was not designed solely for use within MediaWiki, so some features were not built to specifically target or depend on MediaWiki. Therefore, in the development phase, any third-party libraries in use could be replaced with Wikimedia-produced alternatives, if available.

In T379018#10314100, @egardner wrote:

We might need to add a new table empty state message to MW's Codex i18n files – for the time being I'm just copying those JSON files over into Codex PHP every time I do a release there.

@AnneT Codex PHP will be used in both MediaWiki and non-MediaWiki environments, so it’s best to add the i18n message separately. @egardner created T379429, which might help.

@AnneT, I noticed something: I think the i18n message for 'There is no data available' does not exist.

In T355150#10308304, @Bugreporter wrote:

Personally I do not support deploying Adiutor to Wikimedia. Wikimedia has multiple series of community moderation tools in parallel (extensions: Adiutor, PageTriage; Gadgets: Twinkle, etc.) and many of them are community specific and hard to customize. What I want is let all of these to be gone, and replaced with a new extension with high level abstraction - see the last section of https://meta.wikimedia.org/wiki/User:Okeyes_%28WMF%29/Localising_page_curation (yes, this will replace at least all page and user related functionalities of Twinkle).

The current code of Adiutor supposes wiki to have a AFD/CSD/PROD process. Though they can be disabled, they are bad by design (and it is why PageTriage fail to be useful outside enwiki) - In an extension we should not preassume such process will exist. These should be always configured in client side (with a template for common tasks cross-wiki like speedy deletion).

Open Letter to the Wikimedia Foundation:

Open Letter to the Wikimedia Foundation:

Open Letter to the Wikimedia Foundation: