Hi @Caleb, Hope this feedback helps:
Hm, I think a documentation effort would be useful once the next FC is released. This way it’ll be easier for others to understand the system so they can improve, fork, remix, etc. Also, it would be helpful to know how much of the v1.0 is going to be deprecated so we could document what will still be useful from that version.
Generally, I think documentation is an accessible way for the community to help out. Check out this quote:
from Building Open Source Hardware (page 227)
"Valuable content could be a simple blog post that someone writes about the project. It could be a video, tutorial, or article…Community building even helps in sharing documentation standardization!
The documentation is what keeps the project alive and the community thriving. In a way, the documentation is a good place where past or current contributors can share with future ones. Think of documentation as a kind of asynchronous communication channel."
Since I’m coming from the 3D printing community, here is an example I can offer for documentation inspiration.
I liked @gordonb’s post calling for hackers to help him. It’s provided me a nice project-based way to further understand the OpenAg brain and an opportunity to help the core dev team. Would be nice to see more “job postings” from OpenAg. Check out this quote too:
from Makers (page 120)
"Once you seed your community with content and start attracting users, your job is to give them jobs. Elevate people who seem to be constructive participants to moderator status, and give especially friendly and helpful members a “noob ninja” badge. Once you promote/reward enough of them for doing a good job of constructive community building, you’ll find that members typically help one another, saving you the work.
Advice from other OSHW projects?
Has anyone tried to reach out to Chris Anderson, Adrian Bowyer, David Lang, and other open source hardware champions for advice on building this community and project?