-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
Convert project roadmap into a wiki page and link all of the milestones #3200
Comments
@DonnieBLT Sir, should I also deploy the wiki page and provide the url here, or just share the documentation created? |
I would say both. |
sure sir, I'll get on it |
@DonnieBLT sir, please review the website template and suggest viable corrections/improvements I should make, I've also resolved #3202 in this Screen.Recording.2025-01-05.at.6.10.56.PM.mov |
Looks great! Can you please also get the other milestones from the flutter app so we have everything that is listed in the project board? |
sure thing sir! |
Maybe it would be better to have everything in one list? So I can see all milestones without clicking and all dependencies without clicking. |
@DonnieBLT I made segregations so users could easily toggle through their field of interest. What are your reviews on this approach? If this doesn't seem efficient, I'll gladly form a list and divide that in various sections |
We have this tool that uses AI https://blt.owasp.org/submit-roadmap-pr/ if it can be read by AI ok then it's fine. Otherwise I think a list (even if it's long) is better, and I like the categories too. It looks great I just want to make it easy for humans and AI |
@DonnieBLT sir, please review this website where I've implemented all the three issues requiring wiki pages (#3202, #3201). I tried testing the AI tool against other PRs which aren't associated with website and the milestones present in the website; but was repeatedly getting 500 error: Screen.Recording.2025-01-06.at.4.06.41.PM.mov |
This is for the GitHub wiki so the pages are in markdown. |
No description provided.
The text was updated successfully, but these errors were encountered: