Contributing Guide needs improvement about project HOT 4 CLOSED

One possible workflow on the hardware side is below. I'm not married to it, but it should serve to start the conversation.

* Discussion and initial proposals happen on the forums, if only because GH issues are a little tougher to follow and higher barrier to entry for some people, especially hardware people.
* If the community thinks an idea sounds worth prototyping, a reasonable effort should be made to research what the requirements are and what specific solutions exist. A complete schematic and a "core" parts list are required to advance to the next step.

< Spilt between modules and Tessel platform hardware >

### Modules

* A first pass prototype of the hardware should be built and corresponding software (drivers) should be written.
* Once the prototype is completed, the candidate module should be put on the agenda for the next SC meeting by a Collaborator. Discussion topics:
 * Is this something we should roll in as a first party module, or merely an addition to our third party library? Default to 3rd party.
 * If the module will become a 1st party module, what constitutes reasonable reimbursement for the creator in terms of material prototyping costs?
 * What budget, if any, shall be allocated for future development?
* If the concept is to become a first-party module (criteria include "will we sell more than 100 of these per year"?, "is this a problem we should be solving in hardware?", etc.), then the creator of the prototype is reimbursed for prototyping expenses immediately. If it is not to become a first party module, the creator shall not be reimbursed.
* If the hardware is to become a first party module, the SC and the community at large should continue discussion as to if the best possible solution has been chosen. Some combination of the SC member in charge of hardware and the OP will then work to develop the module.

### Tessel

* A proposal/spec should be submitted to the SC member responsible for hardware by a Collaborator in the form of an issue on the appropriate repo (presumably the v2 hardware repo?). Realistically, this proposal will be added to a list of RFCs for hardware to be considered...whenever it's time for new hardware, which is something the SC will presumably make a call on.
* When the time comes to develop new hardware, the SC will review the backlog of issues. The SC member in charge of hardware will work to integrate new features as per the result of the discussion.


...So that's a first pass anyway. Takeaways are

* Don't do it all on GH
* Reimbursements for work that becomes 1st party...but how much and *how* are still totally up in the air. I personally like a percentage cut of ongoing sales paired with reimbursement for material prototyping costs.
* SC decides if something enters the 1st party circle