Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings
Discussion options

febus982
Oct 10, 2023

As mentioned in the other discussion (#217) there are some packaging issues and legacy code that make the development experience complex and the result inefficient (especially impactful where lot of events might need to be processed).

Is the roadmap for V2 yet to be defined? If the answer is yes I'd like to contribute. Can I just send a proposal? Where?

If we document how V2 should look like, we could formalise the architectural documentation and the community could help in writing V2.
You must be logged in to vote

Replies: 1 comment · 1 reply

Comment options

xSAVIKx
Oct 10, 2023
Maintainer

Hey, sorry, no work done in that direction yet. I'd be glad to review the proposal. You can just create a PR with a v2-roadmap.md file and we can check it out in the PR if that works for you.
You must be logged in to vote
1 reply
@febus982
Comment options

febus982 Oct 10, 2023
Author

Cool, I'll prepare something in the next days. I have an idea in mind but I need some time to think about it and produce an acceptable document.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
@febus982 @xSAVIKx
Morty Proxy This is a proxified and sanitized view of the page, visit original site.