Thanks Justin. To further address your listed points:

P0: tvm.io

The original project only uses the domain tvm.ai, which is redirected to
the https://tvm.apache.org/.
Other tvm related domain names have nothing to do with ApacheTVM. Note that
because TVM as a three letter abbreviation is quite common and could have
other
meanings. The project uses the name ApacheTVM during the podling name
search.

We agree with the need to discuss with trademark in terms of the domain
names and will do it now as what we did for the other branding related
requests [1].

We agree that customary the community usually makes more releases to
graduate. The TVM community is working on some major features right now and
the PMC would like to focus
effort on producing a high quality major release, but of course because of
the focus on the quality and uncertainty in terms of the cutting edge
technology we are developing,
it might take longer to produce the release. In the meantime, the community
could try to produce minor maintenance releases if there is a strong
feeling for such demonstration.

After discussion with our mentors we agree that it is not a hard blocker.
>From the community, and quality point of view the project is already
running like an Apache project.
That is why we bring up the case.

Thank you!
TQ

---
- [1]
https://lists.apache.org/thread.html/r8559979c58fb92f08f3e253522dc227a51313dafff2ec19076e1093c%40%3Ctrademarks.apache.org%3E

On Fri, Aug 28, 2020 at 7:41 PM Justin Mclean <jus...@classsoftware.com>
wrote:

> Hi,
>
> Thanks for the response. I think the docker issue is resolved.
>
> I still have concerns about use of tvm.io. I have discovered several
> other subdomains (six in total) that do not redirect to the Apache site,
> there might be others. It's still unclear who has control of this domain
> name. The issue here, is not the use of the forum but of the domain name
> and who it is controlled by, branding policy is clear on the use of such
> names. I suggest you discuss this with trademarks / branding.
>
> I still have concerns about the low number of release (i..e two) and there
> have been only a singe release manager. It’s generally expected that a
> project make 3 or 4 releases with a couple of different release managers,
> this certainly isn’t a hard rule but two in this case doesn’t seem enough.
> How much effort would it be to make another release with a different
> release manager?
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Reply via email to