Governance doesn't describe the YTEP process well enough

[munkm]

Our governance defines a specific decision-making process here: https://yt-project.github.io/governance/voting.html#the-decision-making-process . This is more to resolve conflict(s) within the community about decisions where there might be a disagreement.

We mention YTEPs in various places in the governance documentation. However, we do not describe what a YTEP is, or how it should be merged. We should add a section to do that.

A few things that should be covered:

• How long YTEPs remain open
• When should they be merged?
• Where in implementation of a new feature should it be merged?

I do worry about being too prescriptive here; we don't want to limit contributions by adding unnecessary barriers. But we should have a clear general process so that devs understand the YTEP process.

[munkm]

At minimum for a YTEP to be merged I suggest:

• all conversations should be resolved
• it must be open for at least two weeks after it is announced to the community
• it must be announced in all relevant dev channels (yt dev, slack, etc.)
• after all conversations are resolved, it should be open for at least one more week to allow for feedback.

[matthewturk]

That sounds pretty reasonable!

[chummels]

+1

…

On Fri, Feb 26, 2021 at 12:07 PM Matthew Turk ***@***.***> wrote: That sounds pretty reasonable! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB66M56HLNHZQMHXNNHYHLLTA75QBANCNFSM4YJAESVA> .

-- Cameron Hummels Computational Astrophysicist California Institute of Technology http://chummels.org