[docs] Update links to the public roadmap

[mnajdova]

The new link to MUI Core public roadmap https://github.com/orgs/mui/projects/18/views/1

[mui-bot]

Netlify deploy preview

• docs/data/material/discover-more/roadmap/roadmap.md

Bundle size report

No bundle size changes

Generated by 🚫 dangerJS against 5906dd9

[samuelsycamore]

Maybe we should revise roadmap.md to put these roadmap links front and center? A lot of the text on that page feels like of generic filler, but I think readers would prefer to get straight to these tangible details. We could at least bump them up above the "Priorities" section.

[mnajdova]

@samuelsycamore I moved the section above, I will merge as the PR only affects urls. We can revisit this page later.

[oliviertassinari]

@mnajdova Great that we work on this. It's important. Thoughts:

1. The board and the roadmap feel like two different things. The board (what we link now) seems to include lower-level items. I don't think that most developers would have the time to check this out (noise). It seems to be what we use internally for the day-to-day so mostly relevant for contributors.

I think that for the public roadmap, we need to have larger chunks. The problem it would solve is for the community to get a sense of the long-term direction, to know if it's safe to get onboard as a new user, and for the community to steer the boat when they feel we are going sideways.

https://www.youtube.com/watch?v=Zt8mO_Aqzw8 makes this point about React on how it's important.

https://github.com/orgs/github/projects/4247 is close to what I think would help the most the community. However, at our scale, from what we learned with past and today's needs, it would make more sense to have rolling quarters:

• Active quarter (next 3 months)
• Next quarter (next 6 months)
• Future

Also, IMHO no PRs should be displayed on the roadmap, it's too ephemeral.

2. As a developer, the experience on the classic board feels a bit better. It is clearly displayed under the repository. No confusion is possible. But yeah, it can be worth giving up on the classic board if the new GitHub project has automation features that save time.