5:44 a.m.
I also think that the integration of a Google calendar is the best solution. Do we already
have a Google account for the calendar?
Harald Pehl
He/Him/His
Principal Software Engineer
On Feb 6, 2025 at 12:38 +0100, Yeray Borges Santana <yborgess(a)redhat.com>, wrote:
On Wed, Feb 5, 2025 at 11:25 PM Brian Stansberry <brian.stansberry(a)redhat.com>
wrote:
> Despite Jason's best efforts, this didn't really progress. I think it
foundered on discussions of how to maintain the ics file, and ideas around automation of
that (we're engineers!) etc.
>
> What I propose instead is we create a google calendar. Harald Pehl has demonstrated
a good looking embedding of such a calendar in a page on wildfly.org. We can share the
calendar giving edit rights to the folks who act as release coordinators for WildFly
releases (since a lot of the cal entries are various release preparation milestones) and
to folks who are helping coordinate various community activities like the WildFly Mini
Conference. It should be simple enough to maintain.
>
> Thoughts?
>
That sounds like an ideal solution to move on and would make the maintenance easier,
so +1.
> If it sounds ok I'll get it set up the week after next, after I get done with
some travels. Or if there's a groundswell of enthusiasm, maybe I can get it going this
week.
>
> > On Tue, Aug 8, 2023 at 2:32 PM Jason Lee <jasondlee(a)redhat.com> wrote:
> > > I have a PR open that is a first step in creating a calendar of
WildFly-related events: https://github.com/wildfly/wildfly.org/pull/439
> > >
> > > Brian does a great job of emailing the WF dev schedule to this list, but,
for me, it tends to get buried and lost. What I'd love to be able to do is subscribe
to a .ics and have events show up on my calendar. This is a step toward that. What would
be nice is to take that one step further and make it available in a human-friendly form on
wildfly.org as well.
> > >
> > > All that said, I would love feedback on the idea itself, the contents of
the calendar, etc. to see if this would be useful to more than just myself. Additionally,
I know we have various community efforts going on at the moment, so if this overlaps with
any of that, I'm happy to roll this into those efforts.
> > >
> > > Jason Lee
> > > Principal Software Engineer
> > > Red Hat JBoss EAP
> > > _______________________________________________
> > > wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> > > To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
> > > Privacy Statement: https://www.redhat.com/en/about/privacy-policy
> > > List Archives:
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...
>
>
> --
> Brian Stansberry
> Principal Architect, Red Hat JBoss EAP
> WildFly Project Lead
> He/Him/His
> _______________________________________________
> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
> Privacy Statement: https://www.redhat.com/en/about/privacy-policy
> List Archives:
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...
_______________________________________________
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives:
https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...