Closed mhauru closed 1 year ago
For now, let's use the issue on GitHub as the notification "target," rather than individuals.
If there's a use-case for matching Forecast people with GitHub users, note it in the comments below.
One use case is anything we want to do with emoji reactions, which we presumably would want to match with Turing emails. Another might be if we want to do something with Github assignees, though not sure what that would be. Not saying these are high priorities, but in the long run having the user data merged feels like The Right Thing To Do.
Agree with emojis, because in the long run we'd like auto-scheduling. Suggest deprioritising now, however.
Quite a lot of people have their emails hidden on Github, and have names and logins that don't match the ones on Forecast. E.g. we might have a Forecast person "Margaret Smith" with "msmith@turing.ac.uk", and we would need to match that with a Github user with login "ms578", no visible email, and name "Maggie Smith" or maybe even just "Maggie". This seems undoable programmatically, so we'll probably have to manually maintain a list of Forecast -> Github mappings for these cases (many can, and should, be automatically matched).
Not sure where to keep that though, and in what format. Having it be under version control sounds like a bad idea (for e.g. privacy/GDPR), but it should be shareable within Hut23.