LLVM Qualification Group - Backlog documentation and Discussion Updates

[CarlosAndresRamirez]

I have created backlog file for the Qualification group that contains all the topics currently under discussion and I have added the new section in the main group's page, referencing the backlog.

This Backlog will be used as the quick reference for anyone to know what are the current topics under discussion and what priorities have been given to them by the group.

Note for future editors: Add "Last updated:" comment on top of the document, easily keep track of the last updated dates.

[github-actions]

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

[CarlosAndresRamirez]

Hello @kbeyls ,
I noticed you were the reviewer for our first PR (the LLVM Qualification WG). Could you help us with this one?
I am not able to specify reviewers, I hope I did not miss any step.

Thanks

[kbeyls]

I can do a review, but can't review the details in depth as I'm not participating in the qualification working group.

I left a separate comment about the license header you're adding here: I'd remove that one.

Other than that, my main observation is that it might incur quite a bit of overhead to keep living documents in the llvm docs github repo.
Also, whenever an LLVM release is made, I guess that whatever state these documents are in at that point, will always be part of that LLVM release.
I think it might be better to keep living/frequently changing documents (like a backlog) in a document outside of the git repo. Other LLVM sync-up groups often use a public google doc or similar. Of course a pointer to the living document outside of the git repo could be very useful to have in the docs in git/on the website.

[kbeyls]

This looks fine to me now.
Let me know if you can merge this (i.e. you see a merge button on the PR).
If not, I can merge this PR for you.

[CarlosAndresRamirez]

Hello @kbeyls ,
Thanks for the review. I do not have the Merge option on my side. Could you be so kind and merge this please?

Thank you!

[github-actions]

@CarlosAndresRamirez Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as the builds can include changes from many authors. It is not uncommon for your change to be included in a build that fails due to someone else's changes, or infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail here.

If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!