adminandClaude Opus 5
79843aa2ae
Erster Stand der Hintergrundprozesse, die auf der Synology unter /volume1/homes/wagner/SolarManager laufen: der Manager selbst, die Sammler je Geraet, die MQTT-Bruecke, der Wecker und - neu hinzugezogen - der AutoAction-Runner, der als Hintergrundprozess hierher gehoert und nicht ins Web-Verzeichnis. Zugangsdaten stehen nicht mehr im Quelltext, sondern in config.ini, die nicht mit eingecheckt wird. Vorlage ist config.ini.example, gelesen wird sie von konfig.py. Betroffen waren solarManager.py (Datenbank und Wattpilot), zeit.py, gatherWaterData.py, wecker.py und skoda_testdaten.py, das sich das Passwort bisher aus dem Quelltext eines anderen Moduls herausgesucht hat. Die Kia-Anbindung ist mit dem Fahrzeug entfallen: kiaTest.py, gatherCarData.py und hyundai_kia_connect_api sind nicht mehr dabei, ebenso gatherInverterData.py, auf das nur noch eine auskommentierte Zeile zeigte. Die mitgelieferten Bibliotheken bleiben im Repository - die NAS hat kein pip, sie muessen neben den Skripten liegen. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
115 lines
5.7 KiB
Markdown
115 lines
5.7 KiB
Markdown
# Contributing to Paho
|
|
|
|
Thanks for your interest in this project!
|
|
|
|
You can contribute bugfixes and new features by sending pull requests through GitHub.
|
|
|
|
## Legal
|
|
|
|
In order for your contribution to be accepted, it must comply with the Eclipse Foundation IP policy.
|
|
|
|
Please read the [Eclipse Foundation policy on accepting contributions via Git](http://wiki.eclipse.org/Development_Resources/Contributing_via_Git).
|
|
|
|
1. Sign the [Eclipse CLA](http://www.eclipse.org/legal/CLA.php)
|
|
1. Register for an Eclipse Foundation User ID. You can register [here](https://dev.eclipse.org/site_login/createaccount.php).
|
|
2. Log into the [Projects Portal](https://projects.eclipse.org/), and click on the '[Eclipse CLA](https://projects.eclipse.org/user/sign/cla)' link.
|
|
2. Go to your [account settings](https://dev.eclipse.org/site_login/myaccount.php#open_tab_accountsettings) and add your GitHub username to your account.
|
|
3. Make sure that you _sign-off_ your Git commits in the following format:
|
|
``` Signed-off-by: John Smith <johnsmith@nowhere.com> ``` This is usually at the bottom of the commit message. You can automate this by adding the '-s' flag when you make the commits. e.g. ```git commit -s -m "Adding a cool feature"```
|
|
4. Ensure that the email address that you make your commits with is the same one you used to sign up to the Eclipse Foundation website with.
|
|
|
|
## Contributing a change
|
|
|
|
1. [Fork the repository on GitHub](https://github.com/eclipse/paho.mqtt.python/fork)
|
|
2. Clone the forked repository onto your computer: ``` git clone
|
|
https://github.com/<your username>/paho.mqtt.python.git ```
|
|
3. Most changes will go to branch ``master``. This include both bug fixes and
|
|
new features. Bug fixes are committed to ``master`` and if required,
|
|
cherry-picked to the release branch.
|
|
|
|
The only changes that goes directly to the release branch (``1.4``,
|
|
``1.5``, ...) are bug fixes that does not apply to ``master`` (e.g. because
|
|
there are fixed on master by a refactoring, or any other huge change we do
|
|
not want to cherry-pick to the release branch).
|
|
4. Create a new branch from the latest ```master``` branch
|
|
with ```git checkout -b YOUR_BRANCH_NAME origin/master```
|
|
5. Make your changes
|
|
6. Ensure that all new and existing tests pass by running ```tox```
|
|
7. Commit the changes into the branch: ``` git commit -s ``` Make sure that
|
|
your commit message is meaningful and describes your changes correctly.
|
|
8. If you have a lot of commits for the change, squash them into a single / few
|
|
commits.
|
|
9. Push the changes in your branch to your forked repository.
|
|
10. Finally, go to
|
|
[https://github.com/eclipse/paho.mqtt.python](https://github.com/eclipse/paho.mqtt.python)
|
|
and create a pull request from your "YOUR_BRANCH_NAME" branch to the
|
|
``master`` (or release branch if applicable) to request review and
|
|
merge of the commits in your pushed branch.
|
|
|
|
|
|
What happens next depends on the content of the patch. If it is 100% authored
|
|
by the contributor and is less than 1000 lines (and meets the needs of the
|
|
project), then it can be pulled into the main repository. If not, more steps
|
|
are required. These are detailed in the
|
|
[legal process poster](http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf).
|
|
|
|
|
|
|
|
## Developer resources:
|
|
|
|
|
|
Information regarding source code management, builds, coding standards, and
|
|
more.
|
|
|
|
- [https://projects.eclipse.org/projects/iot.paho/developer](https://projects.eclipse.org/projects/iot.paho/developer)
|
|
|
|
Contact:
|
|
--------
|
|
|
|
Contact the project developers via the project's development
|
|
[mailing list](https://dev.eclipse.org/mailman/listinfo/paho-dev).
|
|
|
|
Search for bugs:
|
|
----------------
|
|
|
|
This project uses [Github](https://github.com/eclipse/paho.mqtt.python/issues)
|
|
to track ongoing development and issues.
|
|
|
|
Create a new bug:
|
|
-----------------
|
|
|
|
Be sure to search for existing bugs before you create another one. Remember
|
|
that contributions are always welcome!
|
|
|
|
- [Create new Paho bug](https://github.com/eclipse/paho.mqtt.python/issues)
|
|
|
|
|
|
## Committer resources:
|
|
|
|
Making a release
|
|
----------------
|
|
|
|
The process to make a release is the following:
|
|
* Update the Changelog with the release version and date. Ensure it's up-to-date with latest fixes & PRs merged.
|
|
* Make sure test pass, check that Github actions are green.
|
|
* Check that documentation build (`cd docs; make html`)
|
|
* Bump the version number in ``paho/mqtt/__init__.py``, commit the change.
|
|
* Make a dry-run of build:
|
|
* Build using hatch: ``python -m hatch build``
|
|
* Check with twine for common errors: ``python -m twine check dist/*``
|
|
* Try uploading it to testpypi: ``python3 -m twine upload --repository testpypi dist/*``
|
|
* Do a GPG signed tag (assuming your GPG is correctly configured, it's ``git tag -s -m "Version 1.2.3" v1.2.3``)
|
|
* Push the commit and it's tag to Github
|
|
* Make sure your git is clean, especially the ``dist/`` folder.
|
|
* Build a release: ``python -m hatch build``
|
|
* You can also get the latest build from Github action. It should be identical to your local build:
|
|
https://github.com/eclipse/paho.mqtt.python/actions/workflows/build.yml?query=branch%3Amaster
|
|
* Then upload the dist file, you can follow instruction on https://packaging.python.org/en/latest/tutorials/packaging-projects/#uploading-the-distribution-archives
|
|
It should mostly be ``python -m twine upload dist/*``
|
|
* Create a release on Github, copy-pasting the release note from Changelog.
|
|
* Build and publish the documentation
|
|
* To build the documentation, run `make clean html` in `docs` folder
|
|
* Copy `_build/html/` to https://github.com/eclipse/paho-website/tree/master/files/paho.mqtt.python/html
|
|
* Announce the release on the Mailing list.
|
|
* To allow installing from a git clone, update the version in ``paho/mqtt/__init__.py`` to next number WITH .dev0 (example ``1.2.3.dev0``)
|