Background

There has not been a community driven runtime upgrade so far on the Joystream mainnet, but in the future there are likely to be many attempts. Upgrades are both valuable and risky, where risks primarily come from the possibility of altering the runtime in some way which is

• harmful to the objectives of the community, either by intention or malintent.
• deemed as illegitimate by some material contingent, in terms of the process.

The only way to manage these risks is to have well documented and clear rules, generally accepted as legitimate, for the process of how runtime upgrades are conducted. At this time no such rules exist, and unfortunately since there is no constitution, there is no place for people to easily identify, review or suggest changes to any candidate rules.

Proposal

Write an initial set of simple rules to get us started, should cover exactly how someone would proceed if they have an upgrade in mind, what counts as a legitimate initiative and what other key actors are responsible for doing as part of this process, such as the council and builders, but also how all stakeholders can weigh in.

┆Issue is synchronized with this Asana task by Unito