-
Notifications
You must be signed in to change notification settings - Fork 136
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
[FEATURE REQUEST] Public Roadmap #453
Comments
I would like to work on this feature :) Do we want to create a dashboard of sorts for displaying all action items? |
We discussed about that during the last community meeting. My proposal is to use GitHub projects (I enabled it) to store the proposals and link to a milestone. Then, milestone can host the roadmap. |
I'd suggest following steps
|
@flyrain fully agree, that's also my suggestion. |
As reminder, we already have a "plug" on the website: https://polaris.apache.org/community/proposals/ So, we should be able to easily populate the public roadmap on the website here. |
Based on the suggestions here, I believe we can work on this in two simultaneous phases. First would be creating a placeholder issue circulated in the community where we ask contributors to comment on what major features they are working on and manually populating the ones with high votes in the project section. Second phase would be to fetch the listed tasks in the project section using the GitHub API and displaying in the community proposals section of the Polaris site. Does this sound correct? |
Is your feature request related to a problem? Please describe.
Lots of folks are interested in what is going on with the project but there is currently no clear way to see what folks are working on and what they plan to working on next
Describe the solution you'd like
Either we start using milestones or perhaps some projects to help folks to understand what is going on and who is working on what, as well as potential timelines
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: