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
First and foremost, thank you very much for your excellent contribution to the RL community! I was wondering if it would be possible to create a simple roadmap or a to-do list as part of this repository? This list could enumerate bugs and features that are planned to be tackled or are already being tackled by your team. While I've noticed comments scattered throughout the GitHub discussions as well as in the paper, it would be immensely helpful to have a single place providing a general overview.
I believe such a roadmap could be invaluable for individuals considering using or relying on this project in their production use cases. Additionally, it would also be beneficial to those interested in contributing to the project itself (i.e., calling dibs on solving a particular thing). I would be happy to come up with an initial template and gather already open issues, in case that would help.
Cheers!
The text was updated successfully, but these errors were encountered:
Thank you for your kind comments and great suggestion, Aleksa! We will prepare such a roadmap. There is still a lot to be done but we are working on them. Thank you.
Hi there,
First and foremost, thank you very much for your excellent contribution to the RL community! I was wondering if it would be possible to create a simple roadmap or a to-do list as part of this repository? This list could enumerate bugs and features that are planned to be tackled or are already being tackled by your team. While I've noticed comments scattered throughout the GitHub discussions as well as in the paper, it would be immensely helpful to have a single place providing a general overview.
I believe such a roadmap could be invaluable for individuals considering using or relying on this project in their production use cases. Additionally, it would also be beneficial to those interested in contributing to the project itself (i.e., calling dibs on solving a particular thing). I would be happy to come up with an initial template and gather already open issues, in case that would help.
Cheers!
The text was updated successfully, but these errors were encountered: