You can tackle this in 2 ways: 1 consolidate the research in a file like this (preferably in markdown) or you can open a "research issue" on the repo. (The issue route makes it easy to discuss your findings with the issue comments). I'd suggest the markdown file route for any documentation that isn't going to change much but that's just me.
You can tackle this in 2 ways: 1 consolidate the research in a file like this (preferably in markdown) or you can open a "research issue" on the repo. (The issue route makes it easy to discuss your findings with the issue comments). I'd suggest the markdown file route for any documentation that isn't going to change much but that's just me.