Skip to content

Instantly share code, notes, and snippets.

@oxarbitrage

oxarbitrage/zcashGrant_nov2019.md

Last active December 4, 2019 13:19
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save oxarbitrage/ff4290e1cc3d20a2c009c353bd74242e to your computer and use it in GitHub Desktop.
Save oxarbitrage/ff4290e1cc3d20a2c009c353bd74242e to your computer and use it in GitHub Desktop.
Download ZIP
Raw
zcashGrant_nov2019.md

Zcash core developer

This proposal aims to introduce 1 C++/Python developer into the task of resolving open issues in the main zcash repository: https://github.com/zcash/zcash/issues

It is also the proposal scope to help in the review process of open pull requests from the public list: https://github.com/zcash/zcash/pulls

Context

The Arborist Team members as part of the ECC are the bigger contributors to the zcash main repository. They do an excellent job, however the number of tasks is so big and the obligations of this team are so many that issues sit undone for long periods of time. Community contributes however it is not enough.

The intention of this proposal is collaboration between me(the new proposed developer), the community and the Arborist team for faster resolution of different tasks on usability, rpc interface, error handling, test case coverage, Bitcoin code port, code cleanup, technical debt, etc that will lead to better software.

This proposal intent is not to interfere in the bigger decisions, consensus, architecture or any other epic task. The community already have very competent engineers and protocol designers to do so, this proposal is to work in smaller, specific technical issues from the public list.

The current labelling strategy employed for the issues of the repository is well designed that is relatively easy to start making progress right away. To get familiar with the codebase the author had worked in the following pull requests, some of them already merged, most of them already approved and in the merge queue:

Goal

  • Work on open issues of different categories inside the zcash main repo. Previous coordination with the Arborist team to make sure there is no double efforts.
  • Provide code review. No push access is needed.

Condition

  • Arborist team need to invest time in code review at their speed and availability.

Scope labels

Some labels where this proposal aims to be working on are but not limited to:

Prioritization of issues

Initially all open issues and pull request are candidates to be resolved/reviewed/closed/commented/etc however some of them may be more urgent. A priority list will be created and mantained with community and zcash teams feedback.

Milestones

Every 15 days progress done.

Duration

6 months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment