Code Bounty Program

Get paid to contribute to Open Source!

The Machi-Systems engineering team is small, and we’re always looking for new contributors to our Open Source codebases. Our Bounty program is an opportunity to solve issues that could be neglected otherwise. Contributors who fix these issues will be rewarded financially.


With money, but not only about money

Our bounty program is about creating opportunities for our community to contribute to Machi-Systems, to make it their own. It also gives us an opportunity to get to know developers who we could potentially work with more in the future. We celebrate making open-source contributions more sustainable by payingbut money alone shouldn’t be the primary motivation for participation.

No compromise on quality

We’re not able to accept Pull Requests that aren’t completed to a high standard in a reasonable timeframe. Please only pick up bounties that you are confident you can complete at your current knowledge and skill level. We will not accept Pull Requests or pay bounties for code that’s not up to the standard we need to maintain for the Collectives who rely on this platform.

Our dev team is happy to answer questions and provide some limited support, but we don’t have the capacity to mentor junior developers through the bounty program.

For general guidelines about what’s expected in the code, see more info here.

How it works

For reference, until July 2021, we used the following model:

  • $100: minimal or unknown complexity
  • $200: simple complexity
  • $500: medium complexity

But since then we plan to move to a more flexible one. Based on the importance of the issue and its complexity, we attach a bounty between $100 and $1000 to the ticket.

We want to attract quality contributions. The issue will only be considered complete and approved for payment if the Pull Request is merged by a Machi-System Core Developer.

Workflow for Bounty Program Contributors

  1. Search for issues with attached bounties:
  2. Express interest by commenting on the issue and asking to be assigned
  3. Open a Pull Request and ask for feedback and review
  4. Incorporate feedback from Core Developers, if applicable
  5. PR is reviewed, approved, and merged by a Core Developer
  6. Get paid:
    • If you can issue an invoice, submit it as an expense to Machi-Systems Engineering
    • If you can’t issue an invoice, ask to be rewarded with a Gift Card

See more info about getting paid through Machi-Systems

Workflow for Core Contributors

  1. Make sure the issue is understandable for newcomers and expectations are clearly set
  2. Tag issues with the “bounty” label and amount (e.g. “$100”)
  3. Add a comment with a basic explanation of the Bounty process and link to BOUNTY.mdA $100 bounty was attached to this issue. Anyone submitting a Pull Request will be rewarded with $100 after it is reviewed, accepted, and merged. More info
  4. Make sure the issue is understandable for newcomers and expectations are clearly set

Contributor Ladder

  1. First-Time Contributors
    • Not part of the Machi-Systems GitHub organization
    • Fork our projects on GitHub and push changes on their forks
    • Have access to minimal or simple complexity issues
    • Should comment on bounty issues to get assigned (limited to one at a time)
  2. Contributors (at least 1 completed issue)
    • Added to the “Contributors” group in the Machi-Systems GitHub organization
    • Can push branches to the Machi-Systems repositories
    • Have access to minimal, simple, or medium complexity issues
    • Can assign themselves bounty issues (limited to one at a time)
  3. Recurring Contributors (3 or more completed issues)
    • Added to the “Recurring Contributors” group in the Machi-Systems GitHub organization
    • Can assign themselves two bounty issues at a time
  4. Confirmed Contributors (3 or more completed issues including at least 2 with medium complexity)
    • Added to the “Confirmed Contributors” group on the Machi-Systems GitHub organization
    • Become candidates to work on complex issues or projects on a negotiable per-project or hourly rate

Code Bounty

List of active code bounties

Elementor JS On Click Method

Code Bounty is up for grabs here:

Recommended Method:

Method Used: Also see:

Added link to Elementor Image Box “#ms-tawk-chat”

var a = document.querySelector('a[href="#ms-tawk-chat"]');
if (a) {
  a.setAttribute('href', 'javascript:void(Tawk_API.toggle())')

GF Shortcode produced anomalous styles in header of Astra Theme

Code Bounty is up for grabs here:

Striping the button of its default style and just let it inherit the parent’s style, leave the class attribute empty, like this:

<!-- See Menu and Order Example Shortcode -->
[restaurant-menu-and-ordering-ssm class="" 

But, produces anomalous styles, whereas html does not:

<!-- See Menu and Order Example HTML--> 
<span class="" data-glf-cuid="" data-glf-ruid= 
"9623cd8f-bd4a-4f42-ac20-0a14faf7b88d" data-location= 
"9623cd8f-bd4a-4f42-ac20-0a14faf7b88d" id="glfButton1" 
style="">Order Now! </span>


We hope you’ve found this doc useful. Is anything missing? If so, email us at and we’ll get it sorted for you.




Questions? Send us a note and we’ll get right back to you.

Was this article helpful?