See mw:Bugwrangler for more information.
I am not a Product Manager.
@ThurnerRupert: Please see https://meta.wikimedia.org/wiki/Requesting_wiki_configuration_changes for future reference (and https://www.mediawiki.org/wiki/Review_queue about deploying code bases that have not been used on any Wikimedia servers before).
@Paarmita: Thanks for the patch! Please fix the six problems pointed out by jenkins-bot (linked in its comment in Gerrit) and improve the commit message (better summary, use imperative mood, link to corresponding Phabricator task) and amend your patch (that link also covers how to change the commit summary).
Whoever is "on duty" in the SRE team (#wikimedia-operations on Freenode IRC) is supposed to follow https://wikitech.wikimedia.org/wiki/SRE_Clinic_Duty#Review_incoming_tasks
(This is still missing any steps to reproduce. We still do not know which exact steps you performed which resulted in that URL/link that you posted. Please follow the format on https://www.mediawiki.org/wiki/How_to_report_a_bug when reporting problems.) Anyway, the most important question is:
@Shahadat: Thanks for reporting this. Please follow https://www.mediawiki.org/wiki/How_to_report_a_bug and provide clear steps to reproduce, step by step, as a list of steps, including URLs.
Can Misibacsi please try again with safemode=1? This allows you to test if a problem is because of your user scripts or personal gadgets without uninstalling them. See https://www.mediawiki.org/wiki/Help:Locating_broken_scripts for more information.
Are there any errors in the "Console" or "Network" tab of the Developer Tools? See https://docs.microsoft.com/en-us/microsoft-edge/devtools-guide/console
For the records, de says "from the translation system", cs also says "from translation", fr says "from translations to do".
When creating a task using the simple creation form, users should be required chose a subtype, defaulting to task.
I'd not want this option shown for all and any users. Adds just more clutter to the UI and for some users everything is a bug while it's a feature for PMs and devs.
@Paarmita: Hi, if there is a good reason that you want to travel into the past (e.g. you cannot reproduce an issue with the latest code in git master) and want to get the code at the time when a specific revision was given a tag: I assume you already cloned the repository via git clone..git tag -l lists all available tags. For example, git checkout tags/0.27.6 will locally set the code to the revision when the 0.27.6 tag was created.
Also, what do you mean by "bz issue"?
Yes, the project is stalled for the foreseeable future and should be archived. I've updated the project description in Phabricator.
Wrong place. See https://www.mediawiki.org/wiki/Phabricator what this is (not).
Requested public project WebPageReplay has been created: https://phabricator.wikimedia.org/project/view/3619/
@Paarmita: Thanks. Please see https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker
because on a search for possible older tickets this was not shown to me (I searched for redirect, the other one has redirection, maybe this matters).
Step3 on https://www.mediawiki.org/wiki/Wikimedia_Security_Team/Policy/Access_to_security_issues says "Sign a volunteer non-disclosure agreement or a WMF employee non-disclosure agreement;" (emphasis by me) so I don't see anything to update.
I should have used https://phabricator.wikimedia.org/transactions/editengine/maniphest.task/defaults/33/ instead of https://phabricator.wikimedia.org/transactions/editengine/maniphest.task/edit/33/ and paid more attention. :-/
Sorry, fixed now!
This task welcomes a problem description. Currently it only offers a potential solution to an unknown problem.
Hi @Zzmonty. For a configuration change, local consensus is required according to 'Requesting wiki configuration changes'. Could you bring up the matter on the Village pump page of your wiki (or any other appropriate place) to confirm that this change is wanted by the community, and paste the link to that discussion here?
I see some patterns, like
@Flixtey: Hi, this is Operations so the process described on https://wikitech.wikimedia.org/wiki/SRE_Clinic_Duty applies
Thanks! So you end up at null because of the second parameter and because $(cp).click(_public.analyzeThisPage); is ignored.
@Formatierer: Let's please keep the discussion centralized in one single place. Thanks. :)
Any debug output with debug=true? See https://www.mediawiki.org/wiki/Help:Locating_broken_scripts
Confirming. No output in the developer tools' console when trying with debug=true either.
Could someone from the Growth-Team clarify please, to not leave this in a confusing limbo which won't allow other contributors to chime in?:
@Mz83ude: CC-BY-NC-4.0 is a non-free license and (in my understanding) violates the requirements to be hosted in Wikimedia Gerrit.
@Olaf_Simons: Any news?
Previous "Preamble" content on https://phabricator.wikimedia.org/transactions/editengine/maniphest.task/edit/33/ :
Use this form for requesting an extension or skin to be archived. * **Title:** Replace `<name of extension/skin>` with the name of extension or skin you want to be archived. * **Tags** ** Replace the tag #mediawiki-extensions-general-or-unknown and #Other-skins with the Phabricator project of the extension/skin if it has a dedicated Phabricator project. ** If there's no documentation of this project on any wikis, feel free to remove the #Documentation tag. * **Descripition:** ** Please provide a reason on why the the extension needs to be archived. ** Add any other maintainers as subscribers to this ticket so they're aware of it. ** Provide any notes here if there's anything else that others might need to know. ** Remove any of the following actions if they're not applicable to this extension/skin. ** If your extension/skin has a dedicated Phabricator project, replace `<#ProjectX>` with the project name.
Requested public project Commons-Twitter-Bot has been created: https://phabricator.wikimedia.org/project/view/3616/
I kept the name consistent with the Gerrit repo name and added an alias for the proposed name.
Yes, thanks. Looks like https://tools.wmflabs.org/wm-commons-emoji-bot/ and https://tools.wmflabs.org/admin/tool/wm-commons-emoji-bot , for the project description.
Requested public project MediaWiki-extensions-ChangeUserPasswords has been created: https://phabricator.wikimedia.org/project/view/3615/
@Mz83ude: Would it be possible to add a license-name field/value to extension.json and the infobox on https://www.mediawiki.org/wiki/Extension:ChangeUserPasswords ?
wikibasemediainfo ? If not please correct
IMO, open tasks should be added to Security and closed ones are not worth worrying about.
Could this be split into subtasks with documentation how to find instances and turned into Google-Code-in-2018 tasks, maybe?
Unfortunately closing this report as no further information has been provided.
srodlund created this object with edit policy "Custom Policy".
Might be rather Apache territory than a site request? not sure though
Sorry, quoting Google:
It is not a "task" to require someone to make an account, sign up for a mailing list, or follow you on social media. Some of those things are overhead, some of the others are blatant marketing and don't benefit the student. We understand that sometimes this kind of trivial task is used as a beginner / hook task, but you'll need to find other things that are not trivial and don't violate privacy concerns.
Who's responsible for the development of Quibble?
Please read its project description page as it lists an owner...
Same in many other channels such as #wikimedia-tech, #wikimedia-devrel etc.
#wikidata went for "Only registered (and authenticated) users will be heard when talking" today.
@MaroonPixel: Thanks! Please see https://www.mediawiki.org/wiki/Google_Code-in/Mentors for how to mentor and requirements.
Which exact MediaWiki and extension versions and branches are used?
@Pine: Please provide the message headers of one of these messages - unfortunately the archive at https://lists.wikimedia.org/pipermail/education/2018-September.txt.gz does not include them.
Glad you found the reason. Closing this task as invalid as there is no wrong behavior.
@kaldari: Workboard visualization out of sync, I guess... I tried to drag it from "Revisit" to the "Upcoming Work" column and got Unhandled Exception: Unable to find object "PHID-TASK-bqrlttxcm5qknkucjucy" in column "PHID-PCOL-vaw55qipj2ivbyj6koqk" on board "PHID-PROJ-m5xekuzpcucwdjim2onx. Dragging the other way round (from Upcoming to Revisit) and then back (from Revisit to Upcoming) removed the duplicate. Feel free to file a bug report under Phabricator.
Also see Chad's comment from 2017-02-06 on https://gerrit.wikimedia.org/r/#/c/335714/ again...
In general you should not expect complex templates blindly copied from enwiki to work.
I am closing this task as invalid, in my understanding, as this task is about some on-wiki content.
On-wiki content is out of scope for Phabricator and not handled here in tasks.
Same for querying a list of all Wikidata tasks at https://phabricator.wikimedia.org/maniphest/query/QbWgRtSw4dQk/#R