Sat, Mar 25
Thu, Mar 23
I believe T59152: Echo: talkpage messages without a 4tilde signature, do not generate correct section links or summary is the culprit for that. I've added another note there.
Adding MassMessage, because it is the usual culprit these days.
I.e. All messages sent via MassMessage, will trigger an email-notification and web-notification without any excerpt.
IIUC, This is because MassMessage doesn't usually use a 4-tilde signature, and therefore Echo interprets it as just an edit to existing content on a page.
Wed, Mar 22
Fresh request for this feature at Enwiki.
Can we add a notification for user page edits?
Tue, Mar 21
Mon, Mar 20
My mistake, this does indeed occur for all BFs. I've Updated the description, and now merging a duplicate.
Sun, Mar 19
The use-cases I've seen or wanted myself, would benefit from being able to specify the CONCAT()-like behaviour. I.e. not just linking to a default location based on column names. E.g. If I'm generating a list of usernames, I might want those usernames to be linked directly to:
If we dropped the toollabs example (because my test didn't work with that as an interwiki link) and keep it to simple wikilinks formatted as prefix+suffix, does that simplify things, and point to an answer? I suspect that would solve the majority of use-cases.
(Caveat: I'm not widely familiar with other peoples' Quarry usage, nor a dev, so might be underestimating or misunderstanding)
Sat, Mar 18
IIUC, the missing parts to complete this task, are increasing Quarry's OAuth permission request in order to allow onwiki editing, and then providing a way to assign a specific wiki+wikipage that should be replaced with the current output of the query (in a specified format), plus a button to trigger that update.
Thu, Mar 16
Aha! Yes, turning that gadget off fixes it. CC @Bene
Wed, Mar 15
Tue, Mar 14
I don't think this request is likely to be implemented.
- Editors currently only get a 'notification' about the update, if it's on their talkpage.
- Many other wikis also follow the pattern of storing the barnstars/awards on the userpage, but the editors generally (I believe) want to be able to make the decision themselves, because some barnstars are more humorous than honorary, and don't need to be preserved forever.
- It would definitely make the code more complicated
- it would make the user-interface more complicated if it was presented as an option (anywhere/everywhere).
I suggest declining this task.
If I understand correctly, the issue at mlwikis has been fixed, therefore I will remove that tag.
I think this might be a duplicate of T62725: Use prettier (more colo[u]rful) form submission buttons in MassMessage (which also has a patch-for-review).
Mon, Mar 13
Additional notes and use-cases, from a discussion in IRC:
- Journalists regularly seek this kind of information, and want to know general statistics for their articles, e.g. the rough numbers in https://stats.wikimedia.org/wikimedia/squids/SquidReportPageEditsPerLanguageBreakdown.htm#Portuguese are perfect for them (but that page was last updated in 2013)
- User groups and documentation writers seek this kind of information, whilst trying to define the necessary background information to understand the needs specific to their communities.
- knowing the current breakdown and the relative populations and internet penetration can give a good idea of the potential of each country, because some have very different challenges from the others.
- It would be very useful to have an easy way to see any trends over time, so that the impact of things like outreach programs could perhaps be seen. (Either as a table like https://stats.wikimedia.org/wikimedia/squids/SquidReportPageEditsPerCountryTrends.htm or some sort of graph/visualization)
I've sent a manual email to most of the maintainers of the tools still listed as running, reminding them of the deadline on Tuesday, just in case they somehow missed the notices sent via this task plus the mailing list announcements.
Sun, Mar 12
(Sorry for commenting late.) These lists of navigational links have a unique setup at every wiki, including many designs that assume a placement at page-top and full-width. Additionally, I believe many editors typically use it as a quick-access point -- I.e. they sometimes visit the RC page primarily in order to access this navbox, because RC is linked in the site-wide sidebar. (This is how I find various pages at certain wikis.).
I advise against changing anything related to the MediaWiki:Recentchangestext navbox. I strongly discourage changing its visibility (default-collapsed-state).
Example links (random larger wikis):
Thu, Mar 9
Hiyo. No input beyond what I wrote on the mailing list. (and naming things is hard!)
1 more example:
- Guillom is crazy busy right now, and doesn't have time to maintain https://tools.wmflabs.org/mrmetadata/ - he would be happy for it to have a new maintainer/owner (per direct IRC communication, and purposefully not CCing him)
Do we envision this current informal process as being the preferred one?
I.e. Should I just create a new task for MrMetadata, place it in Tool-Labs-standards-committee and then perhaps also create a wikitech page to list these tasks/tools that need adoption?
Tue, Mar 7
Fri, Mar 3
I've done all the reading I can, and discussed with various people. I've updated the task description with the conclusion and notes. I'm Resolving, but feel free to re-open/re-assign if more needs to be done.
Hmm, and I think this might be a duplicate of the older T32404: InputBox:Possibility to insert entered string in a predefined search containing boolean operators.
+1. (There's a similar thread at https://www.mediawiki.org/wiki/Topic:Tm0pld07rfuoifsy where the editor is asking for the ability to add "incategory:foo", without having to resort to the "default=" parameter - which can confuse the end-users, and means they have to both avoid deleting it, and add a space afterwards before they can begin typing.)
Thu, Mar 2
Copy from merged task:
It seems that the special page "BrokenRedirects" does not take the new addition of Global User Pages into account when deciding if a redirect leads to nowhere.
Wed, Mar 1
I guess it would be low priority, and I think the custom forms will suffice for now. Quick questions:
- Is it already possible for us to add a placeholder in the "Title" field? (i.e. Create task currently has "Type a username..." in the "Assigned To" field. We could add a concise tip, in the "Title" field.)
- If not, then let's add a brief tip in the current header-banner callout, underneath the link to "How to write a good bug report."
@Sumit Because of the significant complexities involved - in legal-areas, community-areas, and technology-areas - plus advice above from experienced developers (and it being marked it as "epic" on the multimedia workboard), I suggest removing Possible-Tech-Projects because this seems unsuitable for a newcomer-developer to work on. (As I understand it, possible-tech-projects should be well-defined and clearly-scoped, and this task is currently neither.)
Tue, Feb 28
Mon, Feb 27
Feb 25 2017
This enhancement request might ultimately be a ticket against MediaWiki extensions --> WikimediaMessages, but this needs further thought and consideration first. I think a clear problem has been identified (footers that are duplicative and difficult to maintain), I'm just not sure what the best path forward is yet. There are other options such as interwiki transclusion (hah). We need to develop a plan.
TLDR: We currently have hundreds of local variants, each of which have to be created, and translated, and then maintained, separately. (e.g. 18 translations at mediawikiwiki, and 4 translations at metawiki)
I've overhauled the description above by reformatting it, and adding this major detail:
- Plus, the entire section is completely missing, if we have our language-preference set to a non-local-default, and that language-variant has not been manually created locally. (try looking at this usercontribs page with your UI language set to anything other than French.)
Feb 24 2017
I would like:
- A way to add keywords, and improve the descriptions, for each tool. [problem#1]
- Either a semi-formal ontology, or at least some sort of guidance/suggestions with keywords, to reduce some of the problems like plurals and synonyms. [problem#1]
- A way to add tools myself, without having to sign-up for x different repositories/trackers.
- A way to add/show screenshots, for us visual-thinkers, who don't remember what the tool was called, but do remember what it looks like. [Perhaps, via Extension:PageImages accessing any existing screenshots (which we'd encourage/add) in the primary documentation pages at mediawiki/wikitech?]
- The ability to add tools that are not hosted on our infrastructure. But clearly marking them as "off-wikimedia". [to avoid privacy confusions]
- The ability to add links to documentation about historic/defunct tools, so that people can at least learn about them. But clearly marking them as "not available". [cf. some great items in Atlasowa's page, linked in the task description.]
- A link pointing to the sourcecode for each, and perhaps something indicating what license it is under.
- A link pointing to a feedback page for each, to encourage wikilove from users.
- A link to the where we (especially non-developers) can help with UI translation for each, if the tool is configured for that.
- A pony. [tradition]
Feb 22 2017
Declaring resolved. Followup continues in mailing list.
Feb 21 2017
Fresh request for this feature from a Slovenian-language editor, at https://www.mediawiki.org/wiki/Topic:Tlgxli72jrmajwpw and specifically mentioning subpages.
I miss notifications if someone edited my user page or subpage.
Feb 17 2017
Feb 16 2017
Feb 15 2017
Hi, I might be able to help, if the task is just understanding where these are containers are coming from? Please could you point towards the existing example(s) that you found? (I couldn't see anything in the older task, but might've missed it)
Feb 14 2017
+1 to "Editing help" being normal linked blue text.
1 emphatic request: Please make the main links use the normal Blue color, as per almost all standard links on our sites.
- Context: I first did a mouse-over of (more) because it was the only blue link (but then I saw it was just another local search). After I realized that "Irlanda" was the direct link, I tried clicking on ALL the bold black text (and icon), because I was suddenly unsure which parts were links, and which were just bold text...
Feb 13 2017
Feb 12 2017
I think we just need these actions, to resolve this task:
- Amir1, Huji, and EranRoz, to join the IRC channel.
- Discuss a regular meeting. (Not everyone is permanently on IRC, so I guess the mailing list will be our "coordinate with everyone" method. I've started a thread...)
Feb 11 2017
Feb 10 2017
Feb 9 2017
- Admin email fwd'd to Huji.
- List settings changed to private archives, require "Confirm and approve" for new subscriptions, plus added description, and short subject line prefix ("TLSC").
- I'll mass-invite the rest of you.
(Sorry for the delay. Phab-mail backlog)
Feb 8 2017
- Template code: Yes please, to divs instead of tables! - However, it might be prudent/practical to wait for Global Templates to arrive, before actually launching widespread changes. (But code them up beforehand, so that they're ready to propose/deploy)
- Image-wrap/whitespace: When the template is displayed in the visual editor edit-notice box, I think it would be fine to make the text wrap around the icon.
- Image location: In the above circumstance, relocating the image to the top-right corner (for LTR) seems potentially reasonable.
- I assume relocating it to the top-left corner would cause some text line-wrap ugliness? Perhaps we could try out limiting the image height to a certain pixel limit, so that it only wraps after 2 lines or so?)