From b54ab586efcba4095eb656dadf91205539f5c68b Mon Sep 17 00:00:00 2001 From: Ethan Li Date: Wed, 7 Feb 2024 10:45:27 -0800 Subject: [PATCH] Update description of governance plan in `README.md` --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index d9d80c04..5627a712 100644 --- a/README.md +++ b/README.md @@ -30,7 +30,9 @@ Forklift is guided by the following values for infrastructural software in the P - Thoughtfulness: Its design must be rigorous, deliberate, and considerate of how it will impact people. We must not commit to new features or changes in system behavior until we thoroughly understand their consequences. - Transparency: Its architecture and behavior must be sufficiently simple and easy to observe, fully explain, fully understand, troubleshoot, and learn from. -Currently, design and development of Forklift prioritizes the needs of the PlanktoScope community. Thus, for now decisions will be made by the PlanktoScope software's maintainer as a "benevolent dictator"/"mad scientist" in consultation with the PlanktoScope community in online meetings and discussion channels open to the entire community. Because Forklift is still an experimental tool and is still only used for the PlanktoScope software, governance of the [github.com/PlanktoScope/forklift](https://github.com/PlanktoScope/forklift) repository will remain in this benevolent-dictatorship model in order to ensure that the Forklift system develops in a cohesive way consistent with the values listed above and with the PlanktoScope community's use-case for Forklift. We encourage anyone who is interested in adapting Forklift to fork this repository for experimentation and/or to [create new discussion posts in this repository](https://github.com/PlanktoScope/forklift/discussions/new/choose), though we can't make any guarantees about the stability of any APIs or about our capacity to address any external code contributions or feature requests. +Currently, design and development of Forklift prioritizes the needs of the PlanktoScope community. Thus, for now decisions will be made by the PlanktoScope software's maintainer as a "benevolent dictator"/"mad scientist" in consultation with the PlanktoScope community in online meetings and discussion channels open to the entire community. This will remain the governance model of Forklift while it's still an experimental tool and still only used for the standard/default version of the PlanktoScope's operating system, in order to ensure that Forklift develops in a cohesive way consistent with the values listed above and with the PlanktoScope community's use-case for Forklift. Once Forklift starts being used for delivering/maintaining variants of the PlanktoScope's operating system, for integration of third-party apps from the PlanktoScope community, or for software configuration by ordinary users, then governance of the [github.com/PlanktoScope/forklift](https://github.com/PlanktoScope/forklift) repository will transition from benevolent dictatorship into the PlanktoScope project's [consensus-based proposals process](https://github.com/PlanktoScope/proposals)). In the meantime, we encourage anyone who is interested in using/adapting Forklift to fork this repository for experimentation and/or to [create new discussion posts in this repository](https://github.com/PlanktoScope/forklift/discussions/new/choose), though we can't make any guarantees about the stability of any APIs or about our capacity to address any external code contributions or feature requests. + +If other projects beyond the PlanktoScope community decide to use Forklift as part of their software delivery/deployment infrastructure, we can talk about expanding governance of Forklift beyond the PlanktoScope community - feel free to start a discussion in this repository's GitHub Discussions forum. ### Architecture