-
Notifications
You must be signed in to change notification settings - Fork 27
Interop 2024 process retrospective #611
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
Comments
Is there any consideration of making the interop selection process more transparent? If love to know more about why jpeg XL got passed by this year. Thanks! |
@jamesbiederbeck I will make sure to bring up the JPEG XL proposal and post-launch feedback in our retrospective, to discuss what we should change in our process for next year. |
Proposed agenda items:
|
Thanks @nairnandu! As you are no doubt aware, there has been frustration about this in public forums like reddit, and I'm just the guy who commented about it. I appreciate you coming back with updates on this. If it would help, I would be willing to aggregate public forum discussion for review by any relevant committees. |
Closing this as we have completed our retrospective. |
After Interop 2024 launches, we should do a retrospective to identify things in need of improvement.
I'm filing this issue now mostly to link to one piece of feedback about automatically reproposing features:
#594 (comment)
The text was updated successfully, but these errors were encountered: