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.
#pgpday User Profile Extension
The purpose of the bounty is to add features to postActiv, specifically, to add additional profile fields to a user.
It consists of four programming tasks:
- Devising a means by which arbitrary profile fields can be added to postActiv via a plugin.
- Providing the database interface for these fields.
- Adding to the users setting page a means to edit these fields as desired.
- Patching display of these fields into the Qvitter plugin.
Ideally, this would be extensible for any future arbitrary fields. Please use "Public email" (that is displayed on the profile if desired), "XMPP" and "PGP Key Fingerprint" as the test fields. Provided reference implementation must include this.
A plugin exists already that you can rewrite for arbitrary fields that may speed this task:
Payment: 20$ via Paypal (you must have a paypal 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
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:
- We get back to you with what we think of the bounty abstract - if we think its okay, if we'd want changes (knowing the codebase, limitations, practicalities, and other concerns), or if we're not interested. If we need revisions, go back to step 1 :)
- Once the abstract is approved, you send us the money via either Paypal or Bitcoin
- Once the money is received it is held by us, and the bounty is posted on that page.
- When the bounty is claimed we review the submission ourselves, and then with yourself, to see if it fulfills your abstract.
- Any revisions are sent back to the claimant.
- Once any and all revisions are complete, the bounty is paid out, and we're done