Wikifunctions:Project chat

From Wikifunctions
(Redirected from Wikifunctions:CHAT)

Welcome to the Project chat, a place to discuss any and all aspects of Wikifunctions: the project itself, policy and proposals, individual data items, technical issues, etc.

Other places to find help:

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose most recent comment is older than 30 days.

Midnight talk


Are you sure about the schedule for the next Volunteers' Corner?

That would be April 8 at 10:30 p.m. (UTC) or 22:30 (UTC). So for Sannita in Italy, the event will be at 00:30 on April 9 (CEST)?

Regards. ―Eihel (talk) 16:18, 29 March 2024 (UTC)[reply]

Yes, we did so to accomodate people who live in East Asia and Oceania who are prevented to join normally, because the usual timing it's too early in the morning for them. It will be a one off, for the moment.
Unfortunately, there is no possibility to accomodate people from all time zones, if we take a decision someone will be left out, because that's how it is. We're still working on a solution for that, but it will be complicated to find one. Sannita (WMF) (talk) 11:06, 30 March 2024 (UTC)[reply]
I think if you want to reach people more people who work during the day you should do the Volunteer corner meeting on Saturday. The mentioned time is at the early mornging for people in East Asia as far as I did a correct calculation of the time. I do not live there but at least I am not attending at events like the volunteer corner meeting during the day or in the mornging if I work on that day. Having the volunteer corner meeting at different times is something I really support so far. Hogü-456 (talk) 19:52, 9 April 2024 (UTC)[reply]


Why do URLs for ZObjects often have /view/language_code/ in the URL, where other wiki sites usually have /wiki/? Amir E. Aharoni (talk) 13:51, 1 April 2024 (UTC)[reply]

Mostly because ZObjects can be multilingual and there needs to be a way to send links to specific language variants. I believe this is the piece of code that handles this. Philipnelson99 (talk) 14:27, 1 April 2024 (UTC)[reply]
If this is indeed the intention, it's not a good solution. Moreover, the intention seems unnecessary in the first place.
The current situation is quite inconvenient: I use Wikifunctions in Hebrew, so most of the time, these links look like /view/he/ to me. If I send this to someone who doesn't know Hebrew, they'll open a link in Hebrew and will have to change the language. And the other way around: people send me links with /view/en/, but I want to read things in my language, so I have to switch all the time.
Why not just make it like in Wikidata, which has a similar structure of language-agnostic numeric IDs and labels in various languages? It has the same URLs for all the languages, shows the page in the user's previously chosen language, and lets the user choose another language if necessary. Amir E. Aharoni (talk) 15:05, 1 April 2024 (UTC)[reply]
I agree it's not ideal. There's an open epic on phabricator to improve the current experience around WikiLambda's multi-lingual support. I haven't read through all of the associated tickets there but it may be of interest to you. Philipnelson99 (talk) 04:48, 2 April 2024 (UTC)[reply]

If this is indeed the intention, it's not a good solution. Moreover, the intention seems unnecessary in the first place.

@Amire80: Product decided that we needed to do better than the Wikidata experience for our logged-out users, who are the majority of our eventual targets. Your team were consulted as part of this work, of course.

shows the page in the user's previously chosen language

Your assumption that readers are logged-in and have set a language preference is showing. :-)
The current situation is imperfect, certainly, but significantly better than any other Wikimedia project on the axes we planned.
It's correct that URLs are moderately less "shareable" for multi-lingual users, but that wasn't considered a big issue during the design phase compared to the other issues. One proposal, not currently planned but potentially something we could work upon, was to allow for users to specify an ordered list of their preferred languages which would over-ride their request URL and instead serve them what we think they want (T290537). Properly, this is blocked by T290595, which is your team's area rather than ours
I would recommend that you discuss with your team for what changes you'd like to recommend, and follow-up in the usual way. :-) Jdforrester (WMF) (talk) 20:45, 3 April 2024 (UTC)[reply]
But why did product decide that Wikifunctions needs to do better than the Wikidata experience for logged-out users? (I'm not asking in the staff hat, just as a curious editor.) Amir E. Aharoni (talk) 18:49, 4 April 2024 (UTC)[reply]
@Amire80: Because language support is fundamental to what we're doing with Wikifunctions? I would have thought it was obvious. Jdforrester (WMF) (talk) 20:09, 4 April 2024 (UTC)[reply]

New wikilambda editsource script!🔌λ

User:מקף/wikilambda editsource.js

Hi everybody,
I created a script for a source code editor👆.
Hope it will be useful, and I would be even more happy if other JS programmers and interface editors agree to help me improve it, and maybe turn it into a gadget.
For now, you can easily try using it by jumping into Special:mypage/common.js and adding the following line:

mw.loader.load( '//מקף/wikilambda_editsource.js&action=raw&ctype=text/javascript' ); // [[:f:User:מקף/wikilambda_editsource.js]]

Feedback is welcome.
Thank you, · מקף Hyphen · 02:18, 2 April 2024 (UTC)[reply]

Can you say a bit more about what it does and in which circumstances you expect it to be most useful? --99of9 (talk) 05:17, 2 April 2024 (UTC)[reply]
  • The script retrieves the content of the edited item, represented in JSON format (Wikifunctions:Function_model). It allows the editor to access the raw representation directly, and edit it textually.
  • This feature is especially useful when there is a need or preference to perform operations, which are not easy to perform in the user interface. The interface includes a built-in limitation of repetitive selection and typing (which are also done in an order that cannot be changed or started in the middle/end).
    For exmple:
    1. Typing a long list of strings (such as Hebrew list of strings: Number names (default-female) (Z14617)).
    2. Import content that the user has produced elsewhere.
    3. Copying from one item to another, with some specific changes.
    4. Splitting an item
    5. Changing internal order (such as replacing the order of composition of multiple functions) without retyping everything.
...and maybe other things I haven't thought of.
I also created this script as a possible basic infrastructure for creating future scripts that can accompany and help us edit. For example, tasks suggest translations for fields with common names.
~ · מקף Hyphen · 17:42, 2 April 2024 (UTC)[reply]
I have added the script to Wikifunctions:User scripts. --Ameisenigel (talk) 19:51, 2 April 2024 (UTC)[reply]
@99of9 it also allows using an edit summary, something that is sorely lacking for the normal editing of connecting/disconnecting implementations and tests --DannyS712 (talk) 01:09, 9 April 2024 (UTC)[reply]

Question regarding identifying failing or unconnected tests

Is there a way to identify failing tests yet? I understand this might be a limitation in the current implementation of the WikiLambda extension. I'm really interested in trying to identify the tests that are currently failing or unconnected and rectifying that situation. Thanks! Philipnelson99 (talk) 04:38, 2 April 2024 (UTC)[reply]

Tracked in Phabricator:
Task T328708
Not yet.
You can see functions with counts of disconnected tests at Wikifunctions:WikiProject Maintenance but tests are often disconnected for a good reason. Perhaps the reason should be given on the Test case’s talk page, when this is the case? Feel free to suggest that at Wikifunctions talk:Best practices#Connecting tests. GrounderUK (talk) 08:40, 2 April 2024 (UTC)[reply]
Any chance of an update on that list @Azertus:? --99of9 (talk) 12:24, 2 April 2024 (UTC)[reply]
@99of9 unless I'm misreading it, the database dumps haven't been updated since then. Philipnelson99 (talk) 13:03, 2 April 2024 (UTC)[reply]
Done, thanks for the ping! I didn't realize my bot request had gone through already. Azertus (talk) 08:41, 4 April 2024 (UTC)[reply]

Wikifunctions & Abstract Wikipedia Newsletter #150 is out: Product Update on Diff and Upcoming API Improvements

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss our latest blog post on Diff, and we take a look at the latest software developments.

Want to catch up with the previous updates? Check our archive!

Also, we remind you that if you have questions or ideas to discuss, the next Volunteers' Corner will be held on April 8, at 22:30 UTC (link to the meeting).

Enjoy the reading! -- User:Sannita (WMF) (talk) 10:23, 4 April 2024 (UTC)[reply]

We’re looking for research participants

Hey everyone,

This is Amin, one of the designers behind Wikifunctions. We are currently seeking research participants to join a study about the Wikifunctions integration into Wikipedia.

We’d like to invite you to a 75-minute virtual conversation (video call) with us about Wikifunctions, starting next Monday, April 8th. To see if you qualify for this study, please fill out this short (2 minutes) survey [1]. If you are a good fit for this study, we will contact you with details about scheduling. Participants who complete a conversation will be offered a monetary “thank-you gift”.


You may view the Privacy Policy for this form here: AAlhazwani (WMF) (talk) 09:44, 5 April 2024 (UTC)[reply]

What is a "virtual conversation"? Also, the window seems short, I think perhaps you should have given at least a week's notice? Lofhi (talk) 09:20, 7 April 2024 (UTC)[reply]
"Virtual conversation" as video call, I edited the wording to make it more clear, thank you for pointing that out. The current window is open-ended, meaning that we are available to start interviews this week, but it will depend on people's availability. AAlhazwani (WMF) (talk) 10:27, 8 April 2024 (UTC)[reply]

Finding task lists

I'm new here and am still learning to find my way around. I've noticed that functions, implementations, and test cases are not categorized. I'm wondering if there is a way for me to find / generate the following lists of items. These lists would help me better understand the state of the project, prioritize what to work on, and work on tasks systematically.

  1. All functions.
  2. All functions that lack an English label.
  3. All functions that lack a Python implementation.
  4. All Python implementations that lack an English label.
  5. All Python implementations that lack test cases.

If these lists already exist I think they should be made easier to find.

As a side note, have we decided what to call the things in mainspace? Are they pages? Items? Objects?

Thank you,

— excarnateSojourner (ta·co) 02:27, 9 April 2024 (UTC)[reply]

  1. The list of all functions is at Special:ListObjectsByType/Z8. You can see lists of all the different types of object by following the links at the bottom of that page (or see here: Special:ListObjectsByType).
  2. Perish the thought! If I find one, I’ll let you know how I did it. I think I mentioned this in Phab:T343565#9580365 but feel free to add your thoughts there.
  3. I don’t think we can do that. There is a Phabricator ticket for such suggestions at phab:T359672.
  4. Another suggestion for phab:T343565 but they get picked up through Special:NewPages. (Note that the current label is always shown here, as elsewhere.)
  5. I think I would translate this to: functions with a Python implementation and no test cases. This is not currently possible, but you can see functions listed with the number of connected and unconnected tests at Wikifunctions:WikiProject Maintenance. This is a sortable list (which is great 💯@Azertus🙏) but it is currently based on database dumps, so always a little out of date.
Navigation here might be improved. Currently Wikifunctions:Catalogue and Wikifunctions:Multilingual function as hubs. They both link to Special:ListObjectsByType/Z8 already but perhaps a link to Wikifunctions:WikiProject Maintenance should be added? Feel free to act boldly!
As for those things in Mainspace, we don’t call them “items”. Officially their label is ”persistent object” but, depending on the context, we would generally use either “Object” or “Page” as a shortened form for a “Persistent object’s page in Mainspace” (hence: “Special:ListObjectsByType”, which provides links to the Mainspace page for each Persistent object in the list). GrounderUK (talk) 08:55, 9 April 2024 (UTC)[reply]
I left a new function unlabelled and it didn’t appear at all in Special:ListObjectsByType/Z8. It appeared in Special:NewPages and Special:RecentChanges as “Untitled”. GrounderUK (talk) 19:33, 9 April 2024 (UTC)[reply]

To prevent spam I propose this page be indefinitely semi-protected. GZWDer (talk) 11:15, 9 April 2024 (UTC)[reply]

It looks like it has had eight edits this year, including reversions. Shall we wait until it’s more of a problem? GrounderUK (talk) 12:55, 9 April 2024 (UTC)[reply]
I don't think it needs protection at this point - it looks pretty well monitored (and I just added it to my watchlist). I've also just set up archiving so it should be easier to see if problematic edits are made. --DannyS712 (talk) 19:46, 9 April 2024 (UTC)[reply]

Wikifunctions & Abstract Wikipedia Newsletter #151 is out: New API for calling Wikifunctions and celebrating 1000 functions

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue, we discuss the new API for calling Wikifunctions, we celebrate our first 1,000 functions, and we take a look at the latest software developments. Also, there's a job opening for joining our team!

Want to catch up with the previous updates? Check our archive.

Enjoy the reading! -- User:Sannita (WMF) (talk) 09:57, 12 April 2024 (UTC)[reply]