then i think user_is_flagged_as_bot_in_mediawiki_group (please reword) but something longer and more explicit
@JAllemandou what is the difference between user_is_bot_by_name and user_is_bot_by_group/
Did you tested that you had access @Julia.glen ? Can you confirm things are working?
@Yair_rand The guidelines are not confidential, they apply to a set of systems that only people working at WMF (and research collaborators) have access to , as such it is posted to WMF internal wiki.
Thu, Mar 21
FYI that this blocks some changes to improve refinement of data, cause until these schemas are changed they cannot be refined with the new code. Ping @AndyRussG
Can we have an ETA of when this work would be completed (since it is not a code patch it will not be visible here on ticket). Once fixed we can refine that data and make it available on hive using the schema.
@chelsey: you just need to submit a CR, we will look at it, thanks
Wed, Mar 20
Please add other subtasks here @Neil_P._Quinn_WMF that woudl be helpful
Tue, Mar 19
Super thanks @Pchelolo for looking at this so fast
Ah, yes, @JAllemandou is totally right as always.
I think the suggestion of escaping all white-space characters (end-of-lines, spaces, tabs etc) actually makes sense.
I also think we should update the page-title extraction function to better handle the special <script> case shown here.
+1, these changes are to happen on pageviewdefinition java classes rather than HIVE
Moved to ML from radar column.
Rather than close you can move to blocked and leave it open , i do not think anything is happening in the near future.
Change tag tables (not as part of mw history) are in scooped in hadoop.
Mon, Mar 18
Now available: https://stats.wikimedia.org/v2/#/pa.wikisource.org
Ping @JAllemandou while task is in CR there is no patch , maybe we need to push to gerrit/update bug in commit?
Fixed, now it says "last 12 months (month year - month year)"
@fgiunchedi sounds good, will try to set up short 30 min meeting?
Fri, Mar 15
Overall idea looks good. Adding screenshots for UX issues:
Ping @fgiunchedi about putting this as a commong goal next quarter
Spreadsheet with dashboards triage: https://docs.google.com/spreadsheets/d/1Znl8Tu_OlmOoah4PwSKhK09ZoGJzv9Wnc2X4Oo_Mgug/edit#gid=0
@Anomie this is concerned with eventbus data that is real time, most of the data wanted here is less than couple months old as information wether edits where a revert exists on other datasets for data older than that. So (it seems) that having "rollback" or "undo" tags is actually a good measure of whether a revert has happened. In which case adding tags to this schema should be sufficient:
Thu, Mar 14
ping @Tgr to clarify if we are thinking about ipblocks or rather status of users as autoconfirmed
Blocked on http://phabricator.wikimedia.org/T215442
blocked on http://phabricator.wikimedia.org/T215442
Stalled on https://phabricator.wikimedia.org/T216528
@jmatazzoni sounds good, many thanks.
Wed, Mar 13
@mforns restarted job, this one shoudl have correct e-mail: https://hue.wikimedia.org/oozie/list_oozie_coordinator/0147256-181112144035577-oozie-oozi-C/
Ok, the workflow has the success e-mail: https://hue.wikimedia.org/oozie/list_oozie_coordinator/0131427-181112144035577-oozie-oozi-C/
Looking at the patch, it seems like it doesn't actually include our email address (
That is correct the patch is generic, it is the job which should be configured with the e-mail address in question
Ok, approved on my end please see June 30th end date.
Does anyone on Core Platform Team have any worlds of advice here?