Apply for OSH Certification #1

Open
opened 2023-01-25 15:46:41 +01:00 by swendel · 0 comments
Owner

https://application.oshwa.org/apply

Application

BASIC INFORMATION

  • Name of Individual, Company, or Organization Responsible for the Certified Item
  • If not an Individual, name of Individual with Authority to Bind the Company or Organization
  • Country
  • Street Address Line 1
  • Street Address Line 2
  • City/town/village
  • State/Province/Region
  • Zip Code/Postal code
  • OSHWA Contact Email Address
  • Public contact email address

PROJECT INFORMATION

  • Project name
  • Project version
  • Have you previously registered a version(s) of your project with OSHWA?
  • Project description
  • Project website
  • Primary Project Type
  • Additional Project Types
  • Project Keywords
  • Where can the documentation be found for your project?
  • All project documentation and design files are available in the preferred format for making changes.
  • Citation Title
  • Citation URL

LICENSING INFORMATION

  • What license is your project's hardware licensed under?
  • Examples of Hardware Licensing
  • Examples of Software Licensing
  • Examples of Documentation Licensing
  • The project is licensed in a way to allow for modifications and derivative works without commercial restriction.
  • There is no restriction within my control to selling or giving away the project documentation.
  • Where possible, I have chosen to use components in my hardware that are openly licensed.
  • I understand and comply with the "Creator Contribution requirement," explained in the Requirements for Certification.
  • There is no restriction on the use by persons or groups, or by the field of endeavor.
  • The rights granted by any license on the project applies to all whom the work is redistributed to.
  • The rights granted under any license on the project do not depend on the licensed work being part of a specific product.
  • The rights granted under any license on the project do not restrict other hardware or software, for example by requiring that all other hardware or software sold with the item be open source.
  • The rights granted under any license on the project are technology neutral.

CERTIFICATION

  • I have provided OSHWA with accurate contact information, recognize that all official communications from OSHWA will be directed to that contact information, and will update that contact information as necessary.
  • I will only use the certification mark in compliance with official certification guidelines.
  • I acknowledge that all right, title, and interest in the certification mark remains with OSHWA.
  • I acknowledge that OSHWA has the right to enforce violations of the use of the mark. This enforcement may involve financial penalties for misuse in bad faith.
  • I have the ability to bind those responsible for the certified item to this agreement.
  • If you do not agree with any of the above terms, please explain.
  • Relationship to certified item
  • I agree to the terms of the OSHWA Open Source Hardware Certification Mark License Agreement

Notes

https://application.oshwa.org/apply ## Application ### BASIC INFORMATION * Name of Individual, Company, or Organization Responsible for the Certified Item * If not an Individual, name of Individual with Authority to Bind the Company or Organization * Country * Street Address Line 1 * Street Address Line 2 * City/town/village * State/Province/Region * Zip Code/Postal code * OSHWA Contact Email Address * Public contact email address ### PROJECT INFORMATION * Project name * Project version * Have you previously registered a version(s) of your project with OSHWA? * Project description * Project website * Primary Project Type * Additional Project Types * Project Keywords * Where can the documentation be found for your project? * All project documentation and design files are available in the preferred format for making changes. * Citation Title * Citation URL ### LICENSING INFORMATION * What license is your project's hardware licensed under? * Examples of Hardware Licensing * Examples of Software Licensing * Examples of Documentation Licensing * The project is licensed in a way to allow for modifications and derivative works without commercial restriction. * There is no restriction within my control to selling or giving away the project documentation. * Where possible, I have chosen to use components in my hardware that are openly licensed. * I understand and comply with the "Creator Contribution requirement," explained in the Requirements for Certification. * There is no restriction on the use by persons or groups, or by the field of endeavor. * The rights granted by any license on the project applies to all whom the work is redistributed to. * The rights granted under any license on the project do not depend on the licensed work being part of a specific product. * The rights granted under any license on the project do not restrict other hardware or software, for example by requiring that all other hardware or software sold with the item be open source. * The rights granted under any license on the project are technology neutral. ### CERTIFICATION * I have provided OSHWA with accurate contact information, recognize that all official communications from OSHWA will be directed to that contact information, and will update that contact information as necessary. * I will only use the certification mark in compliance with official certification guidelines. * I acknowledge that all right, title, and interest in the certification mark remains with OSHWA. * I acknowledge that OSHWA has the right to enforce violations of the use of the mark. This enforcement may involve financial penalties for misuse in bad faith. * I have the ability to bind those responsible for the certified item to this agreement. * If you do not agree with any of the above terms, please explain. * Relationship to certified item * I agree to the terms of the OSHWA Open Source Hardware Certification Mark License Agreement ## Notes * https://gitlab.opensourceecology.de/verein/projekte/cab/CAB/-/wikis/2-Guides/application-guide * https://en.oho.wiki/wiki/Request_certification_for_your_project
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: curious.bio/smart-energy-monitor#1
No description provided.