aki

Yes, I see that user repos set up the way you're describing would work. I'm just saying that that's not how people do things right now, and it would require significant workflow changes to switch to. Specifically, I'm usually pushing from a repo that the builds can't see. Which means I need to push to a repo that builds *can* see, and right now that's either the try repo, or a user repo at somewhere like people.mozilla.org. It's extra work to set up the latter, and few people currently do it. So if you set up a generic place that people can push to just so it hangs around long enough for the builds, you're reinventing the try repo. (Well, since it doesn't need to be canonical anymore, you could have rolling monthly repos or team repos or whatever; there's no longer any need to have *everything* in one pile. But they'd still be provided to the developers, not maintained by devs as user repos would be.)

I won't argue for dynamic dependencies, I just wanted to check whether you knew of anywhere they're still needed or wanted.

For the community stuff, I was talking about outputs from "official" jobs to community subscribers. So no need for flagging. It's more about defining the schema with which job results are published to eg a pulse server. The current schema is a little ad hoc, and would probably need to be modified if jobs were defined more generally.

(And yes, this is sfink; my home DSL is alternating between being dead and having serious DNS issues, so I wasn't able to log in before.)