In T46787#5640173, @kostajh wrote:I agree that there are many nice UX possibilities proposed here but as someone who might work on this with pretty limited time (or for any other developer interested in this), it would be really nice to see the phab task description updated with a consensus on exactly what to implement.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Nov 12 2019
Nov 12 2019
Quiddity updated the task description for T234649: Wikimedia Technical Conference 2019 Session: Front-end modernization and standardization.
Nov 7 2019
Nov 7 2019
Quiddity added a comment to T51501: Gadget preferences should indicate whether a gadget is enabled by default.
Related/possible duplicate, I think it should be indicated for ALL preferences: T70689: User Preference's default options/values should be automatically marked in the special page itself
Quiddity updated the task description for T70689: User Preference's default options/values should be automatically marked in the special page itself.
Nov 4 2019
Nov 4 2019
IIRC , we're not meant to create aliases for valid language codes, of which TEM is the one for https://en.wikipedia.org/wiki/Temne_language
(I can't quickly find if/where that general rule is documented.)
MOD should be ok, as it's the code for the extinct language https://en.wikipedia.org/wiki/Mobilian per https://en.wikipedia.org/wiki/ISO_639:m
Oct 31 2019
Oct 31 2019
Oct 30 2019
Oct 30 2019
In T46787#5620984, @kostajh wrote:Do you have any thoughts on what the UX for this feature could look like?
Oct 24 2019
Oct 24 2019
Quiddity updated subscribers of T91201: [GOAL] Accessibility settings/preferences on desktop and mobile.
Quiddity added a comment to T91201: [GOAL] Accessibility settings/preferences on desktop and mobile.
Oct 23 2019
Oct 23 2019
Quiddity updated the task description for T234907: RFC: Where to implement Desktop Improvements project.
Oct 21 2019
Oct 21 2019
Oct 18 2019
Oct 18 2019
Jules78120 awarded T118024: When deleting StructuredDiscussion content, deleted content is misattributed to the sysop that deleted it a Manufacturing Defect? token.
Oct 17 2019
Oct 17 2019
Quiddity updated the task description for T235750: [20hrs] Prototype first few feature ideas for desktop improvements.
Oct 16 2019
Oct 16 2019
Quiddity added a comment to T234634: Wikimedia Technical Conference 2019 Session: On-wiki documentation & documentation as code: strengths, weaknesses, and compromises.
In T234634#5578955, @josephine_l wrote:
Quiddity added a comment to T233928: Reach out to community for general feedback on all the work we’ve had so far.
Message drafted, translated, and delivered to the Global message delivery, with nuances in T233929: Identify and reach out to potential test wikis
Message: https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Outreach
Quiddity updated the task description for T233928: Reach out to community for general feedback on all the work we’ve had so far.
Initial outreach to see if some specific wikis are interested, is being done via an addition paragraph in the massmessage outreach.
The bolded section in this message https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Outreach
is being delivered to the wikis in this list https://meta.wikimedia.org/wiki/User:Quiddity_(WMF)/Global_message_delivery_split_3
These wikis were chosen based on prior interest in this project or related projects, or uniquely relevant features at those wikis.
Further outreach will be done based on the initial responses here.
Quiddity triaged T233928: Reach out to community for general feedback on all the work we’ve had so far as High priority.
Oct 15 2019
Oct 15 2019
In T18691#5574534, @Pigsonthewing wrote:If the page is long, a reader would have to scroll all the way to the top to copy the link and remember the name of the section they wanted to share.
A radical proposal: Instead of a "share" link, have a "TOC" link that links to the relvant line in the TOC (rather like links from citations to where the citation lies in the body text).
Oct 14 2019
Oct 14 2019
Quiddity updated subscribers of T234957: Wikimedia Technical Conference 2019 Session: Developing in Mediawiki without breaking Gadgets.
In T234957#5571404, @Tgr wrote:Would it be useful to create some sort of inventory of gadgets (not necessarily names/URLs of the most used/important user scripts, but possibly an inventory of functionalities and workflows that editors use gadgets for)?
Very useful, and not primarily for interaction with MediaWiki changes (although that's useful as well). The increased discoverability of gadgets used by other communities would be a huge boon in itself.
Quiddity added a comment to T234634: Wikimedia Technical Conference 2019 Session: On-wiki documentation & documentation as code: strengths, weaknesses, and compromises.
Thoughts (with obligatory "i am not a dev" disclaimer, and a "sorry for the linkdump, this probably belongs elsewhere, but since you asked..." apology):
- The Documentation tag's workboard has benefited from a recent major sorting effort by @srodlund (ty!). Other people assisting with that, regularly, and thus also becoming familiar with the individual tasks in the backlogs and offering input on them (or pointing other people towards them), would be great.
- High-level on-wiki documentation overviews: There are various ongoing and past efforts to create hubs - organized overviews of the most fundamental/important pages. More people assisting with those would be great (give ideas, ask questions, give feedback, etc).
- Existing wikipage efforts
- The mainpage at mw.o was overhauled recently. https://www.mediawiki.org/wiki/MediaWiki
- The developer hub is important and could always use more eyeballs/watchlisters/editors. https://www.mediawiki.org/wiki/Developer_hub
- The page https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker is the 3rd crucial hub, one that most newcomers are directed towards.
- All would benefit from improvements to all the pages they link to.
- Ongoing/future/historic wikipage efforts
- The six "User pages" links at the bottom of https://www.mediawiki.org/wiki/User:APaskulin_(WMF) are among the most useful/relevant.
- The ongoing GSoD work of https://www.mediawiki.org/wiki/User:Pavithraes/Sandbox/ is also very important
- I made a list a couple of years ago at https://www.mediawiki.org/wiki/User:Quiddity_(WMF)/Hubs_and_docs which might be useful
- Existing wikipage efforts
- Individual wikipages:
- It can be hard for a user to determine how uptodate a page is. It might help if we create & standardize a way we indicate a doc-page's quality and importance?
- Currently we just use these generic cleanup templates: https://www.mediawiki.org/wiki/Documentation/Style_guide/templates
- Perhaps we want to use some sort of scoring-system, like the Wikipedia's sometimes use "stub/start/c/b/a/good/featured" (quality) and "top/high/mid/low" (importance) type ratings?
- See also https://www.mediawiki.org/wiki/User:Pavithraes/Sandbox/Technical_documentation_prioritization
- It can be hard for a user to determine how uptodate a page is. It might help if we create & standardize a way we indicate a doc-page's quality and importance?
- Off-wiki and Cross-wiki docs and tools:
- Self-documenting code, annotated source-code, docs.wikimedia.org, etc - I don't know anything about these.
- Wikitech vs Mediawiki - this is always complicated, due to the historical/idealistic split of wiki-roles. Nothing that can be done, for now. Wikitech should be SUL eventually, which will improve things a bit.
- I keep a list of seemingly-important links & subdomains at https://wikitech.wikimedia.org/wiki/User:Quiddity#Bookmarks (which might be relevant here. I regularly forget what they're all for!)
- Other:
- There's probably still some good ideas worth more discussion/effort at https://www.mediawiki.org/wiki/Developer_Wishlist/2017/Documentation
- This group was recently renamed/rebooted/opened-up, and everyone should watchlist it (for now. More info/outreach soon): https://www.mediawiki.org/wiki/Wikimedia_technical_documentation:_friends_of_the_docs
- There's a listing of external "good docs examples" reference material that anyone can add to at (the group's old name) https://www.mediawiki.org/wiki/Technical_Document_Re-working_Group/Resources
- Support channels:
- Complicated, because different methods/platforms are best suited to (A) different types of questions, (B) different archetypes of users. Plus (C) the people with the knowledge to answer a question might not be in (nor want to be in) the chosen platform. E.g. An inexperienced newcomer who is slowly learning how a code-review system works, needs different support from an experienced newcomer who needs to understand how our platforms relate to what they learned elsewhere. -- The platforms themselves (Onwiki/Discourse discussion; VS Mailing-list discussion; VS IRC/Telegram/Zulip discussion) each have different pros/cons, too, such as searchability, filterability (the usual cause of channel-fragmentation or an individual just leaving a channel, is trying improve the signal-to-noise ratio for themselves), difficulty of joining-in, and speed-of-average-response.
- Conference idea:
- Perhaps discussing the specific types of documentation that we're most in need of (improving or creating), would be helpful?
- See TLDR of the types at https://www.mediawiki.org/wiki/Documentation/Style_guide#Deciding_on_a_document_type
- and a list of accurate & distinct terminology (with examples) at https://www.mediawiki.org/wiki/User:Pavithraes/Sandbox/Technical_documentation_templates_and_suggestions#Tips_for_writing_in_genres
- Perhaps discussing the specific types of documentation that we're most in need of (improving or creating), would be helpful?
Hopefully something in there helps, and doesn't just distract/tangent! Sorry again. >.>
Quiddity added a comment to T234633: Wikimedia Technical Conference 2019 Unconference: Reducing barriers to entry for new developers.
Onboarding thoughts (with obligatory "i am not a dev" disclaimer):
- Primary existing pages:
- https://www.mediawiki.org/wiki/New_Developers
- https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker
- https://www.mediawiki.org/wiki/How_to_contribute (also lists the non-development-related areas)
- Personas: Overall, I think we need to constantly keep in mind the various demographics/target-audiences, because their needs often wildly differ from each other, with some overlap.
- E.g. new gadget-authors -- vs -- new SRE staff -- vs -- new external-researchers -- vs -- new external wikidata collaborators
- Past attempts at defining them include:
- https://www.mediawiki.org/wiki/User:APaskulin_(WMF)/Docs_Personas
- https://www.mediawiki.org/wiki/Wikimedia_Cloud_Services_team/Our_audiences
- https://meta.wikimedia.org/wiki/Research:Growth_and_diversity_of_Technology_team_audiences#Results
- https://www.mediawiki.org/wiki/Wikimedia_Product_Development/Person%C3%A6#Technical_contributors_and_software_or_content_re-users
- https://www.mediawiki.org/wiki/Web_APIs_hub#Personas
- Existing per-person onboarding docs examples: There are (some quite old) examples from various WMF Product/Tech dept teams. Similar to the gitlab template linked by TheDJ above. E.g.
- https://www.mediawiki.org/wiki/Wikimedia_Cloud_Services_team/Onboarding_Hieu
- https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Onboarding (e.g. T214556: Onboarding Brennen)
- https://www.mediawiki.org/wiki/Wikimedia_Discovery/Team/Onboarding
- https://www.mediawiki.org/wiki/Team_Practices_Group/Onboarding (historic)
- Collecting more info (pre-TechConf?):
- I think it would be useful for other groups/affiliates/teams to share what they currently use (e.g. WMDE?)
- It might be useful for any recent newcomers to the movement to explain what pain points they remember being specifically confused/frustrated by. (ideally right here, and before TechConf!)
Oct 13 2019
Oct 13 2019
Quiddity placed T115650: Create an authoritative and well promoted catalog of Wikimedia tools up for grabs.
Oct 11 2019
Oct 11 2019
Quiddity updated the task description for T234661: Wikimedia Technical Conference 2019 Session: Developer Productivity & onwiki tooling.
Oct 10 2019
Oct 10 2019
Quiddity updated the task description for T234907: RFC: Where to implement Desktop Improvements project.
Quiddity added a comment to T221119: "This namespace is reserved for content page translations" when trying to translate a recently created translation unit.
Might this be related to T235027: Translate does not update content page when saving units ?
• Elitre awarded T215922: Community input for patrol log reviews in 'all public logs' a Like token.
Oct 8 2019
Oct 8 2019
I agree that we need a different interface option for galleries where there are dozens of images in the slideshow.
Oct 3 2019
Oct 3 2019
Quiddity moved T117736: Convert Special:Contributions to OOUI from In current Tech/News draft to Already announced/Archive on the User-notice board.
Oct 1 2019
Oct 1 2019
Sep 28 2019
Sep 28 2019
Quiddity updated the task description for T234144: Expand link for history page "filter revisions" section has display issues on Wikitech.
Sep 27 2019
Sep 27 2019
Aklapper awarded T211620: Change some default Notification settings on officewiki a Like token.
Sep 26 2019
Sep 26 2019
Done. Thanks for the reminder, and for making it work. :)
Sep 25 2019
Sep 25 2019
Quiddity awarded T212881: addWiki.php broken creating ES tables a Love token.
In T224681#5523545, @Elitre wrote:In T224681#5522742, @Aklapper wrote:@JLetangWMF: https://wikimedia.org.au/wiki/Calendar seems to use the Cargo extension.
That extension is not deployed on Wikimedia servers so it would have to go through a review.What about https://outreach.wikimedia.org/wiki/GLAM/Calendar ?
Sep 23 2019
Sep 23 2019
Johan awarded T232379: MassMessage problems - multiple deliveries and missing deliveries a Like token.
Sep 21 2019
Sep 21 2019
Quiddity updated the task description for T213778: Update link colors in Vector 2022 for improved UX (and consistency).
Sep 21 2019, 7:43 AM · User-notice-archive, MW-1.39-notes (1.39.0-wmf.26; 2022-08-22), Design-System-Team (Design-System-Sprint), Web-Team-Backlog (Kanbanana-2022-23-Q1), Editing-team, DiscussionTools, OWC2020 (OWC2020 Replying 2.0), Desktop Improvements (Vector 2022), UI-Standardization, Vector (legacy skin)
Sep 20 2019
Sep 20 2019
• Elitre awarded T232379: MassMessage problems - multiple deliveries and missing deliveries a Barnstar token.
sguebo_WMF awarded T232379: MassMessage problems - multiple deliveries and missing deliveries a Like token.
Sep 19 2019
Sep 19 2019
Quiddity awarded Blog Post: Cloud-vps Puppetmasters Moved to VMs, thanks to Krenair a Love token.
Sep 18 2019
Sep 18 2019
Quiddity updated subscribers of T232379: MassMessage problems - multiple deliveries and missing deliveries.
@Pchelolo @EvanProdromou How complicated would it be to implement the aforementioned (T232379#5480718) deduplication feature, and is that within your team's area of responsibility?
These bugs are making the MassMessage system as a whole completely unreliable, and it's one of the main systems for cross-wiki communication for a multitude of groups.
Thanks!
Quiddity added a comment to T232379: MassMessage problems - multiple deliveries and missing deliveries.
In T232379#5497392, @Johan wrote:Have we seen any arguments against a new deduplication flag so far?
Sep 13 2019
Sep 13 2019
Done x3.
Quiddity added a comment to T232379: MassMessage problems - multiple deliveries and missing deliveries.
I've asked on m:Talk:MassMessage and wikitech-ambassadors@.
Quiddity added a comment to T231000: Close #wikimedia-devrel Freenode IRC channel and redirect it to #wikimedia-tech.
Right. Yup. Sorry, I didn't mean that exact phrasing, but was typing out quickly during the meeting. The intent was more... somehow provide the usernames that people can potentially ping, perhaps giving specific circumstances/specializations. E.g. "Ping andre__ for questions about [...]". -- However, your idea would work as well, just in a slightly more fragmented way. :-)
• Elitre awarded T224681: Events Portal Creation on Wikis a Like token.
Sep 12 2019
Sep 12 2019
Quiddity added a comment to T231000: Close #wikimedia-devrel Freenode IRC channel and redirect it to #wikimedia-tech.
Group thoughts: probably #wikimedia-tech, and update the team page to specify that "You can find us on IRC at [...] and you should ping (just type) these nicknames to get our attention if we're working at that time: andre__ srish_aka_tux srrodlund" (so that we don't need to alter the channel topic)
Sep 10 2019
Sep 10 2019
Quiddity updated subscribers of T232379: MassMessage problems - multiple deliveries and missing deliveries.
In T232379#5480718, @Pchelolo wrote:[...]
Seems like we need a new deduplication flag, like deduplicate_unique that would make it ignore exactly the same job regardless of the timing. This, however, will make it impossible to send exactly the same message to the user.
Quiddity updated subscribers of T232379: MassMessage problems - multiple deliveries and missing deliveries.
Sep 9 2019
Sep 9 2019
Quiddity added a comment to T232408: Create a comprehensive overview of documentation page for WMCS.
Note, there are already these 3 compendiums. It might be good to update 1 of them, instead of creating a 4th, although possibly that's what is meant by "create a page". :)
https://wikitech.wikimedia.org/wiki/Help:Cloud_VPS
https://wikitech.wikimedia.org/wiki/Category:Cloud_VPS
https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin
Quiddity added a comment to T232379: MassMessage problems - multiple deliveries and missing deliveries.
Re: non-delivery - AFAICT this problem is not the "readonly" bug, because the local logs don't contain any of those errors, e.g. https://id.wikipedia.org/wiki/Istimewa:Catatan/massmessage
Sep 6 2019
Sep 6 2019
Quiddity moved T156096: Deprecate and then reject empty operators from Announce in next Tech/News to In current Tech/News draft on the User-notice board.
Sep 5 2019
Sep 5 2019
@Daimona Please could you suggest an appropriate way to phrase this in Tech News? Ideally a 1 (or 2) sentence description that is easily translatable. Thanks!
Quiddity moved T201520: Create a global Talk page filter from In current Tech/News draft to Already announced/Archive on the User-notice board.
I've copied the etherpad into https://wikimania.wikimedia.org/wiki/2019:Hackathon/Outcomes
Quiddity added a comment to T222360: Add new "button" for Wiki URL shortener in the menu in Wikipedia.
There's also a gadget at Frwiki: https://fr.wikipedia.org/wiki/MediaWiki:Gadget-ShortenUrl.js
Which can be added to your global.js with
// ShortURL in the 'Tools' sections of sidebar mw.loader.load('https://fr.wikipedia.org/w/index.php?title=MediaWiki:Gadget-ShortenUrl.js&action=raw&ctype=text/javascript');
Ok, thanks. :)
Very good specific points, thank you for that information. With that in mind, and especially the missing 2FA, I suppose this proposal might be declinable.
Sep 4 2019
Sep 4 2019
• OldUser02 awarded T231954: Increase session length for OTRS ticket system a Dislike token.
Sep 3 2019
Sep 3 2019
Aug 31 2019
Aug 31 2019
Quiddity moved T201520: Create a global Talk page filter from To Triage to In current Tech/News draft on the User-notice board.
Aug 30 2019
Aug 30 2019
Quiddity removed a project from T231695: Innu language displays "Undefined" as tooltip in ULS: ULS-CompactLinks.
Thanks, Herald! That was the one I wanted.
Aug 29 2019
Aug 29 2019
Thanks x2! (link to end result: https://tools.wmflabs.org/global-search/ )
- Please update the documentation page at https://www.mediawiki.org/wiki/Help:New_filters_for_edit_review/Advanced_filters to cover this new feature.
- How would you like the Tech News item to be phrased? I'm guessing something like:
The advanced version of the edit review pages (Recent Changes, Watchlist, and Related Changes) now include two new filters. These filters are for "All contents" and "All discussions" and will filter the view to just those namespaces, however they do not include pseudo talk pages such as discussions that are in the Project: namespace.
Please edit that, or write whatever you'd like it to say, including the link to the docs page (once updated). (All within the next ~20 hours, before the hard freeze for Tech News translations.)
Thanks!
Quiddity updated subscribers of T231312: WikiContrib violates user privacy by loading third party content from Google.
@Rammanojpotla too! (Sorry I missed you initially)
Quiddity updated subscribers of T231312: WikiContrib violates user privacy by loading third party content from Google.
@srishakatux @Tuxology Please see this task.
Note: this code might help: https://github.com/toolforge/fontcdn/
Quiddity added a comment to T179183: Delete 24gb worth of unused files owned by tool.theoslittlebot.
I think this task is resolved now? Afaict the cleanup was done (per T179183#3716725 above), and the original bot no longer needs a new maintainer (because it has been turned off or is just inactive, per contribs).
Quiddity moved T223859: Bring the ppp-sparql tool back to life from Incoming to Maintainer needed on the Toolforge-standards-committee board.
Quiddity moved T223858: Bring Bene's sparql tool back to life from Incoming to Maintainer needed on the Toolforge-standards-committee board.
Quiddity removed the point value for T231312: WikiContrib violates user privacy by loading third party content from Google.
Aug 23 2019
Aug 23 2019
Thanks all, and happy 17th birthday to Estonian Wikipedia!
Aug 22 2019
Aug 22 2019
Quiddity added a comment to T199385: Develop a workflow to recommend / propose developers who should have +2 rights in Gerrit.
Related policy now exists at https://www.mediawiki.org/wiki/Gerrit/Privilege_policy (per recent email)
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL