Hi

Afaik, these domains/website are about to not be used. The PPMC members I
talked with don't have a lot of details about these domains. Let me dig.

Regards
JB

On Thu, Jun 11, 2026 at 8:55 AM Justin Mclean <[email protected]>
wrote:

> Hi,
>
> While it is not required, has the project filled out a maturity model?
>
> I noticed a minor trademark issue on your website, i.e., no use of TM.
>
> However, there is a more serious trademark issue - the use of these
> domains: quickstart.resilientdb.com, cloud.resilientdb.com,
> explorer.resilientdb.com, status.resilientdb.com, blog.resilientdb.com,
> expolab.resilientdb.com and a few others. In general, the use of domains
> like resilientdb.com is not allowed. The branding policy explicitly
> states: "Projects may not use domain names owned by third parties to host
> official project content. The content must be migrated, or the domain
> registration must be transferred to the ASF."
>
>  Anything related to the project needs to be on ASF infrastructure under
> the apache.org domain name. These pages also have numerous trademark and
> branding issues, ranging from failing to use the correct project name
> (dropping Apache)  to omitting the ASF’s trademark attribution. This is one
> reason we ask you about trademark use in every incubator report, and why
> the maturity model includes a section on trademarks and branding.
> https://expolab.resilientdb.com/ also has an issue with the placement of
> logos and language that could imply ownership.
>
> I also notice some content on these sites is being served from expolab.org;
> again, all content needs to live on ASF infrastructure.
>
> These two GitHub accounts also exist: github.com/ResilientApp and
> github.com/ResilientEcosystem, which should be, I believe, repos under
> the Apache organization. If they are 3rd part repos, they cannot use those
> names.
>
> Who has control of https://twitter.com/resilientdb?
>
> Please speak with your mentors about these issues so they can be addressed.
>
> Kind Regards,
> Justin
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to