update licensing info for this fork of the community edition (#1)

* update submodule url

* update licensing info for this fork of the community edition

* restore source files headers

* Use the new VID:PID allocated to Librekeys by OpenMoko

* doc cleanup

Author: Lab-8916100448256

.github/FUNDING.yml

@@ -33,10 +33,7 @@ By checking the box below, you confirm ALL of the following:
 
 - You are the author of this contribution, or you have the right to contribute it.
 - You have read `CONTRIBUTING.md`.
-- You agree that this contribution may be merged, used, modified, and redistributed:
-  - under the AGPLv3 Community Edition, **and**
-  - under any proprietary / commercial / Enterprise editions of this project,
-    now or in the future.
+- You agree that this contribution may be merged, used, modified, and redistributed under the AGPLv3
 - You understand that submitting this PR does not create any support obligation,
   SLA, or guarantee of merge.
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,3 +1,3 @@
 [submodule "pico-keys-sdk"]
 	path = pico-keys-sdk
-	url = https://github.com/polhenarejos/pico-keys-sdk
+	url = ../pico-keys-sdk

.gitmodules

@@ -17,8 +17,8 @@
 
 cmake_minimum_required(VERSION 3.13)
 
-set(USB_VID 0x2E8A)
-set(USB_PID 0x10FE)
+set(USB_VID 0x1D50)
+set(USB_PID 0x619B)
 
 if(ESP_PLATFORM)
 set(DENABLE_POWER_ON_RESET 0)

CMakeLists.txt

@@ -2,28 +2,17 @@
 
 Thank you for your interest in contributing to this project.
 
-This repository is published in two forms:
-- a Community Edition released under AGPLv3, and
-- a proprietary / commercial / Enterprise Edition offered to organizations.
-
-To keep that model legally clean, we need to be explicit about how contributions can be used.
+This repository is published under AGPLv3
 
 By opening a pull request, you agree to all of the following:
 
 1. **You have the right to contribute this code.**
    You are either the original author of the contribution, or you have obtained the necessary rights/permissions to contribute it under these terms.
 
-2. **Dual licensing permission.**
+2. **Licensing.**
    You agree that your contribution may be:
    - merged into this repository, and
-   - used, copied, modified, sublicensed, and redistributed
-     - under the AGPLv3 Community Edition, and
-     - under any proprietary / commercial / Enterprise editions of this project,
-       now or in the future.
-
-   In other words: you are granting the project maintainer(s) the right to include
-   your contribution in both the open-source (AGPLv3) codebase and in closed-source /
-   commercially licensed builds, without any additional approval or payment.
+   - used, copied, modified, sublicensed, and redistributed under the AGPLv3
 
 3. **Attribution.**
    The maintainers may keep or add attribution lines such as
@@ -36,14 +25,6 @@ By opening a pull request, you agree to all of the following:
    service-level agreement, warranty, or guarantee that the contribution
    will be reviewed, merged, or maintained.
 
-5. **Potential rejection for business reasons.**
-   Features that fall under "Enterprise / Commercial" functionality
-   (e.g. multi-tenant provisioning at scale, centralized audit trails,
-   corporate policy enforcement, attestation/branding flows, key escrow / dual-control,
-   etc.) may be declined for the public AGPLv3 tree even if technically valid.
-   That is normal: some functionality is intentionally offered only
-   under commercial terms.
-
 If you are not comfortable with these terms, **do not open a pull request yet.**
 Instead, please open an Issue to start a discussion.
 
@@ -76,9 +57,6 @@ Please keep PRs focused (one logical change per PR if possible).
   - impact on existing flows / security model
   - any new dependencies
 
-This helps avoid doing a bunch of work on something that won't be accepted
-in the Community Edition.
-
 ### 4. Coding style / security posture
 - Aim for clarity and small, auditable changes. This code runs in places
   where secrets live.
@@ -91,7 +69,7 @@ in the Community Edition.
 - In the PR description, please include a short summary of what was changed and why.
 - At the bottom of the PR description, **copy/paste and confirm the licensing line below**:
 
-  > I confirm that I have read `CONTRIBUTING.md` and I agree that this contribution may be used under both the AGPLv3 Community Edition and any proprietary / commercial / Enterprise editions of this project, now or in the future.
+  > I confirm that I have read `CONTRIBUTING.md` and I agree to its terms
 
 A PR without that confirmation may be delayed or closed without merge.
 

CONTRIBUTING.md

@@ -1,3 +1,26 @@
+This project is licensed under the GNU Affero General Public License v3
+(AGPLv3). The full text of this license is reproduced at the bottom of
+this document.
+The copyright holders are indicated at the top of each file.
+
+The project is using the following libraries, sdk or portions of code:
+- mdebtls, licensed under Apache-2.0 and GPL-2.0-or-later licenses,
+  https://github.com/Mbed-TLS/mbedtls
+- tinyUSB, licensed under the MIT License,
+  https://github.com/hathach/tinyusb
+- tinycbor, licensed under the MIT license,
+  https://github.com/intel/tinycbor
+- mlkem-native, the Apache-2.0 license OR the ISC license OR the MIT
+  license, https://github.com/pq-code-package/mlkem-native
+- USB CCID from Raspberry Pi (Trading) Ltd, licensed under the
+  BSD-3-Clause license,
+- Raspberry Pi Pico SDK, licensed under BSD 3-Clause "New" or "Revised"
+  License, https://github.com/raspberrypi/pico-sdk
+- Espressif IoT Development Framework (ESP-IDF), licensed under Apache
+  License Version 2.0, https://github.com/espressif/esp-idf
+
+________________________________________________________________________
+
                     GNU AFFERO GENERAL PUBLIC LICENSE
                        Version 3, 19 November 2007
 
@@ -658,4 +681,4 @@ specific requirements.
   You should also get your employer (if you work as a programmer) or school,
 if any, to sign a "copyright disclaimer" for the program, if necessary.
 For more information on this, and how to apply and follow the GNU AGPL, see
-<https://www.gnu.org/licenses/>.
+<https://www.gnu.org/licenses/>.