> On Aug 18, 2026, at 12:39 PM, Javier Jardón <[email protected]>
> wrote:
>
> Hey Rich!
>
> I think a colleague of mine replied to you directly some time ago (I think
> around 2026-07-30 maybe?) to arrange this
> Can you check you inbox in case it got lost or something? :)
I just heard from Annie, so it’s possible that I missed it last time. Thanks
for following up!
—Rich
> On 2026-08-18 16:48, Rich Bowen wrote:
>> Just in case y'all thought this was spam, I wanted to ask again if you were
>> at all interested in chatting on the ASF PlusOne podcast about your project.
>> Jorge spoke very highly of your project, and what he's able to do because of
>> it, and it would be great to get more people aware of what you're doing.
>> --Rich
>> On 2026/07/23 15:38:55 "Bowen, Rich" wrote:
>>> Hi folks,
>>> I produce PlusOne, the ASF's interview series where we talk with Apache
>>> project communities about their work. Each episode is a short (15-20 min)
>>> recorded conversation.
>>> Jorge Castro pointed me to BuildStream recently and piqued my interest, so
>>> I did some research. The story is compelling — a build system purpose-built
>>> for reproducible OS-level integration, now powering Project Bluefin's
>>> Dakota variant, with provenance tracking landing in 2.7.0. Some topics that
>>> might work:
>>> • The "integration tool, not a build tool" distinction and what it
>>> enables
>>> • How strict sandboxing and Remote Execution relate to the supply chain
>>> security conversation (SBOMs, SLSA)
>>> • The journey from the GNOME ecosystem to Apache
>>> • Project Bluefin choosing BuildStream for a next-gen desktop
>>> Happy to follow whatever thread is most interesting to you.
>>> Past episodes are at https://plusone.apache.org/ and the video versions are
>>> on the ASF YouTube channel:
>>> https://www.youtube.com/playlist?list=PLU2OcwpQkYCzs8261KxC4BoB2ptHJyMQt
>>> Would anyone from the community be interested in a conversation? Reply here
>>> or email me directly at [email protected].
>>> Rich
>>> [email protected] <mailto:[email protected]>
