Remove "Progress" section from README #9471
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I would personally propose to remove the progress board table from our README.
At the stage where we are at right now with most items in a pre-stable stage I don't think it is a good use of README real estate anymore. It hasn't been updated in over 7 months for a single item and older than a year for most boxes.
For upcoming users the list doesn't present detailed enough explanations of potential pitfalls and may be more confusing by mentioning features that are not really present (e.g. paging). Generally I have the impression that the community generally helps raise awareness about the limitations of the pre-1.0 state together with our release notes that try to highlight the pace of breaking or evolving changes.
Potential users are probably best served by additional links to learn more about our features and generally improved documentation and community tutorials
For contributors that want to look for areas to help out, this view is both not granular enough for real guidance and is maybe even actively harmful in highlighting areas we don't prioritize for 1.0 stability (e.g. notebook integration)
Contributors are probably better served by our planned write-ups around the 1.0 roadmap and updating GitHub Kanban/project boards.