Community Bounties

The developers of postActiv have only so many hours in the day, so both they and the community use bounties to help stimulate development of features that we'd like but don't have time for, or aren't a high priority but someone would like to see sooner rather than later. These can be both bug fixes or new features and functionalities, and anyone who follows the contribution guidelines can submit them. The tendering of community bounties is handled by Maiyannah Bishop, the lead developer, unless specified otherwise.

A Note About Bounties

At all stages of the process - accepting bounties, posting them, accepting and reviewing bounty claims, and payouts, we reserve the right of final decision as to whether the code is something we want in the codebase. Before you contribute, either a bounty to be fulfilled or by claiming a bounty, please make sure you're okay with this. We might not end up accepting the exact way you'd want something done, or you might hack up the code and we decide it's not up to snuff. It can happen, though we try to be considerate of people's time and suggest revisions rather than flat reject something. Nonetheless, keep this in mind before contributing.

Also, depending on financial situations at a given time, renumeration might not be made until the next Patreon cycle.

Current Bounties

The following bounties are open for people to submit merge requests for our consideration:

Zot Federation module

This is an ambitious bounty and likewise there's a fair reward attached. It should be noted that payout will only be tendered for a completed bounty. Payouts for a completed bounty may be delayed by the testing required.

This bounty is for implementing a working federation module for the Zot protocol. The Zot protocol is documented here. The module should be named FederateZot and MUST NOT override any OStatus methods - OStatus federation should still work when FederateZot is enabled. Existing Federation events should be sufficient to hook the required behaviour. Zot data should be mapped as closely as possible to the existing database schema. Where not possible, new data should be placed in a "zot*" table - for example, a generalist zot table would be just "zot", if an additional database table was needed for post-specific information, then it would be in zotnotice, a zot profile in zotprofile, and so forth.

At the bare minimum it should have the following functionality:

Desirable but not a strict requirement would be:

Payment: 150$ via Paypal (you will require a Paypal account for renumeration)

How to Fulfill a Bounty

When writing code for the bounty, remember that you can always ping the contact information given to get information about specifics. Please also keep in mind though that if we had the time to do the grunt work ourselves we would just do it! A bounty is meant to be a financial incentive for the development of code, and try to contact us about the design process if you need guidance, not the implementation process.

With that in mind, review the following three documents to ensure your patch meets our standards:

If you think it does, then you will need to submit a merge request at our gitlab repo at git.postactiv.com/postActiv/postActiv

Then, assuming the merge request is accepted, contact maiyannah.bishop@postactiv.com with a link to the accepted merge request. She will review the code again (along with the b) and if it all looks good she will disburse the payment. Make sure you provide a paypal account or bitcoin wallet address in the email so she can!

How to Offer a Bounty

If you are willing to offer money to a bounty, you will need two things: the money, and an abstract of the feature you'd like added to postActiv (the more detailed the better), or bug you'd like fixed. The process goes like this: