The TZIP Process is completely broken and dead

Hi! Thank you all for flagging this, and for the open discussions at TezDev!

I’m currently gathering various inputs and feedback relating to core development, and I’m happy to help share this relating to the TZIP process.

This topic has come up the various core development teams, and the following action plan may be best:

  1. Moving forwards, TZIPs should focus only on standards, and not on improvements. For instance, standards defining consistent behaviour or interaction of multiple products – like FA2.
  2. Merge or close open MRs in the tzip GitLab repo. We should also deprecate TZIPs that are not relevant, or not defining standards.
  3. Clarify the status of relevant TZIPs, and get them progressing.
  4. Ask everyone to share problem statements and ideas on Agora first, before writing TZIPs.
  5. Gather a small group of editors from projects actively building on Tezos to review TZIPs regularly.
5 Likes