Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consent decision-making #874

Closed
sarayourfriend opened this issue Mar 9, 2023 · 0 comments · Fixed by #887
Closed

Consent decision-making #874

sarayourfriend opened this issue Mar 9, 2023 · 0 comments · Fixed by #887
Assignees
@sarayourfriend
Labels
📄 aspect: text Concerns the textual material in the repository 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟧 priority: high Stalls work on the project or its dependents 🧱 stack: mgmt Related to repo management and automations

Comments

@sarayourfriend
Copy link
Collaborator

Problem

The Openverse project does not currently follow any specific decision-making process and uses a rough, undefined, and inadequate version of consensus decision-making. Several Openverse sponsored contributors have discussed adopting a modified version of consent decision-making, but we need a document describing how the process would work for our particular project and its unique, asynchronous, online setting.

Description

I've already drafted a version of this that I've shared with many people privately. I will adapt it for a public audience, including the revisions we've agreed upon as we've discussed the proposal.

Additional context

This discussion started in private and significant work was done to refine the process to work for our team and its settings. However, further input is invited once the PR with the public document is available.
@sarayourfriend sarayourfriend added 🟧 priority: high Stalls work on the project or its dependents 📄 aspect: text Concerns the textual material in the repository 🧰 goal: internal improvement Improvement that benefits maintainers, not users labels Mar 9, 2023
@sarayourfriend sarayourfriend self-assigned this Mar 9, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Openverse Backlog Mar 9, 2023
@sarayourfriend sarayourfriend moved this from 📋 Backlog to 🏗 In progress in Openverse Backlog Mar 9, 2023
@sarayourfriend sarayourfriend moved this to Pending proposal in Openverse Discussions Mar 9, 2023
@sarayourfriend sarayourfriend mentioned this issue Mar 10, 2023
Merged
5 tasks
@obulat obulat added the 🧱 stack: mgmt Related to repo management and automations label Mar 27, 2023
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in Openverse Backlog Apr 4, 2023
dhruvkb pushed a commit that referenced this issue Apr 14, 2023
@AetherUnbound @krysal
Use Airflow base Docker image (#874)
f42555b 
* Use the upstream Airflow docker image

* Add new dc recipe and other fixes to get stack to work

* Last few fixes to get stack working

Don't forget to mention that a secret key must now be set

* Make ipython directories available and chowned

* Linting

* Run as root when generating DAG documentation

* Make file writable after generation

* Modify provider creation tests so they don't write to the code path

This also fixes an inadvertent bug where a string was handed in place of a list for media types and subsequently 5 providers were created for each letter in "image"

* Add note to README

* Add clarity to directory creation

Co-authored-by: Krystle Salazar <[email protected]>

* Minor syntax fix

* Minor syntax fix

Co-authored-by: Krystle Salazar <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sarayourfriend sarayourfriend

Labels
📄 aspect: text Concerns the textual material in the repository 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟧 priority: high Stalls work on the project or its dependents 🧱 stack: mgmt Related to repo management and automations
Projects
Openverse Backlog
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add consent decision-making process documentation WordPress/openverse
2 participants
@obulat @sarayourfriend