WildFly Calendary Proposal
by Jason Lee
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
1 year
Results of Preferred Social Media Platforms Survey for WildFly Community
by Ranabir Chakraborty
Hello everyone,
I hope this email finds you well. Recently, we conducted a survey to gather
all valuable inputs on the preferred social media platforms for the WildFly
community. After a month of running the survey, we received a total of 38
responses from the community members. This feedback is crucial to enhance
the WildFly community engagement and outreach efforts. Below I'm listing
down survey results
<https://docs.google.com/spreadsheets/d/1DpWo7JLigdticYqh8G5WjR2UnRbrWr3QS...>
.
*Preferred Social Media platforms:*
1) X - (25/38 Responses) - 65.8%
2) YouTube - (24/38 Responses) - 63.2%
3) LinkedIn - (21/38 Responses) - 55.3%
4) Mastodon - (10/38 Responses) - 26.3%
5) Instagram - (6/38 Responses) - 15.8%
6) Others - (4/38 Responses) - 10.5%
7) Threads - (3/38 Responses) - 7.9%
8) Facebook - (2/38 Responses) - 5.3%
*What type of content do community members want to see?*
1) Project updates and releases - (35/38 Responses) - 94.6%
2) Technical tutorials and guides - (32/38 Responses) - 86.5%
3) WildFly future Roadmap (What's coming soon) - (28/38 Responses) - 75.7%
4) Community highlights and spotlights - (21/38 Responses) - 56.8%
5) Case studies and success stories - (19/38 Responses) - 51.4%
6) Behind-the-scenes development insights - (17/38 Responses) - 45.9%
7) How to get started contributing to a WildFly related project? - (11/38
Responses) - 29.7%
8) Polls and interactive content - (6/38 Responses) - 16.2%
9) Others - (1/38 Responses) - 2.7%
*Additional Feedback*
1) For me WildFly presence in social media is OK. Actually I mainly scan
through WildFly Project News (https://www.wildfly.org/news/) via RSS
subscription :) What I would like to see more is information on CVE (i.e.
security vulnerabilities) as security is very important topic for me and I
mainly learn about it currently from WildFly User or WildFly Developer
mailings groups.
2) Can we have WildFly meet-up just like we have Ansible meet-up and Fedora
meet-up. It would be great to understand more about WildFly, face to face
from the contributors themselves.
Now that we have these insightful results, we'd like to encourage you to
take a moment to look through them and share your thoughts. We have created a
thread in Zulip
<https://wildfly.zulipchat.com/#narrow/stream/174184-wildfly-developers/to...>
to
discuss more about it so that going forward we all can be on the same page.
Please feel free to reach out to me if you have any queries.
~
*Ranabir Chakraborty*
Software Engineer (JBoss SET)
<https://red.ht/sig>
2 years
Shared topic branch for Jakarta EE 11
by Brian Stansberry
I have pushed a new 'EE11' branch to wildfly/wildfly. This can serve as a
shared topic branch as we explore Jakarta EE 11 support for WildFly.
I think anything we do with this branch at this point should be restricted
to WildFly Preview. Hopefully initial work can be limited to using
different component versions as EE 11 artifacts become available. There
will be breaking changes in EE 11 vs 10, but hopefully little or none that
affects our integration code. At this stage these do not need to be
Final/GA artifacts.
At this point the only difference between the EE11 and main branches is one
commit to require use of SE 17+ to build, while still requiring SE 11 as
the source/target/release version. We'll need to compile against SE 17
dependencies, but at this point there's not a strong need for our own code
to move beyond SE 11, and staying there gives us the greatest flexibility.
For more see https://issues.redhat.com/browse/WFLY-18967.
Best regards,
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
2 years
WildFly Glow Beta
by Brian Stansberry
One of the exciting things the WildFly developers did last year was
development of new tooling -- WildFly Glow -- to help you provision a
WildFly server, bootable jar or Docker image that is tailored to the needs
of your application deployment. The WildFly Glow tooling is now available
in beta form, with a goal of general availability in the WildFly 32
timeframe. I encourage you to give it a try and let us know your feedback!
Jean Francois Denise (the main driver behind this work) has just now posted
an extensive introduction to WildFly Glow:
https://www.wildfly.org/news/2024/01/29/wildfly-glow/
Have a look!
Best regards,
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
2 years
Quickstarts: Flattened READMEs
by Eduardo Martins
Hi everyone, this message is just to let everyone know, specially quickstart developers, that we now made a major change wrt documentation in the Quickstarts project, through https://issues.redhat.com/browse/WFLY-18925.
In short this is what changed:
1. move each quickstart README.adoc to README-source.adoc
2. added a GitHub workflow that on any wildfly/quickstart branch push, uses asciidoctor-reduce to generate a flat, totally GitHub friendly, version of README-source.adoc named README.adoc
Obviously, from now on, any quickstart documentation change should be done on the quickstart’s README-source.adoc, not the README.adoc.
I would like to thank Ashwin Mehendale for taking the lead on this work, well done!
—E
2 years, 1 month
