Forked from Joystream/community-repo https://github.com/Joystream/community-repo
Codefikeyz 58848a217d Update discord handles for CM & WG Leads (#874) | 1 tahun lalu | |
---|---|---|
archives | 2 tahun lalu | |
bounties | 2 tahun lalu | |
community-roadmap | 1 tahun lalu | |
contributions | 1 tahun lalu | |
council | 1 tahun lalu | |
helpdesk | 2 tahun lalu | |
scripts | 1 tahun lalu | |
working-groups | 1 tahun lalu | |
.gitignore | 2 tahun lalu | |
.gitmodules | 2 tahun lalu | |
LICENSE | 4 tahun lalu | |
README.md | 2 tahun lalu |
The Joystream Community Repo is meant both as a resource for the community members of the Joystream project, and a place to submit their work or contributions.
If a KPI requires submitting a deliverable, eg. reports or some code, it is expected that a PR is made to this repo in order to qualify.
Although the community is meant to control the repo, Jsgenesis will approve and merge any pull requests for now. Note that the repo is licensed under GPLv3.
The workflow for changing the repo depends on the reason and purpose behind the change. A consistent part is for the contributor to fork the repo, and create a pull request to the applicable branch. All changes need to be approved with a proposal, except for selected files.
When a KPI requires a deliverable to be successful, the following steps must be made:
Submission Log
If the deliverable is made by an individual, eg. for an existing or upcoming funding proposal, the following steps must be made:
Community Contributions
directory.
Bot project - Author Name
Submission Log
If a member of the Jsgenesis team wants to make changes to the repo, the following steps must be taken:
Text
proposal is made to the Joystream testnet.
Submission Log