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

Remove 3rd party references in code and documentation #10666

Merged
merged 8 commits into from
Dec 3, 2024

Conversation

SuGlider
Copy link
Collaborator

@SuGlider SuGlider commented Nov 29, 2024

Description of Change

This PR changes documentation and examples to leave only those platforms that are officially supported by Espressif.

Pending changes to CI and scripts (e.g. renaming files) will be done in a separate PR to minimize breaking changes with existing projects.

Tests scenarios

CI Only

Related links

None

@SuGlider SuGlider self-assigned this Nov 29, 2024
@SuGlider SuGlider added Type: Documentation Issue pertains to Documentation of Arduino ESP32 Area: Tools & Build System Issue is related to tools and/or the build system documentation 📝 Solely about the documentation of the project. and removed documentation 📝 Solely about the documentation of the project. labels Nov 29, 2024
Copy link
Contributor

github-actions bot commented Nov 29, 2024

Warnings
⚠️

Some issues found for the commit messages in this PR:

  • the commit message "feat(support): toll and ci changes":
    • summary looks too short
  • the commit message "fix(support): left over in documentation.":
    • summary should not end with a period (full stop)

Please fix these commit messages - here are some basic tips:

  • follow Conventional Commits style
  • correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue
  • allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test
  • sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter
  • avoid Jira references in commit messages (unavailable/irrelevant for our customers)

TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).

⚠️ Please consider squashing your 8 commits (simplifying branch history).

👋 Hello SuGlider, we appreciate your contribution to this project!


Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 299e41b

@SuGlider SuGlider added this to the 3.0.8 milestone Nov 29, 2024
Copy link
Contributor

github-actions bot commented Nov 29, 2024

Test Results

 56 files   56 suites   4m 15s ⏱️
 21 tests  21 ✅ 0 💤 0 ❌
134 runs  134 ✅ 0 💤 0 ❌

Results for commit c03a574.

♻️ This comment has been updated with latest results.

@SuGlider
Copy link
Collaborator Author

SuGlider commented Nov 29, 2024

@lucasssvaz - Please review the CI Tools changes.
@me-no-dev - I'll also add a PR to Lib Builder.

@pedrominatel | @rftafas | @P-R-O-C-H-Y
These are all places that I found a referece to PIO in this repository.

@Jason2866
Copy link
Collaborator

@SuGlider @me-no-dev This PR removes support for Platformio / pioarduino
Why doing this?

@mathieucarbou
Copy link
Contributor

mathieucarbou commented Nov 30, 2024

Is there an equivalent alternative or backward compatibility "path" somewhere, or the motivation from expressif is really to break the daily dev / build of everyone using pioarduino ?

@SuGlider
Copy link
Collaborator Author

SuGlider commented Nov 30, 2024

This PR is under review. Please fell free to comment with a change request.

It is intended to remove Trade Marks, Brand Names and other reserved name in order to avoid legal issues.
It has been already done with NeoPixel (Adafruit Brand Name).

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keep this file and rename it to pioarduino-build.py any appearance of Platformio can be replaced with pioarduino if needed

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The deleted file is needed. Rename to pioarduino-build.py

Copy link
Collaborator Author

@SuGlider SuGlider Nov 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shall change the name of this file. What is the name of the Community Project?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've found PioArduino (https://github.com/pioarduino/platform-espressif32)
Is that the right repository, @Jason2866?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the right one. There is a Discord also if you need.

Copy link
Collaborator

@Jason2866 Jason2866 Nov 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SuGlider Well, if only trademarks and brands name appearing is the reason, please do the suggested changes without removing. Remove does kill the Open Source Project pioarduino. And yes, that is the correct repo.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What 3rd party software is there?

Copy link
Contributor

@mathieucarbou mathieucarbou Nov 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are also removing third party software.

Arduino Core for ESP32 is somewhat a component for that IDE.

Since when ? Arduino Core has always been the Arduino API on ESP32 chips, that's what has always been stated in the doc so far.

IDE compatibility has nothing to do with a framework and obviously a framework is not a component of an IDE: to build Arduino apps on ESP32 chips, one should not have to be forced to use Arduino IDE, which IMHO, is far from being the best available IDE out there for complex projects and it is about time Espressif recognise this fact. There are reasons why so many people are not using Arduino or ESP-IDF CLI. If it was so good, people would not bother using alternatives.

Some of your doc

So... Should the community understand that Espressif is actually changing the direction of the Arduino Core project completely so that it only becomes available from Arduino IDE ? Which, consequently would break all projects out there based on platformio or pioarduino and would have far more implications than just dropping support for PlatformIO ?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought @VojtechBartoska is the responsible project leader for espressif Arduino.
@rftafas I am interested what is your role regarding espressif Arduino?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vojtech is no longer part of Espressif team. He decided to venture for other endeavors. I've been the Product Manager since 2022.

There are 3 products here:

  1. The Arduino Core for ESP32, that is an 'add-on' to Arduino IDE, reason why even being a 3rd Party Software, Arduino IDE will be kept.
  2. The Arduino Component for ESP-IDF, which most people use along normal/usual ESP-IDF tools.
  3. The source code. People will use it however they please.

Third party software (i.e. not owned or 'managed' by Espressif) will be moved to a specific place in documentation, if/when using updated/supported Espressif software. Changes are on documentation for now, and we are only aiming the software (i.e. the source code) when it is related to trademarks (SuGlider examples). We are making it very clear about what is an Espressif Product and what is not.

Why?

Well... This very thread is an example in itself. The very statement that "Espressif will no longer support PlatformIO" is problematic in its core and it does break one PIO Labs trademark rules, making it appear that we own PlatformIO. We don't. PlatformIO is a commercial product, which is owned, supported and maintained by PIO Labs. We can't be the 'maintainers' or even the 'supporters' of it. It is NOT shared property. PIO Labs is the sole owner.

Simple warnings do not make a difference on defining this (they are there, yet, confusion remains). So, in order to be compliant to any third party projects and their trademarks, what is our product and so on, we are reviewing all content. This is the scope of this PR.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As for renaming to pioarduino-build.py, for example, AFAIK, PIOArduino isn't a trademark (yet). We might think this later, but it doesn't need to be now. Goal for now is documentation update.

@SuGlider
Copy link
Collaborator Author

@Jason2866 @mathieucarbou - We support community initiatives.
No danger or bad intentions to your initiative.
As I said, we shall not use PIO or PlatformIO terms anymore.

Let's focus on that. Please let's work together on it.

@Jason2866
Copy link
Collaborator

@rftafas Thx for the explanation and clarification. Good to hear to keep support for community pioarduino :-)

@SuGlider SuGlider changed the title Platform Support Change Remove 3rd party references in code and documentatin Dec 1, 2024
@lucasssvaz lucasssvaz changed the title Remove 3rd party references in code and documentatin Remove 3rd party references in code and documentation Dec 2, 2024
@TD-er
Copy link
Contributor

TD-er commented Dec 2, 2024

I don't understand it... There were numerous changes requested by @Jason2866, like not to delete files.
There are no new commits since and still the PR is approved???

What am I missing here?

@lucasssvaz
Copy link
Collaborator

@SuGlider @me-no-dev
Updated description to make intentions more clear and reverted changes to scripts as discussed in our internal meeting.

@lucasssvaz lucasssvaz marked this pull request as ready for review December 2, 2024 22:20
@SuGlider SuGlider added Status: Review needed Issue or PR is awaiting review and removed Area: Tools & Build System Issue is related to tools and/or the build system labels Dec 2, 2024
@SuGlider
Copy link
Collaborator Author

SuGlider commented Dec 2, 2024

I don't understand it... There were numerous changes requested by @Jason2866, like not to delete files. There are no new commits since and still the PR is approved???

What am I missing here?

No worries. @Jason2866 request is fine and executed.

@lucasssvaz lucasssvaz added Status: Pending Merge Pull Request is ready to be merged and removed Status: Review needed Issue or PR is awaiting review labels Dec 3, 2024
@SuGlider SuGlider merged commit c7022ca into espressif:master Dec 3, 2024
37 of 39 checks passed
Jason2866 added a commit to tasmota/arduino-esp32 that referenced this pull request Dec 11, 2024
* fix(zigbee): Increase timeout, commision again on failure + setScanDuration (espressif#10651)

* fix(zigbee): Increase timeout, commision again on failure
* fix(zigbee): Update library keywords

* feat(Matter): add new MatterColorLight endpoint (espressif#10654)

* feat(matter): adds Matter Color Light endpoint

* feat(matter): New example => Wifi Prov within Matter as alternative for wireless network provisioning (espressif#10658)

* feat(matter): Arduino WiFi Prov example for Matter

* feat(matter): Adds Matter Enhanced Color Light Endpoint (CW/WW/RGB) (espressif#10657)

* feat(matter): created enhanced color light new matter endpoint and example

* feat(matter): Adds a new Matter Endpoint: Generic Switch (smart button) (espressif#10662)

* feat(matter): adds new matter generic switch endpoint

* fix(matter): no need of arduino preferences here

* ci(pre-commit): Apply automatic fixes

---------

Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>

* BLECharacteristic optimization (espressif#10665)

* BLECharacteristic::notify() optimization

GeneralUtils::hexDump() doesn't output anything if the log level is not "VERBOSE". Additionally, it is very CPU intensive, even when it doesn't output anything. So it is much better to *not* call it at all if not needed. 

In a simple program which calls BLECharacteristic::notify() every 50 ms, the performance gain of this little optimization is 37% in release mode (-O3) and 57% in debug mode. 

Of course, the "#if ARDUHAL_LOG_LEVEL >= ARDUHAL_LOG_LEVEL_VERBOSE" guard could also be put inside the GeneralUtils::hexDump() function itself. But it's better to put it here also, as it is clearer (indicating a verbose log thing) and it allows to remove the "m_value.getValue().c_str()" call, which is in itself quite CPU intensive.

* BLECharacteristic optimization

Calls to BLEUtils::buildHexData() don't output anything when the log level is not "VERBOSE" or "DEBUG". As this function is quite CPU intensive, it is better to not call it when not needed.

* Remove 3rd party references in code and documentation (espressif#10666)

* feat(support): documentation adjustment
* feat(support): readme files, commentaries and examples
* fix(template): Fix Issue Report Template
-----------------------------
Co-authored-by: Lucas Saavedra Vaz <[email protected]>

* Tasmota changes

* optional Ethernet support (JL1101 driver added)
* esp-modem only esp32, esp32s2 and esp32s3
* remove `OpenThread`
* remove all BT BLE libraries
* remove zigbee
* remove SPIFFS
* remove Client Secure
* remove Provisioning
* remove TfLite, Insights and Rainmaker
* make GPIOViewer working see arendst/Tasmota@9696118
* remove FS log which is just littering

* refactor(uart): Refactor UART test to work with any number of UARTs (espressif#10593)

* refactor(uart): Refactor UART test to work with any number of UARTs

Co-authored-by: Rodrigo Garcia <[email protected]>

* fix(uart): Set CPU freq on ESP32

* ci(pre-commit): Apply automatic fixes

* fix(spelling): Fix codespell error

---------

Co-authored-by: Rodrigo Garcia <[email protected]>
Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>

* feat (Variants) Added custom boards variants GLYPH C3, GLYPHC6 & GLYPHH2 (espressif#10671)

* Added custom boards GLYPH C3, GLYPHC6 & GLYPHH2 based on ESP32C3, ESP32C6 & ESP32H2

* feat(Variants) : Added custom boards GLYPH C3, GLYPHC6 & GLYPHH2

Added custom boards variants from PCBCUPID - GLYPH C3, GLYPHC6 & GLYPHH2 based on ESP32C3, ESP32C6 & ESP32H2

* added required fix : moved the variants to end and fixed build.board

* ci(pre-commit): Apply automatic fixes

---------

Co-authored-by: srini <[email protected]>
Co-authored-by: Jan Procházka <[email protected]>
Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>

* feat(Zigbee): Recall bounded devices after reboot + IEEE address option for commands (espressif#10676)

* feat(zigbee): Recall bound devices after reboot

* fix(zigbee): Add missing locks + allow printBoundDevices to Serial

* fix(Zigbee): Add locks to temp sensor setReporting

* fix(Zigbee): remove unnecessary space in formatting

* fix(Zigbee): proper parameter in printBoundDevices

* feat(Zigbee): factory reset when removed from network

* fix(zigbee): Update comment

* fix(zigbee): fix serial and add missing factoryReset to example

* ci(pre-commit): Apply automatic fixes

---------

Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>

* ci(pre-commit): Bump hooks versions and fix leftover files (espressif#10680)

* update(hooks): Bump pre-commit hooks versions

* fix(formatting): Fix python script formatting

* fix(formatting): Fix leftover files on protected folders

* feat(Matter): Creates New Matter Fan Controller Endpoint (espressif#10691)

* feat(matter): creates new matter fan controller endpoint

* change(tools): Push generated binaries to PR

* ci(pre-commit): Add bash script formatter and linter (espressif#10681)

* ci(pre-commit): Add check for bash scripts

* fix(formatting): Fix bash scripts

* docs(pre-commit): Add info about the included hooks

* fix ESP32-U4WDH chip detection by ESP.getChipModel() (espressif#10696)

* fixes chip detection for ESP32-U4WDH

* fix(push): Re-comment unused code

* feat(matter): adds new Temperature Sensor Matter Endpoint (espressif#10698)

* feat(matter): adds new temperature sensor matter endpoint

* feat(matter): commentaries review and fixes

* feat(matter): commentaries review and fixes

* feat(matter): commentaries review and fixes

* feat(matter): commentaries review and fixes

* feat(matter): commentaries review and fixes

* feat(matter): commentaries review and fixes

* feat(matter): general commentaries and code review

* feat(matter): keeping arduino style for local variables (lower case)

* feat(matter): applies a generic temperature unit to the implementation and example

* fix(matter): fixed problem with begin(float) implementation

* fix(matter): fixed begin(float) initiallization

* feat(matter): updated matter temperature keywords with new api

* ci(pre-commit): Apply automatic fixes

* fix(matter): fixed code spell ci errors in matter temperature sensor

---------

Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>

* feat(chip): Add definition for BOOT_PIN for all chips (espressif#10700)

* feat(chip): Add definition for BOOT_PIN for all chips

For use in sketches as default button

* fix(core): Make BOOT_PIN static

* fix(hal): BOOT_PIN should always be defined

* feat(Matter): Adds New Matter Humidity Sensor Endpoint (espressif#10703)

* feat(matter): adds matter humidity sensor endpoint

* Update and rename platformio-build.py to pioarduino-build.py

* feat(matter_examples): apply boot button change to all examples (espressif#10702)

* feat(matter_examples): apply boot button change to all examples

* ci(tests): Re-enable UART test for P4

* Delete libraries/Matter directory

---------

Co-authored-by: Rodrigo Garcia <[email protected]>
Co-authored-by: Jan Procházka <[email protected]>
Co-authored-by: Me No Dev <[email protected]>
Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
Co-authored-by: Sylvain Quendez <[email protected]>
Co-authored-by: Lucas Saavedra Vaz <[email protected]>
Co-authored-by: PCB CUPID <[email protected]>
Co-authored-by: srini <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Michael Stegen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pending Merge Pull Request is ready to be merged Type: Documentation Issue pertains to Documentation of Arduino ESP32
Projects
Development

Successfully merging this pull request may close these issues.

9 participants