LLVM Qualification Group - Backlog documentation and Discussion Updates #156184
Conversation
…rom the main group page.
|
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 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. |
|
Hello @kbeyls , Thanks |
There was a problem hiding this comment.
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.
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.