Re: [DISCUSS] Graduate Apache ResilientDB
Jean-Baptiste Onofré <[email protected]> Mon, 6 Jul 2026 14:49:22 +0200
| Newsgroups | gmane.comp.apache.incubator.general |
|---|---|
| Message-ID | <CAB8EV3TqfFxo7je2701HzOH6UDXhQ3jK=GMw9_VQV=M+F9oHyQ@mail.gmail.com> |
--0000000000003aa75e0655f0b57a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Mohammad, The latest changes look good to me. I propose moving forward with a formal vote for the graduation of ResilientDB. In the meantime, although it is not strictly required, I suggest sharing the maturity matrix ( https://community.apache.org/apache-way/apache-project-maturity-model.html) to address potential questions from the IPMC members. I recall we discussed this briefly on the dev mailing list. Regards, JB On Thu, Jun 18, 2026 at 2:34=E2=80=AFAM Mohammad Sadoghi <msadoghi@expolab.= org> wrote: > Dear Justin > > As requested, we have removed all third-party apps/websites running under > the *.resilientdb.com domain. Now, we only have the main website at > https://resilientdb.incubator.apache.org/. > > We have also renamed/removed the 3rd-party repos > http://github.com/ResilientApp and http://github.com/ResilientEcosystem a= s > requested. > > As for the Twitter handle @resilientdb, it is an account I created in 201= 9 > that has not been used. We have removed it. > > Kindly let us know if any other changes are required. > > --- > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor, Chancellor's Fellow > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > ExpoLab: https://expolab.org/ > Apache ResilientDB (Incubating): https://resilientdb.com/ > The Problems of Consensus: SpringerBriefs in Philosophy > <https://link.springer.com/book/10.1007/978-3-032-07282-5> [Interview > < > https://cs.ucdavis.edu/news/computer-scientists-new-book-explores-philoso= phy-ethics-age-ai > > > ] > Phone: 914-319-7937 > > > > > On Wed, Jun 10, 2026 at 11:55=E2=80=AFPM Justin Mclean <justin@classsoftw= are.com> > 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 domain= s > > like resilientdb.com is not allowed. The branding policy explicitly > > states: "Projects may not use domain names owned by third parties to ho= st > > 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 unde= r > > the apache.org domain name. These pages also have numerous trademark an= d > > branding issues, ranging from failing to use the correct project name > > (dropping Apache) to omitting the ASF=E2=80=99s trademark attribution.= This is > one > > reason we ask you about trademark use in every incubator report, and wh= y > > the maturity model includes a section on trademarks and branding. > > https://expolab.resilientdb.com/ also has an issue with the placement o= f > > 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] > > > > > --0000000000003aa75e0655f0b57a--