[Beyond][Proposal] Categorize all beyond-related stuff in Projects

[delneg]

Hi, Some tiem ago there was an effort to move all Beyond-related issues to https://github.com/orgs/fable-compiler/projects/6

However, now I see that there are multiple [Beyond] issues in this repo.

I think it would be better to align all the issues with the Beyond project, to be able to see clearly current progress as well as possibly release dates / most pressing concerns.

Thanks in advance ! @alfonsogarciacaro

[alfonsogarciacaro]

I wanted to have a kanban view as we did when developing Fable 2 and Fable 3 but when creating the project Github "invited" me to try the new projects which look more like an Excel sheet. I'm very influenceable so I did it 😸 But I'm not convinced now, the new projects seem to be useful when managing a big team but it's probably more than we need. Also, I don't like very much that the projects are linked to the organization and not this repo (the project remains invisible when you click the "Projects" tab above).

I'm considering now to recreate a new "old-style" project for Fable 4: Beyond. The most important thing is that it doesn't become a chore for anybody. I guess we can keep using issues as we're doing now, but I can add the Beyond-related issues to the project. Thoughts? @dbrattli @ncave

Maybe not yet, but I agree than in month or two we should try to decide what issues/features are missing for a beta release so we can have a better idea of the roadmap. For the beta release the AST should more or less stable so we can update the current Fable plugins and convince more users to upgrade so we can get more feedback.