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.

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

Adopt a formal but flexible project life cycle #16

Open
theecrit opened this issue May 15, 2022 · 0 comments
Open

Adopt a formal but flexible project life cycle #16

theecrit opened this issue May 15, 2022 · 0 comments
Labels
Input wanted Issue needs more discussion, clarity or specificity to be completed. suggestion Have an idea for how OpenOakland could work better?

Comments

@theecrit
Copy link
Contributor

Description

Historically, OpenOakland has had various processes and standards for intaking and executing project work. Over time, those processes have become less formalized and more opaque to volunteers and leadership. Without a clear point of view on the project life cycle, an "anything goes" approach has taken root. The result is a lack of efficiency, oversight, accountability and, on occasion, harm to the community.

The goal

Define the project life cycle, including major phases and milestones, and required and recommended activities. This structure needs to balance flexibility and autonomy for volunteer teams with accountability to the public, and need to be accompanied by supportive resources that make the work both manageable and fun. We have an opportunity to help Oaklanders understand and define what equitable tech can look like in our city.

Reference material

@theecrit theecrit added the suggestion Have an idea for how OpenOakland could work better? label May 15, 2022
@theecrit theecrit added the Input wanted Issue needs more discussion, clarity or specificity to be completed. label May 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Input wanted Issue needs more discussion, clarity or specificity to be completed. suggestion Have an idea for how OpenOakland could work better?
Projects
None yet
Development

No branches or pull requests

1 participant