Hello, Le 07/07/2026 à 22:32, Christian Kastner a écrit :
I general I would say the best tool is the one you use to use, so the wiki is probably the best choice.On 2026-07-07 12:38, Talha Havadar wrote:I also agree with having documentation about the items you mentioned [1,4] where should we start putting those?In the past, we used the team wiki for our release plans, see 5.7 and 6.1 pages of https://salsa.debian.org/rocm-team/community/team-project/-/wikis/home For a policy document though, I think a Markdown file in some team repository would be better. There's a clearer history, cleaner versioning, and most importantly changes can be proposed and discussed through MR. Or perhaps Christian B. has a better idea? He's our documentation pro 🙂
I added the https://salsa.debian.org/rocm-team/rocm-team.pages.debian.netproject as it allows partly generated doc and allow to use the ROCm documentation system and have the result here :
https://rocm-team.pages.debian.netIt may be convenient to use this repo as a wiki so we can generate some large table like I did here :
https://rocm-team.pages.debian.net/index-large.htmlIt allows to have both advantage of markdown and ability to use ROCm doc system
I don't know if the gitlab/salsa wiki has a lot of features that were used and would miss, in a git repo.
I started to explore debusine and I think it could be quite usefull as it makes a lot of build test see :
https://debusine.debian.net/debian/r-bayle-rocm/work-request/912205/#work_request I wonder if it would be possible to plug the rocm CI https://ci.rocm.debian.net/ on a debusine PPASalsa runners don't allow to build many package, maybe debusine will do much better.
Ideally I'd like and automated workflow, maybe trying to make salsa push to debusine conditionally to each step/green flag
Regards Christian B.
Best, Christian