Recently I’ve was on-boarding with Anais’s team and getting a better understanding of how internal-tools works as well as the needs we had for the staff tools project.
People I talked to about staff tools overhaul:
- Security: @darcyck, @usingh013, @ktfeucht
- Eng-Ops/Internal-tools: @camicano, @anaisftw, @lynnwallenstein
- App-Eng: @corywilkerson (cc: @nadaaldahleh, @ohitsmekatie because of permissions discussion)
- Other: @gnawhleinad
The discussion was different from team to team:
- For internal-tools, the focus was how to they break the problem down and set them selves up as gate-keepers while allowing other teams to also contribute to the staff-tools overhaul
- The security team is really focused on the highly destructive functionality that people have access to when they can use staff tools
- The app-neg team was interested in how we could potentially use team permissions to solve multiple problems at once
Things we were considering for staff tools:
- Planning a mini-summit with staff tools stakeholders —> the idea here being we would discuss potential implementation options & which teams would be responsible for the work
- Starting with a specific task that internal-tools could create an example of and other teams could use as a template to add new features to staff tools
- Working with @wilkerson and his team, especially as it relates to permissions
Documents & Links:
- Staff tools project proposal
- Staff tools data issue
- Initial plan for staff tools mini-summit
- My notes from my discussions
- Documents from discussions with security team:
Let me know if you have any questions: @lynnwallenstein, @benbalter, @rushtonmd, @anaisftw