Related to T188244: Develop an easy to use workflow to monitor new developer patches that land in Gerrit - we might have new potential developers entering via Phab (assigning a task to themselves?) before maybe managing to get a patch up on Gerrit.
Been wondering lately if there's a quick'n'dirty way to track that a bit better (but: perfect is the enemy of good).
Could (ab)use the weekly Phab projects email in https://phabricator.wikimedia.org/source/operations-puppet/browse/production/modules/phabricator/templates/project_changes.sh.erb by adding yet another SQL query.