The Amplenote Plugin Bounty Program is a way for developers to earn money by building plugins for Amplenote. By participating in the program, you agree to the following terms and conditions:
Plugin Completion. For a plugin author to be eligible to receive a bounty, the plugin must be completed and published to the Amplenote Plugin Directory.
Code Quality. For plugins that perform non-trivial modifications to a user's notes, the plugin creator must test the functionality of the plugin. The plugin creator has to include a file or directory in their repository that contains a test suite covering at least the "actions" of the plugins that modify note data. Tests should be explicit about what scenarios they validate (for example by using comments inside the file). The Amplenote team reserves the right to refuse rewarding plugin work if the test coverage is not deemed sufficient. For an example of adequate plugin tests, see the AI plugin tests.
Author Must Reside in Eligible Country. Eligibility for the program is limited to developers in countries where Amplenote can legally pay out bounties. If you're not sure where the USA can legally send payments to your country, please inquire with support@amplenote.com and we can help you research it.
Plugin Quality. Plugins must be of high quality and provide value to the Amplenote user base. They must not suffer from bugs, and if users mention bugs in the comments, they should be addressed within a couple weeks. Amplenote reserves the right to reject plugins that do not meet our quality standards, or fail to fully satisfy the bounty plugin description.
Public GitHub repository. Plugin creator commits the most recent version of the code to a public repository on github.com, which is linked to from the Amplenote plugin page. Plugin creator is responsible for always keeping the public repository and the plugin page in sync.
Bounty Amount. The bounty amount for a plugin is determined by Amplenote and is subject to change at any time.
Payment. Payments will be made via PayPal, and the plugin author is responsible for any fees associated with receiving the payment. Amplenote will not be responsible for any fees associated with receiving the payment. Author must be able to receive payments via Paypal unless arranged in advance via support@amplenote.com. Payments will be disseminated within 30 days of the plugin being published to the Amplenote Plugin Directory, after the author contacts hello@amplenote.com with an invoice for the bounty amount, which should include a valid Paypal address we can use to send payment to.
Taxes. The plugin author is responsible for any taxes associated with the bounty payment.
First Come, First Serve. If multiple authors submit the same plugin, the bounty will be awarded to the first author to submit a quality, consistently functional and bug-free plugin.
Licensed for Free Use and Modification. After a plugin has been published, it must be licensed under the MIT license or another open-source license that allows for free modification and distribution. If it is going to receive a bounty payment, it must not charge users for its functionality (though if it integrates with a third-party that does charge, that's OK).
No Royalties. The author will not receive royalties for the plugin after the bounty has been paid. No further implicit or explicit expectation of payment is implied by the one-time bounty payment.
Availability/Persistence. Amplenote reserves the right to keep the plugin available in the Amplenote Plugin Directory in perpetuity. The author pledges not to destroy their Amplenote account or removal their plugin code for 3 years (36 months) after receiving a bounty.
Include Usage Video. Plugin creator must create a short video recording (between 1-5 minutes) and share it with team Amplenote (hello@amplenote.com). The video recording must explain the main features of the plugin and how to use them. The video must be made public either by the creator, or by convening to upload it to Amplenote's official YouTube channel. The plugin page must link to the video.
Include Code Overview Video. Plugin creator must create a short video recording (between 1-5 minutes) where they describe the structure of the plugin's repository, document the main behavior of the plugin and explain how other people can contribute to the repository.
Changes to Terms. Amplenote reserves the right to change these terms and conditions at any time.
linkNotifying Others of Intent
If you plan to work on a plugin that will take weeks or months to complete, you can email support@amplenote.com with a description of which plugin you intend to work on, and when you expect to publish it. If your claim is deemed credible by support staff, we will add a note to the plugin's description indicating that you are working on it to reduce the likelihood that others may duplicate your work.
Notifying Amplenote about starting work on a plugin is not required, and if another author submits a quality version of the same plugin sooner than you, they will be awarded the bounty.
linkSubmitting a Bounty Claim
When you have published a bounty plugin to the Amplenote Plugin Directory, you can submit a bounty claim by emailing support@amplenote.com with a link to the plugin. Amplenote will review the plugin and determine if it meets the requirements for a bounty. If it does, we will send you a PayPal payment within 30 days.