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
{{ message }}
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.
first, we would like to thank you for the development of Viper in the last years. In our opinion, Viper is a very handy, valuable and nice tool, which is a fixed part in our eco-system and therefore is used everyday via the (old) API.
Since the last release is been a while, we would like to ask, if there is any chance that Viper, the API and the modules will be further developed in future?
Best regards
The text was updated successfully, but these errors were encountered:
I would be happy to see the tool be developed forward. The time I have to dedicate to this is limited. I would be happy to act in a reviewer function, merge PRs, fix bugs, etc. Unfortunately I am not sure there are others interested in continuing core development at this point.
It is also not fully clear what is the active user base at this point.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Dear maintainer,
first, we would like to thank you for the development of Viper in the last years. In our opinion, Viper is a very handy, valuable and nice tool, which is a fixed part in our eco-system and therefore is used everyday via the (old) API.
Since the last release is been a while, we would like to ask, if there is any chance that Viper, the API and the modules will be further developed in future?
Best regards
The text was updated successfully, but these errors were encountered: