Git Guild Charter (Draft) - GitGuild/gitguild_website GitHub Wiki
Git Guild Charter
This Charter is an agreement voluntarily made to work collaboratively on open source projects. Signers are real people, with real skills and value to offer to the open source community, and agree to abide by the standards and contracts described within this Charter, and sub-documents. Such agreement is made using PGP (Pretty Good Privacy) and tools will be made available in the future to assist with this process.
Membership
The basic membership requirement is to register your GPG identity with the Guild or an official sub-guild, sign the Charter, and have your signature merged by the maintainer.
Seniority
A capitalist meritocracy, seniority in the Git Guild will be quantified by XGG earned. Because XGG has real market value, it is a good proxy for the value the member has provided to others. Furthermore, due to the peer review process, every unit of that value had to meet the standards of the Guild. This also encourages long term commitment to projects and identities.
Rank
Rank is determined purely on seniority, and comes with agreed upon responsibilities and capabilities. For example, higher ranking members may be able to take on harder tasks, or be called upon to review the work of others.
| Rank | Minimum Requirement | Maximum Requirement |
|---|---|---|
| Member | Sign Charter | 1,000 XGG |
| Apprentice | 1,000 XGG | 10,000 XGG |
| Journeyers | 10,000 XGG | 100,000 XGG |
| Masters | 100,000 XGG | N/A |
Officers
The Git Guild as an organization still has some degree of centralization and currently requires a number of specialized officers. These will perform specific duties on behalf of the guild, and may be entitled to compensation, depending on individually negotiated contracts, which must be ratified by a majority of Directors. Directors do not receive any special pay.
| Office | Authorization | Abilities |
|---|---|---|
| Director | The five (5) most senior Guild members as measured by XGG earned. | These are allowed but not necessarily forced to be empowered with signing privileges over Treasury assets. They have decision power over all sponsorships and sub-guild authorization. |
| Ambassador | Majority of Directors | Negotiate sales deals, subject to Treasury approval |
| Council | Majority of Directors | Arbitrate disputed payments, as well as assist with management and financing of traditional equity and assets. |
| Treasurer | Majority of Directors | responsible for accounting and auditing all Treasury assets, on and off blockchain, and issuing quarterly reports. |
Workflows
A workflow represents both the way a team accomplishes a specific task, as well as the contract that they make for the quality and timeliness of the results. This contract should be able to be represented as a smart contract using Rootstock, but the details are TBD.
| Workflow | Role | Responsibility |
|---|---|---|
| idea | Sales | Close financial sponsorship |
| Github issue | Reporter | document and organize the tasks needed to accomplish the sponsors' goals into deliverables and engineering requirements. |
| Pull Request | Developer | Complete the engineering requirements described in the issue, write unit tests and documentation, and package up as a Pull Request |
| Quality Assurance | Tester | exercise Pull Requests by running unit tests, doing code review, and otherwise examining the changes. |
| Documentation | Documenter | read code, comments, READMEs and engineering wikies on approved Pull Requests and mirror changes into public facing documentation and organized release notes. |
| Merge | Maintainer | conduct the final review and checklist of documented, approved PRs and merge. |
Roles List
- Sales
- Reporter
- Developer
- Tester
- Documenter
- Maintainer
Pay Scale and Distribution
Until proper smart contracts can be enforced, each sub-guild (git repository) is responsible for managing its own sub-treasury, which will always be in the form of XGG tokens. It is recommended to keep these in a multisig wallet with the maintainer and two or more other sub-guild stakeholders as co-signers. It is the maintainer and the other co-signer's jobs to pay out XGG tokens to the various contributors upon merging. While each sub-guild can define it's own workflow, roles, and pay scale, the following pay scale is recommended and assumed as a default, unless otherwise specified in a sub-guild charter.
| Role | Pay (% of total / task) | Distribution (% of Role's pay for the task) |
|---|---|---|
| Sales | 5% | 33% on reporter handoff, 33% on merge, 33% distributed in 3 months following merge |
| Reporter | 5% | 50% on merge, 50% distributed in 3 months following merge |
| Developer | 60% | 33% on Tester approval, 33% on merge, 33% distributed in 3 months following merge |
| Tester | 20% | 50% on merge, 50% distributed in 3 months following merge |
| Documenter | 5% | 50% on merge, 50% distributed in 3 months following merge |
| Maintainer | 5% | 50% on merge, 50% distributed in 3 months following merge |
Note that a 3 month tailing distribution is suggested following the merge. This is to ensure no major bugs are discovered. If one or more such bug is discovered, all remaining funds are to be redirected to sponsoring the bug(s).
Treasury
The Git Guild Treasury is responsible for managing the funds backing XGG, with a mandate to operate transparently, and by distributing decision making and signing power to the Guild members as it becomes feasible. Once a month, Guild members will be allowed to change out XGG with a 10% premium. I.e. if a sponsor paid US$1 for 1 XGG, and it is paid to a Guild member, then the Treasury will change it out for US$0.90, assuming no change in the market price. This represents the only "fee" that the Guild imposes. The only other revenue stream that is available to the Treasury is capital gains from appreciation of assets under management.
Monetary Policy
The Git Guild will issue it's own cryptographic tokens (XGG), using the Rootstock smart contract system. A limited number of these tokens will be sold by the Treasury at a price of US$1, and the Treasury reserves the right to sell tokens at any price in the future. Funds raised in this manner go into the Treasury for sponsoring tasks and projects in the Guild. No more than 10% of the amount raised can be paid as bonuses at closing.
For example, a new sponsor pays $25k to the Treasury for 25k XGG. These XGG then get allocated to tasks and projects that the sponsor needs. No more than 2.5k XGG could be paid to sales or referrers for closing the sponsorship. As work is completed on those tasks, the XGG is paid out to Guild members.
Allocation
The Treasury is to use a Value At Risk (VAR) model for fund management.
| Asset | VAR Limit as % of Treasury total |
|---|---|
| BTC | 50% |
| DASH | 50% |
| USD | 25% |
| non-USD fiat | 10% |
| ETH | 25% |
| corporate stocks, bonds or other securities. not including blockchain tokens | 15% |
| Total of (LTC, DCR, NMC, FCT, XMR, MAID) | 10% |
| assets not described above | 10% |
Dash Specific
- At least $10k worth of value will be kept available in limit orders on DASH pairs.
- No less than 1 DASH masternode will be operated, and it's voting will be proxied by the Board of Directors.
Third Party Institutions
The Guild may open accounts at trusted third party institutions for the purpose of liquidity and fund management. The Directors and/or specially appointed Council are the only signers allowed on these accounts, and they must use all 2fa, password management, and other security measures available.
| Name | Trust level | VAR Limit |
|---|---|---|
| Crypto Capital | Sponsor | US$1,000,000 |
| Coinapult | Sponsor | US$1,000,000 |
| Bitt | Sponsor | US$1,000,000 |
| Bitfinex | Industry Leader | US$100,000 |
| Kraken | Industry Leader | US$100,000 |
| Poloniex | Low trust, high opportunity | US$25,000 |
| BTC-E | Low trust, high opportunity | US$25,000 |
| Exmo | Low trust, low opportunity | US$10,000 |
| Bittrex | Low trust, low opportunity | US$10,000 |