Closed mikevanhemert closed 1 year ago
🙌🏼
@mikevanhemert This is great and its good to have a contributing guide at the repo level, but i think we need to apply this across all UDS packages and capabilities. I have made a wiki page as an interim solution to link to in the DoD section across all tickets coming down the pipe, with the intent that it will all be captured as a UDS level ADR, which can be referenced in the future.
@mikevanhemert This is great and its good to have a contributing guide at the repo level, but i think we need to apply this across all UDS packages and capabilities. I have made a wiki page as an interim solution to link to in the DoD section across all tickets coming down the pipe, with the intent that it will all be captured as a UDS level ADR, which can be referenced in the future.
So is it okay to merge this in as is? Do we need to link to that wiki and add a note about a WIP ADR related to definition of done? @zachariahmiller @mikevanhemert
@mikevanhemert This is great and its good to have a contributing guide at the repo level, but i think we need to apply this across all UDS packages and capabilities. I have made a wiki page as an interim solution to link to in the DoD section across all tickets coming down the pipe, with the intent that it will all be captured as a UDS level ADR, which can be referenced in the future.
So is it okay to merge this in as is? Do we need to link to that wiki and add a note about a WIP ADR related to definition of done? @zachariahmiller @mikevanhemert
@anthonywendt I dont feel strongly either way about the path forward. I had made that wiki page to reference in the issues as i was trying to organize them. I dont think that or the potential ADR should be a reason to not merge this PR.
I used inspiration from Zarf and the internet to create this initial Contributors guide.