You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Post Proposal (full Problem/Solution statement) in #expensify-open-source
Wait at least one full business day, and until the post has a majority (2/3) of positive reactions (👍)
Paste Proposal in the space above with a link to the Slack thread
Email strategy@expensify.com and paste in the Proposal
Fill out the High-level overview of the problem, Timeline, and Terminology sections of the Design Doc
Email strategy@expensify.com (continue the same email chain as before) with the link to your Design Doc
Host a pre-design meeting (example) in #expensify-open-source to discuss any necessary details in public before filling out the High-level of proposed solution section.
Fill out the High-level of proposed solution section
Email stategy@expensify.com again with links to the doc and pre-design conversation in Slack
Add the DesignDocReview label to get the High-level of proposed solution section reviewed
Respond to any questions or concerns and bring up blockers in Slack to get a consensus if necessary
Confirm that the doc has the minimum necessary number of reviews before proceeding
⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️
Proposal
➡️DESIGN DOC
WN Post
Tasks
#expensify-open-source
strategy@expensify.com
and paste in the Proposalstrategy@expensify.com
(continue the same email chain as before) with the link to your Design Doc#expensify-open-source
to discuss any necessary details in public before filling out the High-level of proposed solution section.stategy@expensify.com
again with links to the doc and pre-design conversation in SlackDesignDocReview
label to get the High-level of proposed solution section reviewedThe checkboxes above were handled in /~https://github.com/Expensify/Expensify/issues/418617
This GH is a focus on the following points:
#expensify-open-source
to ask for engineering feedback on the technical solution.DesignDocReview
label to this issuestrategy@expensify.com
one last time to let them know the Design Doc is moving into the implementation phasestrategy@expensify.com
once everything has been implemented and do a Project Wrap-Up retrospective that provides:The text was updated successfully, but these errors were encountered: