Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add PID for Raspberry Pi Pico USB I/O Board #35

Merged
merged 1 commit into from
Oct 14, 2021
Merged

Add PID for Raspberry Pi Pico USB I/O Board #35

merged 1 commit into from
Oct 14, 2021

Conversation

notro
Copy link
Contributor

@notro notro commented Oct 12, 2021

This project turns the Raspberry Pi Pico into a USB I/O Board using existing Linux drivers.

License: CC0

Since this license gives people freedom to use whatever license they want, I've made a note in the readme that the USB ID has to be used under a FOSS license.

https://github.com/notro/pico-usb-io-board

This project turns the Raspberry Pi Pico into a USB I/O Board
using existing Linux drivers.
@cuvoodoo
Copy link
Collaborator

Thanks for mentioning the FOSS license restriction.
The source files only have the SPDX-License-Identifier.
Normally the copyright author and date are also required for a license to be effective (to know when the copyright expires and be able to identify the current copyright holder).
But you are using the CC0 license, which is kind of putting it in public domain, so this information becomes irrelevant.
Reusing the PID/VID with the FOSS restriction you mentioned might reintroduce this requirement though.

Thus I am not sure about the outcome.
The easiest solution would be if you could add any author information, and the date the code has been written in in the source files.
If this bothers you, please let me know, and I will have a more detailed look into this issue (I haven't encountered it yet).

@notro
Copy link
Contributor Author

notro commented Oct 13, 2021

I've added this to all the files:

/*
 * Written in 2021 by Noralf Trønnes <noralf@tronnes.org>
 *
 * To the extent possible under law, the author(s) have dedicated all copyright and related and
 * neighboring rights to this software to the public domain worldwide. This software is
 * distributed without any warranty.
 *
 * You should have received a copy of the CC0 Public Domain Dedication along with this software.
 * If not, see <http://creativecommons.org/publicdomain/zero/1.0/>.
 */

Thanks for mentioning this, I think this is better.

Ref: May I apply CC0 to computer software? If so, is there a recommended implementation?

@cuvoodoo
Copy link
Collaborator

thanks a lot. that solves everything.

@cuvoodoo cuvoodoo merged commit bb67b8a into openmoko:master Oct 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants