Similarly, if a project has a mail list, e.g. a
lists.jboss.org one like
this or perhaps a
groups.google.com one, please add the info.
On Mon, May 5, 2025 at 2:38 PM Brian Stansberry <bstansbe(a)redhat.com> wrote:
Thanks for the great response so far!
Flavia mentioned one thing to me -- a number of projects have web sites
with URLs with a pattern like
foo.jboss.org, e.g.
https://jbossmarshalling.jboss.org/. If a project you expect will be part
of the transfer has a site like that, or anything else where the domain
belongs to Red Hat, please be sure to add that info. For sure I don't know
all the various sites like that.
Note: don't worry about foo.github.io sites. Those domains are controlled
by GitHub, not Red Hat.
On Wed, Apr 30, 2025 at 5:46 PM Brian Stansberry <bstansbe(a)redhat.com>
wrote:
> WildFly joining Commonhaus was formally announced today. :-) (See [1]).
> As I noted in the announcement, we're now beginning the process of
> onboarding to Commonhaus. Part of that is identifying the various 'assets'
> that will be transferred from Red Hat to Commonhaus.
>
> HELP WANTED on this! We have an opportunity to proceed more quickly on
> this asset transfer piece than I thought, but only if we act promptly to
> provide information.
>
> I have created a google document at [2] to record details of various
> types of assets we will transfer. I can really use your help with adding
> anything that is missing. Anyone can comment on the doc, so simplest is to
> directly edit the file to add things; your edits will be recorded as
> suggestions.
>
> I'm looking for things in 5 categories -- 'Source Code Repositories',
> 'Domain Names', 'Hosting Accounts', 'Social Media and Email
Accounts' and
> 'Trademarks'. The google doc has definitions of these, and from the ones
> I've already entered you can get a sense of the basic idea.
>
> When in doubt, suggest it! And leave a comment about the doubt.
>
> Note that the discussion of the scope of 'WildFly' on the 'Applying to
> Commonhaus' thread is relevant, so part of doing this will be firming up
> things discussed there. (If something discussed there is not covered in my
> initial draft of the doc; don't read anything into that, just help me by
> pointing that out.)
>
> NOTE: This DOES NOT need to be perfect. We can correct errors, add
> missing things, etc. So don't stress out.
>
>
> [1]
https://www.wildfly.org/news/2025/04/30/WildFly-Commonhaus/ and
>
https://www.commonhaus.org/activity/259.html
> [2]
>
https://docs.google.com/document/d/1qak1F2caFORP2kmDFZI68NsdVkXbslvKndCbe...
>
> Best regards,
>
> --
> Brian Stansberry
> Principal Architect, Red Hat JBoss EAP
> WildFly Project Lead
> He/Him/His
>
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
WildFly Project Lead
He/Him/His