You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
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.
The text was updated successfully, but these errors were encountered: