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

Identify and track problems or obstacles that require changes to the process #188

Closed
justinwb opened this issue Jan 16, 2020 · 2 comments
Closed

Comments

@justinwb
Copy link
Member

We are running into disconnects where proposed changes to the solid process arrive as pull requests without traceability back to the original problem that led to the change. Additionally, we lack an accessible place to discuss the issue, or reference discussions about the issue that happened in any virtual or in-person meetings.

@justinwb
Copy link
Member Author

I believe we should require that any proposed changes or problems with the Solid process first be filed as discrete github issues in the process repo.

I think this should be explicitly specified in the solid process.

@justinwb justinwb changed the title Use of github issues to identify any problems or obstacles that require changes to the process Identify and track problems or obstacles that require changes to the process Jan 16, 2020
@Mitzi-Laszlo
Copy link
Contributor

@justinwb could you add a process proposal pull request with this change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants