Problem Description: 

From a retro on 2/27, we discussed "we need better tracking of project decisions, one line changelogs are useless for devs."

Copying some notes in from the retro:

• Hub architecture drive (used to use)
• concerns about too many places where we document info? (e.g. internal wiki, netifly docs site, and 3rd thing?), Take extra step to go from decision log and take it into docs

• markdown in a file in a repo? https://github.com/rust-lang/rfcs/tree/master/text may be easier to transfer to docs

• other example https://peps.python.org/
• suggestion here is not to replace Jira; it's for engineering specific info: code examples, context about decisions, architecture based, etc
• +1 for markdown, +1 for having some kind of go-to place where every feature has a history of the decisions (jira issues sometimes get closed and replaced, so maybe a seoarate place; google docs tend to accumulate and silently rot)
• create another repo just for project discussions? and use discussion tab or issues there?

outcomes:

• discuss proposal as a team to figure out next steps