'Default' CODE_OF_CONDUCT.md files for the 'wildfly' and 'wildfly-extras' GitHub orgs
by Brian Stansberry
Some project governance stuff....
FYI and input re a couple PRs related to CODE_OF_CONDUCT files. Commonhaus
requires that all repos have one of these, and most do but we have a ton of
repos and many don't. So I filed a couple issues / PRs to take care of all
repos missing these in the 'wildfly' and 'wildfly-extras' orgs.
https://github.com/wildfly/.github/issues/4
https://github.com/wildfly/.github/pull/5
https://github.com/wildfly-extras/.github/issues/6
https://github.com/wildfly-extras/.github/pull/7
The issues explain in more detail what I'm proposing. The gist of it is I
propose using the current 'wildfly/wildfy/CODE_OF_CONDUCT.md' content as a
default CODE_OF_CONDUCT.md for any repos in the 'widlfly' and
'wildfly-extras' orgs that don't already have one. Yeray Borges. Paul
Ferraro, Rado Husar and myself are all willing to act as the contact people
for any conduct issues related to those repos.
If you have any thoughts or concerns about this, please comment here or on
the GH issues/PRs, or directly to me.
Note this is not an invitation for projects with their own file and list of
contacts to drop those files and rely on the new 'default' one.
Best regards,
--
Brian Stansberry
Architect, JBoss EAP
WildFly Project Lead
He/Him/His
8 months
Simplify WildFly Glow installation
by Jean-Frederic Mesnil
Hi,
I’m working on using Glow to build a container image that would provision a WildFly server
based on the deployments that are ADDed to the Containerfile.
To do so, I need to install Glow from my Containerfile. The instructions are not complex[1] but we can
improve the user experience by automating it.
This would improve the usage of Glow by making it very easy to install.
We could have the standard usage of curl-ing a shell script that would do the actual work. All we need is a good
place to host that script.
I was thinking of using wildfly.org<http://wildfly.org> to host this script.
The installation process would simply be:
```
$ curl -s https://wildfly.org/sh/install-glow | sh
```
And WildFly Glow is installed from the local directory and ready to be used.
By default, the latest version is installed. Otherwise, you can use the GLOW_VERSION env var to use another version.
I did this on my fork of wildfly.org:
```
$ curl -s https://jmesnil.github.io/wildfly.org/sh/install-glow | sh
🔍 Fetching latest release from GitHub...
⬇️ Downloading: https://github.com/wildfly/wildfly-glow/releases/download/1.5.0.Final/wil...
📦 Extracting WildFly Glow...
🚀 Installing to /Users/jmesnil/tmp/wildfly-glow
💡 To install shell command completion, you can run:
source <(./wildfly-glow/wildfly-glow completion)
✅ Installation of WildFly Glow 1.5.0.Final complete!
```
I’ve opened a PR for it at https://github.com/wildfly/wildfly.org/pull/838.
Don’t hesitate to give your feedback and comments in the PR.
Once we have done that for WildFly Glow, I’m planning to do something similar with Prospero.
Jeff
[1] https://github.com/wildfly/wildfly-glow?tab=readme-ov-file#using-the-wild...
--
Jeff Mesnil
Software Engineer
Red Hat JBoss EAP
http://jmesnil.net/
IBM
Unless otherwise stated above:
Compagnie IBM France
Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 664 614 175,50 €
SIRET : 552 118 465 03644 - Code NAF 6203Z
8 months, 1 week
