-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal for Collaboration #140
Comments
Hey Martin, Thanks, I'm glad that the project was useful for you, and I see you did some impressive work on it. In general, I'm all up for reducing entropy and limiting the amount of projects that do the same thing. In fact, during the latest FlutterconEU I was talking with widgetbook package maintainers – and that's yet another option to combine efforts with them, as I don't have much time recently to maintain my project, and they have a team working full-time on it (both free open-sourced and paid versions). I haven't made a final decision yet, but there's a high chance that I will discontinue my project in favor of |
Hello, thank you very much for your answer. |
@mjablecnik Hi! What is the status of https://github.com/FlutterPackages/storybook_toolkit_old i see it got archived and renamed to _old I missed any announcement if there was any. Please let me know :) |
@TomaszCz Hello, yes work continue in this repo: https://github.com/StorybookToolkit/storybook_toolkit |
Dear @ookami-kb,
I hope this message finds you well. My name is Martin Jablečník, and I am a mobile application developer specializing in Flutter. Recently, I came across your project, storybook_flutter, which I found extremely useful and have been actively using.
While using it, I noticed some features that could be added or improved, so I decided to create a fork of the project, which I named storybook_toolkit. In this fork, I have added several new features and enhancements, such as:
I believe these enhancements could be beneficial for the broader Flutter community and I am going to maintain this project in the future.
When I mentioned these changes within the Flutter community, it was suggested that I reach out to you with a proposal for collaboration. I would like to ask if you would be open to joining forces and unifying our projects. I believe it would be highly beneficial if we could work together on a single project and thus avoid splitting our efforts.
Specifically, I would like to ask if you would consider accepting another maintainer for your project or not.
Best regards,
Martin Jablečník
The text was updated successfully, but these errors were encountered: