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
Is there a way to make public what the next features to be developed by openhands are? The responses I got when I asked Qs about the enterprise plan had a lot of information about the future of openhand's direction, so I know these plans exist, but maybe it'd help open source contributors to be able to focus their development energy on things aligned with the openhands direction
For an example, currently, we are on release 0.14.2, there could be a section in the main README.md that says:
Describe the UX of the solution you'd like
Upcoming features
[0.15]
Feature 1 [link to issue A,B,C][link to PR X,Y,Z]
Feature 2 [link to issue D,E][link to PR X2, Y2]
[0.16]
Feature 3 [link to issue F]
This way, open source contributors like myself could try and cater PRs towards things that the open hands team is currently focused on?
Do you have thoughts on the technical implementation?
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
What problem or use case are you trying to solve?
Is there a way to make public what the next features to be developed by openhands are? The responses I got when I asked Qs about the enterprise plan had a lot of information about the future of openhand's direction, so I know these plans exist, but maybe it'd help open source contributors to be able to focus their development energy on things aligned with the openhands direction
For an example, currently, we are on release 0.14.2, there could be a section in the main README.md that says:
Describe the UX of the solution you'd like
This way, open source contributors like myself could try and cater PRs towards things that the open hands team is currently focused on?
Do you have thoughts on the technical implementation?
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: