Nick Doty

> If I recall correctly, I wound up building my own entity resolver for performance reasons. Your (awesome) entity resolution requires an n^2 Levenstein distance matrix which was prohibitively expensive...

To summarize: * @npdoty authored a pair-wise distance matrix, Levenshtein distance, and a Juypter notebook that visualizes the matrix and consolidates them individually * @sbenthall authored `process.resolve_sender_entities`, which uses the...

I think my goal for this issue is just to consolidate the `resolve_sender_entities` method to do pairwise distance analysis with configurable cutoff (which I should have code for already) and...

An update, in [this notebook on tenure in IETF WGs](https://github.com/npdoty/bigbang/blob/ietf-participation/ietf-participation/ietf_wgs_tenure.ipynb) I did entity resolution a little differently. 1. I've created new parse functions for normalizing email address and creating a...

This is a great thread, and does seem like a useful utility (for dashboards of different groups, etc.). It might also provide a heuristic for how world-wide a particular group...

#450 helped with the tests piece, but could still use contributor guidelines as part of GitHub interface.

Thanks for noting these terminology and role issues. As I understand it, the code of conduct applies to all members of the Project Community, when they're participating in the project....

I'm fine with that change ("All members of the Project Community" to "All Contributors"), although I'm not sure it makes a huge difference. The Governance document lists as a goal...

I think the ombudsteam can make recommendations (and the project leadership can enact those recommendations), but if those recommendations don't turn into a response, then that will make things a...

I think the ombudsteam is intended to have some separation, which we identified as a goal because you might have complaints that you don't want to share with the full...