-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Go through all old issues and PRs and link all relevant information to current issues and PRs #503
Comments
looks like @adrianbrink is on the case. @adrianbrink, can i help with something specific? |
I didn't go through all the closed ones. What would be extremely helpful if you could go through old issues and PRs where we discussed topics that are relevant today or that you think might be relevant. Ideally you could then link them to the newer issues. This would allow us to not have to reinvent the wheel. |
i don't understand. you want someone to go through 198 closed tickets to recover old discussions that might be relevant now? this doesn't seem like a good use of time. |
Yes. It takes maybe around 2 hours but saves us from solving about the same problem again. |
@jolesbi I actually fully agree with adrian on this one - there was a poor management strategy for knowledge transference on this one - current dev team didn't receive all insights from previously it would be very helpful to link this together save much time and energy in the future |
this is unrealistic and happens organically anyway |
* config option to log gRPC queries * clarify gRPC log comment * create var
* config option to log gRPC queries * clarify gRPC log comment * create var
We had a lot of conversations in the past with many of them being relevant to our current stage in the development.
This entails going through all old and closed issues and PRs after having read the current issues and bring back or link to the relevant current ones.
This is a great first issue to get acquianted with the cosmos-sdk repo.
The text was updated successfully, but these errors were encountered: