tvm-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tianqi Chen <>
Subject [dmlc/tvm] [COMMUNITY][RFC] Transition to Apache (#2907)
Date Wed, 27 Mar 2019 02:33:42 GMT
Thanks to everyone's participation, [TVM Joins Apache](
as an incubator project. This is a public thread to list some of the things we should know
about the transition to Apache and possible discussions.

## What to Anticipate

Here are transition steps what will happen next
- PMC move to (already done)
- PMC invite all existing committers to apache and ask committers to sign iCLA(we will follow
up in the next few weeks)
- Transition the dmlc/tvm repo to apache/incubator-tvm
   - Double check apache/tvm-committers to make sure correct membership 

## Community

Everything should stay the same if there are any further updates we will still resolve publically
as per Apache way.  We will continue bringing in new people following the [community guideline](
There are some delays recently due to PMC list transition, and we will resume now that the
list transition is done:)

## Development

One of the Apache's requirements of development is the [Public Archive Principle](
This is a way to ensure everyone can participate at any time. is now the archive and development mail-list for TVM. You can subscribe
by sending an email to 

The community is using the github issue for technical RFC and a discourse forum for development
discussions. We would like to continue doing so while obeying the principle that "everything
happens (also) happen in dev@". 

We have set up the automatic forwarding so that any thread in github that has the prefix([VOTE],
[COMMUNITY], [RFC], [DEV]) will be automatically mirrored to the dev@, we also mirror the
thread under the development categories to dev@. This way, the community can still enjoy the
modern infrastructure from github and discourse for development while under the Apache framework.
Please be mindful about the [Public Archive Principle](
so that we make sure all important decisions appears in dev@. 

This is a short summary of what we need to know. One thing that worth discussing is whether
we want to continue to use github for VOTE, given that issue is mirrored to dev@, it makes
the vote through github also possible, we would like to hear the community's opinion on this.
Please also feel free to ask questions and share other thoughts.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message