Clarify source files and licensing requirements (#1134)

* Clarify source files and licensing requirements

Clarified prerequisites for project submissions, including licensing requirements and added a note about commercial use starting in 2026.

* Remove commercial change

* Remove trailing space

Author: tannewt

howto.md

@@ -7,8 +7,8 @@ permalink: /howto/
 If your project does not meet the following criteria, your pull request **will** be rejected:
 
  - Publicly available source code repository...
- - Containing schematics or source code for a device with a USB interface...
- - Licensed under a recognized open source or open source hardware license. Your source code repository must contain a LICENSE file attesting to this fact.
+ - Containing modifiable PCB design files (schematics and layout) and/or source code for a device with a USB interface...
+ - Licensed under a recognized open source or open source hardware license. (See the [Open Source Hardware Definition](https://oshwa.org/resources/open-source-hardware-definition/) for details.) Your source code repository must contain a LICENSE file attesting to this fact.
 
 If your project involves both hardware and software, both need to be licensed under recognised OSS and OSHW licenses. If your project involves only one or the other, we may ask for further justification as to why you need a PID associated with your software project / development board instead of allowing end-users to request their own.