How can newcomers better be directed to collaborate?

[tcr]

The README for this project currently indicates some steps for people to collaborate and submit code. As we grow closer to when Tessel 2 ships, we should be ramping up avenues for involvement as much as possible.

• What can be done without hardware?
• What can be worked on when hardware is available?
• How do we onboard new community members to contribute meaningful things to the project?

[johnnyman727]

Just brain dumping here:

What can be done without hardware?
CLI development (filling out spec, multiple language support, test bench), USB modules, and build tools.

What can be worked on when hardware is available?

The above + firmware, 10-pin modules, hardware modules.

How do we onboard new community members to contribute meaningful things to the project?

I think there are a couple of things we need to improve here. First is awareness of what "beginner level" tasks can be picked up (labeling on Github?). Second is documentation about how Tessel 2 works so they can start learning how to make fixes. Third is information about who to ask for more details.

[johnnyman727]

I created this doc towards this goal. It doesn't go over how to use the developer tools though. That can be added to the doc!

[Frijol]

(under continuous development, make issues for specific needs)