Hello, do you know how to create a Chart model with its demo on a wiki? CSS? What should I do?
Lien : shorturl.at/aqyI5
This page uses StructuredDiscussions. For general Feedback about StructuredDiscussions, please post it on the dedicated page!
Previous discussion was archived at User talk:Trizek (WMF)/Archive 1 on 2015-09-30.
Hello, do you know how to create a Chart model with its demo on a wiki? CSS? What should I do?
Lien : shorturl.at/aqyI5
Hello Trizek, Do you know how to activate or add a notice for mediawiki like in the photo? :
Link : ibb.co/pvCtkC5 ibb.co/VvXrfng
Got it!
See m:CentralNotice. You will have to justify the need of a banner, and banners might not be the best medium for your project.
Have a good read at the Usage guidelines: banners are supposed to be a community request, to support a community event.
Hi, wonderful your hardwork will be told to the community: Under section Mentorship, I wonder if you will tvar two links or not? They are now presented in plain text. Are they given so that when the reader pushes the Special: link, then they will jump to Preference?
Hello
Sorry for the late reply, as I was off duty.
It is indeed a mistake. They should have been tvar-ed.
Hopefully, we have great, experienced translators, who haven't translated the special pages title. You event went a bit further by adapting the text, which is great!
Thank you for being conscientious as always.
Hi Trizek,
I just saw your announcement on yuewiki. I’m wondering where I should go if I want to fix the date formatting, or is this something that needs to be fixed at the source code level? Thanks!
Never mind, I found it; I wish I knew this was going out before it went out, but I’d still like to know if there’s a way to fix $defaultformat at the source
Hello Al12si.
We can change $defaultformat to match yue language. Just let me know what the format should be.
We use PHP formatting for #time. For instance, {{#time:H:i e|2023-03-01T14:00}}
displays 14:00 UTC. Numerous options are provided to format the time the way you need it.
And good news: fixing it no means that is will be fixed once for good for future announcements.
Hi Trizek,
In yue a short date (month and day) looks like this:
n月j號
A long date (year, month and day) looks like this:
Y年n月j號
(yue is kind of an exception; in most other CJK languages that use kanji (ja, lzh and zh) these would read n月j日
and Y年n月j日
instead. 號 literally means “number”, as in the day number within the month; 日, used in ja, lzh and zh, literally means “day”.)
(ko is in theory the same as ja/zh but they spell it in Hangul instead of using kanji.)
You can verify this by checking recent Tech News editions for yue, ja and zh etc. I know this is also affecting ja (I’ve fixed the ja announcement); I don’t know if this is affecting zh and ko.
If it involves time, it goes after the date. Time zone is a bit tricky though; I don’t think there’s anything that matches how I hear it said, so I guess we can keep time zone as-is.
(The way I’ve heard it said puts time zone first, but we don’t use the English zone names so that’s a no-go; I’ve also heard it said as a numeric offset, but we only say the number of hours, so that’s also a no-go.)
Thank you for the explanations, and the updates.
I checked on this message, and it should display the name of the day, the number of the day, the name of the month, and the year (as in "Wednesday 1 March 2023"). Can you fix it?
Regarding the timezone, car we assume that most yue users live in certain timezones? Some languages adapted the announcement regarding times to highlight places where the language is most spoken (for instance, French highlights Québec, Western Europe, Western Africa and Central Africa).
Fixed.
As to the timezone, yes, most yue users would live in GMT+8, but I’m not sure what best to call it. We could call it 加八時區 (lit. “[the] +8 timezone”, I’ve heard it called this); or we could could pick a region, but that would be a political decision (as in literally political, as in siding with a certain political ideology).
BTW, if we need year and date-of-the-week for that string, the Japanese translation needs to be fixed too. I fixed it (I don’t speak Japanese, but date strings are cognate within all CJK languages); you might or might not want to get someone to double-check my fix.
That string is also broken in Korean (I just checked it), but I’ll not be able to fix Korean. Their dates are also cognate but they spell everything in an alphabet and I won’t know how anything is spelled.
Thank you for the fix. For the timzeone, it could literally use the mention of local time and the UTC time: "22:00 local time (14:00 UTC)". What do you think ?
I'll find a Japanese and a Korean speaker to fix the strings, thank you for spotting them.
Bonjour, Trizek. J'ai par le passé utilisé à plusieurs reprises ce livret (Participer à Wikipédia) comme aide pour expliquer comment contribuer : il couvrait beaucoup de sujets. Par contre, j'ai voulu l'utiliser récemment et j'ai constaté qu'il n'était plus à jour, sur quelques points, comme les colonnes de gauche et de droite ou les liens inter-langues. Une nouvelle version est-elle prévue ?
Bonjour
C'est à Trizek qu'il faudrait poser la question.
Et une mise à jour n'est pas d'actualité.
Hi Trizek!
I wanted to ask you something I've been thinking about for a while. We had several mentors who were blocked and after the block, I saw some mentees ask them questions. We can't see which mentees assigned to them until these questions. Even then it's hard to keep track of them. If some mentors are blocked on a particular wiki, let's say... about a month or so could you create a solution that will automatically transfer the mentees to another mentor or could you create a page to list the blocked mentor's mentees?
Hello Anerka
Thank you for contacting me! We already had some community inputs regarding this idea, which has been documented.
We currently have a solution for people who'd like to voluntary quit mentoring, but we don't have (yet) a real solution about people who are banned, blocked, or who quit and forgot to leave mentorship.
If you have a list of users of which mentees should be reassigned, please let me know. We can do the change manually.
Thanks for the offer :)
We have 3 users in tr.wiki in this situation;
Cedreon, Leaply, and Victor Trevor
Hello @Anerka,
I'm not sure if you're monitoring Phabricator. My name is Martin Urbanec, and I'm an engineer who will work on reassigning the mentees to other mentors. To make that possible, I will need a tr translation of https://translatewiki.net/wiki/MediaWiki:Growthexperiments-quit-mentorship-reassign-mentees-log-message/en (at Translatewiki, Phabricator or here, whatever you prefer). Once that's translated, I can start the process on my end.
Hi again,
I filled a request to reassign the mentees one more user from Turkish Wikipedia.
Hey Trizek! I saw that many years ago you had notified our community about the existence of ORES. I was wondering, does ORES still learn from our edits or from any other source? Is it improving somehow?
Hello Klein Muçi
Good question. I haven't worked for this project since a loooong while! :)
If I remember correctly, the training your community worked on is still the data used by ORES. IF you think it should be improved (r just to be sure I'm not wrong), I encourage you to contact the project owners.
Should I contact them there? The page doesn't look like it gets a lot of traffic. Maybe I can contact them personally on their user pages if you show me who exactly I should contact. I checked the page history but it had a lot of contributors.
Try the project talk page first. ORES is a mature project, with few improvements. Seeing low traffic there doesn't mean that there is nobody watching. ;)
I checked who are the project owners, and the Machine Learning team is more on Talk:Machine Learning now.
Hope this helps!
Hey, Trizek! :)
Lately I've been made aware of a situation in our homewiki (SqWiki) which you may already know but I thought I'd let you know anyway.
If you remember, I was very excited with the whole mentorship idea. We activated it as soon as possible but we have a small active community. We only have 3 mentors in total, myself included. The problem is that even though I tried to choose the most active users, the 2 other people still aren't fast enough in their answers. I've seen users on their pages ask 2 questions in a row or more because their first one never got an answer. We've set it so all questions get redirected to the mentors' talkpages but from the POV of most new users they don't fully understand what's happening. They just see a place where to ask a question and go with it. And when they don't get an answer, they ask again in the only place they know and therefore end up asking the same unresponsive user again. This may end up being very frustrating for them.
I was thinking that maybe we should "tweak the system" so that if you have unanswered questions by the help panel for X period of time on your talkpage you get a notification that reminds you to answer them. Or maybe automatically removes you from the list of mentors after giving you a notification about your "demotion deadline". Or maybe a notification telling the users that want to ask a second question after they have 1 unanswered one that maybe they should consider asking somewhere else. Anything really. The whole idea is to make users not get trapped in a single unresponsive page.
Hello Klein Muçi, and thank you for letting us know!
A agree on the fact that it is demotivating for newcomers to post on unresponsive pages.
The idea of the notification would be nice, but our wiki talk pages aren't structured. It makes it difficult to find which messages remain unanswered.
A possibility of improvement would be to have a centralized help desk instead of the mentoring system. This way, the page would be monitored by all users, and the ones who know the answer can participate. te.wikipedia posts these messages directly on the village pump (or equivalent) so that questions are immediately visible!
The mentorship system would return when the community would have grown up.
That's what we had (and we still have the Q&A page made specifically for that reason) but we changed it to using talk pages because unfortunately it wasn't working like that. At least some questions get answered like this. The only problem is that new members may get "trapped forever" with an unresponsive mentor. I think a system should be devised to protect against this kind of situation. Maybe by automatically removing names from the list once a certain criteria is reached. I can, of course, remove them myself now but in general it's not good practice to just count only on one user for a specific thing. I do understand that the lack of structured discussions proves a challenge though. If any changes happen in regard to this in the future, I'd be interested to read them.
Hi!
You get this message because you are an admin on a Wikimedia wiki.
When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.
Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.
If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.
We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.
Thank you. /Johan (WMF)
18:17, 4 January 2022 (UTC)