prosody-modules
c217f4edfc4f
CONTRIBUTING

Find changesets by keywords by author, files, the commit message, revision number or hash, or revset expression.

Software / code / prosody-modules

File

CONTRIBUTING @ 5671:c217f4edfc4f

misc/mtail: Start of an mtail config Stashing it here in case anyone wants to continue working on it. Currently it's only counting log messages by level. Due to the permissions set by systemd on Prosody logs, mtail never managed to start correctly until permissions were manually relaxed.
author Kim Alvefur <zash@zash.se>
date Sun, 17 Sep 2023 13:36:30 +0200
parent 1809:0b7d65b4f576
line wrap: on
line source

Contributing
============

Guidelines for developers
-------------------------

-   Each module should be contained in a folder of its name (e.g.\
     `mod_ping/mod_ping.lua`)
-   Each module should have a `README.markdown` page in their folder
    with a description, usage, configuration and todo sections (feel
    free to copy an existing one as a template)
-   Commit messages should begin with the name of the plugin they are
    for (e.g. `mod_ping: Set correct namespace on pongs`)

Instructions on cloning the repository are at
<https://prosody.im/doc/installing_modules#prosody-modules>