IEEE.org     |     IEEE Xplore Digital Library     |     IEEE Standards     |     IEEE Spectrum     |     More Sites

PROPOSAL-OSH-review.md 1.84 KB
Newer Older
Martin Haeuer's avatar
Martin Haeuer committed
1
2
3
Review of open source hardware
-

4
##### Refer to the [Review of open source software](url) document when applicable.
Martin Haeuer's avatar
Martin Haeuer committed
5
6
7
8
9
10
11
12
13
14
15
16

# Scope

- **Assessment of technical documentation of open source hardware.** _Just_ the documentation (at the beginning). Including assessment/certification of the actual technology would result in a much bigger need regarding reviewing and administrative resources. (Also not sure what a certificate for a technological review would mean in terms of liability etc.)
- more specifically: assess completeness, quality and accessibility of technical documentation after clear, technology-specific requirements
- technical documentation shall:
    - provide sufficient information so that specialists in the fields of corresponding technologies would require to exercise the four rights of open source (hardware) (→ study, modify, make/use, distribute/sell)
    - be published under a free/open license
    - accessible via the internet
    - bear reference of a defined set of metadata (name or working title, author(s), license, functional description, release number etc.)

# Process
17
(Note: in this initial proposal, the mention of a "certification body" is suggested. That is an option that may or may not be included in the final proposal)
Martin Haeuer's avatar
Martin Haeuer committed
18
19
20
21
22

1. project submits a release of its technical documentation to a certification body / conformity assessment body
2. body moderates anonymous peer-reviewing process
3. when all comments/issues are clarified, the body issues a certificate / an attestation to the applicant
4. certificate / attestation can be challenged (e.g. when the documentation is not accessible anymore or license terms changed)
23
5. all relevant information (documentation releases, peer-reviews, certificates/attestations,…) are published under a free/open license by this body → hence "hard forks" of the whole body are technically possible