OSEGeV Conformity Assessment Body issueshttps://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/issues2021-09-07T11:26:52+02:00https://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/issues/66Attestation Format2021-09-07T11:26:52+02:00Martin HäuerAttestation FormatMaybe that's a duplicate, so feel free to close this issue if that's the case.
I heard that the format in which the attestation is issued remains to be an open question. Here's a suggestion:
- We publish a release of the assessed OSH, ...Maybe that's a duplicate, so feel free to close this issue if that's the case.
I heard that the format in which the attestation is issued remains to be an open question. Here's a suggestion:
- We publish a release of the assessed OSH, annotated accordingly (something like `v.1.0.2-attested`)
- …alongside with Export files etc. _and_ a pretty PDF (something like this: [ugly](https://cloud.opensourceecology.de/index.php/f/289776), [pretty-1](https://cloud.opensourceecology.de/index.php/f/305672), [pretty-2](https://cloud.opensourceecology.de/index.php/f/305673))
- optional: we link the repo with [Zenodo](https://zenodo.org/) and automatically provide a DOI to the release (see [this guide](https://guides.github.com/activities/citable-code/) for GitHub)
@niles @lukassDocumentationhttps://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/issues/63Self-Assessment of Open Source Hardware2021-07-19T09:46:00+02:00Nils WeiherSelf-Assessment of Open Source Hardware- [x] Discussion
- [ ] Documentation
Components used during the assessment can be standard components (e.g. with ISO standards), proprietary components (e.g. available as purchase) or Open Source Hardware.
# Requirements of proprietar...- [x] Discussion
- [ ] Documentation
Components used during the assessment can be standard components (e.g. with ISO standards), proprietary components (e.g. available as purchase) or Open Source Hardware.
# Requirements of proprietary components **PROPOSAL!**
- Dimensions of the components have to be given
- The component is purchasable and offered for international shipping
# Requirements of Open Source Hardware
There are two ways to qualify as Open Source Hardware according to DIN SPEC 3105.
## 1. Community based assessment **PROPOSAL!**
- Project is assessed according to the process given in DIN SPEC 3105-2
- A Community Assessment Body (CAB) confirms the confirmity according the the DIN SPEC 3105-1
- If a complaint is reaching the CAB the confirmity has to be verified again and can be revoked
## 2. Self assessment **PROPOSAL!**
- The author of the project officially declares the project as
- This declaration has to be published at the project repository
## Embedding Self-assessed Open Source Hardware
If self assessed Open Source Hardware (here: component) is embedded in an Open Source Hardware project that is undergoing assessment (here: main project), the self-assessment for the component can be trusted. However, if - again - a complaint is reaching the CAB that is responsible for the confirmity of the main project, the self-assessment for the component can be rejected and thus has to qualify either as proprietary component (e.g. by being purchasable) or be re-assessed as Open Source Hardware.Documentationhttps://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/issues/61[Workflow] Assessment of libraries2021-07-19T07:41:31+02:00Nils Weiher[Workflow] Assessment of libraries- [x] Discussion
- [ ] Documentation
The question is how available components can be assessed, so that they do not have to be checked over and over again.
Concrete: The [UPKLib](https://gitlab.opensourceecology.de/verein/projekte/cab/C...- [x] Discussion
- [ ] Documentation
The question is how available components can be assessed, so that they do not have to be checked over and over again.
Concrete: The [UPKLib](https://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/issues/58) is a set of components that is the base for a several other OSH projects. Great example of an modular design principle that could help OSH to jump out of the DIY niche.
> Ich würde gern zeitnah eine Besprechung zu den UniProKit Projekten ansetzen. Neben dem allgemeinen Zeitplan soll es darum gehen, wie wir mit den UPKLib Elementen umgehen. Konkret kam die Idee auf, dass wir während des Assessments der einzelnen Projekte eine Art Produktdatenmanagement für die UPKLib Bauteile betreiben. Zu gut deutsch: Jedes mal wenn eines der Elemente genauer überprüft wird, als das für "available components" erforderlich wäre, wird das Teil in der UPKLib abgehakt, sodass wir nach und nach die Bibliothek jenseits des Basiskits abarbeiten.\
> @niles
> je nachdem was der Sinn ist. Klingt aber genau nach dem, was ich mal angemerkt habe: das UniProKit selbst ist nicht wirklich ein Open Source Hardware Produkt sondern ein Set bestehend aus 'Available Components' könnte man aber auch anders handhaben, nur dann wird es sehr viel genauer eingefordert (Einzelbauteilzeichnung als CAD Dateien + Technische Zeichnungen etc).
Gleichzeitig wäre aber eben der Ansatz möglich jedes Produkt (Fräse, Drucker, SolarBox etc.) zu prüfen und dabei eine Art Review der Bauteile mit vorzunehmen, dann wird aus einem vorherigen 'Available Component' mit reinen Eigenschaften/Schnittstellen/Maßangaben eben jetzt auch ein Open Source Element von einem neuen Review. Bleibt halt die Frage ob das so sinnig ist, bzw im Verhältnis zum Aufwand steht.\
> @timm
Thus, for the assessment, the idea is to create a list with all the components in UPKLib and to complete the list for all components that can be assessed as Open Source Hardware by providing:
- source files
- export files (technical drawing)
This way a bibliography providing all CAD-files for the standardised components can be created. This would be a "Lego" for Open Source Hardware and a great step towards replicability.
Open quesitons:
- BPM and assembly are required for OSH but inapplicable for available components
- Maybe actually a new category is required for available components!?Documentationhttps://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/issues/27[Workflow] How to apply for assessment?2021-07-19T11:04:19+02:00Martin Häuer[Workflow] How to apply for assessment?Maybe I'm just missing something, but as far as I see it, we don't any official way for applicants defined at the moment.
Once elaborated, this should be documented in an application guide and as a very brief version in the ReadmeMaybe I'm just missing something, but as far as I see it, we don't any official way for applicants defined at the moment.
Once elaborated, this should be documented in an application guide and as a very brief version in the ReadmeDocumentationTimm Willetimm.wille@ose-germany.deTimm Willetimm.wille@ose-germany.de