Ladislav Thon

I think we can only resolve this once we have experience with real-world usage of Gizmo 2. I feel like it's gonna be a significant hindrance, but I hope I'll...

As I mentioned, I started porting ArC to Gizmo 2. I naturally started with the simplest cases, but got far enough to have a first-hand experience with this, see https://github.com/Ladicek/quarkus-arc/commit/2579b697d59951f925a78a13416d649122cf19b9...

I think so, yes. Splitting complex codegen into 2 phases is a nuisance, but it leads to better code overall, so that's what I would recommend.

> I'd like to fix this myself, please let me know if it's fine for me to contribute. Of course! :-)

The `spi` module that contains runtime SPI seems backwards. Most extensions do not expose public API directly, they just expose the API of the underlying library/framework. But I know we...

So in my eyes, SPI is part of API. API is what users are supposed to _use_. Some usages are consumption, some are participation, but it's all API. If you...

> However, let's imagine we can't have a clean cut (and the CDI event is an example of this ambiguity). Should we have an `api` module that contains both the...

Currently, we describe/prescribe package names and directory names (Maven module names). Should we also describe/prescribe Maven artifact IDs?

Do you know if there's some, you know, _actual documentation_? What you link to and the pages accessible from there don't explain anything except "here's how you configure your client...

The analysis seems correct. As for the sentinel password, adding a field on `RedisSentinelConnectOptions` seems best. I'm not sure how we should treat the password in the URI in this...