-
Notifications
You must be signed in to change notification settings - Fork 670
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 and ideas #281
Roadmap and ideas #281
Changes from all commits
a52de0d
5612bb7
860dfd7
ad0aede
8464194
0e1b5ed
b7d768f
b50954d
5b79979
163f564
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,3 +13,4 @@ Flyte is a structured programming and distributed processing platform created at | |
|
||
whatis | ||
docs_overview | ||
roadmap |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
.. _introduction-roadmap: | ||
|
||
############### | ||
Roadmap | ||
############### | ||
|
||
How the core team works | ||
======================== | ||
Flyte is used actively in production at Lyft and its various subsidiaries. The core team is very customer focused and cares deeply about a high quality customer experience. Thus we always | ||
prioritize stability, reliability, observability and maintainability over raw feature development. Features are developed usually in response to specific use cases and user scenarios. That being said, | ||
we are proactively thinking about the evolution of the system and how we want to keep adapting to changing requirements. Thus most of our changes reflect future development scenarios and in | ||
cases where we feel rapid prototyping would enable us to discover potential pitfalls or uncover hidden use cases we would proactively develop features, behind feature flags. | ||
|
||
We want to extend the same sense of customer obsession to our Open Source community. We would love to hear use cases that various teams are solving and see how we could adapt parts of Flyte to meet | ||
those requirements. We welcome collaboration and contributions, but please follow our Contribution Guidelines. | ||
|
||
We will divide our roadmap into multiple sections. Please refer to each section's description to understand its goal. | ||
|
||
Continuous work | ||
================= | ||
This section highlights features and issues that are a continuous area of Focus and will always be in progress. | ||
|
||
1. Documentation | ||
---------------- | ||
Flyte's aim is to make it absolutely easy for any new user, administrator, contributor to read the documentation and complete their job successfully. We realize That we are not even close. This | ||
effort will continue on an ongoing basis and we would love feedback on the top areas where we should improve. | ||
|
||
2. Bug Fixes & Reliability Improvements | ||
---------------------------------------- | ||
As mentioned since Flyte is being actively used at Lyft and our scale is always increasing, there are always bugs that we want to squish. So Bugs, are always work in progress and most often then | ||
not receive highest priority. | ||
|
||
3. Observability | ||
---------------- | ||
We are currently working on a one time Observability epic that will enable open source users to use dashboard templates exactly like we use within Lyft (as of April 2020). Going forward, | ||
Observability is one of the pillars of Flyte. We will continue emphasizing on this aspect and improving it with every iteration. | ||
|
||
|
||
Living Roadmap | ||
=============== | ||
We are trying to maintain a Living roadmap `here <https://docs.google.com/spreadsheets/d/1V8DQfcsX_02Zac5EfAo0UrGJtLwdMPcw3wuuigVIMZU/edit?usp=sharing>`_ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Perhaps some treatment on how the open source community can voice their opinion and get things added to the roadmap? Should they open GitHub issues? Will they be required to defend their ideas in the weekly meetings? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. agreed, lets add something |
||
|
||
We also maintain a raw list of all the ideas `here <https://docs.google.com/document/d/1yq8pIlhlG3gci3GJQNjdAd9bzZ-KYyLfm6I5NVms9-4/edit?usp=sharing>`_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes it feel like bugs are a low priority, which isn't always the case depending on the severity of the bug.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
really, I feel this says bugs are found and fixed continuously, but maybe we need to create a process of ranking. I do not want to say we will get to them ASAP, as we have not done that