Title: PIVX Dev Funding (Oct-Dec 2020) Name: PIVX-Dev-OctDec2020 Term: 3 Cycles Cycle Amnt: 25000 PIV Total Amnt: 75000 PIV Author: Fuzzbawls Receiver: Fuzzbawls Address: DSzmDVFAMAUELrCMkRVYUgRpSmwVFwEkHa Created: 2020-09-17 Status: Active Vote Hash: e66af24c75a2dbd11f956965a4022f71ffddeea9105098779ee8ba5a9dda7898
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 of the 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 re-balancing 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|
|PIVX iOS Wallet||https://github.com/pivx-project/pivx-ios|
|PIVX Android Wallet||https://github.com/pivx-project/pivx-android|
|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 (7000 PIV)
- Furszy - Core Dev (9000 PIV)
- Random Zebra - Core Dev (9000 PIV)
We have accumulated a suitable amount of PIV from past cycles for the purpose of paying community developers for their submissions, which have been few and far between. Therefore, we are temporarily suspending our asking of
additional budget funds so as to free up more of the budget for other proposals. Any contributions that merit a payout will come from the existing fund pool, and this additional asking will resume at a later date.
Total Per Cycle: 25000 PIV
Community Developer Funding Pool
We recognize that contributions from non-core developers can be beneficial, and have accumulated a sufficient amount of PIV from past proposals 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).
Community developer contributions are organized and filed under a GitHub project: https://github.com/PIVX-Project/PIVX/projects/26
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 community 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.
Changes since the last proposal (PIVX-Dev-JulAug2020):
- Reduced budget asking amount by 2500 PIV per cycle. Temporary suspension of asking for monthly community dev funds.
To vote yes:
mnbudgetvote many e66af24c75a2dbd11f956965a4022f71ffddeea9105098779ee8ba5a9dda7898 yes
To vote no:
mnbudgetvote many e66af24c75a2dbd11f956965a4022f71ffddeea9105098779ee8ba5a9dda7898 no