@DILLA2: Thanks for reporting this. For future reference, please use the feature request form (linked from the top of the task creation page) to create feature requests, and fill in all the sections in the template. Thanks.

Since https://we.phorge.it/T15554, Phorge shouldn't spectacularly blow up anymore when running into a PHP8 issue. However after running PHPStan (static code analysis) I believe there's still quite some stuff to potentially fix in upstream, however those might be less common code paths.

I deleted that Phabricator Diffusion repository (which just had two files saying it's dead anyway)

I sent them an email requesting a reply on this task back on May 31st.

@Nintendofan885: Could you please answer the last comment? Thanks in advance!

In T201251#9852700, @Pppery wrote:

you are welcome to file another task for it.

@Atieno: Would you know who could look into this / who's the owner of that info nowadays? TIA! (Asking as you're assigned to T372295)

@Techwizzie: Hi, you are listed as a maintainer on https://www.mediawiki.org/wiki/Extension:PagePermissions . Could you please share the dedicated place for bug reports and feature requests and document that, so you'll see them? If you'd like to use Wikimedia Phabricator for PagePermissions' bug reports and feature requests, please request a dedicated project tag via https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects - thanks a lot!

That's the same underlying problem.

On MediaWiki 1.41.0

https://www.mediawiki.org/wiki/Release_notes/1.41 does not list 1.41.2; https://www.mediawiki.org/wiki/Release_notes/1.40 does not list 1.40.4.

This looks like https://www.mediawiki.org/wiki/Extension:Cookiecutter ; are you involved in its development?

See https://www.mediawiki.org/wiki/Phabricator/Project_management#Types_of_Projects for our taxonomy.
Also, what would happen to the subproject at https://phabricator.wikimedia.org/project/view/6190/ ?

https://meta.wikimedia.org/wiki/Template:Portal_navigation

@SD0001: Please don't change task scope after a task was resolved but file a new task for different things - thanks. :)

Never seen again. Please reopen if this still happens.

@diegodlh: Thanks for participating in the Hackathon! We hope you had a great time.

• If this session took place: Please change the task status to resolved via the Add Action... → Change Status dropdown.
  • If there are session notes (e.g. on Etherpad or a wiki page), or if the session was recorded, please make sure these resources are linked from this task.
  • If there are specific follow-up tasks from this session / event: Please create dedicated tasks and add another active project tag to those tasks, so others can find those tasks (as likely nobody in the future will look at the Hackathon workboard when trying to find something they are interested in).
• In this session / event did not take place: Please set the task status to declined.

@Susannaanas: Thanks for participating in the Hackathon! We hope you had a great time.

@Maurusian: Thanks for participating in the Hackathon! We hope you had a great time.

@srishakatux, @MaryMunyoki: Hi,

• If this initiative took place: Please change the task status to resolved via the Add Action... → Change Status dropdown.
• In this session / event did not take place: Please set the task status to declined.

Thank you, Phabricator housekeeping service

@JWheeler-WMF, hi!

• If this initiative took place: Please change the task status to resolved via the Add Action... → Change Status dropdown.
• In this session / event did not take place: Please set the task status to declined.

Thank you, Phabricator housekeeping service

• If this session took place: Please change the task status to resolved via the Add Action... → Change Status dropdown.
  • If there are session notes (e.g. on Etherpad or a wiki page), or if the session was recorded, please make sure these resources are linked from this task.
  • If there are specific follow-up tasks from this session / event: Please create dedicated tasks and add another active project tag to those tasks, so others can find those tasks (as likely nobody in the future will look at the Hackathon workboard when trying to find something they are interested in).
• In this session / event did not take place: Please set the task status to declined.

@Moberg: Thanks for reporting this. For future reference, please use the bug report form (linked from the top of the task creation page) to create a bug report, and fill in all the sections in the template.

@zhuyifei1999 ping

The main drawback is that you cannot add an URI to observe a repo if you don't change the other automatically-generated URIs (generally 4 for each repo) either to No I/O or Read Only. If you don't do that, Phabricator simply won't let you add an URI to Observe. Doing the disables via the UI is a pain as you have to disable manually each and every one of them.

I'm going to decline this as these six URIs are only listed in a view not accessible by average users thanks to our custom downstream patch for T361997: Expose only canonical Clone URI in Diffusion when repo hosted externally and Differential disabled, and as the time-consuming aspect of having to edit all of them as a member of Diffusion-Repository-Administrators in order to allow observing an external repository URI should be gone once T224753: Set new Diffusion repos URIs to No I/O by default has been merged and deployed in our instance.

I found my own notes in T347577#9284700 again linking to https://we.phorge.it/book/phorge/article/diffusion_uris/#reference-i-o-types to remember that I don't want to touch the rather confusing IO_DEFAULT logic and realized that changing Phorge's behavior when it itself creates/initializes a new repo (no user interaction invoved at this stage) would be the least invasive (and most maintainable) thing to do.

Forcing more than 30 volunteers to use closed-source

Proposed in upstream as https://we.phorge.it/D25777

Fixed by https://gitlab.wikimedia.org/repos/phabricator/deployment/-/commit/e6dbd6f64658738ce1f4d1f2d29f0ae272b2a2d6

If anyone wanted to write custom code to query global locks on connected SUL accounts before UPDATEing a Phab user's sessionKey, per past discussions in https://secure.phabricator.com/T4806 that should likely go into loadUserForSession() in https://phabricator.wikimedia.org/source/phabricator/browse/wmf%252Fstable/src/applications/auth/engine/PhabricatorAuthSessionEngine.php

@Guseynaga: If you want to make this configuration change yourself, please see https://wikitech.wikimedia.org/wiki/Wikimedia_site_requests and give it a try in Gerrit.

I get the spirit but I would not want to force folks who over years have gathered expertise and established workflows to smoothly run an important aspect of an event to use other folks' hardware (if it was me it would stress me out). It's the personal freedom of each individual which software they prefer to run on their systems and IMHO that freedom outweighs ideology aspects (YMMV), sorry.

Yeah overengineering or maybe categorizing for the sake of categorizing (though with good intentions) has its popular moments...

Cleaning the backlog a bit as I do not plan to work on this but please do reopen once someone contributed a patch!

I'm tempted to resolve this task tagged with Phabricator and create a separate one for MediaWiki-Vagrant (is the modules/profile/templates/idp/client/httpd-puppetboard-ng.erb result in Puppet relevant?) because I dislike fixed issues displayed as unresolved tasks in my backlog. Eh?

+dark-mode so people can find dark mode issues

Hi @Superraptor123. This does not sound like something is wrong in the code base (a so-called "software bug"), but instead like a support request (how to change settings, questions how to do something, etc.).
As Wikimedia Phabricator is for bug reports, enhancement requests, and planning work, please check https://www.mediawiki.org/wiki/Communication - Thanks for your understanding!

@dchan: Unrelated but could you please also link your LDAP account to be listed on https://phabricator.wikimedia.org/p/dchan/ ? Thanks!

Folks are free to use the "Back" button of their browser, I'd say. I don't see how the current behavior is a bug...

Hi, the repository is hosted in https://github.com/WikiEducationFoundation/WikiEduDashboard and does not use Wikimedia Phabricator for issues. Please file your ticket in GitHub. Thanks.

+1 on Krinkle's comment in T143162#7252814

I guess this task can be closed as invalid nowadays as it's a placeholder that no team plans to work on?