Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Joystream Task Force (JTF) #4453

Open
bedeho opened this issue Nov 19, 2022 · 0 comments
Open

Joystream Task Force (JTF) #4453

bedeho opened this issue Nov 19, 2022 · 0 comments
Labels
feedback Feedback from production users

Comments

@bedeho
Copy link
Member

bedeho commented Nov 19, 2022

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

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

#4454

@bedeho bedeho added the feedback Feedback from production users label Nov 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback Feedback from production users
Projects
None yet
Development

No branches or pull requests

1 participant