Joystream / Joystream/joystream

Joystream Task Force (JTF)

Open
#4,453 0 comments 5 reactions 0 assignees View on GitHub
feedback
Dominant language
Rust
Stars
1.4k
Forks
116
PR merge metrics
No merged PRs in 30d

Description

# Background

As we near mainnet, there have been some rumblings in the community about the need for there to be more thought put into how well the infrastructure is working, and having different parties work together to move this forward. It is clear that finding an organised way to facilitate such collaboration will be useful beyond this narrow first topic, not only to make it easy for people to create and manage new efforts, but also for everyone in the Joystream ecosystem to have a clear conception of how this activity relates to everything else going on.

# Proposal

A Joystream Task Force (JTF) is an unincorporated, not-for profit and off-chain association which aims to support the development of the Joystream Network. Some examples which inspire this proposal are

- [Bitcoin Core](https://bitcoin.org/en/development#starter-projects)
- [Ethereum core developers](https://github.com/ethereum/pm)
- [W3C](https://www.w3.org/)
- [IEEE SA](https://standards.ieee.org/)

Specifically, JTFs are characterised by being

- **Independent:** The financing, priorities, processes and roles not directly depend on the Joystream DAO itself. The DAO may be a stakeholder, perhaps even a prominent one on a case by case basis, but the interests of other third parties in the ecosystem also may have a place, for example
- Independent contributors
- Gateway operators
- Storage and content delivery providers
- Creators
- Validators
- Jsgenesis
- Exchanges
- Wallet providers
- **Transparent:** The activities, meeting, decisions, discussions and plans of such bodies should be as transparent as possible, ideally all published in the clear for all stakeholders to observe and comment upon, and also to encourage entry.
- **Open-Source:** All the the source code, standards, artefacts, reports, analysis, research, media or other work products should be openly shared and permissively licensed.

Detailed prescriptions for how these characteristics should be realised are left open, but next I suggest a template can be used as a default starting point for anyone who wants to get started.

# Example

https://github.com/Joystream/joystream/issues/4454

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.