Code:
Title: PIVX Dev Funding (Aug-Oct 2019)
Name: PIVX-Dev-AugOct2019
Term: 3 Cycles
Cycle Amnt: 27500 PIV
Total Amnt: 82500 PIV
Author: Fuzzbawls
Receiver: Fuzzbawls
Address: DSzmDVFAMAUELrCMkRVYUgRpSmwVFwEkHa
Created: 2019-07-19
Status: Active
Vote Hash: 6646b160b0ffddc6e7ac4aeea7c562639af7c67c9a1df233af667ef22ba4ab0b
Abstract
This document outlines the funding for the PIVX Core Dev Team, including who is to be paid, their position, and the amount they are expected to be paid each cycle. Additionally, new term and format commitments for all future Core Dev Team proposals are included.
Term and Format Commitment
Given the fluctuations in PIVX and BTC prices, and taking into consideration that people’s schedules can change, or a change number of people intended to be covered by this document, the PIVX Core Dev Team will only be submitting proposals with a maximum term of three (3) cycles.
This means more frequent proposal submissions, and more responsibility from voters to actually vote, but also allows for any changes to the team’s structure, members, positions, or duties to be assessed and formalized more frequently.
The format for these proposals will be as follows:
- Each member of the team will be listed
- Their position will be listed
- Their expected monthly salary will be listed
- Any member notes, changes, exceptions will be listed
- Extra funds (if any) will be rationalized
PIVX Core Dev Responsibilities
All Core Devs are expected to participate in the issue/pull request review process, as well as attend weekly internal team meetings with reliable frequency. Individual salaries are subject to internal adjustment and rebalancing if deemed appropriate at the time of salary payout.
The following software projects fall under the care and responsibility of the PIVX Core Dev team:
PIVX Core Wallet | https://github.com/pivx-project/pivx |
SPMT | https://github.com/pivx-project/spmt |
PET4L | https://github.com/pivx-project/pet4l |
PIVX iOS Wallet | https://github.com/pivx-project/pivx-ios |
PIVX Android Wallet | https://github.com/pivx-project/pivx-android |
PIVXj | https://github.com/pivx-project/pivxj |
PIVX Light Desktop Wallet | Private |
PIVX Core Dev Funds Allotment
The PIVX Core Dev Team is proposing the following funding be made by the DAO’s budget:
- Fuzzbawls - Core Dev & Team Manager (6000 PIV)
- Furszy - Core Dev (6000 PIV)
- Random Zebra - Core Dev (6000 PIV)
- Warrows - Core Dev (6000 PIV)
- Mrs-X - Core Dev (2000 PIV)
Total Per Cycle: 27500 PIV
Outside Developer Funding Pool
We recognize that contributions from non-core developers can be beneficial and, as mentioned above, are requesting an allotment of 1500 PIV per cycle to help incentivize such outside contributions as tips.
Post-contribution discussion and review is done internally to determine if a contribution warrants a monetary tip, as well as an appropriate amount. Contributors are encouraged to join the PIVX-Dev Discord server (https://discord.gg/ra3atpD).
Donations and Receiving of Additional Funds
Any funds received by the proposal payout address from any source other than the PIVX network’s in-built budget distribution system will be considered as donations to be distributed to one or more of the above listed person(s), reserved in the outside contributors pool, or a combination thereof at our sole discretion.
The PIVX Core Dev Team reserves the right to decide for ourselves the area(s) of focus that may or may not be added due to an increase in funds received, as well as the priority of any such added areas of focus.
Notable Changes
Changes since the last proposal (PIVX-Dev-MayJul2019):
- Added section detailing the software projects falling under the care and responsibility of the PIVX Core Dev Team.
- Removed Blondfrogs (previously inactive) due to extended time constraints. We wish him well and hope to see future contributions from him as his time allows.
- Added section expanding on the purpose and process for the outside dev funding pool.
- Added section detailing the receiving of donation funds.
To vote yes:
mnbudgetvote many 6646b160b0ffddc6e7ac4aeea7c562639af7c67c9a1df233af667ef22ba4ab0b yes
To vote no:
mnbudgetvote many 6646b160b0ffddc6e7ac4aeea7c562639af7c67c9a1df233af667ef22ba4ab0b no
Last edited: