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
I've been looking through the currently open issues and a lot of the bug reports are issues with a particular encoder/decoder not working as expected with a particular image when the decoder/encoder used is provided by another crate with it's own repository.
Should we move these issues to their respective upstream repositories since that is likely where the code and pull requests will need to be made in order to resolve the issues?
If so, two ways I can think of improving this for the future cases is to add a CONTRIBUTING.md file that outlines such an please-report-bugs-upstream policy. Secondly we could add a note/checkbox to the bug report issue template.
As for all the already open issues that fit this description, we could either leave them open until if/when their respective issues get resolved upstream or we could manually migrate them to their upstream repositories ourselves.
The text was updated successfully, but these errors were encountered:
I've been looking through the currently open issues and a lot of the bug reports are issues with a particular encoder/decoder not working as expected with a particular image when the decoder/encoder used is provided by another crate with it's own repository.
Should we move these issues to their respective upstream repositories since that is likely where the code and pull requests will need to be made in order to resolve the issues?
If so, two ways I can think of improving this for the future cases is to add a
CONTRIBUTING.md
file that outlines such an please-report-bugs-upstream policy. Secondly we could add a note/checkbox to the bug report issue template.As for all the already open issues that fit this description, we could either leave them open until if/when their respective issues get resolved upstream or we could manually migrate them to their upstream repositories ourselves.
The text was updated successfully, but these errors were encountered: