“I'm finding a lot of projects these days not wanting a fix. They'd rather just want your ideas and your feedback, because generating code is easy enough, and the maintainers can do that themselves. So what they tend to prefer is just talk to them and share your experiences rather than a pull request.”

…and seeing things play out. So a pattern that we might have said, or might have predicted perhaps, and we see a completely different pattern actually being used in real life. It's like, hang on, all that stuff you predicted, all that was wrong, clearly. You didn't need all that. So, yeah.

Let's just say a developer here has found something that breaks when two implements. Implementations meet, what's the most useful way for them to bring that experience to the work that the AAIF is doing?

Beyond membership growth, how do you tell whether an open source project actually has a healthy community? And where does that community sort of need more support?

So, membership growth is only one aspect of the foundation. A much bigger, and in my opinion, more important aspect is the developer community. People who are actually using the code, who are downloading it, who are building on top of it, who are extending it, who are improving it. So, that's sort…

What's one practical thing you hope people do differently after hearing the news from the AIF, but also after this conference broadly?