Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[COMMUNITY][RFC] Transition to Apache #2907

Closed
tqchen opened this issue Mar 27, 2019 · 1 comment
Closed

[COMMUNITY][RFC] Transition to Apache #2907

tqchen opened this issue Mar 27, 2019 · 1 comment

Comments

@tqchen
Copy link
Member

tqchen commented Mar 27, 2019

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 private@tvm.apache.org (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
    • We will send out notice and RFC beforehand and everything should work smoothly.

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 that everyone can participate at any time.

dev@tvm.apache.org is now the archive and development mail-list for TVM. You can subscribe by sending an email to dev-subscribe@tvm.apache.org.

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.

@tqchen
Copy link
Member Author

tqchen commented Mar 27, 2019

#2906

@tqchen tqchen pinned this issue Mar 27, 2019
@tqchen tqchen closed this as completed Apr 13, 2019
@tqchen tqchen unpinned this issue Apr 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant