Large-scale refactoring is not something you want from an external contributed, especially not if unsolicited.
Typically such refactoring is done by the core development team / maintainers, who are very familiar with the codebase. Also because DOING such a change is much easier than REVIEWING it if done by someone else.
Besides the fact that it makes no sense to import Facebook-style data into a chat, doing so would only be useful if more than a tiny amount of the data in Workplace was actually worth keeping.
You probably don't need a virus or anything running in the end user's network.
If your Sonos can access the API to mark a device as recycled, so can you. So if you can predict serial numbers or just bruteforce them (depending on how complex they are) you might be able to brick every single Sonos out there...
I highly doubt they assign unique keypairs etc. to every single device...
No, what you need to do is fix your package's code to work on Python 2 and 3 without running 2to3 on it. The only case where this doesn't work is if you have binary extensions - but then you need separate wheels in any case.
Typically such refactoring is done by the core development team / maintainers, who are very familiar with the codebase. Also because DOING such a change is much easier than REVIEWING it if done by someone else.