presentations: add talks about pipewire and wireplumber

requested review from @wlozano

assigned to @daissi

I think it makes sense to have Pipewire and Wireplumber presentations in this section, same as we do with other projects (LAVA, libweston, etc). However, I fell that having so many (specially of one specific topic) shifts the focus.

I think we should take one (or many) of these actions 1- Add only the more relevant 2- Add a new section/page with presentations that are worth to mention but are not meant to be highlighted. 3- Other idea???

What do you think?

I feel the same, there are too many talks for pw and wp (and I didn't add everything).

Without answering your question since I'm still not sure. I can remove all talks about Wireplumber 0.5 (which represents half of the talks) since we are still using Wireplumber 0.4 in Apertis (pkg/wireplumber!44 (closed)).

But, I agree maybe we should create a new page for talks about Apertis' components and thus left the initial page for talks about Apertis?

Let's ping @martyn

After more thinking, one idea is to keep here those links that are more high level, as the overview section aims for that. Other presentations can be placed in architecture if we introduce a Pipewire and Wireplumber with a small doc. The same can happen for other packages that we are interested, like ostree, flatpack, etc.

I'd probably only add things that explicitly talk about Apertis, else we'll end up with a silly number of links here.

Based on previous comments, I would add Pipewire links that are relevant for us to Pipewire's specific page. I mean, not any reference to Pipewire, but only those that are somehow connected to Apertis or embedded systems.

I removed some talks and I moved the others to the audio-management page.

Maybe this audio-management page should be moved to architecture instead of concepts

No, that document reads as a concept design. There's lots of hypothetical stuff in it that we don't have implemented in Apertis.

As @martyn points, this is a concept document where some rationale and ideas are presented. Apertis is a distribution, so the ideas in this document probably will not be implemented in Apertis itself, but will provide pointers to product teams trying to build product.

Now more specifically about the references, if those make sense for this doc I am fine with including them. On the other hand, we can write a small document and placed in https://www.apertis.org/architecture/distribution/ describing PipeWire, its benefits, as prodiding these references.

Just as an example https://www.apertis.org/architecture/platform/software_bill_of_materials/

added 8 commits

• aa062c0e...18ff8feb - 7 commits from branch master
• 001de994 - audio-management: add talks about pipewire and wireplumber

Compare with previous version