While I believe that a TKLDev with QEMU would be the best long-term direction, it's probably also the most complicated. Most RPi users would probably be more interested in using TKLDev on their RPi to create and build images for flashing (at least at first). It would probably be a pretty slow process, but for novice users, it's logically more straightforward to have everything occur on the same platform. (I can hear all of the confusion about "chroot? What's that?")
That being said, perhaps the very first step after discussing more with the TKL team would be reaching out to the RPi developers and people in the Foundation (I'm not seeing that the forums are going to get the necessary attention, unfortunately). While I'm sure you could get a bootstrap in pretty short order, there have been a lot of tweaks specific to the hardware. For instance, Debian doesn't (or at least didn't) support ARM's hardware-assisted floating point unit, and it took a good deal of development to get it working. Also, there's the GPIO mess. While the board uses pretty standard hardware, there have been tons of tweaks to squeeze out performance and keep the kernel small. I'm sure it's documented, but it would be a headache to track it all down and figure it out yourself.
There are two directions. On one hand, you could contact the leadership of the Foundation. They're probably more responsive, but they're also likely a bit less technical and may brush you off. On the other hand, you could try your luck pinging the lead contributors to the GitHub repository. They might be less responsive, and it's harder to tell who is "officially" involved with the project, but they would better understand what you're talking about and needing. Perhaps take both approaches in tandem? Either way, having a good elevator pitch that concisely explains TKL/TKLDev, what it could bring to the RPi, and what you need is a must. Since most people aren't familiar with TKL and don't know how well-polished TKLDev is at building ISOs, you need to get their attention without sounding like a bad infomercial, if you get what I mean.
Let me know how I can help. At the very least, I'm really good at tracking down contact information, and I could pull together a list of people to reach out to.
Time to reach out to RPi team?
While I believe that a TKLDev with QEMU would be the best long-term direction, it's probably also the most complicated. Most RPi users would probably be more interested in using TKLDev on their RPi to create and build images for flashing (at least at first). It would probably be a pretty slow process, but for novice users, it's logically more straightforward to have everything occur on the same platform. (I can hear all of the confusion about "chroot? What's that?")
That being said, perhaps the very first step after discussing more with the TKL team would be reaching out to the RPi developers and people in the Foundation (I'm not seeing that the forums are going to get the necessary attention, unfortunately). While I'm sure you could get a bootstrap in pretty short order, there have been a lot of tweaks specific to the hardware. For instance, Debian doesn't (or at least didn't) support ARM's hardware-assisted floating point unit, and it took a good deal of development to get it working. Also, there's the GPIO mess. While the board uses pretty standard hardware, there have been tons of tweaks to squeeze out performance and keep the kernel small. I'm sure it's documented, but it would be a headache to track it all down and figure it out yourself.
There are two directions. On one hand, you could contact the leadership of the Foundation. They're probably more responsive, but they're also likely a bit less technical and may brush you off. On the other hand, you could try your luck pinging the lead contributors to the GitHub repository. They might be less responsive, and it's harder to tell who is "officially" involved with the project, but they would better understand what you're talking about and needing. Perhaps take both approaches in tandem? Either way, having a good elevator pitch that concisely explains TKL/TKLDev, what it could bring to the RPi, and what you need is a must. Since most people aren't familiar with TKL and don't know how well-polished TKLDev is at building ISOs, you need to get their attention without sounding like a bad infomercial, if you get what I mean.
Let me know how I can help. At the very least, I'm really good at tracking down contact information, and I could pull together a list of people to reach out to.