Contributing guidance

[em-jones]

I'd like to make some contributions, and in order to make those contributions I'd love to find some guidance. I'm not able to find any sort of guidance besides the development section of the README.md. I'd like to start by working with the leadership and contributing community to create a contribution guide of some form or another.

Can I ask for support with identifying responsible, accountable, consulted, and informed collaborators (RACI model reference)

ASIDE:
I think this project is an incredible tool and the community work that's going into it is so beautiful. I'd already heard about Livebook over the past year/so in various podcasts. 🏆 🥇 to you all
Here are some talks that have inspired me to reengage with the elixir ecosystem(in case anybody else is at a similar point in their relationship with systems building):

• Using Livebook to teach Elixir
• Stop shipping dead programs

@-ing my mentee @osmanthusleaf for visibility

[jonatanklosko]

Hey @em-jones! The best way to contribute is to look at the issues tracker and ask for more details if unclear (or just ask to make sure nobody else is working on it already). In case of a new feature idea, a good staring point is opening a discussion. We are also happy to review any PRs as they come :) We are a small team and we usually discuss the next steps internally, issues are mostly to keep track of them and are oftentimes brief, but anyone willing to contribute can ask for clarifications!