Early versions of debcraft will focus on compatibility with the existing format, and aim to help unify workflow across our Ubuntu Developer community.
A notorious number of maintaining teams are the same for both distros and there hasn't been a problem I could think of.
> And takes some of the edge off of Ubuntu getting so much mileage out of Debian effort
And if you look on those teams' Debian QA pages you'll see that Sid isn't the upstream, this "mileage" has worked both ways for many years, for example Plasma 5 and 6 updates started in Unstable after they were deployed and ate most of the bugs in Ubuntu.
> I'll still continue to be all about Debian Stable
Which is the reason you probably don't know about the above since all of that work is to get updates into Testing.
Hopefully this won't in any way adversely affect development and maintenance of packages for Debian.
Nobody wants embrace-extend-extinguish, nor poaching of volunteers, nor Debian starting to get second-hand packaging that goes to Ubuntu first, etc., even accidentally.
> The Debcrafters must spend the majority of their work time on Ubuntu, but they will be encouraged to spend a day per week contributing to other distributions to gain understanding, and bring fresh perspectives to Ubuntu (and the reverse, hopefully!). This will be structured as a literal day per week, agreed with the team management - for example “I work on NixOS on Tuesdays”.
That's a good open source company practice. And takes some of the edge off of Ubuntu getting so much mileage out of Debian effort, but making the brand all their commercial one.
I'll still continue to be all about Debian Stable, since it's actually been better for production use than Ubuntu has been for me.