I'm sorry, so very sorry, that I did an insulting to you in that gerrit patch page, my brain couldn't control my hand in that time. I also promise that in the future, even if such -2 happened again, I either don't pay attention to that, or if that affects my UI experience, I will try to persuade the corresponding developer team(s) on Phabricator or public discussion pages such as VisualEditor/Feedback. I kindly know that unlike Phabricator, anyone's comment on gerrit can't be removed, and may make one untrusted.
I see that you did some work with the Growth team (https://www.mediawiki.org/wiki/Growth), specifically: https://github.com/wikimedia/mediawiki-extensions-GuidedTour/blob/master/extension.json#L4
Here's the thing: I need to reach some data on guided tours for a recent campaign that we've run in WMDE. However, I can't figure out where to look for the data that I need, so I thought it would be the best to reach someone from the Growth team and ask for advise.
Goran S. Milovanović, PhD
Data Analyst, Software Department
@GoranSM Sure. Basically, you need to set shouldLog to true in the tour (if this is false or omitted, no data will be recorded; example with true is here), then you can get data from the relevant EventLogging schemas. See the list of schemas.
If you're not familiar with accessing EventLogging, you can start here.
The tables have names that are the schema, plus underscore, then the ID. E.g. GuidedTourGuiderImpression_8694395 . So basically:
- ssh stat1006.eqiad.wmnet
- mysql --defaults-file=/etc/mysql/conf.d/research-client.cnf -hanalytics-store.eqiad.wmnet log
- SELECT * FROM GuidedTourGuiderImpression_8694395 LIMIT 1;
If one of the first 2 steps fails, you will need to request access on Phabricator. If you have issues, you can ask here, or in #wikimedia-collaboration (if more GuidedTour-focused) or #wikimedia-analytics (if more EventLogging-focused) on Freenode.
@Mattflaschen-WMFThank you so much. I have access to production and routinely use MariaDB replicas - I work as contractor Data Analyst for WMDE. Your suggestion on how to track the guided tours data:
"... you need to set shouldLog to true in the tour (if this is false or omitted, no data will be recorded; example with true is here)..."
is exactly what I was looking for.
Again: thank you very much!
Stop reverting start talking
Seriously. It is annoying. We need to talk.
Please read what I wrote on my talkpage and over at User talk:MSchottlender-WMF
If you disagree with some of my improvements then you can discuss them on that talkpage.
Are you serious??
Please apologize to everyone involved and never try to do something like that again. Thank you. ~~~~
Oh and please delete flow, it is a stupid idea and a waste of money.
Weigh in on whether to finalize the new version of the "Conflict of interest" section
You participated earlier in discussion about the "Conflict of interest" section of the draft Code of Conduct for technical spaces. There was not consensus to approve an earlier version of this section. I'm contacting you to let you know the draft has been updated, and we are now discussing whether to finalize the new version.
Please participate here.
Please participate again in improving the "Conflict of interest" section
The "Conflict of interest" section was not approved earlier.
There has been further discussion on it, aiming to solve those issues. Please participate in the sub-sections of Talk:Code of Conduct/Draft#Finalize "Conflict of interest" section? and make sure your concerns are being addressed.
User:Mattflaschen-WMF 03:55, 28 September 2016 (UTC)
Test page names
FULLPAGENAME - Topic:Tb72ghabbl04qv3y
PAGENAME - Tb72ghabbl04qv3y
BASEPAGENAME - Tb72ghabbl04qv3y
SUBPAGENAME - Tb72ghabbl04qv3y
SUBJECTPAGENAME - Topic:Tb72ghabbl04qv3y
ARTICLEPAGENAME - Topic:Tb72ghabbl04qv3y
TALKPAGENAME - :Tb72ghabbl04qv3y
ROOTPAGENAME - Tb72ghabbl04qv3y
Instead of "Firefox 3+" it probably should be "Firefox <4", or perhaps "Firefox 3.*". Similarly for the others, "Opera 10+" ''would'' include Opera 10.5+…
What do you think?
It's intentional. My understanding is it means basically, "The no-JS experience is intended to work and provide essential user actions in Firefox 3+, etc.". It does not mean Firefox 3+ deliberately gets the no-JS experience. It might sometimes get no-JS (e.g. due to a transient network failure), but normally as you note it doesn't. In some cases e.g. IE >= 6 < 9 we do deliberately serve all Grade C browsers of that type no-JS (unless the Grade C is also Grade A), but not for Firefox.
@Krinkle and I discussed this leading up to that edit. This is my understanding from that discussion.
Deletion of Flow topic/comment
Hello Mattflaschen, we've had some instances of vandalism/spam on Flow pages on gomwiki, such as this:
I've deleted the topic, but the text in the subject, which can be still be seen, even by non-logged in users, is quite offensive. How can I make this topic title hidden (as an admin)? I'm looking for something like a revision delete for the Flow page history or a page delete for the topic.
You need to suppress it. It doesn't look like anyone in gomwiki has suppress (see https://gom.wikipedia.org/w/index.php?title=%E0%A4%B5%E0%A4%BF%E0%A4%B6%E0%A5%87%E0%A4%B6:ListUsers&group=oversight and https://gom.wikipedia.org/w/index.php?title=%E0%A4%B5%E0%A4%BF%E0%A4%B6%E0%A5%87%E0%A4%B6:ListUsers&group=suppress ).
You can ask a steward. If it's urgent, you can use !steward in #wikimedia-stewards on Freenode. If it's slightly less urgent, you can use Meta:Vandalism reports.
In the future, you may want to ask about getting a local oversighter for your wiki.
This is analogous to how deleting a page does not hide the page name (it's still in Special:Log/delete).
The suppressor can actually do the action at https://gom.wikipedia.org/w/index.php?title=%E0%A4%B5%E0%A4%BF%E0%A4%B6%E0%A4%AF:T5crnav4dljy4wo2&action=history (it should show 'suppress' in parentheses).
Thanks for your advice, Matt. I have requested for suppression.
...and that led to this: https://phabricator.wikimedia.org/T137288
Sorry, if you suppress the topic directly, it works fine. But it turns out there is a problem if the topic is first deleted, then later suppressed. I'm working on it.