Khronos encourages developers to request features through this forum. This is far from ideal:
- We need to request the same features over and over again with each release of OpenGL.
- There is no good way to follow the discussion, evolution and current state of any single feature over time. Topics like “feature requests for OpenGL 3.0/3.1/3.2” mix all feature discussions together.
- There is no good way to obtain statistics for features. For example, when was a feature first requested, how often is it requested and so on.
I understand that Khronos has direct communication pathways for vendors and corporate users (and that those carry more weight on the evolution of OpenGL than the opinions of independent developers), but a public bug/feature tracker would be more efficient across the board.
The ideal solution is something integrated with these boards (so we don’t need separate logins). The second best solution is to “open up” the Khronos public bugtracker (i.e. make it publicly searchable on the web, add new categories for feature requests). Trusted members of the community can be involved in cleaning up reports and removing duplicates, to remove this burden from Khronos itself.
Is there interest in something like this? Would the powers-that-be consider implementing or opening up the public bugtracker?