See mw:Bugwrangler for more information.
I am not a Product Manager.
Hi @Jidanni, this lacks a use case. Which underlying problem is solved by knowing the number of topics on a Flow talk page?
Asking as we do not display the number of sections or the number of words on a page either. We can display lots of things to make a page less readable, but there need to be use cases which get solved by displaying things.
@MohammadtheEditor : No problem, thanks for the update! :)
Hi @Joanmp14, for future reference, see https://meta.wikimedia.org/wiki/Requesting_wiki_configuration_changes - thanks!
Hi @RIT_RAJARSHI. This task sounds like a support request (how to change settings, questions how to do something, etc.). Wikimedia Phabricator is for bug reports and enhancement requests. Please ask support questions on the MediaWiki Support Desk or ask on a dedicated project/extension talk page if existing. Thanks.
Thanks. If Yahoo is involved, then quite often Yahoo is the problem (there are quite some tasks about Yahoo Mail here).
@318anushka: Whatever is written on https://www.mediawiki.org/wiki/Outreachy/Participants#Application_process_steps should be followed, I'd say. :)
@RIT_RAJARSHI: I'm asking you for another time to please summarize your "suggestion on quiz layout" by editing the task summary field and making the task summary more specific. Thanks!
Thanks. I guess it would help me and others if Vue.js had a better project description than "Tracking for Vue.js related work" (which sounds rather long-term to me), so I'm still wondering what exactly "the project" is in the sentence "The project is over". :)
So if I get you right this is something like "Write a project report for Vue.js powered search" or something?
@Tgr: There are a bunch of open tasks on the AICaptcha workboard , some "Done", some "Doing". That board and project looks neglected. What should happen with these tasks after this exploration? If some tasks should remain open, which codebase are these tasks about if they have no other project tag assigned, and should the artificial-intelligence tag be added in addition? Thanks.
Thank you Luke081515!
@Niedzielski: Which "project" is this about, and could you add that project to the task summary please? Thanks. (I guess that the Vue.js project itself is not over. ;)
@bd808: Yeah I only kept interfaceadmin in there because of the Main_Page. Thanks for your edits, appreciated!
@Jpgusanito: No problem at all, happy to help :)
(Hmm probably yes, but why is there a need to ever abandon changes in the Sandbox?)
@AlQaholic007: Why don/t you just try, but ask instead?
Here's the link to the bug i fixed.
Thanks. That is after the deadline which was four days ago.
@Ashuro07: Hi, you changed "Have you contacted your mentors already?" from "No" to "Yes". When exactly did you contact the mentors?
@eprodromou: Could you please answer the last comment? Thanks!
Personally I don't think that any developer should spend time on this if no interest has been expressed by the Commons community beforehand.
@srishakatux: I'm wondering
so the wiki pages will not require constant maintenance and updating, and it's not required to re-read and check the entire email templates to manually find items which need updating, instead of once simply searching for XXXXXX.
@Riley_Huntley: Is there a canonical way (e.g. a category name) on Commons to identify images/content as "not safe"?
Would these be recommendations for authors? Or only for blog admins who'd have to (re)format drafts in random formats provided by authors?
OK, but there is no "branding" at say, the bottom, indicating what is making it different.
(A statistics page has literally nothing to do with any DiscussionTools.)
but now what if I want to see the info page again?
@Ashuro07: Hi and welcome! See https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker#Feedback,_questions_and_support
If you have a good technical understanding and can both find and compare the docs both on mediawiki.org and in the mediawiki/core git repo , sure! :)
gives following error:
@AlQaholic007: Please always post text as text, so it can be indexed and searched for.
Please also always provide complete steps. This seems to be after running git review -d 585759. See https://www.mediawiki.org/wiki/How_to_report_a_bug
Alright, I rewrote https://www.mediawiki.org/wiki/User:AKlapper_(WMF)/Sandbox/T241646 to use TemplateStyles only and not (ab)use MediaWiki:Common.css.
I checked T213780 and I see that the user in question doesn't have a Kerberos account, how are you guys accessing Eventlogging data?
@Der_Keks: Thanks for the clarification, very appreciated!
Please see the documentation at https://www.mediawiki.org/wiki/Gerrit/Commit_message_guidelines
I added you by momentum. I guess adding someone to the subscribers is the appropriate way to go.
@Gbahdeyboh: I don't understand. :) If this is a "solution" then this maybe could have been added to the existing task, to avoid fragmentation of conversations?
Adding WMF-Design as this task lacks code or team tags.
@Arrbee: No reply for many years, hence closing
I am going to decline this task.
People often still tag tasks good first task without making sure first that these tasks have sufficient information, so we try to triage "the most recent ones" at least.
We have a huge backlog of hundreds of tasks and many of them are likely not always good first tasks by definition (either lack of information, or outdated) and we do not even have capacity to "triage" all these tasks, much less capacity to drag stuff into workboard columns.
Thanks Tobias1984! (I just gave it a read.)
...and I finally realize that we really must rework https://www.mediawiki.org/wiki/User:AKlapper_(WMF)/Sandbox/T241646 and cover TemplateStyles.
TemplateStyles are the way to go. See T228604 or T248416 for more references.
Hi @HarishPandalangatt, thanks for taking the time to report this and welcome to Wikimedia Phabricator!
This is on-wiki content at https://en.wikipedia.org/wiki/Template:GeoTemplate which is not tracked in Phabricator, as far as I know.
Feel free to edit that template page content.
Cannot reproduce in Firefox 74. I can only sometimes reproduce in Chromium 80.
@Jidanni: Please always provide browser and browser information when reporting issues, so people don't have to interpret.
Also note that the zoom button itself does NOT move. The viewport in your browser of the complete page moves.
Hence I do not think that there is anything to fix in Wikimedia code if your browser thinks that your browser should focus something lower on the page.
Hi, please see https://www.mediawiki.org/wiki/How_to_report_a_bug#Reporting_a_login_problem and report back.
@RIT_RAJARSHI: Also, the taks summary is still too vague, as pointed out in my previous comment. Please make the task summary more specific, otherwise all feature request only say "Suggestions", and nobody knows which feature requests is about what when looking at the list of open tasks. Thanks.
@RIT_RAJARSHI: This is an interesting idea however I am afraid that this task cannot be worked on for several reasons and hence will be declined: It includes several different feature requests (please read https://www.mediawiki.org/wiki/How_to_report_a_bug ), bascially proposes a complete re-write of the code base, and would require templates to be global (see T121470).
@RIT_RAJARSHI: Hi and welcome. Please edit the task summary and summarize your "Suggestion on Quiz Layout" in the task summary and please explain which actual problem you'd like to solve by your proposal. Please see and follow https://www.mediawiki.org/wiki/How_to_report_a_bug
You can edit the task summary and description by clicking Edit Task. Thanks a lot!