-
Notifications
You must be signed in to change notification settings - Fork 3
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
Roadmap #3
Comments
Tip: convert this to a checklist with the following markdown: - [ ] task todo
- [X] task done Note the space between the square brackets on the 'task todo'. |
Done. Does the roadmap seems ok to you? Something like: cleanup, stabilize and distribute then talk about the features to add trying to avoid bloat |
Yeah, it helps me to understand your vision for the project 😺 Also, the tasks seem well defined and achievable. It might be good to spread them across multiple milestones (see #5 for a start). |
I'm not sure about how to organize the milestones as I have no experience with them. I can give you write access if you wish so that we work together on this project more efficiently. What do you think about this? |
Now that we have the 0.2.0 milestone, it would be good to break this issue into sub-tasks. Each task can be assigned to the 0.2.0 milestone, and moved later (e.g. to a 0.3.0 milestone) if needed. |
Sounds good. I promise not to abuse the privilege. |
Granted. If you could start by organizing correctly the milestones it would be cool |
Regarding the final two tasks:
It seems like having them as separate projects could keep the chartflow project small and focused. They could use chartflo as a dependency, without bulking up the core chartflow module. |
I mentioned this as a possible option but thinking about it you are right: less complexity, less dependencies and less code to maintain is always good. About the research on a way to get a ready to use chart view its something that we can discuss separately and remove from 0.2 roadmap
One of them already does so that's fine like this. After all this module is for the lazy ones, lets be lazy if it is wise |
OK, clear. Should we go ahead and close this issue, since the other issues are now opened for discussion? |
That's fine: thanks for organizing the issues and milestones |
And then add features:
The text was updated successfully, but these errors were encountered: