Try to be concise with answers
Each project submission has to be reduced to around 400 words
</aside>Project Description
<aside> 👉Fill this in with a brief, general description of the project
</aside>Project Goals
<aside> 👉List the goals of the project. Why are we investing in this, what does it provide Sentry or the broader industry?
</aside>Technical Uncertainties
<aside> 👉Duplicate the toggle header for each uncertainty this project contained and fill in the sections accordingly. These uncertainties are what the CRA will be specifically looking at when reviewing or auditing the claim
</aside>Uncertainty #1
<aside> 👉Describe the uncertainty. What was the challenge or problem that we did not have an answer to? Is there prior art that we could use to base our problem solving on? If not, why?
</aside>Experiments
<aside> 👉List attempts or experiments that were conducted to learn about the uncertainty
</aside>Results / Learnings / Success
<aside> 👉List what we learned from the experiments. Were any of them deemed successful? If so, how did the success move our understanding forward?
</aside>Uncertainty-Specific Documentation & Links
Project Docs:
<aside> 👉Notion, github discussions, extracts from slack, meeting notes, personal files, blog posts, etc. that relate specifically to this uncertainty. General project docs can go in the section below.
</aside>PRs
<aside> 👉Links to individual PRs, or PR searches that encompass the work done for this uncertainty. Try to limit the search time period to FY’25. General project PRs can go in the section below.
</aside>Participants
<aside> 👉Who worked on this, what % of their yearly time was dedicated to this, and what was their specific role in executing the work?
</aside>Project Documentation & Links
Project Docs:
<aside> 👉Notion, github discussions, extracts from slack, meeting notes, personal files, blog posts, etc
</aside>PRs
<aside> 👉Links to individual PRs, or PR searches that encompass the work done for this project. Try to limit the search time period to FY’25
</aside>