Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83D\uDDE3 Discussion topics

Item

Presenter

Notes

SMIRNOFF committee policy/structure changes?

JW

  • I made this committee largely with placeholder rules and no limitations on what the committee could do, with the intent for the first committee actions to be “coming up with better rules”

  • Do want to have monthly-ish meetings?

  • Are we happy with committee composition?

  • Should all decisions continue to require unanimity?

  • DLM background:

    • Current process owned too much by infrastructure team, including:

      • (possibly) define spec change

      • Review change, discuss spec change, answer questions, defend spec change, carefully consider all aspects

      • Get stakeholders to agree/iterate to convergence

      • implement

    • Creates perverse/adverse incentives: Requires a huge amount of work to define the work that needs to be done.

    • Possible new procedure:

      • The infrastructure team is only involved in review, final approval, and implementation; there needs to be another driver

        • Driver has the right to limit scope, e.g. “This is a good thing to consider but falls outside scope of current proposal; suggester can create new proposal and be driver on that”

Add LJPME to spec

MT

Clarify switching function

MT

✅ Action items

  •  

⤴ Decisions

  • No labels