Document best practices for coordinating collaborations

[GBKS]

In our first collaborations with projects, we've already noticed a few best practices that should be helpful to future projects so we don't keep reinventing the wheel as far as coordination and planning go.

I am starting a document here. Reach out if you want edit access.

Planning calls, managing communication, etc are not the most sexy aspects of open collaboration. We prefer to code and design and built things. By standardizing some of our planning and communication, we can maybe simplify the tedious parts and allow us to focus more on the fun parts. For example, I've noticed multiple collaborations come to the conclusion that regular check-ins are helpful - why not just always plan for those. This if of course something that everyone can chime in on, and all contributors can choose how they want to go about things.

[Bosch-0]

Requested access, couldn't see it in a view only mode though?

[GBKS]

Sorry, gave you access and fixed the link.