See mw:Bugwrangler for more information.
I am not a Product Manager.
Asked followup question in https://gitlab.com/Bitergia/c/Wikimedia/support/issues/54 (eliminating duplicates automatically for mirrored repositories?); plus want to sort out https://gitlab.com/Bitergia/c/Wikimedia/support/issues/55 first before trying this.
See https://wikitech.wikimedia.org/wiki/Deployments#Near-term for available deployment slots (once the patch has been written, reviewed, and merged).
Hi @Anthony_Appleyard, thanks for taking the time to report this! Which exact version of MediaWiki do you use?
What is "the fault" exactly? Please describe expected behavior and follow https://www.mediawiki.org/wiki/How_to_report_a_bug - thanks!
It looks like the caption does not belong to the gallery.
And which mode sets the caption centered? On the page you linked there is no information about which mode centers the caption and which not.
You can see it in the examples.
On the next screenshot the caption is even completely off the gallery
Please always provide clear steps to reproduce a problem if you think that something is "centered incorrectly for too few images" somewhere: https://www.mediawiki.org/wiki/How_to_report_a_bug Currently there are no steps at all here.
That's normal if you don't set a mode which centers captions.
@Sadads: In short: Someone needs to write a patch and put it into Gerrit. Then someone needs to review and +2 the patch. Then the patch gets automatically merged into the repository. The latest code in a repository gets deployed once a week onto servers to become available to everybody accessing Wikimedia sites in their browser, or earlier if someone explicitly schedules it for a SWAT deployment.
there should be time during Tech Day on Wednesday
Oh thanks! Alright, there is a GDoc for Wed where we can add talks for Tech at least. Feel free to join. :)
@AlexisJazz: Thanks for taking a look at the code! If you feel like proposing software changes to be reviewed and merged, you are very welcome to use developer access to submit the proposed code changes as a Git branch directly into Gerrit. If you don't want to set up Git/Gerrit, you can also use the Gerrit Patch Uploader.
@nirajan_pant: For future reference, please follow https://meta.wikimedia.org/wiki/Requesting_wiki_configuration_changes (and check the preview of the task description). Thanks!
https://zh.wikipedia.org/wiki/File:Ampallang2.jpg?redirect=no now states that it has been deleted?:
2019年1月17日 (四) 04:25 AT（讨论 | 贡献）删除页面File:Ampallang2.jpg （F6 (TW)） （感谢）
@biplabanand: For future reference, please follow https://meta.wikimedia.org/wiki/Requesting_wiki_configuration_changes - thanks a lot!
@Majora: For future reference, please follow https://meta.wikimedia.org/wiki/Requesting_wiki_configuration_changes - thanks a lot!
Please [[phab:|report bugs]] if you see them.
To notify Tech News, see Notice. Small nitpick: Please avoid linking to the generic Phab front page. :) [https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=projecttag1,projecttag2 foo] could be more helpful (full URL as ? breaks stuff when using [[internal|links]]).
Assuming this is about Wikibase-Quality-Constraints
Note: A custom dashboard for Xen exists at https://xen.biterg.io/app/kibana#/dashboard/C_Community_Focused_Dashboard with a widget called "Top People Reviewing Patches". Not sure how supported that is (custom, plus that instance is still running an older software version).
Documented in https://www.mediawiki.org/w/index.php?title=Community_metrics&type=revision&diff=3056548&oldid=3056018 what's possible and where.
Please do not set a deadline when there is no deadline: https://www.mediawiki.org/wiki/How_to_report_a_bug
If there is a need for @Matthias_Geisler_WMDE to confirm his identity, please suggest the preferred way to do it.
As far as I know there is no setting that allows raising that limit per wiki, hence removing Wikimedia-Site-requests
I realize that anything with storage in its name should clarify the difference to media-storage on Wikimedia servers, if someone more tech-savvy could write a sentence explaining that. :-/
I'm afraid #mediawiki-page could be too ambiguous for task reporters (I remember Page-Issue-Warnings was initially called #Mobile-Page-Issues making people report any random issues they have with mobile pages).
Sigh, naming is hard.
Removing Developer-Advocacy as I don't see a relation.
Closing as per last comments.
Not sure which project tags apply here, someone please correct. General docs: https://www.mediawiki.org/wiki/API:Showing_nearby_wiki_information
Unrelated to the MW-1.32-notes, hence removing that tag.
It might be unrealistic but then I might miss the point of the entire proposal? :)
Which underlying problem is solved by spending time categorizing things if noone plans to take care about the items in the categories?
my racconicorn no like dragon
Thanks for filing this.
Leaving a talk page message for the authors to watch the relevant projects.
This needs to happen before creating a project tag, and getting consent and agreement from the developer/maintainer that they want to use Wikimedia Phabricator for tracking tasks and especially that there is not already an issue tracker somewhere else. I do not want to create a place in Wikimedia Phabricator where people file tasks while the maintainer/developer of a codebase expects those tasks to be filed somewhere totally else.
@Alex_brollo: Please always provide links so no-one has to guess what you refer to. :)
I guess this is about https://en.wikisource.org/wiki/User:Phe-bot which links to https://tools.wmflabs.org/phetools/ .
It now does not seem anymore that this has mostly stopped, hence reverting the Priority change from a few days ago.
@Alex_brollo: Please explain what/in which gadget or application or server "Merge and Split tool" is and follow the structure in https://www.mediawiki.org/wiki/How_to_report_a_bug when creating tasks here. Thanks!
Unfortunately closing this report as no further information has been provided.
Hi @DonTrung, thanks for taking the time to report this!
Unfortunately this report lacks some information. If you have time and can still reproduce the problem: Please add a more complete description to this report by providing a specific link to an example where the issue can be seen and information about your web browser(s) and operating system.
You can edit the task description by clicking Edit Task.
Ideally, exact and clear steps to reproduce should allow any other person to follow these steps (without having to interpret those steps) and see the same results. Problems that others can reliably reproduce can get fixed faster. Thanks!
Hi @AtulAhire007. Thanks for taking the time to report this, however Wikimedia Phabricator is for reporting software issues only. For more general discussion of the content in English Wikipedia articles, please refer to https://en.wikipedia.org/wiki/Wikipedia:Help_desk . For future reference, see https://www.mediawiki.org/wiki/How_to_report_a_bug how to structure tasks in Phabricator - thanks!
In my understanding this is exactly what Event Metrics is about. Hence please don't duplicate work but team up? :)
(Removing Language-Team as it is up to each team to decide what they work on.)
@Pavel.petrovic: Welcome to Wikimedia Phabricator. No need for swearing. :) Different people and different teams may have different priorities given their limited resources. Please feel free to help by testing and improving the proposed patches linked above.
Is this "on wikitech.wikimedia.org" or where will deployment(s) take place?
@Praveenp: For future reference, please try to add appropriate project tags so the software maintainers can find this task.
(ContentTranslation maintainers will likely not see / follow tasks which are tagged only as Malayalam-Sites, I'm afraid.) :) Thanks!
Hmm. My main concern is that https://www.mediawiki.org/wiki/Extension:NamespaceRelations states that it is unmaintained.