Crash course on open hardware from nothing to succesfull gitlab contributions

🚀 I think people need some kind of introduction to have a smooth transition from wanting, to actually being able to work and contribute in an open hardware project

This is an epic, a big user story. Here I post some reflections and ideas to develop it further.

Context considerations:

• Many people want to contribute and work on open hardware projects but is difficult to start for them as they need to learn different concepts, tools, meet new people etc. They need a step by step course to onboard succesfully in a project.
• Other people want to lead projects, and share them with others, they also would like to gain contributors, but they don't know how to grow succesfully a community and sustain it.

Ideas for solution:

Content idea and example

• Mozilla Open Leaders is a great example for this solution Table of contents:
• Intro to GO!Commons

• Story, Vision, Why and How
• Focus on teachning how to work and lead open source in the context of Hardware
• Learn by doing

• The basics of working open

• Find something to work on and improve(a project, a repo, an idea, an issue)
• Start small, preferably learn from others for some time from 4 weeks to 3 months
• Learn by doing fork a repo, request access to join a team, jump in the chat, connect with others

• Open Hardware Documentation

• BOM and Source files
• Development status
• Versions, Variants and releases
• License

• Learn Gitlab

• What is GitLab?
• What is Git?

• Sustaining your project and community

Technical proposal:

• Reuse the open leader template provided by mozilla with new content