👷‍♂️ Good first issues, Bounties 💰 & Help wanted 👷‍♀️

[Echolon]

To all contributors

Thank you for considering to contribute to Converse!

Please see the Converse Documentation, particularly the Development Documentation.

Good first issues

If you're new to the project, it might make sense to to look at the issues tagged with good first issue.

Good first issues, ranked by upvotes

Bounties

Some select issues have a bounty label, which means that a bounty of $100 will be paid out to whoever fixes the issue.

Rules regarding bounties:

• Anyone can work on a bounty ticket.
• Don't ask for a bounty ticket to be assigned to you.
• Bounties can be paid out via crypto (Bitcoin, Ethereum, Monero) or bank transfers to US or EU banks.

To qualify for a bounty, your pull request must:

• fix the issue to the satisfaction of the reviewers
• include tests to verify your changes
• include relevant documentation if applicable (e.g. for a new config setting)
• be merged to the master branch

See all Bounty issues, ranked by upvotes

The funds for the bounties come from our generous sponsors. If you'd like to contribute funds for bounties, please consider becoming a sponsor.

XEP Requests

The XMPP protocol is extensible and we do this with XMPP Extension Proposals (XEPs).

Here is a list of tickets requesting support for XEPs in Converse.

[Echolon]

@jcbrand I pinned this one - let me know if you don't like this.

[Echolon]

@jcbrand this is already in the top ten popular traffic pages in this repository: https://github.com/conversejs/converse.js/graphs/traffic
So may I can add more useful guidance

[jcbrand]

Yeah please do @Echolon 👍

[newfadel]

For tackling frontend issues in Converse.js, leveraging browser developer tools is key. You can often identify UI problems or JavaScript errors by inspecting elements, checking the console for errors, and using breakpoints in the Sources tab. This is especially helpful for understanding the flow and state within the application. 😊