Plan: this feels like a "many eyes make all bugs shallow" kind of thing. There are a lot of data pipelines involved and we can find all the affected ones together!
Those of us who are familiar with the pipelines, especially @JAllemandou, @mforns, @Milimetric for any batch jobs and @Ottomata for any EventBus-generated streams, should definitely be involved. But @ntsako, @Snwachukwu, and @Antoine_Quhen have all worked on at least some of the affected jobs. It's probably useful for everyone to search and think on their own for a couple hours and then have a couple of meetings where we brainstorm together. Beyond that though, if we miss something, the impact should be very obvious and we should be able to recover easily by going back to the source data and re-running jobs. So it probably isn't worth spending a huge amount of time making sure we don't miss a single line of SQL.
**Steps**
[] Work in pairs or small groups to discuss what data pipelines might be affected by IP masking
[] Brainstorm in a bigger meeting the workflows, processes or data pipelines affected (if any)
[] Decide as a team if IP masking affects our team or not and communicate it via this phab ticket
[] Fix accordingly
Timeline: If there are any fixes needed, they should be done by Q1 next fiscal year
*useful links*
* https://office.wikimedia.org/wiki/Product/IP_Masking#FAQ
* https://office.wikimedia.org/wiki/Product/IP_Masking#Important_links
* https://phabricator.wikimedia.org/T326816