-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web Components: Conduct interviews #383
Comments
We've talked to a few folks already and plan to schedule more sessions over the next few weeks. Other work (WC landscape analysis, govt teams and tools survey) is taking priority right now. |
We've conducted 8 interviews so far. We hope to speak with a few more people (particularly about edge stress cases govt agencies have experienced and system resilience required) so this is still in progress. |
I've reached out to a few key contacts but have not had a lot of luck with scheduling. Will consider reaching out to a few more, and also consider other ways to gather data about govt stress 'edge cases.' Maybe it's something I can gather with some desk research if all we're hoping to gather is a few examples/scenarios. |
I think the direction we decided to go in was to shift to finding case studies and scenarios published online. If we see particular cases we'd like to follow-up with, we'll potentially reach out and schedule meetings with those folks. But this round of interviews can largely be considered "done." Moving to FFR. |
Done! |
Conduct interviews of relevant stakeholders and people with experience in Web Components and web performance. See research plan for details.
The text was updated successfully, but these errors were encountered: