There is room for showing what you have built in the introduction round. But 
there is only time for showing a couple of screenshots and saying something 
short about them.

If you have a longer talk, I'll schedule it for the user day in 2027 ;-)

Regards, Johan

Op donderdag 16 april 2026 om 17:08 schreef Matt Pavlovich 
<[email protected]>:

> Hi Johan-
> 
> If you are looking for more content for the Wicket day, I’m available to 
> share how we (at HYTE https://hyte.io <https://hyte.io/>) are using Apache 
> Wicket for our main product, customer portal and upcoming control plane.
> 
> We build a managed platform for Apache ActiveMQ (I’m also PMC on Apache 
> ActiveMQ).
> 
> Thanks!
> Matt Pavlovich
> 
> > On Apr 15, 2026, at 8:52 AM, Johan Stuyts <[email protected]> 
> > wrote:
> >
> > Hi,
> >
> > Here is our second (and final) attempt for the Wicket User Day: 
> > <https://www.meetup.com/wicket-enthusiasts-europe/events/314295653/?utm_medium=referral&utm_campaign=announce_event&utm_source=link&utm_version=v2&member_id=479250162>
> >
> > There are some differences with the previous attempt:
> > -  We have speakers!
> >   - Jonathan Locke will talk about how he sees the future of Wicket: Wicket 
> > Next: Towards a Wicket for Modern Java.
> >   - I will talk about a DSL for Kotlin: Markup DSL for Kotlin.
> > - The event will be hybrid, so you can join even if you are not able to go 
> > to Dordrecht.
> >
> > Please let us know whether you will attend, and whether you will come to 
> > Dordrecht or want to participate online. You can do that on the event page 
> > on Meetup, or send me an email directly.
> >
> > I hope to see you there.
> >
> > Kind regards, Johan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to