So... I believe that understanding and defining which pages should be Tutorials vs How-Tos vs References is the key.
I urge anybody to read https://www.divio.com/en/blog/documentation/ (pretty much the talk I attended at Write The Docs conference).
What would "better error handling" be?
@Pablo-WMDE: Please make sure that either the status of tasks is changed to "resolved" once these tasks are done, or that open tasks have active projects (like WMDE-Fundraising-Tech) associated so they can be found on workboards. Could you please update this task accordingly? Thanks!
No, as for sidebar items it feels more usual to link to some anchors. I would not expect that from a top-level logo link... :)
If you refer to a comment on Gerrit you likely want to reply on Gerrit. So everybody involved can actually see the context. :)
I do not consider this a bug as the name of an anchor on a page is not the same as the name of a page?
Item is now called Changesets Statistics (Open Time in Days) hence closing this task. Thanks!
Hi @Uchup19, 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 (a list of steps to reproduce which leave no room for interpretation what to do, describing actual results and expected results after performing the steps to reproduce, attaching or linking to a public testcase, browser information, MediaWiki version information, etc). You can edit the task description by clicking .
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!
Nothing fixed, hence nothing resolved :)
Sat, Sep 23
I do not think that the AjaxQuickDelete gadget maintainers use Phabricator to track AjaxQuickDelete related tasks (but I am happy to be proven wrong) so I'm afraid this issue is out of scope for Phabricator as we don't track issues of random gadgets here.
Have you considered reporting this on https://commons.wikimedia.org/wiki/MediaWiki_talk:Gadget-QuickDelete.js ?
Requested public project WDQS-Optimizer has been created: https://phabricator.wikimedia.org/project/view/3027/
I'd say so. I currently rather see us commit to featured projects (and their tasks) offering mentors than specific tasks offering mentors.
My question is: in which file of luasandbox distribution can I inject a reference to an additional library for the C linker? Or is there an altogether neater way to fo it?
This sounds like a support question and not like a bug report or feature request which Phabricator is meant for?
Or is this a request to enhance the documentation (if yes, where exactly would you expect this to be documented)?
Argh, page setup... Let's try again (works as expected in rsvg-view-3):
Not Developer-Relations, adding Analytics-Tech-community-metrics
Same as T151488: Provide equivalent of korma's "Gerrit review queue" (listing the 'worst' SCR repositories) in Kibana. For general info, see https://www.mediawiki.org/wiki/Community_metrics
Is this the same as T13524: Add a system messages for categories?
I go to https://commons.wikimedia.org/wiki/Category:Clovis,_California?debug=true in Firefox 55 on Linux and I do not see any such error pop-up displayed. :(
Fri, Sep 22
Same applies for "Services" (not many projects/tasks to point to). Or QA/CI. Or MediaWiki core...
Thu, Sep 21
Thanks for reporting this. Is this only about the mobile version, or the desktop version? Can you provide a full link where to see the problem, please?
Approximately how many entries does your watchlist have? ("Raw watchlist" might display that).
Is there any Developer Tools output when going to https://en.wikipedia.org/wiki/Special:Watchlist?safemode=1&debug=true instead?
Clear steps to reproduce the problem are welcome, including links, the skin used, and the settings for "grouping" (?).
[ Removing unrelated projects ]
Wed, Sep 20
Solved by adjusting the Lock and Hide fields settings. Which I somehow overlooked. :-/
Setting project to Wikimedia-Site-requests, as this request is about settings / configuration of a Wikimedia website.
For more information about how to request these kinds of changes, please see https://meta.wikimedia.org/wiki/Requesting_wiki_configuration_changes
Oh, hadn't seen that one! Nice, might also totally work!
In any case, the open-ended questions still left were pretty much what you've mentioned: reasoning for the hierarchy of blocks and why some blocks are bigger than others (e.g. MW Core).
Probably should have the same width in the link that you provided, indeed. Or height in my quick drawing above.
Two questions on the diagram:
- Does documentation, design and translation placement the way it is right now mean anything?
In theory - I thought that the areas left of these columns rely on docs, design, translation. But as the rest of the element positions are no clear hierarchy I'm not too convinced either...
- Analytics - in general, is it an area that one could contribute to, if so where do we point people to who are willing to help?
There are some smaller tasks but not a specific area in Analytics to point to, no.
[ Please try to summarize the actual problem in the task description, by also using a verb. ]
What does "don't appear" mean exactly? What does appear? How does it look? What is an example of what is shown, and what is an example what you would expect to be shown? (Without private info such as IP addresses.)
I don't have access to the example links you provided...
Shizhao added a project: User-notice.
@Shizhao: I don't see why?
@Wladek92; As the page shows, this comes from: "Message definition (Semantic Extra Special Properties)". Its extension page says it is hosted on GitHub. Hence problems need to be reported on GitHub as the project does not use Wikimedia Phabricator: https://github.com/SemanticMediaWiki/SemanticExtraSpecialProperties/issues
Closing task as invalid here (as it is a valid task but in the wrong place). Thanks for your understanding!
How is this request different from T176140 ?
Thanks for creating this ticket.
Please provide all the required information.
If you think your request has gone unnoticed and the event is about to start, go to the IRC channel #wikimedia-tech on Freenode IRC and ask for help (general information on using IRC).
Tue, Sep 19
Thanks, that makes sense!
@Sau226: Please do not prioritize tasks if you do not plan to work on them. Thanks!
@Rammanojpotla: I unfortunately have problems to read and understand the last comments. What is "ings" in "is given as ings command no address"?
In general, using proper punctuation is very welcome to structure comments - this helps avoiding misunderstandings. Thanks!
Hi @jaydenmilne, thanks for taking the time to report this!
I currently don't see how there is anything in MediaWiki code to fix.
This looks rather like code in Edge/IE to fix?
Have you reported this to the Edge/IE developers?
The first reply in https://translatewiki.net/wiki/Thread:Support/NEED_YOUR_HELP_PLEASE_!!! links to https://translatewiki.net/wiki/Translatewiki.net_languages#Enabling_a_new_language_for_localisation_at_translatewiki.net which explains which information in which steps to provide where.
2017 Q3 is not ambiguous.
I don't plan to prepare a public Tech Talk currently.
I'm more happy to 'open' such a session to more Wikimedia folks who are interested, of course.
Any idea how this shows up in the database?
Removing Operations as it's not Operations territory. Sounds like an alias?
Office-IT project description says "Project to track internal Office IT projects." hence not applicable either...
For Wikimedia employees, see https://office.wikimedia.org/wiki/Office_IT .
Hence closing task as invalid here as this seems to not be handled in Phabricator.
Mon, Sep 18
I've filed https://gitlab.com/Bitergia/c/Wikimedia/support/issues/6 to warn Bitergia about our needs in advance.