Mercurial > prosody-modules

view CONTRIBUTING @ 4876:0f5f2d4475b9

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_http_xep227: Add support for import via APIs rather than direct store manipulation In particular this transitions PEP nodes and data to be imported via mod_pep's APIs, fixing issues with importing at runtime while PEP data may already be live in RAM. Next obvious candidate for this approach is rosters, so clients get immediate roster pushes and other special handling (such as emitting subscribes to reach the desired subscription state).
author Matthew Wild <mwild1@gmail.com>
date Tue, 18 Jan 2022 17:01:18 +0000
parents 0b7d65b4f576
children
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>