sopel-meetbot
The meetbot plugin formerly shipped with Sopel prior to version 8.0.
Note: Not super actively maintained. Open an issue if you're interested in taking over this particular piece of the project!
Installation
Place meetbot.py into ~/.sopel/plugins/
Configuration
[meetbot]
meeting_log_path = ~/www/meetings
# Path to where the plugin should store meeting logs.
# Intended to be served by a webserver (Apache, Nginx, etc.)
meeting_log_baseurl = https://example.com/~sopel/meetings
# Where the above path can be accessed via HTTP(S)
# (omit trailing slash)
# This will be used to build links to the finished meeting logs.
Special thanks
All contributors to the original meetbot plugin for
Sopel.
Changelog
1.1.0
Changed:
- Require Sopel 8.0+ (#5)
Fixed:
- Sopel 8 moved built-in plugins from
.modulesto.builtins(#6)
Meta:
- Modernize package layout & metadata (#5)
- Automate PyPI releases using Trusted Publishing
1.0.0
Initial release of meetbot.py from Sopel 7.1.x as its own package.
Metadata
Release files for sopel-meetbot 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sopel_meetbot-1.1.0.tar.gz | 8.2 kB | With provenance | Details for sopel_meetbot-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sopel_meetbot-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for sopel_meetbot-1.1.0-py3-none-any.whl |
Total release size: 16.0 kB
Release files / sopel_meetbot-1.1.0.tar.gz
| Download URL | sopel_meetbot-1.1.0.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6676e26a17190b24af16095d181ada173f5712f893edc19e30e0a12602d5d2d6
|
|
BLAKE2b-256 checksum How to use checksums |
c13dde86d08be77e96e667e00165e58929082213dd01547d4d3c1348bdbab40b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 14, 2025.
Transparency logRelease files / sopel_meetbot-1.1.0-py3-none-any.whl
| Download URL | sopel_meetbot-1.1.0-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d54be6d27e6c66800b9d2ac6b8a5887fcf16b1f17006e7f05110c9d2219a610
|
|
BLAKE2b-256 checksum How to use checksums |
9f79cfbdbc8ee7467beda308a9d61590cc33046fb1f50fbf55cef0b07712495b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 14, 2025.
Transparency logSecurity for sopel-meetbot 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for sopel_meetbot-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 14, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.