--- robots: nofollow, noindex tags: shield --- # Shield Dev Introduction This doc is targetted at devs starting shield, perhaps for the first time. This is more an index of other resources than a large document itself. We are looking at how to adjust shield going forward, but this document covers expectations today. ## Issue and PR assignment Once your shield rotation starts, you will get every new issue and PR assigned to you. If you have e-mail notifications setup on github, your mailbox will likely be flooded with notices. ## Basic expectations ### Issues For issues, you are responsible for investigating the issue assigned to you into a fixable state. This means, checking for dupes, confirming repro, investigating cause, and finally proposing fix. Depending on the complexity of the issue you may or may not be able to complete everything above alone, and that's ok. Here's the queries to drive to zero in order 1. [![](https://i.imgur.com/aNMAYwg.png) Needs Triage - Sorted by Oldset](https://github.com/microsoft/fluentui/issues?q=is%3Aopen+is%3Aissue+label%3A%22Needs%3A+Triage+%3Amag%3A%22+label%3A%22Fluent+ui+react%22+sort%3Acreated-asc+) - These issues will be triaged by PM - High priority ones will be tagged with ![](https://i.imgur.com/xQeY87E.png) - The ones that need follow up will be tagged with![](https://i.imgur.com/29t7km7.png) and assigned to Shield dev by default - Questions get converted to [Discussions](https://github.com/microsoft/fluentui/discussions) 2. [![](https://i.imgur.com/xQeY87E.png) High Priority - Sorted by Age](https://github.com/microsoft/fluentui/issues?q=is%3Aopen+is%3Aissue+label%3A%22Priority+1%3A+High%22+sort%3Acreated-asc+) - These issues are high priority and we need Shield dev to follow up on them to drive the resolution - This could be just fixing the simple issues or following up with the assigned engineer on a fix 3. [![](https://i.imgur.com/97uYkvk.png) Needs Attention - Sorted by time since Updated](https://github.com/microsoft/fluentui/issues?q=is%3Aopen+is%3Aissue+label%3A%22Needs%3A+Attention+%3Awave%3A%22+sort%3Aupdated-asc) - These are issues where the author has responded to a request for more information and we need to follow up. - Priortize working through these irrespective of assignment. - Some of these it may be just pinging the assigned to person via Teams, or re-assigning as appropriate 4. [![](https://i.imgur.com/29t7km7.png) Needs Investigation - Assigned to You](https://github.com/microsoft/fluentui/issues?q=is%3Aopen+label%3A"Needs%3A+Investigation"+assignee%3A%40me) - [Alternate link excluding "needs author feedback" and "needs discussion"](https://github.com/microsoft/fluentui/issues?q=is%3Aopen+label%3A%22Needs%3A+Investigation%22+assignee%3A%40me+-label%3A%22Needs%3A+Discussion+%F0%9F%99%8B%22+-label%3A%22Needs%3A+Author+Feedback%22) - **For most issues, we should understand the issue, point folks in the right direction and offer our support with reviewing the fix.** - Avoid replying and saying we'll fix it soon, unless you ensure we do so - Then: - If the issue is not High Priority and seems reasonable for a contributor to tackle it. Tag it with: ![](https://i.imgur.com/GamEDZo.png) - If you can get the issue narrowed down enough that a new comer could tackle it (with some effort of their own). Tag it with: ![](https://i.imgur.com/KX9Nr9U.png) - [What makes a good first issue on GitHub?](/uSwz52AERCy2mNF-rmJf1w) - If you aren't able to get the issue to a reasonable end state. Get positive hand off with another dev who will pickup the investigation and actively work to propose a fix or fix the issue (assign the issue to them) - If doesn't repro: ![](https://i.imgur.com/0iPnl7E.png) - If need input from author: ![](https://i.imgur.com/SnqLRbr.png) ### PRs For PRs, you are responsible for keeping an eye on PRs from folks outside the team and making sure they are getting traction. - You can use [fluentui-open-prs.xlsx](https://microsoft.sharepoint-df.com/:x:/t/FluentUIInternal/EQe5f2t-7iJGoBPoTCySmukB_s7ZRJH9A7SxF_MRbmhUIw?e=hK2n7B) to help monitor these. - You can also look at [least recently updated PRs](https://github.com/microsoft/fluentui/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-asc) ### Questions For questions there are two locations: 1. Monitor the [Fluent UI React (Web)](https://teams.microsoft.com/l/channel/19%3a86b094239256467da9dfa96ba0897ca2%40thread.skype/Fluent%2520UI%2520React%2520(Web)?groupId=ffe264f2-14d0-48b5-9384-64f808b81294&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47) community channel and attempt to answer questions or direct our team to answer questions. 2. Monitor unanswered questions on [Our Discussions](https://github.com/microsoft/fluentui/discussions?discussions_q=is%3Aunanswered) answer questions the questions you can. Feel free to ping engineers internally asking folks to answer open questions ## Links - [Shield Cheatsheet](/wJwTino2T1i_v0r7RXEMCQ) - [Shield Wiki](https://uifabric.visualstudio.com/UI%20Fabric/_wiki/wikis/UI-Fabric.wiki/70/Shield) - [Template responses for Shield](/IcudV52OS3ufaaMcOq2ktA) - [Fluent UI Issue Triage and Expectations.docx](https://microsoft-my.sharepoint-df.com/:w:/p/aneeshak/EYp-9Yv_uypFk-skO55vQX0BR_WZBlnH_nw-aLdGmipM3Q?e=d2wl65)