User Details
- User Since
- Oct 24 2014, 11:57 PM (513 w, 4 d)
- Roles
- Disabled
- IRC Nick
- joakino
- LDAP User
- Jhernandez
- MediaWiki User
- JHernandez (WMF) [ Global Accounts ]
May 13 2024
Dec 6 2023
Nov 21 2023
Oct 6 2023
Nov 21 2022
Nov 17 2022
@Madalina and I talked and she mentioned it is a bit too early to look into specifics until the project brief is written and reviewed. So for now we will hold on working on this task until she says so.
@Madalina and I talked and she mentioned it is a bit too early to look into specifics until the project brief is written and reviewed. So for now we will hold on working on this task until she says so.
Nov 10 2022
The SRE documentation is here: https://wikitech.wikimedia.org/wiki/VRT_System which provides insights about the operations side of the system. Very complete page.
Here is some information about VRT from WMFs perspective https://office.wikimedia.org/wiki/Community_groups/VRT who can be contacted and how and other useful information.
Oct 14 2022
Code repos are here: https://github.com/znuny
Oct 13 2022
@Djackson-ctr & @eigyan , is this done? given the wave 3 was already completed I assume this can be moved to product signoff and resolved?
Oct 11 2022
Jul 8 2022
Dec 3 2021
@jsn.sherman Hey! I forgot adding this context, we did a spike to how that site name and server name should be if it was shared in surveys across many wikis, and this is the task with the answers: T295751: [8h] Dynamically change the survey question based on the project domain
Dec 2 2021
Dec 1 2021
I did answer both questions in slack where they were asked as well.
We've had a discussion with Tanja, Sandister, Krishna, Amin and myself, and we have agreed on the following values:
Nov 30 2021
Ok cool. I've resolved those two, made this one a subtask of T296483: Run test safety survey on 2 wikis instead of T296660: Add the safety translation strings to Extension:WikimediaMessages, since this last one can already be done with the English messages.
@phuedx and I made a specific QuickSurveys dashboard based on the EventLogging one which should help in the future:
100 people/day initial coverage was a figure that we eyeballed in a conversation, but the important point is to affect a small % of editors in the initial deploy. If everything goes well, a few days later we can up the coverages once there is confidence everything is working as expected.
Looks good to me @TAndic. This means that T295558: Link to the privacy statement and T295559: Link to the Community Safety page (child tasks of this one) can be resolved, right?
This should roll out this week, so if there is any effects we should see them in the dashboard hopefully. It would be good to verify if there's any change or not.