Certify a project

This is a list of the metadata retrieved for project Snow shoes. Do the following:

  1. Review the parameters drawn from the documentation. If any has an error or is missing, go back to the documentation page and edit the appropriate template.
  2. Fill out the missing information in the form below or make any necessary changes.
  3. Make the request by submitting the information at the end of the page.

Please note that OSHWA will contact you directly regarding the status of your submission. This script makes a direct submission using the OSHWA API. Appropedia does not keep track of any applications and will not store copies of the information entered on this page.



Basic information —Section 1 of 4

This part of the form asks for basic information about the responsible party for the project to be certified, such as the name of the individual, company, or organization certifying the project and contact information for any future correspondence from OSHWA regarding your certification.

Appropedia will select organization if there is an affiliation named on the documentation, but you can override this.
If hardware is certified on behalf of a company or organization, the first item of the attribution parameter on Template:Page data.
The first page author is selected by default.
Country (and other location information) is calculated from the metadata added to the page, if available.
City (and other location information) is calculated from the metadata added to the page, if available.
State (and other location information) is calculated from the metadata added to the page, if available.
Postal code (and other location information) is calculated from the metadata added to the page, if available.
This email address will be kept private and only used for official communications from OSHWA about your certification. Appropedia will not keep a copy of this.
This address will be made publicly available in the certification directory.

Project information —Section 2 of 4

This part of the form asks for information about the project you wish to certify. Information submitted here will appear on your project’s profile listing.

Defaults to the Appropedia project page title. If you wish to rename it, consider moving the page.
v
This displays the edit count at the time of submission. Feel free to override this if you keep a different version control system.
If you have previously registered a version(s) of your project with OSHWA, type in the UID for that project
Provide a brief description of your project (500 characters).
This defaults to Appropedia's URL but you can override it if you want to point to a different documentation page. Include the protocol to your URL (e.g. http:// or https://)
This will search the uses parameter on Project data for the first occurrence of any of the following keywords: 3D Printing, Agriculture, Arts, Education, Electronics, Enclosure, Environmental, Home Connection, IOT, Manufacturing, Robotics, Science, Sound, Space, Tool, Wearables. If your project doesn't fall into any of these types, add "Other".
This will search the uses parameter for any occurrence (other than the first) of any of the following keywords: 3D Printing, Agriculture, Arts, Education, Electronics, Enclosure, Environmental, Home Connection, IOT, Manufacturing, Robotics, Science, Sound, Space, Tool, Wearables. You can select more than one option (press CTRL to select multiple options).
If you would like your project to be searchable by specific keywords, add them here separated by commas.
Defaults to the Appropedia documentation page URL.

Does your project incorporate or build upon other open projects that are not currently certified by OSHWA? If so, use this space to cite those projects

Citation title
Citation URL
Citation title
Citation URL
Citation title
Citation URL

Licensing information —Section 3 of 4

This part of the form asks for information about your project’s licensing. In order to qualify for OSHWA certification, you must have chosen an open source license for your hardware, your software (if any), and your documentation. Your licenses for each of these elements will appear on your project’s profile listing.

Any changes to the hardware license must be done at the page.
Any changes to the software license must be done at the page.
Any changes to the documentation license must be done at the page.
The project is licensed in a way to allow for modifications and derivative works without commercial restriction.
If you answered no, please explay why
There is no restriction within my control to selling or giving away the project documentation.
If you answered no, please explay why
Where possible, I have chosen to use components in my hardware that are openly licensed.
If you answered no, please explay why
I understand and comply with the "Creator Contribution requirement," explained in the Requirements for Certification.
If you answered no, please explay why
There is no restriction on the use by persons or groups, or by the field of endeavor.
If you answered no, please explay why
The rights granted by any license on the project applies to all whom the work is redistributed to.
If you answered no, please explay why
The rights granted under any license on the project do not depend on the licensed work being part of a specific product.
If you answered no, please explay why
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.
If you answered no, please explay why
The rights granted under any license on the project are technology neutral.
If you answered no, please explay why

Certification —Section 4 of 4

This part of the form asks you to certify that you agree to specific terms of the OSHWA Certification Mark License Agreement.

You agree to the following terms:
Provide a brief explanation (500 characters)
Briefly describe your relationship to the certified item.