@Cosmos
Positive post coming up.
Community development projects. :grouphug:
For your consideration.
This is how I would see this working.
Any member of the forum can suggest a piece of hardware to be designed.
Any member can take up the project request.
Any member can submit their code, schematics and/or documentation to the project as long as it complies with the rules.
Multiple submissions would be considered for the best implementation. Also multiple projects may have parts of those projects combined into a 'best of' implementation.
For continued development support as long as the member complies with Rule 1 the community would continue to support and advise on the development. Must comply with the other rules aswell.
Rule 1:
All code, schematics and documentation must be released at regular intervals, whether the code, schematics and documentation are ready or not. That is even if the code is non functioning, the schematics are incomplete or the documentation is only partial and still needs to be proofread.
Basically, you release what you've got, say every week for the first four weeks then every four weeks after that.
This is to promote trust in those providing the technical help etc.
Rule 2:
The license the code, schematics and documentation are released under should allow anybody to do what they want with it so long as their project complies with the following criteria.
a.) The using project can only use the code, schematics and documentation if the using project is non-commercial.
b.) The using project can only use the code, schematics and documentation if the using project is an open project.
c.) The using project can only use the code, schematics and documentation if the using project does not restrict other open projects from integrating the using project into other open projects .
d.) The using project can release the component parts of their project (code, schematics and documentation ) under a different license only so long as the using project's license complies with and does not infringe on Rule 2c.
e.) Projects from other sources may not be intergrated into community projects without the original developers permission and only if that project complies with all the licensing rules.
f.) All community members must agree to not tell the authorities that these projects have not gone through the CE or FC process.
Rule3:
Commercial exemption is only provided by the community under the following criteria.
a.) A price is set for 'kit builders' and 'fully assembled product builders' by the community. 'kit builders' and 'fully assembled product builders' would be allowed to make a profit which would be set by the community.
Too low and no one will build kits or assemble full products.
Too high and no one will buy it.
b.) 'kit builders' and 'fully assembled product builders' must provide samples to selected (community voted) testers for quality and safety checking before they would be permitted to become a 'kit builder' or a 'fully assembled product builder'.
C.) 'kit builders' and 'fully assembled product builders' can only sell Kits and assembled products within this community, due to Rule 2f
Rule4:
All final decisions would be made by a community council, voted in by the community.
Any member of the forum would have the right to call for a full community vote on the grounds that the community council's decision is not complying with the rules of the Community development projects.
Rule5: No member may pass wind while discussing projects on the forum. OK, so I'm running out of ideas for rules. :roll:
I would volunteer to do any documentation for the projects, assuming I got voted in as a documenter. I would also be willing to drive this idea. That is being the central point for communication and status reports, at least until you find someone better.
[Disclaimer] I am a meat popsicle. As such I know zip about electronics. When I do (say in about 10years) I'll take this on.
Unless you really want this to happen now, I'm in.
