New Category: Node #1145
Description
Since we've not been able to agree on any of the detailed categorisation suggested here (cc @nhenin):
... and since there hasn't been community support for a more detailed categorisation scheme suggested here:
... the outcome of CIP meetings & GitHub discussion in the last couple of months has only required we come up with one additional category to address performance issues that are likely too complex or long-term to address in the issue queue for the Haskell node, and which also could lead to performance degradation or failure of other connected node types unless coordinated with other node teams.
Therefore, after some push-back on a Node category in years gone by — from editors and community members alike — it is now the consensus that we move forward with a Node category and apply it to its current best-fitting CIP submission (about to be declared a candidate now that we have category to assign to it):
@perturbing and @colll78 were instrumental in the meeting today in achieving this consensus and tentatively confirming that "the" node (either the community of nodes, or the Haskell node, since [as Phil argued today] their need for interoperability requires that these be seen congruently) is the only class of problems in the Cardano stack that we would need a new CIP category for: given that "cross-cutting concerns" affecting Network and Consensus would already have their own categories for CIP submission, review, and implementation.
Like #937 before it, this will lead to a PR for a new Node category CIP — and like the earlier issue that production is currently limited by substantial changes to time available to CIP editors. Once that worload issue is resolved, we will be able to move forward on that writing & obtain stakeholder consensus for the CIP definition of this new category as well.