I'd personally prefer to combine both requests in one task since it's not very different, technically speaking. The software changes required for both are pretty much the same (i.e the changes will be made in one place and not two).

It is no big deal, IMHO. Now that we separated them, let's leave it this way. Whomever writes a patch might actually write the other as well.

In T174562#3567405, @Niharika wrote:

I'd personally prefer to combine both requests in one task since it's not very different, technically speaking. The software changes required for both are pretty much the same (i.e the changes will be made in one place and not two).

The reason I separated them out is because it is possible that we may want to do one and not the other, so I think considering them separately helps. If you use the same patch for both, it can be tagged against multiple tasks, so there's no overhead there.

Anyway, I'm not strongly tied to any particular task configuration. It's your project, so if you'd prefer to merge them together, I have no objections. :-)

Pinged WMF Privacy/Legal/Security to get feedback on this before moving forward.

Approved by Legal.

Any progress? The Legal team approved this two and a half months ago.

I started working on it but I found out that the first thing we need is a way to create login records from an arbitrary IP address (because I only have one test VM, and all edits from it will have the same IP i.e. 127.0.0.1

I worked on creating a maintenance script that would create a login attempt from an arbitrary IP, and tried to model after our unit testing code, but did not finish the job. I think it is best if we create a subtask for it, and perhaps someone else can help develop that script. Overall, any help in this area is appreciated, as I have run into a bit of difficulty finding time to work on patches recently.