Re: [VOTE] Graduate Apache bRPC to a TLP

[Tianqi Chen]

+1 (binding)

Best wishes
TQ

On Fri, Nov 11, 2022 at 10:16 AM Yu Xiao  wrote:

> + 1 （non-binding）
>
> Best wishes!
>
> Yu Xiao
> Apache ShenYu
>
> Jerry Tan  于2022年11月11日周五 22:48写道：
> >
> > Hello, dear IPMC members,
> >
> > following the [DISCUSS] thread at [1],
> >
> > I'd like to call a vote to graduate bRPC to a TLP.
> >
> >
> > Please vote accordingly:
> >
> > [ ] +1 Apache bRPC (incubating) is ready to graduate to a TLP
> >
> > [ ] +0 No opinion.
> >
> > [ ] -1 Apache bRPC (Incubating) is not ready to graduate (please state
> > reasons)
> >
> >
> > Thank you for participating in the vote!
> >
> >
> > Best regards
> >
> > Jerry Tan
> >
> >
> > ---
> >
> > Project Updates since 2018-11-13:
> >
> > ---
> >
> >
> > 1. We release 1.0.0,1.1.0, 1.2.0, 1.3.0, 4 apache releases, and
> > 0.9.6,0.9.7, 2 disclaim releases; by different release managers
> (including
> > Jerry Tan, Jiashun Zhu, Lorin Lee, Wang Weibing, Shuai Liu, Xiguo Hu)
> (see
> > it at [2])
> >
> >
> > 2. We add 5 new PPMC members including Jiashun Zhu, Wang Weibing, Cai
> > Daojin, He Lei, and Lorin Lee. see it at [2]. Now we have 10 PPMC members
> > altogether, they are from different companies, including ByteDance
> (James Ge,
> > He Lei), Baidu (Yao Wang, Wang Weibing), Google (Jiashun Zhu), 4Paradigm
> (Jerry
> > Tan), Shopee (Cai Daojin), Momenta.AI (Zhangyi Chen), Ant Group (Bear
> Jiang
> > ), Freelancer (Lorin Lee).
> >
> >
> > 3. We add 9 new committers, including Cai Daojin, He Lei, Mou Gaidong,
> Lorin
> > Lee, Wang Wei, Shuai Liu, Wang Xiaofeng, Xiguo Hu, and Guangming Chen.
> see
> > it at [2].
> >
> >
> > 4. There are 17 members subscribed to the private email list and 60
> > engineers subscribed to the dev mail list. The discussion on the dev mail
> > list is active, including release, roadmap, committer related topics. see
> > it at [3]
> >
> >
> > 5. Branding issues have been solved and name searching has been
> completed.
> > See it at [4]
> >
> >
> > 6. Assessment of the maturity model is available at [5]. All answers to
> > these check items are 'Yes'.
> >
> >
> > 7. The bRPC website has passed the Apache Podling Website Checks [6].
> >
> >
> > 8. 1000+ issues resolved[7], and 600+ pull requests merged and closed[8].
> >
> >
> > 9. bRPC has been widely adopted outside Baidu since incubating, including
> > iQiyi， Bytedance， Bilibili， Bigo， Didi， Weibo， Vivo，4padradigm， X
> > iaohongshu， Ishumei， Doris， Amap， etc.
> >
> >
> > And we plan to move on with new features and new scenarios, such as RDMA
> > support has been integrated into the trunk and will be included in the
> next
> > release, and extend bRPC with service mesh features.
> >
> > ---
> >
> > Draft resolution
> >
> > ---
> >
> > Establish the Apache bRPC Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> >
> > the Foundation and consistent with the Foundation's purpose to establish
> >
> > a Project Management Committee charged with the creation and maintenance
> >
> > of open-source software, for distribution at no charge to the public,
> >
> > related to an industrial-grade RPC framework for building reliable and
> >
> > high-performance services.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >
> > (PMC), to be known as the "Apache bRPC Project", be and hereby is
> >
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache bRPC Project be and hereby is responsible for
> >
> > the creation and maintenance of software related to an industrial-grade
> >
> > RPC framework for building reliable and high-performance services; and
> >
> > be it further
> >
> > RESOLVED, that the office of "Vice President, Apache bRPC" be and hereby
> >
> > is created, the person holding such office to serve at the direction of
> >
> > the Board of Directors as the chair of the Apache bRPC Project, and to
> >
> > have primary responsibility for management of the projects within the
> >
> > scope of responsibility of the Apache bRPC Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> >
> > appointed to serve as the initial members of the Apache bRPC Project:
> >
> > * Bear Jiang 
> >
> > * Cai Daojin 
> >
> > * He Lei 
> >
> > * James Ge 
> >
> > * Jean-Baptiste Onofré 
> >
> > * Jerry Tan 
> >
> > * Jiashun Zhu 
> >
> > * Juan Pan 
> >
> > * Lorin Lee 
> >
> > * Von Gosling 
> >
> > * Wang Weibing 
> >
> > * Yao Wang 
> >
> > * Zhangyi Chen 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that James Ge be appointed to
> >
> > the office of Vice President, Apache bRPC, to serve in accordance with
> >
> > and subject to the direction of the Board of Directors and the Bylaws of
> >
> > the Foundation until death, resignation, retirement, removal or
> >
> > disqualification, or until a successor is appointed; and be it further
> >
> > RESOLVED, that the Apache bRPC Project be and 

Re: [VOTE] Graduate Apache MXNet to a TLP

[Tianqi Chen]

> > > RESOLVED, that the Apache MXNet Project be and hereby is responsible
> for
> > >
> > > the creation and maintenance of software related to a flexible and
> > >
> > > efficient library for Deep Learning; and be it further
> > >
> > > RESOLVED, that the office of "Vice President, Apache MXNet" be and
> > >
> > > hereby is created, the person holding such office to serve at the
> > >
> > > direction of the Board of Directors as the chair of the Apache MXNet
> > >
> > > Project, and to have primary responsibility for management of the
> > >
> > > projects within the scope of responsibility of the Apache MXNet
> Project;
> > >
> > > and be it further
> > >
> > > RESOLVED, that the persons listed immediately below be and hereby are
> > >
> > > appointed to serve as the initial members of the Apache MXNet Project:
> > >
> > > * Anirudh Subramanian 
> > >
> > > * Bing Xu 
> > >
> > > * Bob Paulin 
> > >
> > > * Carin Meier 
> > >
> > > * Chiyuan Zhang 
> > >
> > > * Chris Olivier 
> > >
> > > * Dick Carter 
> > >
> > > * Eric Xie 
> > >
> > > * Furkan Kamaci 
> > >
> > > * Haibin Lin 
> > >
> > > * Henri Yandell 
> > >
> > > * Hongliang Liu 
> > >
> > > * Indhu Bharathi 
> > >
> > > * Jackie Wu 
> > >
> > > * Jason Dai 
> > >
> > > * Jian Zhang 
> > >
> > > * Joe Evans 
> > >
> > > * Joe Spisak 
> > >
> > > * Jun Wu 
> > >
> > > * Leonard Lausen 
> > >
> > > * Liang Depeng 
> > >
> > > * Ly Nguyen 
> > >
> > > * Madan Jampani 
> > >
> > > * Marco de Abreu 
> > >
> > > * Markus Weimer 
> > >
> > > * Mu Li 
> > >
> > > * Nan Zhu 
> > >
> > > * Naveen Swamy 
> > >
> > > * Przemysław Trędak 
> > >
> > > * Qiang Kou 
> > >
> > > * Qing Lan 
> > >
> > > * Sandeep Krishnamurthy 
> > >
> > > * Sergey Kolychev 
> > >
> > > * Sheng Zha 
> > >
> > > * Shiwen Hu 
> > >
> > > * Tao Lv 
> > >
> > > * Terry Chen 
> > >
> > > * Thomas Delteil 
> > >
> > > * Tianqi Chen 
> > >
> > > * Tong He 
> > >
> > > * Tsuyoshi Ozawa 
> > >
> > > * Xingjian Shi 
> > >
> > > * YiZhi Liu 
> > >
> > > * Yifeng Geng 
> > >
> > > * Yu Zhang 
> > >
> > > * Yuan Tang 
> > >
> > > * Yutian Li 
> > >
> > > * Zhi Zhang 
> > >
> > > * Zihao Zheng 
> > >
> > > * Ziheng Jiang 
> > >
> > > * Ziyue Huang 
> > >
> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sheng Zha be appointed to
> > >
> > > the office of Vice President, Apache MXNet, to serve in accordance with
> > >
> > > and subject to the direction of the Board of Directors and the Bylaws
> of
> > >
> > > the Foundation until death, resignation, retirement, removal or
> > >
> > > disqualification, or until a successor is appointed; and be it further
> > >
> > > RESOLVED, that the Apache MXNet Project be and hereby is tasked with
> the
> > >
> > > migration and rationalization of the Apache Incubator MXNet podling;
> and
> > >
> > > be it further
> > >
> > > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > >
> > > MXNet podling encumbered upon the Apache Incubator PMC are hereafter
> > >
> > > Discharged.
> > >
> > > —--
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Apache MXNet (incubating) as a Top Level Project

[Tianqi Chen]

+1 Great to see it

TQ

On Thu, Jun 2, 2022 at 2:21 AM Jialin Qiao  wrote:

> Hi,
>
> +1
>
> Good luck!
> —
> Jialin Qiao
> Apache IoTDB PMC
>
>
> Ziheng Jiang  于2022年6月2日周四 01:34写道：
>
> > +1
> >
> > Looking forward to the graduation!
> >
> > - Ziheng
> >
> > On 2022/05/02 17:29:53 Joe Evans wrote:
> > > Hi Apache Incubator Community,
> > >
> > > Apache MXNet (incubating) recently held a community discussion[1] and
> > > vote[2] to graduate to a top level project. The community vote
> passed[3]
> > > and we would like to start a discussion with the incubator community
> > about
> > > graduating the project.
> > >
> > > Here is a brief overview of the progress of the Apache MXNet
> (incubating)
> > > project and community since entering the incubator:
> > >
> > > Community
> > >
> > >-
> > >
> > >37 new PPMC members were added, bringing the total number of PPMC
> > >members to 50
> > >-
> > >
> > >56 new committers were added (which include new PPMC members),
> > bringing
> > >the total number of committers to 87
> > >-
> > >
> > >The total number of contributors is now 870 and growing.
> > >
> > > Project
> > >
> > >-
> > >
> > >18 releases[4] by 13 different release managers. All compliance
> issues
> > >have been resolved with the 1.9.0 and 2.0.beta releases.
> > >-
> > >
> > >MXNet website[5] is now compliant with Apache Project Website
> > >requirements[6]
> > >-
> > >
> > >MXNet has completed the project maturity self assessment[7]
> > >
> > >
> > > I’ve also attached the proposed board resolution below. We welcome any
> > > feedback or comments.
> > >
> > > This discussion will remain open for at least 72 hours.
> > >
> > >
> > > References:
> > >
> > > [1] https://lists.apache.org/thread/l9h2qgb2vqs2y0cm46wh83sgomr9w190
> > >
> > > [2] https://lists.apache.org/thread/py1nw6whov78sch5kkm1gcg7cv3zb2sv
> > >
> > > [3] https://lists.apache.org/thread/b8bngc6qcb33n0jo6m1rw0ylwlqzkmgx
> > >
> > > [4] https://github.com/apache/incubator-mxnet/releases
> > > [5] https://mxnet.apache.org/
> > > [6] https://www.apache.org/foundation/marks/pmcs
> > > [7]
> > >
> >
> https://cwiki.apache.org/confluence/display/MXNET/Apache+Maturity+Model+Assessment+for+MXNet
> > >
> > >
> > > Proposed resolution:
> > > -
> > >
> > > Establish the Apache MXNet Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > >
> > > the Foundation and consistent with the Foundation's purpose to
> establish
> > >
> > > a Project Management Committee charged with the creation and
> maintenance
> > >
> > > of open-source software, for distribution at no charge to the public,
> > >
> > > related to a flexible and efficient library for Deep Learning.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > >
> > > (PMC), to be known as the "Apache MXNet Project", be and hereby is
> > >
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache MXNet Project be and hereby is responsible
> for
> > >
> > > the creation and maintenance of software related to a flexible and
> > >
> > > efficient library for Deep Learning; and be it further
> > >
> > > RESOLVED, that the office of "Vice President, Apache MXNet" be and
> > >
> > > hereby is created, the person holding such office to serve at the
> > >
> > > direction of the Board of Directors as the chair of the Apache MXNet
> > >
> > > Project, and to have primary responsibility for management of the
> > >
> > > projects within the scope of responsibility of the Apache MXNet
> Project;
> > >
> > > and be it further
> > >
> > > RESOLVED, that the persons listed immediately below be and hereby are
> > >
> > > appointed to serve as the initial members of the Apache MXNet Project:
> > >
> > > * Anirudh Subramanian 

Re: Re: [VOTE] Graduate Apache ECharts as TLP (round 2)

[Tianqi Chen]

+1 （binding）

 TQ

On Mon, Nov 23, 2020 at 8:38 AM Kevin Ratnasekera 
wrote:

> +1 ( binding )
>
> On Mon, 23 Nov 2020 at 18:54, 张铎(Duo Zhang)  wrote:
>
> > +1 (binding)
> >
> > Good luck~
> >
> > Kris Calvin  于2020年11月23日周一 下午8:51写道：
> >
> > > +1 non-binding, good luck
> > > CalvinKirs
> > >
> > > Liu Ted  于2020年11月23日周一 下午8:22写道：
> > >
> > > > +1, binding.
> > > > Ted Liu
> > > >
> > > >
> > > >在 2020 年 11月 月 23 日週一，時間：19:54 ， vongosling 
> > 寫道：
> > > >  +1, binding
> > > >
> > > >
> > > > Best Regards,
> > > > Von Gosling
> > > >
> > > > lidong dai  于2020年11月23日周一 下午7:38写道：
> > > >
> > > > > +1 non-binding
> > > > > looking forward to ECharts graduation as TLP
> > > > >
> > > > >
> > > > > Best Regards
> > > > > ---
> > > > > DolphinScheduler(Incubator) PPMC
> > > > > Lidong Dai 代立冬
> > > > > dailidon...@gmail.com
> > > > > ---
> > > > >
> > > > >
> > > > > On Mon, Nov 23, 2020 at 7:33 PM tison 
> wrote:
> > > > >
> > > > > > +1 non-binding
> > > > > >
> > > > > > Good luck!
> > > > > >
> > > > > > Best,
> > > > > > tison.
> > > > > >
> > > > > >
> > > > > > Willem Jiang  于2020年11月23日周一 下午7:28写道：
> > > > > >
> > > > > > > +1 （binding）
> > > > > > >
> > > > > > > Willem Jiang
> > > > > > >
> > > > > > > Twitter: willemjiang
> > > > > > > Weibo: 姜宁willem
> > > > > > >
> > > > > > > On Mon, Nov 23, 2020 at 4:31 PM Ovilia 
> > > > wrote:
> > > > > > > >
> > > > > > > > Hi everyone,
> > > > > > > >
> > > > > > > > After discussion with the community [1], and a positive vote
> > > result
> > > > > [2]
> > > > > > > and
> > > > > > > > the
> > > > > > > > discussion under general mailing list [6], we believe
> > > > > > > > ECharts is ready for graduation to a TLP, and we'd like to
> call
> > > on
> > > > > the
> > > > > > > vote
> > > > > > > > to
> > > > > > > > graduate Apache ECharts as TPL.
> > > > > > > >
> > > > > > > > This is a formal voting thread about Apache ECharts's
> > graduation,
> > > > > > please
> > > > > > > > Vote:
> > > > > > > > [ ] +1 - Recommend graduation of Apache ECharts as a TLP
> > > > > > > > [ ]  0 - I don't feel strongly about it, but don't object
> > > > > > > > [ ] -1 - Do not recommend graduation of Apache ECharts
> > because...
> > > > > > > >
> > > > > > > > The VOTE will open for at least 72 hours.
> > > > > > > > <
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://www.timeanddate.com/countdown/vote?iso=20201126T1435=237=%5BVOTE%5D+Graduate+Apache+ECharts+as+TLP=serif=1
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://www.timeanddate.com/countdown/vote?iso=20201126T1635=237=Graduate+Apache+ECharts+as+TLP=serif=1
> > > > > > > >
> > > > > > > > -
> > > > > > > >
> > > > > > > > X. Establish the Apache ECharts Project
> > > > > > > >
> > > > > > > > WHEREAS, the Board of Directors deems it to be in the best
> > > > > > > > interests of the Foundation and consistent with the
> > > > > > > > Foundation's purpose to establish a Project Management
> > > > > > > > Committee charged with the creation and maintenance of
> > > > > > > > open-source software, for distribution at no charge to
> > > > > > > > the public, related to a charting and data visualization
> > > > > > > > library written in JavaScript.
> > > > > > > >
> > > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > > > > > > > Committee (PMC), to be known as the "Apache ECharts Project",
> > > > > > > > be and hereby is established pursuant to Bylaws of the
> > > > > > > > Foundation; and be it further
> > > > > > > >
> > > > > > > > RESOLVED, that the Apache ECharts Project be and hereby is
> > > > > > > > responsible for the creation and maintenance of software
> > > > > > > > related to a charting and data visualization
> > > > > > > > library written in JavaScript; and be it further
> > > > > > > >
> > > > > > > > RESOLVED, that the office of "Vice President, Apache ECharts"
> > be
> > > > > > > > and hereby is created, the person holding such office to
> > > > > > > > serve at the direction of the Board of Directors as the chair
> > > > > > > > of the Apache ECharts Project, and to have primary
> > responsibility
> > > > > > > > for management of the projects within the scope of
> > > > > > > > responsibility of the Apache ECharts Project; and be it
> further
> > > > > > > >
> > > > > > > > RESOLVED, that the persons listed immediately below be and
> > > > > > > > hereby are appointed to serve as the initial members of the
> > > > > > > > Apache ECharts Project:
> > > > > > > >
> > > > > > > >* Houjin Huang  
> > > > > > > >* Deqing Li
> > > > > > > >* Dong Rui  
> > > > > > > >* Kener Linfeng
> > > > > > > >* Kevin A. McGrail  
> > > > > > > >* Wenli Zhang  
> > > > > > > >* Shen Yi  
> > > > > > > >* Shuang Su
> > > > > > > >* Siwen Su  
> > > > > > > >* Junting Wang 

Re: Missing graduation resolutions

[Tianqi Chen]

Thanks Justin. We have sent the resolution to the board a while ago[1],
please let us know if there is additional action to be taken

TQ

[1]
https://lists.apache.org/thread.html/r407930963ef19516074d403703d8173413dd0e395493b9a22d05b7b7%40%3Cboard.apache.org%3E

On Wed, Nov 11, 2020 at 2:16 AM Justin Mclean 
wrote:

> Hi,
>
> Several projects have discussed graduation but I’m not seeing any
> proposals submitted. [1] It best to get them in early so board members can
> review them in time.
>
> I think we should have proposals for:
>  - TVM
>  - Superset
>  - Flagon
>  - ECharts?
>
> I’ve added Superset.
>
> Thanks,
> Justin
>
> 1. https://whimsy.apache.org/board/agenda/2020-11-18/
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[RESULT][VOTE] Graduate Apache TVM as TLP

[Tianqi Chen]

Dear Community:

Here is the result thread of the TVM TLP voting .

Voting thread:
https://lists.apache.org/thread.html/re02a2685f10d8655db192667aaa2e93b979882a4fad4a48f66d5f797%40%3Cgeneral.incubator.apache.org%3E

+1 votes
Henry (binding)
Markus (binding)
Furkan (binding)
Gon (binding)
Sebastian (binding)
Kevin (binding)
Felix (binding)
Timothy (binding)
Willem (binding)

+0 none
-1 none

The vote passes with 9 +1(binding) votes, no 0 votes and no -1 votes.

Thanks everyone!
TQ

[VOTE] Graduate Apache TVM as TLP

[Tianqi Chen]

Dear Incubator:

A month ago we brought up the discussion about graduating TVM as TLP. After
great discussions in the apache way [2],
we get good support from the incubator and also get helpful feedback about
producing another release.
The TVM PPMC always focused on getting consensus, and is fully committed to
building a better community,
as a result, we decided to withdraw the graduation until there has been
another release.

Now that the community has produced another release by two new release
managers from different organizations
and a after new round of discussion[1], we propose to formally vote on
TVM's graduation.

Please also see the community discussion thread[3], voting thread[4].

This is a formal voting thread about Apache TVM's graduation, please Vote:
[ ] +1 - Recommend graduation of Apache TVM as a TLP
[ ]  0 - I don't feel strongly about it, but don't object
[ ] -1 - Do not recommend graduation of Apache TVM because...

The VOTE will open for at least 72 hours.

--
Summary of community status:

Compliance

Compliance is what every project is required to do. These policies are set
to protect Apache’s brand,
encourage community over code and set a common foundation for the projects.
Usually compliance is well documented (as per-apache way, what is not
documented did not happen).
The TVM PPMC has been diligently upholding compliances, including, but not
limited to

- T0 Project website hosted at ASF https://tvm.apache.org/.
- T1 Produce apache release, no cat-X code.
- T2 No advertising non-release items as Apache release.
- T3 Protect Apache brand, working with trademark to resolve branding
concerns.
- T4 Clearly marks third party artifacts and makes sure they comply with
trademark policies.
- T5 Open development: everyone happens (also) happens on dev@
- T6 Consider all forms of contributions for committer nomination.
- T7 Make sure release processes are clearly documented, reproducible by
any committers.

Community

The “community over code” is one of the most important factors of
the Apache way.
The TVM PPMC has been working very hard to foster a healthy, diverse and
independent community,
and will continue to do so.

- C0: Consider all forms of contributions as merit.
- C1: Encourage community diversity by only nominating people from
different organizations.
- C2: Actively discusses, and brings in new committers from diverse
backgrounds.
The community grows healthily and is quite vibrant.

-

Establish the Apache TVM Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to compilation of machine learning models to run on a wide range of
hardware platforms...

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache TVM Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache TVM Project be and hereby is responsible for the
creation and maintenance of software related to compilation of machine
learning models to run on a wide range of hardware platforms; and be it
further

RESOLVED, that the office of "Vice President, Apache TVM" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache TVM
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache TVM
Project; and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache TVM Project:

 * Tianqi Chen 
 * Timothy Chen 
 * Zhi Chen 
 * Byung-Gon Chun 
 * Ziheng Jiang 
 * Furkan Kamaci 
 * YiZhi Liu 
 * Masahiro Masuda 
 * Thierry Moreau 
 * Jared Roesch 
 * Henry Saputra 
 * Haichen Shen 
 * Markus Weimer 
 * Eddie Yan 
 * Lianmin Zheng 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tianqi Chen be appointed to
the office of Vice President, Apache TVM, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed; and be it
further

RESOLVED, that the Apache TVM Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator TVM
podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
TVM  podling encumbered upon the Apache Incubator PMC are hereafter
Discharged.

---
- [1]
 
https://lists.apache.org/thread.html/r30929c68769ccb9fb67710e12f82f05f2141957cc52238dc02d12337%40%3Cgeneral.incubator.apache.org%3E
<https://lists

Re: [DISCUSS] Graduate Apache TVM as a TLP

[Tianqi Chen]

Thanks everyone. We plan to start a new voting thread in 72 hours.

TQ

On Wed, Oct 14, 2020 at 9:56 PM Henry Saputra 
wrote:

> As mentor for the podling, I have seen the Apache TVM community has worked
> hard to address the concerns and comments from previous graduation
> discussions.
> With another successful release, it has shown that it is ready and capable
> to continue its journey as TLP in Apache Software Foundation.
>
> The community has developed and embraced the Apache way of transparency and
> the community over code principal.
>
> I am supportive to vote yes for it to be TLP in ASF.
>
> - Henry
>
> On Tue, Oct 13, 2020 at 8:28 AM Byung-Gon Chun  wrote:
>
> > Tianqi,
> >
> > Thank you for initiating this discussion.
> > The TVM community reflected the feedback received from the previous
> > discussion, and did another release.
> > The project's in great shape.
> >
> > Thanks!
> > -Gon
> >
> >
> > On Sat, Oct 10, 2020 at 11:16 AM Tianqi Chen  wrote:
> >
> > > Dear Incubator:
> > >
> > > A month ago we brought up the discussion about graduating TVM as TLP.
> > > After great discussions in the apache way [1], we get good support from
> > the
> > > incubator and also get helpful feedback about producing another
> release.
> > > The TVM PPMC always focused on getting consensus, and is fully
> committed
> > to
> > > building a better community, as a result, we decided to withdraw
> > > the graduation until there has been another release.
> > > Now that the community has produced another release by two new release
> > > managers from different organizations.
> > >
> > > We feel it is the right time to bring up this topic.
> > >
> > > Here is the summary of the state:
> > >
> > > Compliance
> > >
> > > Compliance is what every project is required to do. These policies are
> > set
> > > to protect Apache’s brand,
> > > encourage community over code and set a common foundation for the
> > projects.
> > > Usually compliance is well documented (as per-apache way, what is not
> > > documented did not happen).
> > > The TVM PPMC has been diligently upholding compliances, including, but
> > not
> > > limited to
> > >
> > > - T0 Project website hosted at ASF https://tvm.apache.org/.
> > > - T1 Produce apache release, no cat-X code.
> > > - T2 No advertising non-release items as Apache release.
> > > - T3 Protect Apache brand, working with trademark to resolve branding
> > > concerns.
> > > - T4 Clearly marks third party artifacts and makes sure they comply
> with
> > > trademark policies.
> > > - T5 Open development: everyone happens (also) happens on dev@
> > > - T6 Consider all forms of contributions for committer nomination.
> > > - T7 Make sure release processes are clearly documented, reproducible
> by
> > > any committers.
> > >
> > > Community
> > >
> > > The “community over code” is one of the most important factors of
> > > the Apache way.
> > > The TVM PPMC has been working very hard to foster a healthy, diverse
> and
> > > independent community,
> > > and will continue to do so.
> > >
> > > - C0: Consider all forms of contributions as merit.
> > > - C1: Encourage community diversity by only nominating people from
> > > different organizations.
> > > - C2: Actively discusses, and brings in new committers from diverse
> > > backgrounds.
> > > The community grows healthily and is quite vibrant.
> > >
> > > Thank you!
> > >
> > > - [1]
> > >
> > >
> >
> https://lists.apache.org/thread.html/r215d3ecbd9bbf4db20dcaffa4fa2ec00e49e71fdcec7fa954d75f84a%40%3Cgeneral.incubator.apache.org%3E
> > > - [2] Maturity
> > >
> > >
> >
> https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing
> > >
> >
> >
> > --
> > Byung-Gon Chun
> >
>

Re: New distribution guidelines

[Tianqi Chen]

Sharing some thoughts about this particular question. The intention of the
guideline is to clearly distinguish the Apache from non-apache ones (to
protect apache's brand).

There are a few ways to achieve so:

- W0: Change the release note to indicate the tag is non-apache
- W1: Change the release title in the github page to include non-apache or
pre-incubation
- W2: Delete the original tag and create a new tag with pre-incubation
suffix (note that many projects might use tag that follows semantic
versioning).

W0 + W1 already serves the purpose pretty clearly, as users who browse the
github release tag page would clearly get the information.

As Ovilia mentioned,  W2 might create some disruptions for users who wish
to use pre-incubation releases and makes the transition less smooth for the
podling.
It might also create confusion about the software's history as some
project might expect the tag might need to follow semantic versioning.
Not requiring W2 might be desirable to make the new podling transition
smooth while also protecting apache's brand(via W0 and W1)

TQ

On Sat, Oct 10, 2020 at 2:23 AM Ovilia  wrote:

> Hi Justin,
>
> I have a question about the guidelines.
>
> > Any releases that exist before coming into incubation need to be clearly
> described on the release page and tagged as such on
>
> Does this mean that we need to change the tag/release name from something
> like "4.1.0" to be "4.1.0-non-apache-release" or "4.1.0-before-incubation",
> or just add a notification in the description that this is a release before
> incubation?
> P.S. I'm not sure if changing the version name would break some CDN relying
> on GitHub version.
>
> Thanks
>
> *Ovilia*
>
>
> On Mon, Oct 5, 2020 at 12:26 PM Justin Mclean 
> wrote:
>
> > Hi PPMC members,
> >
> > New distribution guidelines, that we have been working on for some time,
> > have been published here:
> > https://incubator.apache.org/guides/distribution.html
> >
> > They contain information on distributing releases on 3rd party platforms
> > including Maven, GitHub*, *Docker, NPM and PiPy.
> >
> > Note that these are good suggestions on best practice and incubating
> > projects can do things differently, but if you follow these guidelines,
> you
> > are less likely to have issues on graduation.
> >
> > If you have any questions or feedback on these guidelines, please do so
> on
> > the Incubator general list.
> >
> > Thanks,
> > Justin
> >
>

[DISCUSS] Graduate Apache TVM as a TLP

[Tianqi Chen]

Dear Incubator:

A month ago we brought up the discussion about graduating TVM as TLP.
After great discussions in the apache way [1], we get good support from the
incubator and also get helpful feedback about producing another release.
The TVM PPMC always focused on getting consensus, and is fully committed to
building a better community, as a result, we decided to withdraw
the graduation until there has been another release.
Now that the community has produced another release by two new release
managers from different organizations.

We feel it is the right time to bring up this topic.

Here is the summary of the state:

Compliance

Compliance is what every project is required to do. These policies are set
to protect Apache’s brand,
encourage community over code and set a common foundation for the projects.
Usually compliance is well documented (as per-apache way, what is not
documented did not happen).
The TVM PPMC has been diligently upholding compliances, including, but not
limited to

- T0 Project website hosted at ASF https://tvm.apache.org/.
- T1 Produce apache release, no cat-X code.
- T2 No advertising non-release items as Apache release.
- T3 Protect Apache brand, working with trademark to resolve branding
concerns.
- T4 Clearly marks third party artifacts and makes sure they comply with
trademark policies.
- T5 Open development: everyone happens (also) happens on dev@
- T6 Consider all forms of contributions for committer nomination.
- T7 Make sure release processes are clearly documented, reproducible by
any committers.

Community

The “community over code” is one of the most important factors of
the Apache way.
The TVM PPMC has been working very hard to foster a healthy, diverse and
independent community,
and will continue to do so.

- C0: Consider all forms of contributions as merit.
- C1: Encourage community diversity by only nominating people from
different organizations.
- C2: Actively discusses, and brings in new committers from diverse
backgrounds.
The community grows healthily and is quite vibrant.

Thank you!

- [1]
https://lists.apache.org/thread.html/r215d3ecbd9bbf4db20dcaffa4fa2ec00e49e71fdcec7fa954d75f84a%40%3Cgeneral.incubator.apache.org%3E
- [2] Maturity
https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing

Re: [VOTE] Release Apache TVM (incubating) v0.7.0.rc0

[Tianqi Chen]

+1, carrying over my vote (binding).

TQ

On Tue, Oct 6, 2020 at 4:31 PM Ziheng Jiang  wrote:

> Dear community,
>
> This is a call for a vote to release Apache TVM (incubating) version
> 0.7.0. This is a maintenance release incorporating important bug
> fixes. All users of Apache TVM (incubating) 0.6 are advised to
> upgrade. This release is co-managed by Zhi Chen.
>
> Apache TVM (incubating) community has voted and approved the release,
> with three +1 votes from IPMC members (Tianqi Chen, Byung-Gon Chun, Markus
> Weimer).
>
> Vote thread:
>
> https://lists.apache.org/thread.html/re73cf4c733c0671bdc893fecf038c14ce7dd34c43a3e712660bca35e%40%3Cdev.tvm.apache.org%3E
>
> Result thread:
>
> https://lists.apache.org/thread.html/r929370e94c8385cbc151fb86c74629f34fb19708cb22fc1d235d2215%40%3Cdev.tvm.apache.org%3E
>
> 1) Link to release notes:
> https://github.com/apache/incubator-tvm/releases/tag/v0.7.0.rc0
>
> 2) Link to release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/tvm/tvm-v0.7.0-rc0
>
> The vote will be open for at least 72 hours.
>
> +1 = approve
> +0 = no opinion
> -1 = disapprove (provide reason)
>
> Thanks,
> Ziheng
>

Re: [VOTE] Release Apache DataSketches-cpp 2.1.0-incubating-rc1

[Tianqi Chen]

+1 (binding)

 - Incubating in name
 - DISCLAIMER-WIP exists
 - LICENSE and NOTICE are fine
 - checksums

Best
TQ

On Wed, Sep 16, 2020 at 11:59 PM Furkan KAMACI 
wrote:

> Hi,
>
> +1 from me (binding, carrying over my vote).
>
> Kind Regards,
> Furkan KAMACI
>
> On Thu, Sep 17, 2020 at 2:18 AM Dave Fisher  wrote:
>
> > Carrying over my VOTE +1(binding)
> >
> > There was another IPMC vote which makes two, and we are looking for one
> > more IPMC vote.
> >
> > Regards,
> > Dave
> >
> > Sent from my iPhone
> >
> > > On Aug 31, 2020, at 11:52 AM, Jon Malkin  wrote:
> > >
> > > Hello IPMC and Apache DataSketches Community,
> > >
> > > 1. This is a call for vote to release Apache DataSketches-cpp version:
> > > 2.1.0-incubating-rc1
> > >
> > >NOTE 1: The C++ code provides a header-only library. Compilation
> > > is needed only to build unit tests. A Python extension is also
> > > included in this repository as a set of thin wrappers. That does
> > > produce a compiled artifact, but is not built by default.
> > >
> > >NOTE 2: Compiling the C++ unit tests requires CMake 3.12 or newer.
> > >
> > >NOTE 3: A few non-blocking issues were identified, as noted in
> > section B
> > >
> > >  A. Results from the PPMC vote:
> > >
> > > - 2 (+1 binding) vote, 2 (+1 non-binding) votes
> > >
> > > - The vote thread can be found at the Permalink:
> > >
> >
> https://lists.apache.org/thread.html/rbdcf341dcd41ce542976b9d09125c39c5d6a342d2e720e30e2882d3f%40%3Cdev.datasketches.apache.org%3E
> > >
> > >  B. Testing/actions/votes performed by the voters in the PPMC Stage 1:
> > >- Alexander Saydakov (+1 non-binding)
> > >  Checked:
> > >  - gpg signature
> > >  - shasum
> > >  - cmake, make, make test
> > >
> > >- Michael Himes (+1 non-binding)
> > >  Checked:
> > >  - make, make test
> > >  - python build/install
> > >  - python kll wrapper
> > >  - python vector_of_kll wrapper
> > >
> > >- Dave Fisher (+1 binding)
> > >  - Checked incubating in name
> > >  - Checked signature and checksum
> > >  - Checked LICENSE
> > >  - Checked NOTICE
> > >  - Checked DISCLAIMER-WIP
> > >  - Ran RAT Check. [Jon's comment: non-blocking issues to be fixed
> > > in next release noted next]
> > > * one missing license (common/test/catch.hpp)
> > > * two missing headers (common/test/catch_runner.cpp,
> > > hll/include/hll.private.hpp)
> > >
> > >- Furkan Kamaci (+1 binding)
> > >  I checked:
> > >  - Incubating in name
> > >  - DISCLAIMER-WIP exists
> > >  - LICENSE and NOTICE are fine
> > >  - No unexpected binary files
> > >  - Checked PGP signatures
> > >  - Checked checksums
> > >  - Run make, make test
> > >
> > > 2. Source repository:
> > >- https://github.com/apache/incubator-datasketches-cpp
> > >
> > >Git Tag for this release:
> > >-
> >
> https://github.com/apache/incubator-datasketches-cpp/releases/tag/2.1.0-incubating-rc1
> > > on branch 2.1.x-incubating
> > >
> > >Git HashId for this release starts with: c1a6f8e
> > >
> > > 3. The Release Candidate / Dist (Zip Repository):
> > >-
> >
> https://dist.apache.org/repos/dist/dev/incubator/datasketches/cpp/2.1.0-incubating-rc1/
> > >
> > >The public signing key can be found in the KEYS file:
> > >-
> https://dist.apache.org/repos/dist/dev/incubator/datasketches/KEYS
> > >
> > >The artifacts have been signed with --keyid-format SHORT : 38F334CC
> > >
> > > 4. C++ Test Guide:
> > >-
> >
> https://github.com/apache/incubator-datasketches-cpp/blob/2.1.0-incubating-rc1/README.md
> > > 5. Python Build & Test Guide:
> > >-
> >
> https://github.com/apache/incubator-datasketches-cpp/blob/2.1.0-incubating-rc1/python/README.md
> > >- Most python unit tests are written in a tutorial style that can
> > > be followed as example usage:
> > >
> >
> https://github.com/apache/incubator-datasketches-cpp/tree/2.1.0-incubating-rc1/python/tests
> > >- Only python 3 is supported
> > >
> > > 6. This is the second stage vote:
> > >   - This voting process will remain open for at least 72 hours AND
> > > until at least 3 (+1) IPMC votes or a majority of (+1) are acquired.
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > > Thanks,
> > > Jon malkinjmal...@apache.org 
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Graduate Apache IoTDB as TLP

[Tianqi Chen]

+1 (binding)

TQ

On Fri, Sep 11, 2020 at 7:49 AM Kevin A. McGrail 
wrote:

> I vote +1 (binding). KAM
>
> On 9/10/2020 3:42 AM, Xiangdong Huang wrote:
> > Dear all IPMCs:
> >
> > Following discussions with great support from our mentors,
> > committers and community members.
> > I would like to call for a formal VOTE for graduating Apache IoTDB
> > (Incubating),
> > as a Top Level Project.
> >
> > This is a formal voting thread about Apache IoTDB's graduation, please
> Vote:
> > [X] +1 - Recommend graduation of Apache IoTDB as a TLP
> > [ ]  0
> > [ ] -1 - Do not recommend the graduation of Apache IoTDB because...
> >
> > The VOTE will open for at least 72 hours.
> >
> > Apache IoTDB (Incubating) entered the incubator in Nov 2018, the
> community
> > has grown vibrantly since, with all the design, development happening on
> > the Apache infrastructure, the "Apache Way".
> >
> > To list a few of the community's achievements,
> >
> > - Apache IoTDB name search has been approved
> > - Accepted > 1300 PRs from 75 contributors
> > - Migrated developer conversations to the list at d...@iotdb.apache.org
> >   (more than 3000 mails, without JIRA notifications, and gitbox, are sent
> > by more than 160 persons)
> > - There are 9 versions (3 major versions) released successfully
> conformant
> > to Apache release policy by 5 release managers;
> > - Invited 12 new committers (all of them accepted)
> > - invited 4 of those new committers to join the PMC (all of them
> accepted)
> > - Our proposed PMC is diverse and consists of members from more than 10
> > organizations
> >
> > Preparations and discussions history about the graduation:
> >
> > - The maturity assessment is done [2],
> > - The community agreed on starting the graduation process in a formal
> vote
> > [3] (result see [4]).
> > And, I'd like to note that all our mentors also participated in the vote
> > with a positive vote!
> > - The community also decided about a suggestion for the initial VP, a
> > charter [5, 6] and the initial PMC list [7].
> > - We also received positive feedback from the incubator general mailing
> > list [8].
> >
> >
> > The draft of the resolution:
> >
> > Establish the Apache IoTDB Project
> >
> >WHEREAS, the Board of Directors deems it to be in the best
> >interests of the Foundation and consistent with the
> >Foundation's purpose to establish a Project Management
> >Committee charged with the creation and maintenance of
> >open-source software, for distribution at no charge to
> >the public, related to an IoT native database with high
> performance
> >for data management and analysis, on the edge and the cloud.
> >
> >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >Committee (PMC), to be known as the "Apache IoTDB Project",
> >be and hereby is established pursuant to Bylaws of the
> >Foundation; and be it further
> >
> >RESOLVED, that the Apache IoTDB Project be and hereby is
> >responsible for the creation and maintenance of software
> >related to an IoT native database with high performance
> >for data management and analysis, on the edge and the cloud.
> >and be it further
> >
> >RESOLVED, that the office of "Vice President, Apache IoTDB be
> >and hereby is created, the person holding such office to
> >serve at the direction of the Board of Directors as the chair
> >of the Apache IoTDB Project, and to have primary responsibility
> >for management of the projects within the scope of
> >responsibility of the Apache IoTDB Project; and be it further
> >
> >RESOLVED, that the persons listed immediately below be and
> >hereby are appointed to serve as the initial members of the
> >Apache IoTDB Project:
> >
> >  * Chen Wang  
> >  * Christofer Dutz 
> >  * Dawei Liu 
> >  * Gaofei Cao 
> >  * Haonan Hou 
> >  * Jialin Qiao 
> >  * Jianmin Wang 
> >  * Jincheng Sun 
> >  * Jinrui Zhang 
> >  * Julian Feinauer 
> >  * Jun Yuan 
> >  * Justin Mclean 
> >  * Kevin A. McGrail 
> >  * Kun Liu 
> >  * Lei Rui 
> >  * Rong Kang 
> >  * Rui Liu 
> >  * Shuo Zhang 
> >  * Stefanie Zhao 
> >  * Tian Jiang 
> >  * Tianan Li 
> >  * Willem Ning Jiang 
> >  * Xiangdong Huang 
> >
> >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Xiangdong Huang
> >be appointed to the office of Vice President, Apache IoTDB, to
> >serve in accordance with and subject to the direction of the
> >Board of Directors and the Bylaws of the Foundation until
> >death, resignation, retirement, removal or disqualification,
> >or until a successor is appointed; and be it further
> >
> >RESOLVED, that the initial Apache IoTDB PMC 

Re: [VOTE] Graduate Apache TVM as TLP

[Tianqi Chen]

Thanks everyone who voted, and great discussions.
Per the discussion thread, the incubator recommended for doing another
release.
As per Apache-way, we are always focused on getting consensus.

As a result, we will withdraw the vote for now and will post it again when
there has been another release.

Thanks everyone who provides helpful feedback.

TQ

On Fri, Aug 28, 2020 at 7:57 PM Ming Wen  wrote:

> my -1 non-binding.
> see discuss thread about my concerns.
>
>
> Justin Mclean  于 2020年8月29日周六 上午5:59写道：
>
> > HI,
> >
> > I’m -1 (binding), please see the discussion thread for my concerns.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Markus for chime in on this.

As Markus said, the TVM PPMC is fully committed to work towards consensus
and address issues to the best of our ability.

In particular, to address X1. Following trademark's recommendation and
thanks to INFRA's help,
We have now migrated the community forum to https://discuss.tvm.apache.org/.

We would love to get further constructive feedback.

Thank you!
TQ

On Wed, Sep 2, 2020 at 8:16 AM Markus Weimer  wrote:

> Just to echo and expand on my comment on the vote thread: From my
> perspective as a mentor, TVM is ready to be a top level project.
>
> I base this assessment not on any particular issue, but on how the
> community conducts itself: Everything is discussed out in the open,
> (mirrored) on mailing lists and the community works towards and
> usually achieves consensus, with [VOTE] threads as a last resort. And
> where issues come up, the community generally addresses them swiftly
> to the best of its abilities. This thread is a good example of that.
>
> In terms of genesis and prior setup, TVM resembles a lot of new OSS
> projects: Born on GitHub, with development and communications infra
> provided (for free) by various commercial services. Integrating this
> with the requirements of the ASF to hold the ground truth and paper
> trail on Foundation infra is challenging. TVM has done a fantastic job
> making that happen and to find creative ways to maintain community
> engagement during this transition. I believe some of the approaches
> used (e.g. which notices from GitHub to channel to what mailing list)
> can be used by other projects to bridge this chasm.
>
> Markus
>
> On Tue, Sep 1, 2020 at 2:30 PM Tianqi Chen  wrote:
> >
> > Thanks Justin and Ming for the followup feedback about the
> > https://tvmconf.org/, which I believe we have collectively work to
> resolve
> > the issue.
> >
> > Would love to hear more feedbacks wrt to the current summary of the state
> > in below and suggestions for further improvements.
> >
> > TQ
> >
> > Thanks Justin, Henry, Dave, Ming, Matt for helpful feedbacks.
> > >
> > > Personally I find the current conversation a good living example of the
> > > Apache way for consensus building :)
> > > Thanks to the helpful feedback we have resolved several issues.
> > >
> > > In order to clarify the situation, please allow me to dissect and
> > > summarize the current situation.
> > > There are a few categories of topics (related to the Apache way) this
> > > thread have touched so far:
> > >
> > > Compliance
> > >
> > > Compliance is what every project is required to do. These policies are
> set
> > > to protect Apache’s brand,
> > > encourage community over code and set a common foundation for the
> > > projects. Usually a compliance is
> > > well documented (as per-apache way, what is not documented did not
> > > happen). The TVM PPMC has been diligently
> > > upholding compliances, including, but not limited to
> > >
> > > - T0 Project website hosted at ASF https://tvm.apache.org/.
> > > - T1 Produce apache release, no cat-X code.
> > > - T2 No advertising non-release items as Apache release.
> > > - T3 Protect Apache brand, working with trademark to resolve branding
> > > concerns.
> > > - T4 Clearly marks third party artifacts and makes sure they comply
> with
> > > trademark policies.
> > > - T5 Open development: everyone happens (also) happens on dev@
> > > - T6 Consider all forms of contributions for committer nomination.
> > > - T7 Make sure release processes are clearly documented, reproducible
> by
> > > any committers.
> > >
> > > Customary
> > >
> > > There are also a few topics that touch on what many Apache(incubating)
> > > projects do, but are not (yet) strict compliance.
> > > The TVM PPMC could improve on. Specifically, the following item:
> > >
> > > - K0 Usually an incubator project produces three apache releases, with
> > > multiple release managers.
> > >   So far TVM PPMC produced two apache releases by one manager (many
> PPMC
> > > members helped on the two releases).
> > >
> > > Community
> > >
> > > Finally, the “community over code” is one of the most important
> factors of
> > > the Apache way.
> > > The TVM PPMC has been working very hard to foster a healthy, diverse
> and
> > > independent community,
> > > and will continue to do so.
> > >
> > > - C0: Consider all forms of contributi

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Justin and Ming for the followup feedback about the
https://tvmconf.org/, which I believe we have collectively work to resolve
the issue.

Would love to hear more feedbacks wrt to the current summary of the state
in below and suggestions for further improvements.

TQ

Thanks Justin, Henry, Dave, Ming, Matt for helpful feedbacks.
>
> Personally I find the current conversation a good living example of the
> Apache way for consensus building :)
> Thanks to the helpful feedback we have resolved several issues.
>
> In order to clarify the situation, please allow me to dissect and
> summarize the current situation.
> There are a few categories of topics (related to the Apache way) this
> thread have touched so far:
>
> Compliance
>
> Compliance is what every project is required to do. These policies are set
> to protect Apache’s brand,
> encourage community over code and set a common foundation for the
> projects. Usually a compliance is
> well documented (as per-apache way, what is not documented did not
> happen). The TVM PPMC has been diligently
> upholding compliances, including, but not limited to
>
> - T0 Project website hosted at ASF https://tvm.apache.org/.
> - T1 Produce apache release, no cat-X code.
> - T2 No advertising non-release items as Apache release.
> - T3 Protect Apache brand, working with trademark to resolve branding
> concerns.
> - T4 Clearly marks third party artifacts and makes sure they comply with
> trademark policies.
> - T5 Open development: everyone happens (also) happens on dev@
> - T6 Consider all forms of contributions for committer nomination.
> - T7 Make sure release processes are clearly documented, reproducible by
> any committers.
>
> Customary
>
> There are also a few topics that touch on what many Apache(incubating)
> projects do, but are not (yet) strict compliance.
> The TVM PPMC could improve on. Specifically, the following item:
>
> - K0 Usually an incubator project produces three apache releases, with
> multiple release managers.
>   So far TVM PPMC produced two apache releases by one manager (many PPMC
> members helped on the two releases).
>
> Community
>
> Finally, the “community over code” is one of the most important factors of
> the Apache way.
> The TVM PPMC has been working very hard to foster a healthy, diverse and
> independent community,
> and will continue to do so.
>
> - C0: Consider all forms of contributions as merit.
> - C1: Encourage community diversity by only nominating people from
> different organizations.
> - C2: Actively discusses, and brings in new committers from diverse
> backgrounds.
> The community grows healthily  and is quite vibrant.
>
> Concerns
>
> - X0: Right now, Justin and Ming rightfully point out that while the TVM
> community has fulfilled T7, we could improve in K0.
> - X1: The subdomain name (discuss.tvm.ai) is something that we would like
> to work with trademarks@ to clarify.
>   According to the current policy, the apache trademark cannot be used
> “when the content of that domain is related
>   to any related software products or services”. The subdomain is not
> providing any software product or deriving services
>   related to tvm. The TVM PPMC would be more than happy to follow
> trademark’s suggestion.
>
> Please let me know if the summary could be improved in any way, and we
> would also welcome more feedback.
>
> Thank you!
> TQ
>
> On Fri, Aug 28, 2020 at 9:08 PM Tianqi Chen  wrote:
>
>> I would like to revisit a bit about the release topic to shed light about
>> the release process.
>> The TVM PPMC has always been focusing on producing high quality releases.
>>
>> - The project has produced five major (non-apache) releases prior joining
>> Apache
>> - While most incubator projects start with a DISCLAIMER-WIP, the TVM
>> community strives to keep the release quality high and uses the DISCLAIMER
>>in the beginning of the first release[1]. The first release contains a
>> few rough edges and gets resolved very quickly thanks to the feedback from
>> Justin and other IPMC members.
>>    The second release is super smooth.
>> - Multiple PMC members work together to generate these releases.
>>
>> TQ
>> 
>> - [1]
>> https://lists.apache.org/thread.html/ad19634352f97d0a5b2bec866bcdecd556ca414cc6d4487b2282ce10%40%3Cgeneral.incubator.apache.org%3E
>>
>> On Fri, Aug 28, 2020 at 8:54 PM Tianqi Chen  wrote:
>>
>>> We have also talked to Apache INFRA about the use of the
>>> https://ci.tvm.ai/ due to the need of special setups in terms of GPU
>>> based resources etc.
>>>
>>> So far we have receiv

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Per Justin's feedback. The title has been changed to "Apache TVM and Deep
Learning Compilation Conference".

The TVM PPMC is fully committed to make sure the Apache brand is protected.
Would love to hear about more constructive feedbacks :)

TQ


On Mon, Aug 31, 2020 at 8:40 PM Tianqi Chen  wrote:

> Thanks Justin. As mentioned in the last email. We are following the
> previous naming convention of similar conferences like "Kafka Summit" and
> "Spark + AI Summit".
>
> We would be more than happy to change the title to something like "Apache
> TVM and Deep Learning Compilation Conference" if the trademark advises to
> do so.
>
> TQ
>
> On Mon, Aug 31, 2020 at 7:03 PM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> > The TVM PPMC would certainly be more than happy to follow trademarks
>> > suggestions on event brandings and make sure the event is compliant.
>> > To follow up the naming compliance. Notably, in the main page the
>> project
>> > name "Apache (incubating) TVM" is used in the first and most prominent
>> > reference [1].
>>
>> No it doesn’t the first and most prominent reference is in the title,
>> which you’ll note the policy explicitly mentions. The title fails to
>> mention this is an Apache project.
>>
>> Thanks,
>> Justin
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Justin. As mentioned in the last email. We are following the
previous naming convention of similar conferences like "Kafka Summit" and
"Spark + AI Summit".

We would be more than happy to change the title to something like "Apache
TVM and Deep Learning Compilation Conference" if the trademark advises to
do so.

TQ

On Mon, Aug 31, 2020 at 7:03 PM Justin Mclean 
wrote:

> Hi,
>
> > The TVM PPMC would certainly be more than happy to follow trademarks
> > suggestions on event brandings and make sure the event is compliant.
> > To follow up the naming compliance. Notably, in the main page the project
> > name "Apache (incubating) TVM" is used in the first and most prominent
> > reference [1].
>
> No it doesn’t the first and most prominent reference is in the title,
> which you’ll note the policy explicitly mentions. The title fails to
> mention this is an Apache project.
>
> Thanks,
> Justin
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Ming and Justin.

Yes, the conference is in discussion with trademarks@. The event is
organized by volunteers who are also active contributors to the project and
follows similar patterns of other events.

The TVM PPMC would certainly be more than happy to follow trademarks
suggestions on event brandings and make sure the event is compliant.
To follow up the naming compliance. Notably, in the main page the project
name "Apache (incubating) TVM" is used in the first and most prominent
reference [1].
As for the naming of the conference itself, we are following
similar examples as "Kafka Summit", "Spark + AI summit".

We would be more than happy to follow up with a trademark on their advice
about whether the conference name itself, or other content and make
appropriate changes if necessary.

TQ

---
- [1] https://tvmconf.org/#about-tvmconf


On Mon, Aug 31, 2020 at 12:02 AM Justin Mclean 
wrote:

> Hi,
>
> The conference hasn’t yet been approved by trademarks, but a request to
> use that domain has been asked [1]. I don’t think this is an issue unless
> trademarks says otherwise. My guess is that they may want a little more
> information to see if it complies with event branding policy [2]. It btw
> doesn’t currently seem to comply with [3]
>
> Thanks,
> Justin
>
>
> 1.
> https://lists.apache.org/thread.html/r8559979c58fb92f08f3e253522dc227a51313dafff2ec19076e1093c%40%3Ctrademarks.apache.org%3E
> 2. https://www.apache.org/foundation/marks/events
> 3. https://www.apache.org/foundation/marks/events#naming
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Justin, Henry, Dave, Ming, Matt for helpful feedbacks.

Personally I find the current conversation a good living example of the
Apache way for consensus building :)
Thanks to the helpful feedback we have resolved several issues.

In order to clarify the situation, please allow me to dissect and summarize
the current situation.
There are a few categories of topics (related to the Apache way) this
thread have touched so far:

Compliance

Compliance is what every project is required to do. These policies are set
to protect Apache’s brand,
encourage community over code and set a common foundation for the projects.
Usually a compliance is
well documented (as per-apache way, what is not documented did not happen).
The TVM PPMC has been diligently
upholding compliances, including, but not limited to

- T0 Project website hosted at ASF https://tvm.apache.org/.
- T1 Produce apache release, no cat-X code.
- T2 No advertising non-release items as Apache release.
- T3 Protect Apache brand, working with trademark to resolve branding
concerns.
- T4 Clearly marks third party artifacts and makes sure they comply with
trademark policies.
- T5 Open development: everyone happens (also) happens on dev@
- T6 Consider all forms of contributions for committer nomination.
- T7 Make sure release processes are clearly documented, reproducible by
any committers.

Customary

There are also a few topics that touch on what many Apache(incubating)
projects do, but are not (yet) strict compliance.
The TVM PPMC could improve on. Specifically, the following item:

- K0 Usually an incubator project produces three apache releases, with
multiple release managers.
  So far TVM PPMC produced two apache releases by one manager (many PPMC
members helped on the two releases).

Community

Finally, the “community over code” is one of the most important factors of
the Apache way.
The TVM PPMC has been working very hard to foster a healthy, diverse and
independent community,
and will continue to do so.

- C0: Consider all forms of contributions as merit.
- C1: Encourage community diversity by only nominating people from
different organizations.
- C2: Actively discusses, and brings in new committers from diverse
backgrounds.
The community grows healthily  and is quite vibrant.

Concerns

- X0: Right now, Justin and Ming rightfully point out that while the TVM
community has fulfilled T7, we could improve in K0.
- X1: The subdomain name (discuss.tvm.ai) is something that we would like
to work with trademarks@ to clarify.
  According to the current policy, the apache trademark cannot be used
“when the content of that domain is related
  to any related software products or services”. The subdomain is not
providing any software product or deriving services
  related to tvm. The TVM PPMC would be more than happy to follow
trademark’s suggestion.

Please let me know if the summary could be improved in any way, and we
would also welcome more feedback.

Thank you!
TQ

On Fri, Aug 28, 2020 at 9:08 PM Tianqi Chen  wrote:

> I would like to revisit a bit about the release topic to shed light about
> the release process.
> The TVM PPMC has always been focusing on producing high quality releases.
>
> - The project has produced five major (non-apache) releases prior joining
> Apache
> - While most incubator projects start with a DISCLAIMER-WIP, the TVM
> community strives to keep the release quality high and uses the DISCLAIMER
>in the beginning of the first release[1]. The first release contains a
> few rough edges and gets resolved very quickly thanks to the feedback from
> Justin and other IPMC members.
>The second release is super smooth.
> - Multiple PMC members work together to generate these releases.
>
> TQ
> 
> - [1]
> https://lists.apache.org/thread.html/ad19634352f97d0a5b2bec866bcdecd556ca414cc6d4487b2282ce10%40%3Cgeneral.incubator.apache.org%3E
>
> On Fri, Aug 28, 2020 at 8:54 PM Tianqi Chen  wrote:
>
>> We have also talked to Apache INFRA about the use of the
>> https://ci.tvm.ai/ due to the need of special setups in terms of GPU
>> based resources etc.
>>
>> So far we have received warm help from the INFRA and they are super
>> helpful in helping setting up CI hooks so that the community can enjoy quick
>> development with the volunteer maintained CI. Running and serving the
>> community well, we would certainly happy to use a different name if asked by
>> the trademark.
>>
>> TQ
>>
>> On Fri, Aug 28, 2020 at 8:49 PM Tianqi Chen  wrote:
>>
>>> tvmlang.org was an old url by the project that eventually got
>>> deprecated at some time point, it now redirects to the
>>> https://tvm.apache.org/
>>>
>>> The PMC makes sure to redirect to the static Apache project when
>>> possible for official project related information

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

I would like to revisit a bit about the release topic to shed light about
the release process.
The TVM PPMC has always been focusing on producing high quality releases.

- The project has produced five major (non-apache) releases prior joining
Apache
- While most incubator projects start with a DISCLAIMER-WIP, the TVM
community strives to keep the release quality high and uses the DISCLAIMER
   in the beginning of the first release[1]. The first release contains a
few rough edges and gets resolved very quickly thanks to the feedback from
Justin and other IPMC members.
   The second release is super smooth.
- Multiple PMC members work together to generate these releases.

TQ

- [1]
https://lists.apache.org/thread.html/ad19634352f97d0a5b2bec866bcdecd556ca414cc6d4487b2282ce10%40%3Cgeneral.incubator.apache.org%3E

On Fri, Aug 28, 2020 at 8:54 PM Tianqi Chen  wrote:

> We have also talked to Apache INFRA about the use of the
> https://ci.tvm.ai/ due to the need of special setups in terms of GPU
> based resources etc.
>
> So far we have received warm help from the INFRA and they are super
> helpful in helping setting up CI hooks so that the community can enjoy quick
> development with the volunteer maintained CI. Running and serving the
> community well, we would certainly happy to use a different name if asked by
> the trademark.
>
> TQ
>
> On Fri, Aug 28, 2020 at 8:49 PM Tianqi Chen  wrote:
>
>> tvmlang.org was an old url by the project that eventually got deprecated
>> at some time point, it now redirects to the https://tvm.apache.org/
>>
>> The PMC makes sure to redirect to the static Apache project when possible
>> for official project related information.
>>
>> Due to the mechanism of the discourse website(need an active server), and
>> CI (tracking is not used and is removed). It is necessary to use a
>> standalone domain name
>> - These domains are maintained by volunteers from TVM PMC members
>> (tqchen, yizhi, haichen, jroesch, ziheng, lianminzheng, zhiics, masahi,
>> thierry from different organizations)
>>   as a thirdparty service to help the community.
>> - Given that these domains are not used to represent the official apache
>> project website(no confusion), and the usage voted by the community [2],
>>   the PPMC believes it is fair to use these domains to serve the
>> community, just like the use of thirdparty conference website for some of
>> the ASF projects' developer conferences.
>> - Of course we would love to get approval/feedback from the trademark. We
>> have started a trademark thread on the community discourse forum domain
>> [1],
>>and would be more than happy to follow up the guidance of the
>> trademark discussion.
>>
>> Again the hopefully outcome is not to discourage the use of these
>> services. The PMC members strive to make sure that these thirdparty
>> services are sustained,
>> and remain "non-blocker" even when they go down.
>>
>> - Introduce multiple volunteers from different organizations in the PMC
>> to do the work.
>> - Make sure the messages are backed up to mail-list.
>> - In the case of CI, have a clear workflow(JenkinsFile) and docker source
>> so that any committer could have spin up CI when necessary.
>> - Every development activities (also) happens on dev@
>>
>>
>> TQ
>>
>> ---
>> - [1]
>> https://lists.apache.org/thread.html/rd23004bf526975fceebd1b0bae7120dc1935bb61b7cdd8243fbc36dd%40%3Ctrademarks.apache.org%3E
>> - [2]
>> https://lists.apache.org/thread.html/c34b728f01d1030146594e47e0706cd1990ed731d06e3c179b7d501a%40%3Cdev.tvm.apache.org%3E
>>
>>
>> On Fri, Aug 28, 2020 at 8:20 PM Justin Mclean 
>> wrote:
>>
>>> Hi,
>>>
>>> Sorry my mistake, I meant to say tvm.ai not tvm.io, but as I said
>>> subdomains on tvm.ai are not redirecting. For instance discuss.tvm.ai
>>> stays as it is. Other sub-domains include ci.tvm.ai , tracking.tvm.ai
>>> and docs.tvm.ai that I’ve found. There might be others, of those four,
>>> only docs redirects.
>>>
>>> I notice that forum [1] also states "Open source community on end to end
>>> stack for deploying deep learning workloads to hardware backends
>>> tvmlang.org.” Who controls tvmlang.org? It not clear on that page that
>>> this is a space for discussion about an Apache project.
>>>
>>> Thanks,
>>> Justin
>>>
>>> 1. https://discuss.tvm.ai
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

We have also talked to Apache INFRA about the use of the https://ci.tvm.ai/ due
to the need of special setups in terms of GPU based resources etc.

So far we have received warm help from the INFRA and they are super helpful
in helping setting up CI hooks so that the community can enjoy quick
development with the volunteer maintained CI. Running and serving the
community well, we would certainly happy to use a different name if asked by
the trademark.

TQ

On Fri, Aug 28, 2020 at 8:49 PM Tianqi Chen  wrote:

> tvmlang.org was an old url by the project that eventually got deprecated
> at some time point, it now redirects to the https://tvm.apache.org/
>
> The PMC makes sure to redirect to the static Apache project when possible
> for official project related information.
>
> Due to the mechanism of the discourse website(need an active server), and
> CI (tracking is not used and is removed). It is necessary to use a
> standalone domain name
> - These domains are maintained by volunteers from TVM PMC members (tqchen,
> yizhi, haichen, jroesch, ziheng, lianminzheng, zhiics, masahi, thierry from
> different organizations)
>   as a thirdparty service to help the community.
> - Given that these domains are not used to represent the official apache
> project website(no confusion), and the usage voted by the community [2],
>   the PPMC believes it is fair to use these domains to serve the
> community, just like the use of thirdparty conference website for some of
> the ASF projects' developer conferences.
> - Of course we would love to get approval/feedback from the trademark. We
> have started a trademark thread on the community discourse forum domain
> [1],
>and would be more than happy to follow up the guidance of the trademark
> discussion.
>
> Again the hopefully outcome is not to discourage the use of these
> services. The PMC members strive to make sure that these thirdparty
> services are sustained,
> and remain "non-blocker" even when they go down.
>
> - Introduce multiple volunteers from different organizations in the PMC to
> do the work.
> - Make sure the messages are backed up to mail-list.
> - In the case of CI, have a clear workflow(JenkinsFile) and docker source
> so that any committer could have spin up CI when necessary.
> - Every development activities (also) happens on dev@
>
>
> TQ
>
> ---
> - [1]
> https://lists.apache.org/thread.html/rd23004bf526975fceebd1b0bae7120dc1935bb61b7cdd8243fbc36dd%40%3Ctrademarks.apache.org%3E
> - [2]
> https://lists.apache.org/thread.html/c34b728f01d1030146594e47e0706cd1990ed731d06e3c179b7d501a%40%3Cdev.tvm.apache.org%3E
>
>
> On Fri, Aug 28, 2020 at 8:20 PM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> Sorry my mistake, I meant to say tvm.ai not tvm.io, but as I said
>> subdomains on tvm.ai are not redirecting. For instance discuss.tvm.ai
>> stays as it is. Other sub-domains include ci.tvm.ai , tracking.tvm.ai
>> and docs.tvm.ai that I’ve found. There might be others, of those four,
>> only docs redirects.
>>
>> I notice that forum [1] also states "Open source community on end to end
>> stack for deploying deep learning workloads to hardware backends
>> tvmlang.org.” Who controls tvmlang.org? It not clear on that page that
>> this is a space for discussion about an Apache project.
>>
>> Thanks,
>> Justin
>>
>> 1. https://discuss.tvm.ai
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

tvmlang.org was an old url by the project that eventually got deprecated at
some time point, it now redirects to the https://tvm.apache.org/

The PMC makes sure to redirect to the static Apache project when possible
for official project related information.

Due to the mechanism of the discourse website(need an active server), and
CI (tracking is not used and is removed). It is necessary to use a
standalone domain name
- These domains are maintained by volunteers from TVM PMC members (tqchen,
yizhi, haichen, jroesch, ziheng, lianminzheng, zhiics, masahi, thierry from
different organizations)
  as a thirdparty service to help the community.
- Given that these domains are not used to represent the official apache
project website(no confusion), and the usage voted by the community [2],
  the PPMC believes it is fair to use these domains to serve the community,
just like the use of thirdparty conference website for some of the ASF
projects' developer conferences.
- Of course we would love to get approval/feedback from the trademark. We
have started a trademark thread on the community discourse forum domain
[1],
   and would be more than happy to follow up the guidance of the trademark
discussion.

Again the hopefully outcome is not to discourage the use of these services.
The PMC members strive to make sure that these thirdparty services are
sustained,
and remain "non-blocker" even when they go down.

- Introduce multiple volunteers from different organizations in the PMC to
do the work.
- Make sure the messages are backed up to mail-list.
- In the case of CI, have a clear workflow(JenkinsFile) and docker source
so that any committer could have spin up CI when necessary.
- Every development activities (also) happens on dev@


TQ

---
- [1]
https://lists.apache.org/thread.html/rd23004bf526975fceebd1b0bae7120dc1935bb61b7cdd8243fbc36dd%40%3Ctrademarks.apache.org%3E
- [2]
https://lists.apache.org/thread.html/c34b728f01d1030146594e47e0706cd1990ed731d06e3c179b7d501a%40%3Cdev.tvm.apache.org%3E


On Fri, Aug 28, 2020 at 8:20 PM Justin Mclean 
wrote:

> Hi,
>
> Sorry my mistake, I meant to say tvm.ai not tvm.io, but as I said
> subdomains on tvm.ai are not redirecting. For instance discuss.tvm.ai
> stays as it is. Other sub-domains include ci.tvm.ai , tracking.tvm.ai and
> docs.tvm.ai that I’ve found. There might be others, of those four, only
> docs redirects.
>
> I notice that forum [1] also states "Open source community on end to end
> stack for deploying deep learning workloads to hardware backends
> tvmlang.org.” Who controls tvmlang.org? It not clear on that page that
> this is a space for discussion about an Apache project.
>
> Thanks,
> Justin
>
> 1. https://discuss.tvm.ai
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

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 
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
>
>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Ming.

Certainly, different PMC can take a different approach towards release.
We are not suggesting that every PMC should take our approach.
In the particular case of TVM, the community has been working on several
major features including Ansor, uTVM and it does not make sense to cut
the release say right now.

Again, the PPMC wants to produce high quality releases according to feature
plans coordinated with the community, rather than creating more releases.
Notably the last release was pretty recent as well.

While there is one release manager in the past two releases, many PPMC
members(including myself) participated in the release to make sure that
release is in high quality.
I imagine I could have added my name to the release manager as well :) Also
the PMC contains several Apache members who have previous experiences in
cutting releases in TLP projects. So we are very confident that the PMC can
continue to do so.

TQ

On Fri, Aug 28, 2020 at 7:25 PM Ming Wen  wrote:

> I think only two releases and only one release manager are blocking issues.
>  Considering that TVM merges 150 PRs a month on average, but only two
> releases within a year and a half, that is, users use codes that are much
> behind the master, which is not friendly to the community.
>
> Second, there is no conflict between high-quality releases and frequent
> releases. Many Apache projects have maintained frequent and high-quality
> releases.
>
> Third, since there is a good release document, why is there no other ppmc
> to serve as release manager?
>
> Tianqi Chen  于 2020年8月29日周六 上午9:51写道：
>
> > Thanks Matt!
> >
> > That was indeed the approach we used before. The main problem of this
> > approach is
> > - There could be certain upstream changes (say tensorflow get updated)
> that
> > may not retrigger the rebuild
> > - The CI instance itself can quickly get crowded by the historical cached
> > images and causes disk overflow problems.
> > - Overall we find it is very hard to reproduce the CI error when there
> is a
> > problem because of the potential mismatch(due to stale build)
> >
> > So the community switched to using a stable binary tag as for more stable
> > env without blocking the CI, while periodically updating
> > these images when this is a dependency change.
> >
> > TQ
> >
> > On Fri, Aug 28, 2020 at 6:47 PM Matt Sicker  wrote:
> >
> > > Is there even a need to upload the Docker images for CI? Docker
> > recognizes
> > > layers by checksums, so CI build agents will cache the image layers
> > > regardless of whether or not you upload them to Docker Hub. Layers get
> > > rebuilt when the Docker file changes or you force an update.
> > >
> > > On Fri, Aug 28, 2020 at 20:12 Tianqi Chen  wrote:
> > >
> > > > Thanks Justin and Henry for the discussion thread.
> > > >
> > > >
> > > >
> > > > Please allow me to dissect and summarize again some of the discussion
> > > >
> > > > points:)
> > > >
> > > >
> > > >
> > > > C0: Docker Image
> > > >
> > > > - There was a mis-understanding that the docker image like ci-gpu
> > > >
> > > >   contains tvm. They do not, and instead contain an environment to
> > > >
> > > >   build and run test cases.
> > > >
> > > > - The thirdparty binary cache is used to speed up the test build.
> > Anyone
> > > >
> > > >   could build these binaries from a TVM source.
> > > >
> > > > - To avoid confusion about the branding, we have renamed the docker
> hub
> > > >
> > > > name to
> > > >
> > > >   a different name that does not contain tvm so that it is clear as a
> > > >
> > > > thirdparty.
> > > >
> > > >
> > > >
> > > > C1: Pointing to Apache Release
> > > >
> > > > - The PPMC 100% agree that we should produce high-quality Apache
> > > >
> > > >   compatible releases, and refer to them in the documents.
> > > >
> > > > - The installation documentation points to the official release
> > download
> > > >
> > > > page [1].
> > > >
> > > > - There is a for developer section, which gives instructions to
> > > developers
> > > >
> > > > about
> > > >
> > > >   how to clone the code from the git repo.
> > > >
> > > >
> > > >
> > > > C2: Number of rele

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Matt!

The main reason we used thirdparty(as stated above) is that the TVM PPMC
believes it is important to
protect the Apache brand and release policy(artifact being compatible
apache).
Given some of the optional test packages (e.g. pytorch/tensorflow) are not
what we could control,
and it is hard to validate their compatibility. There are also similar
issues around specific
runtime environments like cuda. Note that CI images are not artifacts that
we release, but merely
as a way to setup the ci build env.

So to keep things simple and clean from branding/licensing concerns, we use
a thirdparty and
clearly distinguish them from ASF artifacts. To the development, there is
no strict location requirement as
long as we can point to a cache. And the cache location can be changed at
any time point by any committer.

TQ

On Fri, Aug 28, 2020 at 7:13 PM Matt Sicker  wrote:

> Makes sense. Do you think the recent changes to Docker Hub will affect
> this? It might be a good idea to move the images into the Apache org, even
> if they’re not for end users.
>
> On Fri, Aug 28, 2020 at 20:52 Tianqi Chen  wrote:
>
> > Thanks Matt!
> >
> >
> >
> > That was indeed the approach we used before. The main problem of this
> >
> > approach is
> >
> > - There could be certain upstream changes (say tensorflow get updated)
> that
> >
> > may not retrigger the rebuild
> >
> > - The CI instance itself can quickly get crowded by the historical cached
> >
> > images and causes disk overflow problems.
> >
> > - Overall we find it is very hard to reproduce the CI error when there
> is a
> >
> > problem because of the potential mismatch(due to stale build)
> >
> >
> >
> > So the community switched to using a stable binary tag as for more stable
> >
> > env without blocking the CI, while periodically updating
> >
> > these images when this is a dependency change.
> >
> >
> >
> > TQ
> >
> >
> >
> > On Fri, Aug 28, 2020 at 6:47 PM Matt Sicker  wrote:
> >
> >
> >
> > > Is there even a need to upload the Docker images for CI? Docker
> > recognizes
> >
> > > layers by checksums, so CI build agents will cache the image layers
> >
> > > regardless of whether or not you upload them to Docker Hub. Layers get
> >
> > > rebuilt when the Docker file changes or you force an update.
> >
> > >
> >
> > > On Fri, Aug 28, 2020 at 20:12 Tianqi Chen  wrote:
> >
> > >
> >
> > > > Thanks Justin and Henry for the discussion thread.
> >
> > > >
> >
> > > >
> >
> > > >
> >
> > > > Please allow me to dissect and summarize again some of the discussion
> >
> > > >
> >
> > > > points:)
> >
> > > >
> >
> > > >
> >
> > > >
> >
> > > > C0: Docker Image
> >
> > > >
> >
> > > > - There was a mis-understanding that the docker image like ci-gpu
> >
> > > >
> >
> > > >   contains tvm. They do not, and instead contain an environment to
> >
> > > >
> >
> > > >   build and run test cases.
> >
> > > >
> >
> > > > - The thirdparty binary cache is used to speed up the test build.
> > Anyone
> >
> > > >
> >
> > > >   could build these binaries from a TVM source.
> >
> > > >
> >
> > > > - To avoid confusion about the branding, we have renamed the docker
> hub
> >
> > > >
> >
> > > > name to
> >
> > > >
> >
> > > >   a different name that does not contain tvm so that it is clear as a
> >
> > > >
> >
> > > > thirdparty.
> >
> > > >
> >
> > > >
> >
> > > >
> >
> > > > C1: Pointing to Apache Release
> >
> > > >
> >
> > > > - The PPMC 100% agree that we should produce high-quality Apache
> >
> > > >
> >
> > > >   compatible releases, and refer to them in the documents.
> >
> > > >
> >
> > > > - The installation documentation points to the official release
> > download
> >
> > > >
> >
> > > > page [1].
> >
> > > >
> >
> > > > - There is a for developer section, which gives instructions to
> >
> > > developers
> >
> > &g

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Matt!

That was indeed the approach we used before. The main problem of this
approach is
- There could be certain upstream changes (say tensorflow get updated) that
may not retrigger the rebuild
- The CI instance itself can quickly get crowded by the historical cached
images and causes disk overflow problems.
- Overall we find it is very hard to reproduce the CI error when there is a
problem because of the potential mismatch(due to stale build)

So the community switched to using a stable binary tag as for more stable
env without blocking the CI, while periodically updating
these images when this is a dependency change.

TQ

On Fri, Aug 28, 2020 at 6:47 PM Matt Sicker  wrote:

> Is there even a need to upload the Docker images for CI? Docker recognizes
> layers by checksums, so CI build agents will cache the image layers
> regardless of whether or not you upload them to Docker Hub. Layers get
> rebuilt when the Docker file changes or you force an update.
>
> On Fri, Aug 28, 2020 at 20:12 Tianqi Chen  wrote:
>
> > Thanks Justin and Henry for the discussion thread.
> >
> >
> >
> > Please allow me to dissect and summarize again some of the discussion
> >
> > points:)
> >
> >
> >
> > C0: Docker Image
> >
> > - There was a mis-understanding that the docker image like ci-gpu
> >
> >   contains tvm. They do not, and instead contain an environment to
> >
> >   build and run test cases.
> >
> > - The thirdparty binary cache is used to speed up the test build. Anyone
> >
> >   could build these binaries from a TVM source.
> >
> > - To avoid confusion about the branding, we have renamed the docker hub
> >
> > name to
> >
> >   a different name that does not contain tvm so that it is clear as a
> >
> > thirdparty.
> >
> >
> >
> > C1: Pointing to Apache Release
> >
> > - The PPMC 100% agree that we should produce high-quality Apache
> >
> >   compatible releases, and refer to them in the documents.
> >
> > - The installation documentation points to the official release download
> >
> > page [1].
> >
> > - There is a for developer section, which gives instructions to
> developers
> >
> > about
> >
> >   how to clone the code from the git repo.
> >
> >
> >
> > C2: Number of releases
> >
> > - The PPMC wants to produce high quality releases according to feature
> >
> >   plan coordinated with the community, rather than creating more
> releases.
> >
> > - The release process is well documented[2],
> >
> > - Per incubator policy[2], number of releases is not a hard bar for
> >
> > graduation.
> >
> >   "Podlings do not need to actually publish a release...". Instead the
> most
> >
> > important
> >
> >   thing is the demonstration of being able to cut apache release.
> >
> > - Besides the release process being well documented and there are already
> >
> >   two high-quality releases(without WIP). The PMC contains several Apache
> >
> > members
> >
> >   who have previous experiences in cutting releases in TLP projects.
> >
> >   We are very confident that the PMC can continue to do so.
> >
> >
> >
> > C3: The discourse forum
> >
> > - The discourse forum, like the use of github, is mainly a way for user
> >
> > community to
> >
> >   engage with the project.
> >
> > - The usage of discourse forum is voted by the community[3]
> >
> > - The community follows the public archive principle, which means
> >
> > everything is archived
> >
> >   to mail-lists. Again, everything happens (also) happens on a mail-list.
> >
> > - The discourse forum is currently maintained by a few PMC members as
> >
> > volunteers,
> >
> >   as a thirdparty service to the community.
> >
> > - Again, the development happens in github, everything mirrored in dev@.
> >
> > The existence of the forum
> >
> >   would not block the development.
> >
> >
> >
> > Finally, to summarize. I believe one of the main reasons behind these
> >
> > issues are trust rather than procedural.
> >
> > As a ASF member, I am certainly strive to make sure the related volunteer
> >
> > maintained resources
> >
> > will continue beyond a certain individual by many ways including:
> >
> >
> >
> > - Introduce multiple volunteers from different organizations in the PMC
> to
> >
> > do the work.

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Justin and Henry for the discussion thread.

Please allow me to dissect and summarize again some of the discussion
points:)

C0: Docker Image
- There was a mis-understanding that the docker image like ci-gpu
  contains tvm. They do not, and instead contain an environment to
  build and run test cases.
- The thirdparty binary cache is used to speed up the test build. Anyone
  could build these binaries from a TVM source.
- To avoid confusion about the branding, we have renamed the docker hub
name to
  a different name that does not contain tvm so that it is clear as a
thirdparty.

C1: Pointing to Apache Release
- The PPMC 100% agree that we should produce high-quality Apache
  compatible releases, and refer to them in the documents.
- The installation documentation points to the official release download
page [1].
- There is a for developer section, which gives instructions to developers
about
  how to clone the code from the git repo.

C2: Number of releases
- The PPMC wants to produce high quality releases according to feature
  plan coordinated with the community, rather than creating more releases.
- The release process is well documented[2],
- Per incubator policy[2], number of releases is not a hard bar for
graduation.
  "Podlings do not need to actually publish a release...". Instead the most
important
  thing is the demonstration of being able to cut apache release.
- Besides the release process being well documented and there are already
  two high-quality releases(without WIP). The PMC contains several Apache
members
  who have previous experiences in cutting releases in TLP projects.
  We are very confident that the PMC can continue to do so.

C3: The discourse forum
- The discourse forum, like the use of github, is mainly a way for user
community to
  engage with the project.
- The usage of discourse forum is voted by the community[3]
- The community follows the public archive principle, which means
everything is archived
  to mail-lists. Again, everything happens (also) happens on a mail-list.
- The discourse forum is currently maintained by a few PMC members as
volunteers,
  as a thirdparty service to the community.
- Again, the development happens in github, everything mirrored in dev@.
The existence of the forum
  would not block the development.

Finally, to summarize. I believe one of the main reasons behind these
issues are trust rather than procedural.
As a ASF member, I am certainly strive to make sure the related volunteer
maintained resources
will continue beyond a certain individual by many ways including:

- Introduce multiple volunteers from different organizations in the PMC to
do the work.
- Make sure the messages are backed up to mail-list.
- Help INFRA to manage certain services instead if they are willing.
However, note in cases like CI
  INFRA is also happy to let the PMC make specific choices.

While many of the arguments in the above points boils down to "what if the
few people did something evil via loophole X".
And similar arguments can be applied to committer nominations in general.
As I may quote from our committer
nomination message "We like to work on trust rather than unnecessary
constraints".
This is the message that keeps bringing me back and makes me proud as a ASF
member.

There is no "one way" to the Apache way[3]. IMHO, the best thing I love
about the ASF is indeed the people, and the
trust we give to each PMC as long as things are operated under the Apache
Way. The TVM PPMC has been working hard to
build a healthy, diverse and independent community. And strives to protect
the Apache brand and uphold apache release policy.
Again, we welcome constructive feedback for continued improvement.

Thank you!

TQ

-
- [1]
https://tvm.apache.org/docs/install/from_source.html#install-from-source
- [2] https://incubator.apache.org/guides/graduation.html
- [3]
https://lists.apache.org/thread.html/c34b728f01d1030146594e47e0706cd1990ed731d06e3c179b7d501a%40%3Cdev.tvm.apache.org%3E
- [4] https://www.apache.org/theapacheway/

On Fri, Aug 28, 2020 at 5:15 PM Henry Saputra 
wrote:

> Sure, that is easy to fix and good suggestion. But, hope it is not a
> blocker issue.
>
> On Fri, Aug 28, 2020, 5:09 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > The "install from source” page should probably point people to the source
> > releases rather than the latest code in GitHub.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Hi Justin:

Again to further clarify the Docker image.

First of all, the PPMC is 100% with you that it is NOT fine to
release docker images with the Apache brand, or not following the
apache official release tag.

The test cache binary used by TVM CI is a different thing.
As the docker image itself is being used for test CI environment purposes.
For example ci-cpu contains the gcc compiler and deps like python,
tensorflow
in order to run the tests. The docker image itself does not contain TVM in
any form.

In order to use the ci-cpu, a developer would need to download a source,
enter the ci-cpu environment, and then type make to build tvm inside.


Q0: Why tag mismatch from Apache release tag

Whenever a ci dependency environment changes(e.g. we want to test against a
new version of tensorflow)
during development. We need to generate a new CI image for the test.
To generate a binary cache for the particular purpose of testing, we use a
new tag.
That is why the tag does not follow the Apache release tag because they are
different thing.

Q1: Why use thirdparty docker

The CI test environment can contain additional dependencies, e.g.
tensorflow/pytorch that may or maynot
be 100% Apache compatible. Because they are only used by the test cases and
are not dependency of the tvm itself.
We choose to use thirdparty binary caches, to simplify trademark concerns.
As per previous comment, we believe this is allowed

Q2: Branding

As mentioned in the above post, we agree that the name tvmai as a
thirdparty binary cache can be confusing,
and will move it to a name that is clearly thirdparty.

Q3: Pointing people to source releases

The PPMC is very mindful to only refer to the official Apache release as
official releases.

The install from source page indeed points people to the official Apache
release!
Note that the mention of github source explicitly contains "Developers
keyword".

TQ

---

- [1]
https://tvm.apache.org/docs/install/from_source.html#install-from-source


On Fri, Aug 28, 2020 at 5:14 PM Henry Saputra 
wrote:

> Look like TQ has given you answer and proposed solution about the Docker
> images.
>
> Hope that helps.
>
> On Fri, Aug 28, 2020, 5:01 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > I am sure there are many other binary packaging out there that use
> Apache
> > > project names, for example this one for Apache Spark:
> > > https://hub.docker.com/r/bitnami/spark/
> >
> > What other Apache projects do (Spark in particular for various reasons)
> > are not always good examples to follow. But you'll note in this case it:
> > a) Calls it Apache Spark
> > b) Includes a link to space.apache.org
> > b) In this case it seem clear it is a 3rd party, unlike TVM.
> >
> > IMO It should also have a trademark disclaimer and I’m not sure that the
> > way they have set up latest would be compliant with ASF policy. Ignoring
> > the latest tag you note that the tags also match Apache releases.
> >
> > > Are you concern about the name? The Docker image hub clearly stated
> this
> > is
> > > not official Docker image from Apache TVM podling. I think that is
> enough
> > > to indicate this is not done by Apache TVM as community.
> >
> > The docker images, if you found them on their own, give no indication
> that
> > is an Apache project or that this are not official releases. If I search
> > for “docker tvm” I get this link [1]. There is very little information on
> > that page, no recognition of Apache trademarks and no disclaimers.There
> are
> > also versions tagged that are not Apache releases.
> >
> > Why didn’t the project use Infra’a docker offering? [3]
> >
> > > And I am kind of surprise about your comment and question about the
> > number
> > > of downloads.
> >
> > A large number of downloads may indicate that users are using the docker
> > images rather than the offical sources. This may be fine if they are
> > released versions, but is probably not be fine if they are not. Hence the
> > latest tag being problematic.
> >
> > I find it odd in the TVM case there are more releases in Docker using the
> > same numbering system as the Apache releases. Why this discrepancy?
> >
> > Thanks,
> > Justin
> >
> > 1. https://hub.docker.com/u/tvmai
> > 2. https://www.apache.org/foundation/marks/#products
> > 3. https://hub.docker.com/u/apache
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Henry.

In this case, we choose the thirdparty for binary testing cache in
particular to simplify the trademark concerns
(since we do not want to vet the license of the test env). Which I believe
is allowed.

In terms of the docker image source, the community strives to release
source releases that are 100% Apache compatible.
The users can optionally build these docker images from the source.

TQ


On Fri, Aug 28, 2020 at 4:44 PM Henry Saputra 
wrote:

> The Apache does have official Docker hub [1].
>
> So, the TVM PPMC could, in the near future, create Docker images for Apache
> TVM for official distribution to help people quickly consume and run the
> source code releases.
>
>
>
> [1] https://hub.docker.com/u/apache
>
>
> On Fri, Aug 28, 2020, 4:29 PM Tianqi Chen  wrote:
>
> > Thanks Justin!
> >
> > Docker Images and Downloads Stats
> >
> > - These images are indeed only used for testing purposes.
> >   Note that there are more than 150 PRs every month, results in more than
> >   tens of thousands of tests being triggered.
> >   Every now and then the CI machine need to pull the fresh new image
> after
> >   the cache is cleared. So it is understandable that they have more than
> 4K
> > Downloads
> > - As a additional note. The image DOES NOT contain TVM in any form. It
> only
> > contains
> >   the build env that makes it easy to build tvm. So even if someone want
> to
> > download
> >   the
> >
> > Advertisement of Docker Page in the Docs
> > - As you rightfully points out, the installation page advertises the
> docker
> > page[1],
> >   however note that the majority of the docker page contains instructions
> > to build
> >   the image from source, which is totally fine because source are 100%
> > Apache compatible.
> > - When docker image is referred in other place of the documents, they
> > refers to the docker image
> >   build from the Apache source release[2].
> > - Base on the same rationale of priorizing Apache compatible branding
> over
> > thirdparties,
> >   we always first mention how build from source first.
> > - When reference to thirdparty image is mentioned, a clear disclaimer is
> > being used
> >   indicating that they are not apache release.
> >
> > - [1] https://tvm.apache.org/docs/install/index.html
> > - [2] https://tvm.apache.org/docs/install/docker.html
> >
> > On Fri, Aug 28, 2020 at 4:24 PM Justin Mclean 
> > wrote:
> >
> > > Hi,
> > >
> > > On that installation pages it does says "We provide docker utility
> > scripts
> > > to help developers to setup development environment. They are also
> > helpful
> > > run through TVM demo and tutorials.” and "You can find some un-official
> > > prebuilt images in https://hub.docker.com/r/tvmai/.” IMO this doesn’t
> > > match with them being just CI images used for testing.
> > >
> > > With the documentation I note in one place it says "to use the official
> > > Docker Image.”
> > >
> > > Thanks,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

To follow up the comment on docker image, as I mentioned in my previous
email.

We are changing the use of docker hub name to a new name that does not
contain tvm https://github.com/apache/incubator-tvm/pull/6360
The tvmai docker hub will be removed after the PR is merged
As I stated in my previous email. The PPMC strives to protect the Apache
brand, and we appreciate your comment on the docker binary cache name.

We would certainly love further constructive feedback on this topic.

Thanks
TQ

On Fri, Aug 28, 2020 at 4:34 PM Henry Saputra 
wrote:

> Hi Justin,
>
> I am sure there are many other binary packaging out there that use Apache
> project names, for example this one for Apache Spark:
> https://hub.docker.com/r/bitnami/spark/
>
> Are you concern about the name? The Docker image hub clearly stated this is
> not official Docker image from Apache TVM podling. I think that is enough
> to indicate this is not done by Apache TVM as community.
>
> And I am kind of surprise about your comment and question about the number
> of downloads. We could not regulate how many people try to dowload the
> images.
>
> - Henry
>
>
> On Fri, Aug 28, 2020, 4:16 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > Then why do they have 40K+ downloads? It also doesn’t explain the
> > version numbers.
> >
> > Sorry 4K I misread that, but even that seem high for something that is
> > used for testing.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Justin!

Docker Images and Downloads Stats

- These images are indeed only used for testing purposes.
  Note that there are more than 150 PRs every month, results in more than
  tens of thousands of tests being triggered.
  Every now and then the CI machine need to pull the fresh new image after
  the cache is cleared. So it is understandable that they have more than 4K
Downloads
- As a additional note. The image DOES NOT contain TVM in any form. It only
contains
  the build env that makes it easy to build tvm. So even if someone want to
download
  the

Advertisement of Docker Page in the Docs
- As you rightfully points out, the installation page advertises the docker
page[1],
  however note that the majority of the docker page contains instructions
to build
  the image from source, which is totally fine because source are 100%
Apache compatible.
- When docker image is referred in other place of the documents, they
refers to the docker image
  build from the Apache source release[2].
- Base on the same rationale of priorizing Apache compatible branding over
thirdparties,
  we always first mention how build from source first.
- When reference to thirdparty image is mentioned, a clear disclaimer is
being used
  indicating that they are not apache release.

- [1] https://tvm.apache.org/docs/install/index.html
- [2] https://tvm.apache.org/docs/install/docker.html

On Fri, Aug 28, 2020 at 4:24 PM Justin Mclean 
wrote:

> Hi,
>
> On that installation pages it does says "We provide docker utility scripts
> to help developers to setup development environment. They are also helpful
> run through TVM demo and tutorials.” and "You can find some un-official
> prebuilt images in https://hub.docker.com/r/tvmai/.” IMO this doesn’t
> match with them being just CI images used for testing.
>
> With the documentation I note in one place it says "to use the official
> Docker Image.”
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Justin for bringing up these points!

P0: tvm.ai domain

- As you can see that the domain redirects to https://tvm.apache.org/.
  So hopefully there is no confusion here.

P2: releases
- The PPMC has a well documented release process[1]
  that anyone can go and produce a release.
- While we understand that it is good to produce more releases,
  hopefully it is not a hard blocker, as the most important thing
  for the PMC to be able to make high-quality Apache releases.

P1: Recognizing reviewers and form of contribution
- As said in the above email, the PPMC considers all forms of
contributions, including
  but not limited to code reviews, code, community building, documentation.
- Just like the (un-official) maturity model, which serves the goal to help
community growth,
  it is not a gatekeeper in anyform. There is nothing that prevents a PMC
member to discuss
  the case of non-code contributors, bringing them in as reviewer (to keep
them in the loop of these perspectives),
  or as committer.
- As a fact, community interaction and contributions documentation and
building are actively being discussed
  and leads to some of the latest committer nominations

P2: Docker image

- These docker images do not contain tvm, instead they contain CI
environment
  to set up dependencies(e.g. compilers libraries) for running integration
tests.
- These images are not Apache releases, there is a clear disclaimer
  that they are thirdparty and not part of the ASF release[1].
  We would be more than happy to improve disclaimer.
- These images can be built by anyone from the source in the TVM repo (not
depending on a single person).
  The docker hub image mainly serves as a cache to make sure the CI does
not have to
  rebuilt them each time.
- The docker caches are maintained by community volunteers, not wearing ASF
hat.
  In an event, say the cache image stops to work.
  The community can always self-operate, by picking a different cache, and
using the same script.
- We view it as similar cases where INFRA allows each project to use
thirdparty services
  for test and integration purposes. The bottom line though is not to
release non-official Apache
  artifacts as Apache.

P3: Trademark and Licensing

- The PPMC fully understands the importance of producing release
  that are 100% Apache compatible and has been doing so in the past two
releases[2].
- The PPMC also clearly understand the need to protect Apache brand, and
  clearly differentiate Apache release from thirdparty ones by adding
disclaimers[3] to places when they are referred to.
- To make things simple, the TVM community only produce source release[2]
  that are 100% Apache compatible.
- We agree that the use of tvmai as a docker hub org name for test cache is
a gray area,
  and might cause confusion for branding despite the disclaimer.
  To ensure better clarity, we will move these binary caches to a different
org
  name that does not contain tvm. Please note again these binaries are only
  used for integration test purposes, the community do not intend to
advertise them as Apache releases.

I think most of the concerns are around whether the community can protect
the Apache brand
and produce high quality apache releases. These are very important
perspectives, and
the PPMC is very committed to these goals,  and making sure that the
project can continue to thrive beyond
the support of a single organization, or participation of single individual:

- The release process is clearly documented.
- The test infra is completely checked into as source of the repo (100%
Apache), anyone can take over and reproduce.
- The documents, tutorials and other things points to
https://tvm.apache.org/.
- When necessary thirdparty items are mentioned, a clear disclaimer is
placed.
- A PMC member only nominates candidates from other organizations to
encourage diverse sustained community growth.
- Engage trademark for permission in terms of community driven event[4]

While we think that the community is matured enough to handle these
perspectives.
We would be more than happy to receive constructive feedback on how we can
continue to do better on these areas.

--
- [1] https://tvm.apache.org/docs/contribute/release_process
- [2] https://tvm.apache.org/download
- [3] https://tvm.apache.org/docs/install/docker.html
- [4]
https://lists.apache.org/thread.html/r8559979c58fb92f08f3e253522dc227a51313dafff2ec19076e1093c%40%3Ctrademarks.apache.org%3E

On Fri, Aug 28, 2020 at 3:08 PM Justin Mclean 
wrote:

> Hi,
>
> I’m also concerned that the person who seems responsible for these docker
> images seems to be the proposed chair of the project.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

%3Cdev.tvm.apache.org%3E
> > [2] https://github.com/apache/incubator-tvm/pull/4636
> >
> > Thanks,
> > Ming Wen, Apache APISIX & Apache SkyWalking
> > Twitter: _WenMing
> >
> >
> > Tianqi Chen  于2020年8月28日周五 上午1:58写道：
> >
> > > Thank you Dave!
> > >
> > > (1) They have invented a new position between Contributor and Committer
> > > > called “Reviewer”. I’m not sure why this was done. It seems to me
> that
> > > > these individuals should just become Committers.
> > > >
> > >
> > > Reviewer is not an official position, but as a way for us to encourage
> > > reviews and find potential candidates for committerships.
> > > We use the following disclaimer which we sent during discussion a
> > reviewer
> > > case and not vote is carried out(to lower bar of entry)
> > >
> > > Background: A Reviewer is not an official role, the community use this
> > > way to recognize potential committers early and bring them to the
> > > project development. Given the reviewer role is not official, we will
> > > only hold a discussion instead of a formal vote. We continue to follow
> > > the community’s principle to only nominate someone from a different
> > > organization.
> > >
> > > The recognition of (un-official) reviewer is voted by the community as
> > part
> > > of Apache transition plan
> > >
> > >
> >
> https://lists.apache.org/thread.html/c34b728f01d1030146594e47e0706cd1990ed731d06e3c179b7d501a%40%3Cdev.tvm.apache.org%3E
> > >
> > > We strongly believe in nurturing contributions, welcome members to the
> > > community, and help the community to grow organically under the Apache
> > way.
> > > The community is actively bringing in new committers, and we are doing
> so
> > > at a monthly rate.
> > > To encourage diversity and healthy growth the PPMC members strive to
> > make a
> > > more diverse community by only nominating people from a different
> > > organization.
> > > So there could be cases where a person from my own organization that I
> > > think should be nominated as a committer, but I wait until the person
> get
> > > recognized by a fellow PMC member
> > > from another organization. This wait usually won't be too long. Even
> > > better, the community members work together with each other,
> > > since  the most important factor is after all the community.
> > >
> > > (2) All discussions are threaded in GitHub and then reflected into the
> > > > dev@tvm mailing list. I just find this strange.
> > > >
> > >
> > > As per apache way, everything happens (also happens) on dev@tvm. We
> try
> > to
> > > set up the mechanism to enable maximum participation from the
> community,
> > > while complying with ASF rules :)
> > > The emails from the dev@tvm are also forwarded to the github thread.
> > >
> > >
> > >
> > > > Also, the discussion thread looks like a vote. Nothing is really
> > > discussed
> > > > about satisfying graduation requirements.
> > > >
> > > > Did TVM fill out a Maturity Model?
> > > >
> > >
> > > Please see the maturity model here
> > >
> > >
> >
> https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing
> > > The maturity model is attached as part of the community discussion as
> > > well(inlined in the email when community model is mentioned.
> > >
> > > TQ
> > >
> > >
> > > On Thu, Aug 27, 2020 at 10:43 AM Dave Fisher  wrote:
> > >
> > > >
> > > >
> > > > > On Aug 27, 2020, at 10:27 AM, Dave Fisher  wrote:
> > > > >
> > > > > Hi -
> > > > >
> > > > > I am bothered by two things that TVM does.
> > > > >
> > > > > (1) They have invented a new position between Contributor and
> > Committer
> > > > called “Reviewer”. I’m not sure why this was done. It seems to me
> that
> > > > these individuals should just become Committers.
> > > >
> > > > Looking a little more closely it seems that Reviewers ought to be PMC
> > > > Members. Please explain.
> > > >
> > > > >
> > > > > (2) All discussions are threaded in GitHub and then reflected into
> > the
> > > > dev@tvm mailing list. I just

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Ming.

While we agree that we have only done two releases so far, both of them are
high quality and follow the Apache release process.

We feel that the community is mature enough that we can push for graduation
as it is, and continue to push for high quality releases concurrently. It
also allows us to focus on cutting feature based releases and focus on
producing high quality releases than more releases.

While it is Yizhi takes the role of the release manager in the previous two
releases. The other PPMC members actively participate and help to create
new releases.
The release process is documented in detail here
https://tvm.apache.org/docs/contribute/release_process.html So that it can
be processed by any release manager.
For example, I could have done these releases as well(yizhi and I are from
different organizations).

So hopefully the number of releases won't be a blocker. Would love to hear
about constructive suggestions on how to improve a specific release or
release process though :)

TQ

On Thu, Aug 27, 2020 at 4:15 PM Ming Wen  wrote:

> I think Apache TVM need more Apache releases and more release manager.
> TVM has two apache releases(12/05/2019 and 07/10/2020), and ONLY one
> release manager(liuyizhi) [1].
>
> [1] https://incubator.apache.org/clutch/tvm.html
>
> Thanks,
> Ming Wen, Apache APISIX & Apache SkyWalking
> Twitter: _WenMing
>
>
> Henry Saputra  于2020年8月28日周五 上午4:44写道：
>
> > Yes, as Tianqi has mentioned, the PPMC members watch the commits and
> > development of TVM podling using Github notifications, which sent to dev@
> > list.
> > So, they are still in the podling list.
> >
> > And of course we can always review the commits@ list via Pony mail [1]
> > when
> > needed.
> >
> >
> > - Henry
> >
> > [1] https://lists.apache.org/list.html?comm...@tvm.apache.org
> >
> > On Thu, Aug 27, 2020 at 12:16 PM Tianqi Chen  wrote:
> >
> > > Thanks Dave!
> > >
> > >
> > > > With no one subscribed to commits@ how is the PPMC watching the
> > > codebase?
> > > >
> > >
> > > I believe most of us watch the codebase through github instead of the
> > > commits@.
> > > Note that the github discuss issues (VOTE, RFC, COMMUNITY) are
> forwarded
> > to
> > > dev@(rather than commits), so we can make sure that anyone who
> > > subscribed to dev@ can follow overall development, without having to
> be
> > > overwhelmed by the information in raw gituhb notifications.
> > >
> > > With only one PPMC member subscribed it would be better not to have
> > > > security list and instead count on securty@apache to inform
> > private@tvm.
> > >
> > >
> > > I agree that is our oversight, I created the security@mail-list, but
> > later
> > > realized that  we can count on securty@apache, the current security
> > guide
> > > https://tvm.apache.org/docs/dev/security.html already points to
> > > security@apache
> > > but I forget to ask infra to remove the list
> > >
> > > To address the question about bringing in people to the committers.
> > > The PPMC totally agrees about bringing in new members actively to the
> > > community! And we are doing so in a quite steady fashion.
> > >
> > > I agree that there could be some cases where a person's proposal could
> be
> > > slightly delayed, because I try to refrain from proposing new
> committers
> > > from our own orgs.
> > > But overall we find that our community members interact with each
> > > other(outside their organizations) more often, and usually my fellow
> PMC
> > > members bring them to the commiterships in a timely manner:)
> > > I also think a slight lag is understandable given that most PPMC
> members
> > > are volunteers from a diverse group and operate on their part time
> > > capacity.
> > >
> > > Given both principles (not nominating from same org and un-official
> > > reviewer) are voted by the community, and we use explicit disclaimer
> for
> > > the cases, I believe it still works under the ASF framework. Just like
> > the
> > > un-official maturity model used by the incubator, which serves a goal
> to
> > > the community to grow, rather than as a gatekeeper
> > >
> > > Again, we strive to continue the effort of bringing in new members to
> the
> > > community, and nurturing community growth as we do so now.
> > >
> > > TQ
> > >
> > >
> > >
> > > > Regards,
> > > > Dave
&g

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thanks Dave!


> With no one subscribed to commits@ how is the PPMC watching the codebase?
>

I believe most of us watch the codebase through github instead of the
commits@.
Note that the github discuss issues (VOTE, RFC, COMMUNITY) are forwarded to
dev@(rather than commits), so we can make sure that anyone who
subscribed to dev@ can follow overall development, without having to be
overwhelmed by the information in raw gituhb notifications.

With only one PPMC member subscribed it would be better not to have
> security list and instead count on securty@apache to inform private@tvm.


I agree that is our oversight, I created the security@mail-list, but later
realized that  we can count on securty@apache, the current security guide
https://tvm.apache.org/docs/dev/security.html already points to
security@apache
but I forget to ask infra to remove the list

To address the question about bringing in people to the committers.
The PPMC totally agrees about bringing in new members actively to the
community! And we are doing so in a quite steady fashion.

I agree that there could be some cases where a person's proposal could be
slightly delayed, because I try to refrain from proposing new committers
from our own orgs.
But overall we find that our community members interact with each
other(outside their organizations) more often, and usually my fellow PMC
members bring them to the commiterships in a timely manner:)
I also think a slight lag is understandable given that most PPMC members
are volunteers from a diverse group and operate on their part time capacity.

Given both principles (not nominating from same org and un-official
reviewer) are voted by the community, and we use explicit disclaimer for
the cases, I believe it still works under the ASF framework. Just like the
un-official maturity model used by the incubator, which serves a goal to
the community to grow, rather than as a gatekeeper

Again, we strive to continue the effort of bringing in new members to the
community, and nurturing community growth as we do so now.

TQ



> Regards,
> Dave
>
> >
> > Hope these answers help clarify your concerns and questions about the
> > Apache TVM community.
> >
> > Thanks,
> >
> > - Henry
> >
> > On Thu, Aug 27, 2020 at 10:58 AM Tianqi Chen  wrote:
> >
> >> Thank you Dave!
> >>
> >> (1) They have invented a new position between Contributor and Committer
> >>> called “Reviewer”. I’m not sure why this was done. It seems to me that
> >>> these individuals should just become Committers.
> >>>
> >>
> >> Reviewer is not an official position, but as a way for us to encourage
> >> reviews and find potential candidates for committerships.
> >> We use the following disclaimer which we sent during discussion a
> reviewer
> >> case and not vote is carried out(to lower bar of entry)
> >>
> >> Background: A Reviewer is not an official role, the community use this
> >> way to recognize potential committers early and bring them to the
> >> project development. Given the reviewer role is not official, we will
> >> only hold a discussion instead of a formal vote. We continue to follow
> >> the community’s principle to only nominate someone from a different
> >> organization.
> >>
> >> The recognition of (un-official) reviewer is voted by the community as
> part
> >> of Apache transition plan
> >>
> >>
> https://lists.apache.org/thread.html/c34b728f01d1030146594e47e0706cd1990ed731d06e3c179b7d501a%40%3Cdev.tvm.apache.org%3E
> >>
> >> We strongly believe in nurturing contributions, welcome members to the
> >> community, and help the community to grow organically under the Apache
> way.
> >> The community is actively bringing in new committers, and we are doing
> so
> >> at a monthly rate.
> >> To encourage diversity and healthy growth the PPMC members strive to
> make a
> >> more diverse community by only nominating people from a different
> >> organization.
> >> So there could be cases where a person from my own organization that I
> >> think should be nominated as a committer, but I wait until the person
> get
> >> recognized by a fellow PMC member
> >> from another organization. This wait usually won't be too long. Even
> >> better, the community members work together with each other,
> >> since  the most important factor is after all the community.
> >>
> >> (2) All discussions are threaded in GitHub and then reflected into the
> >>> dev@tvm mailing list. I just find this strange.
> >>>
> >>
> >> As per apache way, everything h

Re: [DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Thank you Dave!

(1) They have invented a new position between Contributor and Committer
> called “Reviewer”. I’m not sure why this was done. It seems to me that
> these individuals should just become Committers.
>

Reviewer is not an official position, but as a way for us to encourage
reviews and find potential candidates for committerships.
We use the following disclaimer which we sent during discussion a reviewer
case and not vote is carried out(to lower bar of entry)

Background: A Reviewer is not an official role, the community use this
way to recognize potential committers early and bring them to the
project development. Given the reviewer role is not official, we will
only hold a discussion instead of a formal vote. We continue to follow
the community’s principle to only nominate someone from a different
organization.

The recognition of (un-official) reviewer is voted by the community as part
of Apache transition plan
https://lists.apache.org/thread.html/c34b728f01d1030146594e47e0706cd1990ed731d06e3c179b7d501a%40%3Cdev.tvm.apache.org%3E

We strongly believe in nurturing contributions, welcome members to the
community, and help the community to grow organically under the Apache way.
The community is actively bringing in new committers, and we are doing so
at a monthly rate.
To encourage diversity and healthy growth the PPMC members strive to make a
more diverse community by only nominating people from a different
organization.
So there could be cases where a person from my own organization that I
think should be nominated as a committer, but I wait until the person get
recognized by a fellow PMC member
from another organization. This wait usually won't be too long. Even
better, the community members work together with each other,
since  the most important factor is after all the community.

(2) All discussions are threaded in GitHub and then reflected into the
> dev@tvm mailing list. I just find this strange.
>

As per apache way, everything happens (also happens) on dev@tvm. We try to
set up the mechanism to enable maximum participation from the community,
while complying with ASF rules :)
The emails from the dev@tvm are also forwarded to the github thread.



> Also, the discussion thread looks like a vote. Nothing is really discussed
> about satisfying graduation requirements.
>
> Did TVM fill out a Maturity Model?
>

Please see the maturity model here
https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing
The maturity model is attached as part of the community discussion as
well(inlined in the email when community model is mentioned.

TQ


On Thu, Aug 27, 2020 at 10:43 AM Dave Fisher  wrote:

>
>
> > On Aug 27, 2020, at 10:27 AM, Dave Fisher  wrote:
> >
> > Hi -
> >
> > I am bothered by two things that TVM does.
> >
> > (1) They have invented a new position between Contributor and Committer
> called “Reviewer”. I’m not sure why this was done. It seems to me that
> these individuals should just become Committers.
>
> Looking a little more closely it seems that Reviewers ought to be PMC
> Members. Please explain.
>
> >
> > (2) All discussions are threaded in GitHub and then reflected into the
> dev@tvm mailing list. I just find this strange.
> >
> > Also, the discussion thread looks like a vote. Nothing is really
> discussed about satisfying graduation requirements.
> >
> > Did TVM fill out a Maturity Model?
>
> I see you held that back until the VOTE thread.
>
> >
> > Regards,
> > Dave
> >
> >
> >> On Aug 24, 2020, at 2:04 PM, Tianqi Chen  wrote:
> >>
> >> Edit the subject so that it is obvious as a discussion thread in
> >> general@incubator.
> >>
> >> TQ
> >>
> >> FYI, following a heated discussion with great support from our mentors,
> >>> committers and community members.
> >>> The  Apache(incubating) TVM is starting a vote to graduate as TLP
> >>>
> >>> - [1] community DISCUSS thread:
> >>>
> https://lists.apache.org/thread.html/r91b8f469c6a54769869bb2435b7334a28bcff885ae078ab5612dae00%40%3Cdev.tvm.apache.org%3E
> >>> - [2] voting thread:
> >>>
> https://lists.apache.org/thread.html/rd5b8eefe49af09a2d0913758a5e5737b3fdb9072bc0becf4a2b2c7ee%40%3Cdev.tvm.apache.org%3E
> >>>
> >>> TQ
> >>>
> >>> -- Forwarded message -
> >>> From: Tianqi Chen 
> >>> Date: Mon, Aug 24, 2020 at 1:51 PM
> >>> Subject: [apache/incubator-tvm] [VOTE] Apache TVM Graduation (#6332)
> >>> To: apache/incubator-tvm 
> >>> Cc: Subscribed 
> >>>
> >>>
> >>> Dear Community:
> >>>

Re: [VOTE] Graduate Apache TVM as TLP

[Tianqi Chen]

Thanks Dave!

I have opened a discussion thread
https://lists.apache.org/thread.html/r215d3ecbd9bbf4db20dcaffa4fa2ec00e49e71fdcec7fa954d75f84a%40%3Cgeneral.incubator.apache.org%3E
about a while ago, and most of the original discussion happens in the
community thread(with mentors participating there).

Would be more than happy to continue discussion by opening up a new thread.

TQ

On Thu, Aug 27, 2020 at 10:30 AM Dave Fisher  wrote:

> I’m -1 (binding), because this is being rushed. I’ll be willing to change
> after there is actual discussion on general@.
>
> > On Aug 27, 2020, at 10:02 AM, Tianqi Chen  wrote:
> >
> > Dear Incubator:
> >
> > Following a heated discussion with great support from our mentors,
> > committers and community members.
> > The Apache(incubating) TVM community has formally voted for graduation
> and
> > bring the case to the IPMC.
> >
> > Please also see the community discussion thread[1] and voting thread[2]:
> >
> > This is a formal voting thread about Apache TVM's graduation, please
> Vote:
> > [ ] +1 - Recommend graduation of Apache TVM as a TLP
> > [ ]  0 - I don't feel strongly about it, but don't object
> > [ ] -1 - Do not recommend graduation of Apache TVM because...
> >
> > The VOTE will open for at least 72 hours.
> >
> > --
> > The TVM project has been an Apache incubator project for nearly 1.5 year
> > now. In the past one and half year, the community grew healthily under
> the
> > Apache way. Some highlights include:
> >
> > - A successful developer conference that we are continuing to host this
> year
> > - Great community growth, as of now, the community contains 16 PPMC
> > members, 31 committers, from a diverse list of organizations. We are
> > actively growing the list monthly.
> > - Active contributions: ~ 150 PRs merged each month.
> >
> > The community has produced two formal apache releases. While we could
> also
> > wait until more releases. We feel that the community is mature enough
> that
> > we can push for graduation as it is, and continue to push for high
> quality
> > releases concurrently.
> >
> > For reference, we also put together a maturity evaluation doc[3] under
> the
> > Apache maturity model.
> >
> > Some additional note about the resolution below: the current PPMC will be
> > transitioned to the PMC. We have invited all the mentors in the current
> > PPMC who like to stay involved.
> >
> > -
> >
> > Establish the Apache TVM Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to compilation of machine learning models to run on a wide range
> of
> > hardware platforms...
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache TVM Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache TVM Project be and hereby is responsible for
> the
> > creation and maintenance of software related to compilation of machine
> > learning models to run on a wide range of hardware platforms; and be it
> > further
> >
> > RESOLVED, that the office of "Vice President, Apache TVM" be and
> > hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache TVM
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache TVM
> > Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache TVM Project:
> >
> > * Tianqi Chen 
> > * Timothy Chen 
> > * Zhi Chen 
> > * Byung-Gon Chun 
> > * Ziheng Jiang 
> > * Furkan Kamaci 
> > * YiZhi Liu 
> > * Masahiro Masuda 
> > * Thierry Moreau 
> > * Jared Roesch 
> > * Henry Saputra 
> > * Haichen Shen 
> > * Markus Weimer 
> > * Eddie Yan 
> > * Lianmin Zheng 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tianqi Chen be appointed to
> > the office of Vice President, Apache TVM, to serve in accordance
> > with and subject to t

[VOTE] Graduate Apache TVM as TLP

[Tianqi Chen]

Dear Incubator:

Following a heated discussion with great support from our mentors,
committers and community members.
The Apache(incubating) TVM community has formally voted for graduation and
bring the case to the IPMC.

Please also see the community discussion thread[1] and voting thread[2]:

This is a formal voting thread about Apache TVM's graduation, please Vote:
[ ] +1 - Recommend graduation of Apache TVM as a TLP
[ ]  0 - I don't feel strongly about it, but don't object
[ ] -1 - Do not recommend graduation of Apache TVM because...

The VOTE will open for at least 72 hours.

--
The TVM project has been an Apache incubator project for nearly 1.5 year
now. In the past one and half year, the community grew healthily under the
Apache way. Some highlights include:

- A successful developer conference that we are continuing to host this year
- Great community growth, as of now, the community contains 16 PPMC
members, 31 committers, from a diverse list of organizations. We are
actively growing the list monthly.
- Active contributions: ~ 150 PRs merged each month.

The community has produced two formal apache releases. While we could also
wait until more releases. We feel that the community is mature enough that
we can push for graduation as it is, and continue to push for high quality
releases concurrently.

For reference, we also put together a maturity evaluation doc[3] under the
Apache maturity model.

Some additional note about the resolution below: the current PPMC will be
transitioned to the PMC. We have invited all the mentors in the current
PPMC who like to stay involved.

-

Establish the Apache TVM Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to compilation of machine learning models to run on a wide range of
hardware platforms...

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache TVM Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache TVM Project be and hereby is responsible for the
creation and maintenance of software related to compilation of machine
learning models to run on a wide range of hardware platforms; and be it
further

RESOLVED, that the office of "Vice President, Apache TVM" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache TVM
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache TVM
Project; and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache TVM Project:

 * Tianqi Chen 
 * Timothy Chen 
 * Zhi Chen 
 * Byung-Gon Chun 
 * Ziheng Jiang 
 * Furkan Kamaci 
 * YiZhi Liu 
 * Masahiro Masuda 
 * Thierry Moreau 
 * Jared Roesch 
 * Henry Saputra 
 * Haichen Shen 
 * Markus Weimer 
 * Eddie Yan 
 * Lianmin Zheng 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tianqi Chen be appointed to
the office of Vice President, Apache TVM, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed; and be it
further

RESOLVED, that the Apache TVM Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator TVM
podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
TVM  podling encumbered upon the Apache Incubator PMC are hereafter
Discharged.

- [1]
https://lists.apache.org/thread.html/r91b8f469c6a54769869bb2435b7334a28bcff885ae078ab5612dae00%40%3Cdev.tvm.apache.org%3E
- [2]
https://lists.apache.org/thread.html/rd5b8eefe49af09a2d0913758a5e5737b3fdb9072bc0becf4a2b2c7ee%40%3Cdev.tvm.apache.org%3E
- [3]
https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing
<https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing>

[DISCUSS] Apache TVM Graduation

[Tianqi Chen]

Edit the subject so that it is obvious as a discussion thread in
general@incubator.

TQ

FYI, following a heated discussion with great support from our mentors,
> committers and community members.
> The  Apache(incubating) TVM is starting a vote to graduate as TLP
>
> - [1] community DISCUSS thread:
> https://lists.apache.org/thread.html/r91b8f469c6a54769869bb2435b7334a28bcff885ae078ab5612dae00%40%3Cdev.tvm.apache.org%3E
> - [2] voting thread:
> https://lists.apache.org/thread.html/rd5b8eefe49af09a2d0913758a5e5737b3fdb9072bc0becf4a2b2c7ee%40%3Cdev.tvm.apache.org%3E
>
> TQ
>
> -- Forwarded message -
> From: Tianqi Chen 
> Date: Mon, Aug 24, 2020 at 1:51 PM
> Subject: [apache/incubator-tvm] [VOTE] Apache TVM Graduation (#6332)
> To: apache/incubator-tvm 
> Cc: Subscribed 
>
>
> Dear Community:
>
> Thanks  to everyone who participated in the discussion about
> graduation[1]. This is a formal voting thread for Apache TVM’s graduation.
>
> If this vote passes, the next step would be to submit the resolution below
> to the Incubator PMC, who would vote on sending it on to the Apache Board.
>
> Vote:
> [ ] +1 - Recommend graduation of Apache TVM as a TLP
> [ ]  0 - I don't feel strongly about it, but don't object
> [ ] -1 - Do not recommend graduation of Apache TVM because...
>
> The VOTE will open for at least 72 hours.
>
> This thread is mirrored to dev@, please vote by replying to this thread
>
> --
> The TVM project has been an Apache incubator project for nearly 1.5 year
> now. In the past one and half year, the community grew healthily under the
> Apache way. Some highlights include:
>
> - A successful developer conference that we are continuing to host this
> year
> - Great community growth, as of now, the community contains 16 PPMC
> members, 31 committers, from a diverse list of organizations. We are
> actively growing the list monthly.
> - Active contributions: ~ 150 PRs merged each month.
>
> The community has produced two formal apache releases. While we could also
> wait until more releases. We feel that the community is mature enough that
> we can push for graduation as it is, and continue to push for high quality
> releases concurrently.
>
> For reference, we also put together a maturity evaluation doc[2] under the
> Apache maturity model.
>
> Some additional note about the resolution below: the current PPMC will be
> transitioned to the PMC. We have invited all the mentors in the current
> PPMC who like to stay involved.
>
> -
>
> Establish the Apache TVM Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to compilation of machine learning models to run on a wide range
> of hardware platforms...
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache TVM Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache TVM Project be and hereby is responsible for the
> creation and maintenance of software related to compilation of machine
> learning models to run on a wide range of hardware platforms; and be it
> further
>
> RESOLVED, that the office of "Vice President, Apache TVM" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache TVM
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache TVM
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache TVM Project:
>
>  * Tianqi Chen 
>  * Timothy Chen 
>  * Zhi Chen 
>  * Byung-Gon Chun 
>  * Ziheng Jiang 
>  * Furkan Kamaci 
>  * YiZhi Liu 
>  * Masahiro Masuda 
>  * Thierry Moreau 
>  * Jared Roesch 
>  * Henry Saputra 
>  * Haichen Shen 
>  * Markus Weimer 
>  * Eddie Yan 
>  * Lianmin Zheng 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tianqi Chen be appointed to
> the office of Vice President, Apache TVM, to serve in accordance
> with and subject to the direction of the Board of Directors and the
> Bylaws of the Foundation until death, resignation, retirement, removal
> or disqualification, or until a successor is appointed; and be it
> further
>
> RESOLVED

Fwd: [apache/incubator-tvm] [VOTE] Apache TVM Graduation (#6332)

[Tianqi Chen]

Dear IPMC:

FYI,  following a heated discussion with great support from our mentors,
committers and community members.
The  Apache(incubating) TVM is starting a vote to graduate as TLP

- [1] community DISCUSS thread:
https://lists.apache.org/thread.html/r91b8f469c6a54769869bb2435b7334a28bcff885ae078ab5612dae00%40%3Cdev.tvm.apache.org%3E
- [2] voting thread:
https://lists.apache.org/thread.html/rd5b8eefe49af09a2d0913758a5e5737b3fdb9072bc0becf4a2b2c7ee%40%3Cdev.tvm.apache.org%3E

TQ

-- Forwarded message -
From: Tianqi Chen 
Date: Mon, Aug 24, 2020 at 1:51 PM
Subject: [apache/incubator-tvm] [VOTE] Apache TVM Graduation (#6332)
To: apache/incubator-tvm 
Cc: Subscribed 


Dear Community:

Thanks  to everyone who participated in the discussion about graduation[1].
This is a formal voting thread for Apache TVM’s graduation.

If this vote passes, the next step would be to submit the resolution below
to the Incubator PMC, who would vote on sending it on to the Apache Board.

Vote:
[ ] +1 - Recommend graduation of Apache TVM as a TLP
[ ]  0 - I don't feel strongly about it, but don't object
[ ] -1 - Do not recommend graduation of Apache TVM because...

The VOTE will open for at least 72 hours.

This thread is mirrored to dev@, please vote by replying to this thread

--
The TVM project has been an Apache incubator project for nearly 1.5 year
now. In the past one and half year, the community grew healthily under the
Apache way. Some highlights include:

- A successful developer conference that we are continuing to host this year
- Great community growth, as of now, the community contains 16 PPMC
members, 31 committers, from a diverse list of organizations. We are
actively growing the list monthly.
- Active contributions: ~ 150 PRs merged each month.

The community has produced two formal apache releases. While we could also
wait until more releases. We feel that the community is mature enough that
we can push for graduation as it is, and continue to push for high quality
releases concurrently.

For reference, we also put together a maturity evaluation doc[2] under the
Apache maturity model.

Some additional note about the resolution below: the current PPMC will be
transitioned to the PMC. We have invited all the mentors in the current
PPMC who like to stay involved.

-

Establish the Apache TVM Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to compilation of machine learning models to run on a wide range of
hardware platforms...

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache TVM Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache TVM Project be and hereby is responsible for the
creation and maintenance of software related to compilation of machine
learning models to run on a wide range of hardware platforms; and be it
further

RESOLVED, that the office of "Vice President, Apache TVM" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache TVM
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache TVM
Project; and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache TVM Project:

 * Tianqi Chen 
 * Timothy Chen 
 * Zhi Chen 
 * Byung-Gon Chun 
 * Ziheng Jiang 
 * Furkan Kamaci 
 * YiZhi Liu 
 * Masahiro Masuda 
 * Thierry Moreau 
 * Jared Roesch 
 * Henry Saputra 
 * Haichen Shen 
 * Markus Weimer 
 * Eddie Yan 
 * Lianmin Zheng 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tianqi Chen be appointed to
the office of Vice President, Apache TVM, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed; and be it
further

RESOLVED, that the Apache TVM Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator TVM
podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
TVM  podling encumbered upon the Apache Incubator PMC are hereafter
Discharged.

- [1]
https://lists.apache.org/thread.html/r91b8f469c6a54769869bb2435b7334a28bcff885ae078ab5612dae00%40%3Cdev.tvm.apache.org%3E
- [2]
https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.

Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1

[Tianqi Chen]

+1 (binding)

- signature and hashes
- Disclaimer and License

TQ

On Wed, Aug 19, 2020 at 6:47 PM Xingjian SHI  wrote:

> +1 (Binding) I verified autogluon.
>
> Best,
> Xingjian
>
> On 8/19/20, 6:15 PM, "Chen, Ciyong"  wrote:
>
> Hi Jason,
> Thank you for your time to check and vote on this.
>
> Hi IPMC and community,
> We've got two binding votes, and now we're looking forward to one more
> binding votes for this release, please help on this, many thanks!!
>
> Regards,
> -Ciyong
>
> -Original Message-
> From: Jason Dai 
> Sent: Wednesday, August 19, 2020 10:16 PM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1
>
>  +1 (binding)
>
>
> I checked:
>
> - Incubating in name
>
> - Signatures and hashes
>
> - Disclaimer, LICENSE and NOTICE
>
>
> Thanks,
>
> -Jason
>
> On Tue, Aug 18, 2020 at 6:25 PM Michael Wall 
> wrote:
>
> > Thanks for the follow up Ciyong.  You are right, -vv did not enable
> > verbose. If I had used -VV (with capital V's) I would have gotten
> > output.
> >
> > Good luck on the vote.
> >
> > Mike
> >
> > On Tue, Aug 18, 2020 at 2:43 AM Chen, Ciyong 
> > wrote:
> > >
> > > Hi Michael,
> > >
> > > Thank you for your time to review and vote.
> > >
> > > Regarding your questions:
> > > > - Does anything with mshadow need to change now that it has
> passed
> > clearance.
> > > From source code release perspective, I don't think there's
> anything
> > > we
> > need to change as mshadow is already in the code base with the
> correct
> > license header. CC @Sheng to see if any comments.
> > >
> > > > - I tried running tests a couple of ways after the build I build
> > > > but
> > they just hung for 15 min before I control-c'd them.  Maybe I didn't
> > wait long enough, but there was no indication anything was running.
> > > The test suite contains lots of test cases which will be very time
> > consuming, " ctest -vv" doesn't enable the verbose output thus looks
> > like it hung as no output on the terminal.
> > > By using "ctest --verbose" which turns on the verbose and will
> give
> > > more
> > details for all the test cases.
> > > Currently, the entire test suite will run through many different
> > configurations of hardware and docker image via CI pipeline.
> > >
> > > Thanks,
> > > -Ciyong
> > >
> > > -Original Message-
> > > From: Michael Wall 
> > > Sent: Tuesday, August 18, 2020 9:54 AM
> > > To: general@incubator.apache.org
> > > Subject: Re: [VOTE] Release Apache MXNet (incubating) version
> > > 1.7.0.rc1
> > >
> > > +1 from me
> > >
> > > Checked
> > > - signatures
> > > - incubating in name
> > > - License, Notice and Disclaimer
> > > - Compiled from source with CPP bindings using
> >
> https://mxnet.apache.org/versions/1.6/get_started/build_from_source#in
> > stall-mxnet-for-python
> > ,
> > > https://mxnet.apache.org/versions/1.6/get_started/cpp_setup and
> >
> https://github.com/apache/incubator-mxnet/blob/1.7.0.rc1/config/linux.
> > cmake
> > >
> > > Couple of questions
> > > - Does anything with mshadow need to change now that it has passed
> > clearance.
> > > - I tried running tests a couple of ways after the build I build
> but
> > they just hung for 15 min before I control-c'd them.  Maybe I didn't
> > wait long enough, but there was no indication anything was running.
> > >
> > > Here is the run
> > >
> > > ```
> > > [0/1] Running tests...
> > > Test project
> >
> /home/mikewall/Desktop/mxnet-1.7.0/apache-mxnet-src-1.7.0.rc1-incubati
> > ng/build
> > > Start 1: AllTestsInmxnetUnitTests
> > > ^Cninja: build stopped: interrupted by user.
> > > ```
> > >
> > > And here is my history fwiw
> > >
> > > ```
> > > sudo apt-get install -y build-essential git ninja-build ccache
> > libopenblas-dev libopencv-dev cp config/linux.cmake config.cmake rm
> > -rf build cmake -S. -Bbuild -DUSE_CPP_PACKAGE=1
> > -DCMAKE_BUILD_TYPE=Release -GNinja cmake --build build cmake --build
> > build --target test cd build && ctest -vv ```
> > >
> > > On Mon, Aug 17, 2020 at 2:27 PM Sheng Zha 
> wrote:
> > > >
> > > > Hi Justin,
> > > >
> > > > Since the blocking issue has been resolved, would you mind
> > > > changing
> > your vote? Thanks.
> > > >
> > > > Regards,
> > > > Sheng
> > > >
> > > > On 2020/07/26 01:27:39, Justin Mclean 
> > wrote:
> > > > > Hi,
> > > > >
> > > > > -1 (binding) as this release contains code that hasn’t gone
> > > > > though
> > IP clearance (mshadow).
> > > > >
> > > > > I checked:
> > > > > - 

Re: [VOTE] Release Apache NuttX (Incubating) 9.1.0 [RC2]

[Tianqi Chen]

+1(binding)

The sigs and sums match,
LICENSE, NOTICE, DISCLAIMER-WIP are good.  The license header in source
needs to be updated to conform with ASF convention but given the
DISCLAIMER-WIP it is fine.

Cheers
TQ

On Mon, Jul 20, 2020 at 8:12 PM 张铎(Duo Zhang)  wrote:

> +1(binding)
>
> Checked sigs and sum: Matched
> Checked tag hashes: Matched
> Checked source: LICENSE, NOTICE, DISCLAIMER-WIP are in place.
> Built from source:
>
> ./tools/configure.sh sim:nsh
> make
>
> This time it is much easier to build, which is good. Tried with several
> simple shell commands, looks fine.
>
> Thank you all for the great work!
>
>
> Nathan Hartman  于2020年7月19日周日 下午11:24写道：
>
> > Hello IPMC,
> >
> > Ping!!
> >
> > Apache NuttX (Incubating) 9.1.0 [RC2] is awaiting your review and vote.
> >
> > If we could please get a show of support from IPMC members and our
> > mentors, that would be great!
> >
> > Cheers,
> > Nathan
> >
> >
> > -- Forwarded message -
> > From: Brennan Ashton 
> > Date: Sun, Jul 12, 2020 at 7:42 PM
> > Subject: [VOTE] Release Apache NuttX (Incubating) 9.1.0 [RC2]
> > To: 
> >
> >
> > Hello all,
> >
> > This is a call for a vote to release Apache NuttX (Incubating) version
> > 9.1.0.
> >
> > The Apache NuttX community has voted on and approved a proposal to
> > release
> > Apache NuttX (Incubating) version 9.1.0.
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > NuttX is a real-time operating system (RTOS) with an emphasis on
> > standards
> > compliance and small footprint. Scalable from 8-bit to 64-bit
> > microcontroller
> > environments, the primary governing standards in NuttX are Posix and
> > ANSI
> > standards. Additional standard APIs from Unix and other common RTOS’s
> > (such as VxWorks) are adopted for functionality not available under
> > these
> > standards, or for functionality that is not appropriate for deeply-
> > embedded
> > environments (such as fork()).
> >
> > Because this project targets embedded systems there is more complexity
> > involved in the build process. Two starting points:
> >  * README.txt -- This is found in the Apache NuttX source and is
> > extensive.
> >  * Unofficial NuttX Companion --
> > https://nuttx-companion.readthedocs.io/en/latest/user/install.html,
> > this is a currently unofficial opinionated guide maintained by some of
> > the project committers.
> >
> > Apache NuttX community vote and result thread:
> > Result:
> >
> >
> https://lists.apache.org/thread.html/r1a30e5cba2dab57556605fb6570fd722de1eee69244c1b4092579033%40%3Cdev.nuttx.apache.org%3E
> > Vote:
> >
> >
> https://lists.apache.org/thread.html/r751f7ce05b1f0485b5dc9ca7bfb1c5f52abc5676fd81b9fb92910c64%40%3Cdev.nuttx.apache.org%3E
> >
> > The release candidates (RC2):
> > https://dist.apache.org/repos/dist/dev/incubator/nuttx/9.1.0-RC2/
> >
> > Git tag for the release (RC2):
> > https://github.com/apache/incubator-nuttx/releases/tag/nuttx-9.1.0-RC2
> >
> https://github.com/apache/incubator-nuttx-apps/releases/tag/nuttx-9.1.0-RC2
> >
> > Hash for the release incubating-nuttx tag:
> >   e4e4cce6962430e2b07336d2c564b14298995661
> > Hash for the release incubating-nuttx-apps tag:
> >   4fac1c185c01adfa84f04618af9be7b9c4b884f5
> >
> > Release Notes:
> >
> >
> https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-9.1.0-RC2/ReleaseNotes
> >
> >
> > The artifacts have been signed with Key :
> > 3554D78458CEB6954B020E12E1B6E30DB05D6280, which can be found in the
> > keys file:
> > https://dist.apache.org/repos/dist/dev/incubator/nuttx/KEYS
> >
> > Look at here for how to verify this release candidate:
> >
> >
> https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release
> >
> > The vote will be open for at least 72 hours.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Brennan Ashton
> > Apache NuttX
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [RESULT][VOTE] Release Apache TVM (incubating) v0.6.1.rc1

[Tianqi Chen]

Great job TVM community! Congrats

TQ

On Thu, Jul 9, 2020 at 2:27 PM Henry Saputra 
wrote:

> Congrats to the Apache TVM incubating community for another release!
>
> - Henry
>
> On Tue, Jul 7, 2020 at 10:55 PM YiZhi Liu  wrote:
>
> > Thanks to everyone that participated. The vote to release Apache TVM
> > (incubating) v0.6.1 is now closed. I'm glad to announce the results.
> >
> > This vote passes with 5 binding +1, 0 non binding +1, no 0 votes, and 0
> -1
> > vote.
> >
> > binding +1 votes
> > * Tianqi Chen
> > * Markus Weimer
> > * Henry Saputra
> > * Furkan KAMACI
> > * Byung-Gon Chun
> >
> > Vote thread can be found here [1].
> >
> > We will work to complete the release process.
> >
> > [1]
> >
> https://lists.apache.org/thread.html/r1b518c76e261163ba33e08c490de0905cdb779a20558448c508281a4%40%3Cgeneral.incubator.apache.org%3E
> >
> > --
> > Yizhi Liu
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: Issue with releases / feedback from ASF board

[Tianqi Chen]

>
> I’m not aware of any other project that uses CUDU code.
>

I want to point out that most machine learning and analytics related
projects will likely need to involve (and likely distribute) CUDA code,
this would include some of the current TLPs.

Here are some examples using search:
- Arrow https://arrow.apache.org/docs/python/cuda.html
- SystemML https://systemml.apache.org/docs/1.2.0/gpu
- Singa
https://svn.apache.org/repos/infra/websites/production/singa/content/docs/gpu.html

TQ



>
> 1. https://mxnet.apache.org/get_started/?
> 2. https://github.com/apache/incubator-mxnet/releases
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP

[Tianqi Chen]

I see, thanks for the links. I think the past two posts, along with Craig's
suggestion summarizes the cases clearly

TQ

On Thu, Mar 26, 2020 at 7:44 PM Justin Mclean 
wrote:

> Hi,
>
> It easy enough to move off the home page or change the link as Craig
> suggest. I would also suggest change the words to not be a GitHiub
> marketing slogan.
>
> There have been discussion on this in the past, but the main ones I found
> discussion is sadly on private lists, so I’m unable to share that here.
> I’ve asked infra to see if they can clarify.
>
> This it is mentioned in a few board reports and comments, for instance
> search “Fork Me” here:
> https://whimsy.apache.org/board/minutes/Wicket.html
>
> Thanks,
> Justin
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP

[Tianqi Chen]

Like in most cases when the argument can go both ways, I think it would be
helpful to summarize all the views and their pros and cons to give a
comprehensive picture.

The current summary of the points are:

Pros:
 -P0: Encourages developers community participation to the project,
exercise community over code.

Concerns(in someone might view)
- C0: it as un-released distribution, which violates the release policy
- C1: Link to github serves as ads to github

Intent
- The shardingsphere community has good intent starting from P0, but not
necessarily shares the same opinion over C0 and C1.


Again I think the intent is important, after aour goal is welcome and
support these projects and help them grow the community in apache way.
While different people or community might have choose to do it different
like being suggested, I personally might even agree with you that the link
should not be in the frontpage

In this case, if there is no strict ruling, I think it would be helpful to
let the project community choose the verdict, while acknowledging that
there might be different opinions in different communities.
Of course the solution Crag suggested seems to work as well :)

TQ


On Thu, Mar 26, 2020 at 6:25 PM Justin Mclean 
wrote:

> Hi,
>
> By adding that you have placed a large prominent ad to commercial entity
> on your home page. You are also using a marketing slogan from GitHub.  Ask
> yourself would you do that with any other commercial entity on your front
> page?
>
> Thanks,
> Justin
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP

[Tianqi Chen]

I see, in that case, it would be really nice to add a link to the original
email context (about the infra request to remove the github link),
which would help clarified the situation in the first place. And a good way
to exercise the public archival principle.

TQ

On Thu, Mar 26, 2020 at 5:40 PM Justin Mclean 
wrote:

> HI,
>
> I know that other projects have been asked to remove this from the front
> page and move to a “for developers” page. But perhaps Infra view on this
> has changed I’m not sure.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP

[Tianqi Chen]

Also I want to say that the intent is important when discussing many of
these cases.
In this case hopefully most of us we all agree, the original intention of
the project community is to encourage broader participation of the
community, rather than distributing un-released distribution.

TQ

On Thu, Mar 26, 2020 at 5:26 PM Tianqi Chen 
wrote:

> It really depends on how do you interpret the github link as a un-released
> distribution. A tarball of un-released source code is of course a
> un-released distribution.  It seems to be a bit broad to classify a github
> link as a un-released distribution :)
>
> In most cases, github is one of the important places where community
> developments(and possible issue answering) happen, and it seems to be OK
> that the project community can choose to welcome their more developers to
> work together, as per Apache way.
>
> Would be interesting ask INFRA about their position on this issue.
>
> TQ
>
>
>
> On Thu, Mar 26, 2020 at 5:11 PM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> I suggest you talk to Infra about this as this is their policy [1].  See
>> "must not be advertised to anyone outside of the project development
>> community”, having that on the front page does that IMO.
>>
>> Thanks,
>> Justin
>>
>> 1. https://infra.apache.org/release-distribution.html#unreleased
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP

[Tianqi Chen]

It really depends on how do you interpret the github link as a un-released
distribution. A tarball of un-released source code is of course a
un-released distribution.  It seems to be a bit broad to classify a github
link as a un-released distribution :)

In most cases, github is one of the important places where community
developments(and possible issue answering) happen, and it seems to be OK
that the project community can choose to welcome their more developers to
work together, as per Apache way.

Would be interesting ask INFRA about their position on this issue.

TQ



On Thu, Mar 26, 2020 at 5:11 PM Justin Mclean 
wrote:

> Hi,
>
> I suggest you talk to Infra about this as this is their policy [1].  See
> "must not be advertised to anyone outside of the project development
> community”, having that on the front page does that IMO.
>
> Thanks,
> Justin
>
> 1. https://infra.apache.org/release-distribution.html#unreleased
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP

[Tianqi Chen]

I can see arguments goes both ways:)

Apache is about community over code, github is certainly a place where the
(an important part of)community goes to, highlighting the link to that
seems to be OK if the project decide to do so.

TQ

On Thu, Mar 26, 2020 at 4:34 PM Sheng Wu  wrote:

> Hi, Justin
>
> I think you misunderstand my point.
>
> In the GitHub project is just saying the project uses GitHub. Just consider
> it as a widely used platform.
> The fork me thing, is just encouraging people to take part in code
> development. Nothing more.
> I don't think people would think this is a way to get official release.
>
> Of course, my personal perspective, only.
>
> Justin Mclean 于2020年3月27日 周五上午6:31写道：
>
> > Hi,
> >
> > > I agree. `Fork me` is popular in the GitHub projects. :) I think could
> > keep it.
> >
> >
> > You are not a GItHub prohject you are an ASF project.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > --
> Sheng Wu 吴晟
>
> Apache SkyWalking
> Apache Incubator
> Apache ShardingSphere, ECharts, DolphinScheduler podlings
> Zipkin
> Twitter, wusheng1108
>

Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP

[Tianqi Chen]

Looks like the branding issue has been resolve. Good job in building an
active community,
+1

TQ

On Sun, Mar 22, 2020 at 1:44 AM Sally Khudairi  wrote:

> Thank you, Liang. I appreciate your rapid response!
>
> Best,
> Sally
>
> - - -
> Vice President Marketing & Publicity
> Vice President Sponsor Relations
> The Apache Software Foundation
>
> Tel +1 617 921 8656 | s...@apache.org
>
>
> On Sun, Mar 22, 2020, at 04:29, zhangli...@apache.org wrote:
> > I just added to powered by logo in this page and ref="nofollow" for
> organizations' link.
> >
> > I changed back the url from users to powered-by[1].
> >
> > [1] https://shardingsphere.apache.org/community/en/powered-by/
> >
> > --
> >
> > Liang Zhang (John)
> > Apache ShardingSphere & Dubbo
> >
> >
> > zhangli...@apache.org  于2020年3月22日周日 上午11:29写道：
> >> Hi Sally,
> >>
> >> Thanks for the confirmation. I will add the powered by logo in the page
> soon.
> >>
> >> The organizations are not using rel="nofollow", I will fix it ASAP.
> >>
> >> --
> >>
> >> Liang Zhang (John)
> >> Apache ShardingSphere & Dubbo
> >>
> >>
> >> Sally Khudairi  于2020年3月22日周日 上午6:36写道：
> >>> __
> >>> One more thing --to confirm, the links to the organizations on your
> page are going to be rel="nofollow", yes?
> >>>
> >>> That's important.
> >>>
> >>> Many thanks,
> >>> Sally
> >>>
> >>> - - -
> >>> Vice President Marketing & Publicity
> >>> Vice President Sponsor Relations
> >>> The Apache Software Foundation
> >>>
> >>> Tel +1 617 921 8656 | s...@apache.org
> >>>
> >>>
> >>> On Sat, Mar 21, 2020, at 16:32, Sally Khudairi wrote:
>  Hello Liang --thank you for your message. My apologies for the
> delayed response.
> 
>  To me what is proposed seems acceptable, similar to what is being
> done with other Apache projects [1] [2] [3] and many others.
> 
>  You may also wish to consider promoting use of the "Powered by
> Apache" badge for your community --we've created one for you at
> http://apache.org/foundation/press/kit/poweredBy/
> 
>  I'm also copying Mark Thomas, VP Brand Management/Trademarks, for his
> input.
> 
>  Many kind regards,
>  Sally
> 
>  [1] https://cwiki.apache.org/confluence/display/HADOOP2/PoweredBy
>  [2] https://spark.apache.org/powered-by.html
>  [3] https://kafka.apache.org/powered-by
> 
>  - - -
>  Vice President Marketing & Publicity
>  Vice President Sponsor Relations
>  The Apache Software Foundation
> 
>  Tel +1 617 921 8656 | s...@apache.org
> 
> 
>  On Thu, Mar 19, 2020, at 01:15, zhangli...@apache.org wrote:
> > Hi Sally,
> >
> > We are talking about graduation Apache ShardingSphere(incubator)
> project.
> >
> > There is a problem with users page[1]. This page lists all companies
> and organizations who using Apache ShardingSphere(incubator).
> >
> > The source of user list are coming from Github issue[2] which
> registered by users themselves, the logos in user wall picture are
> collected from their official website.
> >
> > We read this[3], it may cross over to sponsorship or may cause
> branding issue.
> >
> > Can the project keep this page? Could you give some advice? Thank
> you very much.
> >
> > [1] https://shardingsphere.apache.org/community/en/users/
> >
> > [2] https://github.com/apache/incubator-shardingsphere/issues/234
> >
> > [3] https://www.apache.org/foundation/marks/linking
> >
> > --
> >
> > Liang Zhang (John)
> > Apache ShardingSphere & Dubbo
> >
> >
> > Dave Fisher  于2020年3月19日周四 上午10:22写道：
> >> Hi -
> >>
> >> I do think that the “user” page should be discussed with either
> Sally at press@ or Mark at trademarks@. They will know best how to create
> a compliant version of what you are trying to do.
> >>
> >> Regards,
> >> Dave
> >>
> >> Sent from my iPhone
> >>
> >> > On Mar 18, 2020, at 6:29 PM, Justin Mclean <
> jus...@classsoftware.com> wrote:
> >> >
> >> > Hi,
> >> >
> >> > I would carefully read this [1]. It may cross over to
> sponsorship. Sponsors pay a lot of money to be listed as such. It may be
> best to speak to branding about this and see what they say.
> >> >
> >> > Thanks,
> >> > Justin
> >> >
> >> > 1. https://www.apache.org/foundation/marks/linking
> >> >
> >> >
> >> >
> -
> >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> > For additional commands, e-mail:
> general-h...@incubator.apache.org
> >> >
> >>
> >>
> >>
> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> 
> >>>

Re: [VOTE] Graduate Apache ShardingSphere (incubating)

[Tianqi Chen]

+1 (binding)

Good luck

TQ

On Fri, Mar 13, 2020 at 6:04 PM Sheng Wu  wrote:

> +1 binding.
>
> Good luck ShardingSphere
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> zhangli...@apache.org  于2020年3月14日周六 上午1:30写道：
>
> > Hi!
> >
> > We've got positive feedback on the DISCUSS thread, I'd like to start an
> > official VOTE thread now.
> >
> > Please vote on the resolution pasted below to graduate Apache
> > ShardingSphere from the incubator to the Top Level Project.
> >
> > [ ] +1 Graduate Apache ShardingSphere from the Incubator.
> > [ ] +0 Don't care.
> > [ ] -1 Don't graduate Apache ShardingSphere from the Incubator because
> ...
> >
> > This vote will open for at least 72 hours.
> >
> > Many thanks to our mentors and everyone else for their support.
> >
> > ---
> >
> > Establish the Apache ShardingSphere Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to Apache ShardingSphere is an ecosystem consisted of a set of
> > distributed database middleware solutions, including 2 independent
> > products, Sharding-JDBC, Sharding-Proxy. They all provide functions of
> > data sharding, distributed transaction, database and data governance,
> > applicable in a variety of situations such as Java isomorphism and
> > heterogeneous language..
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache ShardingSphere Project", be and hereby
> > is established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache ShardingSphere Project be and hereby is
> > responsible for the creation and maintenance of software related to
> > Apache ShardingSphere is an ecosystem consisted of a set of distributed
> > database middleware solutions, including 2 independent products,
> > Sharding-JDBC, Sharding-Proxy. They all provide functions of data
> > sharding, distributed transaction, database and data governance,
> > applicable in a variety of situations such as Java isomorphism and
> > heterogeneous language.; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache ShardingSphere" be
> > and hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache
> > ShardingSphere Project, and to have primary responsibility for
> > management of the projects within the scope of responsibility of the
> > Apache ShardingSphere Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache ShardingSphere
> > Project:
> >
> >  * Craig L Russell   
> >  * Hao Cao   
> >  * Hongjun Du
> >  * Hongtao Gao   
> >  * Juan Pan  
> >  * Jun Zhao  
> >  * Liang Zhang   
> >  * QingYang Chen 
> >  * Sheng Wu  
> >  * Von Gosling   
> >  * Willem Ning Jiang 
> >  * Xiaoguang Ma  
> >  * Yang Yi   
> >  * Yonglun Zhang 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Liang Zhang be appointed to
> > the office of Vice President, Apache ShardingSphere, to serve in
> > accordance with and subject to the direction of the Board of Directors
> > and the Bylaws of the Foundation until death, resignation, retirement,
> > removal or disqualification, or until a successor is appointed; and be
> > it further
> >
> > RESOLVED, that the Apache ShardingSphere Project be and hereby is tasked
> > with the migration and rationalization of the Apache Incubator
> > ShardingSphere podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > ShardingSphere podling encumbered upon the Apache Incubator PMC are
> > hereafter discharged.
> >
> > --
> >
> > Liang Zhang (John)
> > Apache ShardingSphere & Dubbo
> >
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.6.0.rc2

[Tianqi Chen]

+1(binding), I checked

- Keys,
- sha512
- DISCLAIMER-WIP, LICENSE, NOTICE
- No unexpected binary files
- Code compiles under nvcc, g++7(need to set DEV=0 to skip warnings)

TQ

On Tue, Feb 18, 2020 at 10:14 AM Przemysław Trędak 
wrote:

> Dear Community,
>
> This is a gentle reminder to test and vote on this release.
>
> Best regards,
> Przemyslaw Tredak
>
> On 2020/02/10 18:17:26, Przemys��aw Tr��dak  wrote:
> > Dear Community,
> >
> > This is a call for a releasing Apache MXNet (incubating) 1.6.0, release
> candidate 2.
> >
> > Apache MXNet (incubating) community has voted and approved the release.
> >
> > Vote thread:
> >
> https://lists.apache.org/thread.html/6dd3088c053fa111ef93412ac1b07c193d5eeb99dc82eadb99f7562b%40%3Cdev.mxnet.apache.org%3E
> >
> > Result thread:
> >
> https://lists.apache.org/thread.html/6f6118010596532484ee5e38a8c2ebbe5d2e8abd7a40e6964cd43367%40%3Cdev.mxnet.apache.org%3E
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.6.0.rc2/
> >
> > The tag to be voted upon is 1.6.0.rc2:
> > https://github.com/apache/incubator-mxnet/tree/1.6.0.rc2
> >
> > The release hash is 6eec9da55c5096079355d1f1a5fa58dcf35d6752:
> >
> https://github.com/apache/incubator-mxnet/commit/6eec9da55c5096079355d1f1a5fa58dcf35d6752
> >
> > KEYS file available:
> > https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> >
> > For information about the contents of this release, see:
> > https://cwiki.apache.org/confluence/display/MXNET/1.6.0+Release+notes
> >
> > The vote will be open for 72 hours.
> >
> > [ ] +1 release this package as 1.6.0
> > [ ] +0 no opinion
> > [ ] -1 do not release this package because...
> >
> > Best regards,
> > Przemysław Trędak
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

[Tianqi Chen]

+1 (binding)


TQ

On Sun, Dec 8, 2019 at 2:05 PM Furkan KAMACI  wrote:

> Hi,
>
> +1 (binding)
>
> Kind Regards,
> Furkan KAMACI
>
> On Mon, Dec 9, 2019 at 12:14 AM Dave Fisher  wrote:
>
> > +1 (binding)
> >
> > Regards,
> > Dave
> >
> > Sent from my iPhone
> >
> > > On Dec 7, 2019, at 1:55 PM, Gian Merlino  wrote:
> > >
> > > Earlier this year, Druid voted to graduate to a top level project. The
> > vote
> > > passed in the Druid community and the Incubator, and a resolution was
> > > submitted to the Board, but needed to be shelved at the last minute. We
> > are
> > > now ready to proceed to graduation once again, and so I would like to
> > call
> > > another vote. The Druid project has re-voted and has notified the Board
> > of
> > > these developments. We now seek consent from the Incubator community to
> > > propose a graduation resolution for the Dec 18 board meeting.
> > >
> > > The proposed graduation resolution is nearly the same as last time; the
> > > only changes are the addition of four new initial members (fokko,
> furkan,
> > > qmm, and vogievetsky).
> > >
> > > For reference,
> > >
> > > 1) The Druid vote that was just held:
> > >
> >
> https://lists.apache.org/thread.html/3b1432780b8d841fffce3033cd5cc39fe1fe0f46feccb96f036dbf01%40%3Cdev.druid.apache.org%3E
> > >
> > > 2) Our prior Incubator graduation vote, which passed earlier this year:
> > >
> >
> https://lists.apache.org/thread.html/19b703fdf192ddf8e31bda57264e03113c7e44b5954a56886e05@%3Cgeneral.incubator.apache.org%3E
> > >
> > > Please take a minute to vote on whether or not Apache Druid should
> > graduate
> > > to a Top Level Project by responding with one of the following:
> > >
> > > [ ] +1 Apache Druid should graduate
> > > [ ]  0 No opinion
> > > [ ] -1 Apache Druid should not graduate because...
> > >
> > > The VOTE is open for a minimum of 72 hours.
> > >
> > > ---
> > >
> > > Establish Apache Druid Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best
> > > interests of the Foundation and consistent with the Foundation's
> > > purpose to establish a Project Management Committee charged with
> > > the creation and maintenance of open-source analytical database
> > > software, for distribution at no charge to the public.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > > Committee (PMC), to be known as the "The Apache Druid Project",
> > > be and hereby is established pursuant to Bylaws of the
> > > Foundation; and be it further
> > >
> > > RESOLVED, that The Apache Druid Project be and hereby is
> > > responsible for the creation and maintenance of an analytical
> > > database software project; and be it further
> > >
> > > RESOLVED, that the office of "Vice President, Druid" be and
> > > hereby is created, the person holding such office to serve at the
> > > direction of the Board of Directors as the chair of The Apache
> > > Druid Project, and to have primary responsibility for
> > > management of the projects within the scope of responsibility of
> > > The Apache Druid Project; and be it further
> > >
> > > RESOLVED, that the persons listed immediately below be and
> > > hereby are appointed to serve as the initial members of The
> > > Apache Druid Project:
> > >
> > >  * Benedict Jin (asdf2...@apache.org)
> > >  * Charles Allen(cral...@apache.org)
> > >  * Clint Wylie  (cwy...@apache.org)
> > >  * David Lim(david...@apache.org)
> > >  * Dylan Wylie  (dylanwy...@apache.org)
> > >  * Eric Tschetter   (ched...@apache.org)
> > >  * Fangjin Yang (f...@apache.org)
> > >  * Fokko Driesprong (fo...@apache.org)
> > >  * Furkan Kamaci(kam...@apache.org)
> > >  * Gian Merlino (g...@apache.org)
> > >  * Himanshu Gupta   (himans...@apache.org)
> > >  * Jihoon Son   (jihoon...@apache.org)
> > >  * Jonathan Wei (jon...@apache.org)
> > >  * Julian Hyde  (jh...@apache.org)
> > >  * Kurt Young   (k...@apache.org)
> > >  * Lijin Bin(binli...@apache.org)
> > >  * Maxime Beauchemin(maximebeauche...@apache.org)
> > >  * Mingming Qiu (q...@apache.org)
> > >  * Niketh Sabbineni (nik...@apache.org)
> > >  * Nishant Bangarwa (nish...@apache.org)
> > >  * P. Taylor Goetz  (ptgo...@apache.org)
> > >  * Parag Jain   (pja...@apache.org)
> > >  * Roman Leventov   (leven...@apache.org)
> > >  * Slim Bouguerra   (bs...@apache.org)
> > >  * Surekha Saharan  (sure...@apache.org)
> > >  * Xavier Léauté(x...@apache.org)
> > >  * Vadim Ogievetsky (vogievet...@apache.org)
> > >
> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gian Merlino
> > > be and hereby is appointed to the office of Vice President,
> > > Druid, to serve in accordance with and subject to the direction
> > > of the Board of Directors and the Bylaws of the Foundation until
> > > death, resignation, retirement, removal or disqualification, or
> > > 

Re: [ANNOUNCE] Apache TVM (incubating) v0.6.0 Release

[Tianqi Chen]

We would like to thank everyone, including IPMC and our mentors for helping
us getting the first formal ASF Release.
Thank you Justin for your helpful pointers to get the release to hold up to
the Apache standard.

Yesterday the TVM Community held our second annual conference. It is the
first conference we held since Apache incubation. The project get ~70%
growth(both in terms of number of contributors and committers).  Thanks to
the Apache way and the effort of everyone in the community.

We would like to express our gratitude to the incubator community, and
hopefully continue to push things forward under the Apache way.


On Thu, Dec 5, 2019 at 8:29 AM YiZhi Liu  wrote:

> Hi all,
>
> The Apache TVM (incubating) community is happy to announce Apache TVM
> (incubating) version 0.6.0!
>
> Apache TVM (incubating) is an open deep learning compiler stack for
> CPUs, GPUs, and specialized accelerators. It aims to close the gap
> between the productivity-focused deep learning frameworks, and the
> performance- or efficiency-oriented hardware backends.
>
> 0.6.0 is a major release incorporating important features including
> high-level Relay IR, Relay Virtual Machine, training support,
> quantization, TSim, MicroTVM, Rust support, etc. It also contains a
> count of operator support and performance improvement.
>
> A full list of the changes in this release can be found in the release
> notes:
> https://github.com/apache/incubator-tvm/releases/tag/v0.6.0
>
> A link to the download can be found here:
> https://dist.apache.org/repos/dist/release/incubator/tvm/tvm-v0.6.0/
>
> The Release Tag:
> https://github.com/apache/incubator-tvm/tree/v0.6.0
>
> TVM Resources
> - Our discussion forum (https://discuss.tvm.ai/)
> - TVM dev mailing list (
> https://lists.apache.org/list.html?d...@tvm.apache.org)
> - TVM website (https://tvm.apache.org/)
> - Github issues (https://github.com/apache/incubator-tvm/issues)
>
> Best regards,
> Apache TVM (incubating) Team
>
> ___
>
> DISCLAIMER:
>
> Apache TVM (incubating) is an effort undergoing incubation at The
> Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
>
> Incubation is required of all newly accepted
> projects until a further review indicates that the
> infrastructure, communications, and decision making process have
> stabilized in a manner consistent with other successful ASF
> projects.
>
> --
> Yizhi Liu
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tvm.apache.org
> For additional commands, e-mail: dev-h...@tvm.apache.org
>
>

Re: [VOTE] Accept NuttX into the Apache Incubator

[Tianqi Chen]

+1 (binding)

TQ

On Wed, Dec 4, 2019 at 8:40 AM David Sidrane 
wrote:

> +1 (non-binding)
>
> Thank you,
>
> David Sidrane
>
> -Original Message-
> From: 俊平堵 [mailto:junping...@apache.org]
> Sent: Tuesday, December 03, 2019 9:32 PM
> To: general@incubator.apache.org
> Subject: [VOTE] Accept NuttX into the Apache Incubator
>
> Hi folks,
>
>
> The [DISCUSS] thread on NuttX has died down.
>
>
> Accordingly, I would like to call a VOTE to accept NuttX into the
>
> Apache Incubator.
>
>
> Please cast your vote:
>
>
>   [ ] +1, bring NuttX into the Incubator
>
>   [ ] +0, I don't care either way
>
>   [ ] -1, do not bring NuttX into the Incubator, because...
>
>
> The vote will open at least for 72 hours and only votes from the
>
> Incubator PMC are binding, but votes from everyone are welcome.
>
>
> =Abstract=
>
> NuttX is a mature, real-time embedded operating system (RTOS).  It has wide
> usage in IoT projects, control systems, robotics, drones, and many other
> systems.  Unique properties of NuttX are its strict adherence to standards
> and its scalability. NuttX follows the Unix standards as defined
> by OpenGroup.org (POSIX, ANSI, and others).  This allows for a high degree
> of portability. Scalability is supported through a configuration system
> that allows NuttX to run on the smallest embedded platforms and through
> high end single board computers.
>
>
> =Proposal=
>
> NuttX was released under a BSD 3-Clause license on February 17, 2007.  From
> that time until now it has been managed by a single person, Gregory Nutt.
> The user base of NuttX has grown to probably thousands of projects and
> perhaps a hundred active developments at any time.  The code base has grown
> to around 1.5 million lines of code (according to OpenHub.com).
>
> NuttX has benefited from this single person management because this has
> resulted in a consistent architecture and controlled growth.  But now it is
> time to open this project to the participation of others because this
> consistent architecture assures solid future growth, and because the
> magnitude of effort required to support the RTOS exceeds the capability of
> a single person, but also because users of NuttX require a stable road map
> going forward that does not depend on a single person.
>
> For these reasons, I propose that NuttX enter the Apache Incubator as a
> first step in opening the project to wider participation.
>
>
> =Initial Goals=
>
> The initial goal will be to move the existing BSD code base to Apache and
> integrate with the Apache development process and infrastructure. A primary
> goal of incubation will be to grow and diversify the NuttX community. We
> will convert that code base to the Apache license during incubation.
>
>
> =Current Status=
>
> As previously mentioned, NuttX is a mature, stable product in wide use in
> embedded products.
>
>
> ==Meritocracy==
>
> We value meritocracy and we understand that it is the basis for an open
> community that encourages multiple companies and individuals to contribute
> and be invested in the project’s future. We will encourage and monitor
> participation and make sure to extend privileges and responsibilities to
> all contributors.
>
> Being a mature project, NuttX already has an extensive user base with many
> people who understand the software, who have committed hundreds of changes,
> and are happy to participate in the project.  I believe that with a little
> guidance and formalization, a PMC and a large group of experienced
> committers can quickly be established.
>
>
> ==Community==
>
> NuttX has a large, active community.  Communication is via a Google group
> at https://groups.google.com/forum/#!forum/nuttx where there are 395
> members as of this writing.  Code is currently maintained
> at Bitbucket.org at https://bitbucket.org/nuttx/.  Other communications
> are
> through Bitbucket issues and also via Slack for focused, interactive
> discussions.
>
> Keeping up with the communications, requests for help, issues, and
> contributions is more than a full time job at this time.
>
>
> ==Core Developers==
>
> NuttX was initially developed by Gregory Nutt, released as an open source
> project on February 17, 2007, and is still under active development.  There
> are several dozen, active, frequent contributors involved with the project.
> The core OS can be considered finished at this point, but development
> continues in specialized areas of networking, IoT, cryptography, tools, and
> other more specialized functions.
>
>
> =Alignment=
>
> NuttX is an original development with some small percentage of ported
> code.  It stands alone depends on no other projects.
>
>
> =Known Risks=
>
> ==Orphaned Products==
>
> We are committed to the future development of NuttX and understand that
> graduation to a TLP, while preferable, is not the only positive outcome of
> incubation.
>
> Should the NuttX project be accepted by the Incubator, the prospective PPMC
> would be willing to agree to a 

Re: Help Verify Apache(incubating) TVM Release RC

[Tianqi Chen]

Thanks Yizhi.

Thanks Justin for super helpful feedbacks! Please let us know if you have
further suggestions. We plan to start a formal vote in a day if things are
OK(of course the rc will be moved to the dist server).

TQ

On Tue, Nov 26, 2019 at 7:59 PM YiZhi Liu  wrote:

> Thanks Justin and Tianqi. RC2 is created with the fixes,
> https://github.com/apache/incubator-tvm/releases/tag/v0.6.0.rc2
>
> On Tue, Nov 26, 2019 at 2:52 PM Tianqi Chen 
> wrote:
> >
> >   On Tue, Nov 26, 2019 at 2:43 PM Justin Mclean <
> jus...@classsoftware.com>
> > wrote:
> >
> > > Hi,
> > >
> > > > The license [3] actually provides three licenses. The legacy section
> of
> > > > the license indicate that the file is also licensed under MIT and
> > > > University of Illinois/NCSA.
> > >
> > > Forgot to say this isn’t a case of dual licensing, in this case all
> > > licenses apply to different bits of the code, so you cannot just
> select the
> > > license you want.
> > >
> >
> > The file we are referring to was licensed under MIT and according to
> > https://llvm.org/docs/DeveloperPolicy.html#legacy it will still be
> > available under MIT, as long as we do not pull the updated version of the
> > file after they completed the codebase migration.
> >
> > Thanks,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
>
>
>
> --
> Yizhi Liu
> Bay Area, the United States
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Help Verify Apache(incubating) TVM Release RC

[Tianqi Chen]

  On Tue, Nov 26, 2019 at 2:43 PM Justin Mclean 
wrote:

> Hi,
>
> > The license [3] actually provides three licenses. The legacy section of
> > the license indicate that the file is also licensed under MIT and
> > University of Illinois/NCSA.
>
> Forgot to say this isn’t a case of dual licensing, in this case all
> licenses apply to different bits of the code, so you cannot just select the
> license you want.
>

The file we are referring to was licensed under MIT and according to
https://llvm.org/docs/DeveloperPolicy.html#legacy it will still be
available under MIT, as long as we do not pull the updated version of the
file after they completed the codebase migration.

Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Help Verify Apache(incubating) TVM Release RC

[Tianqi Chen]

Thanks Justin, these are super helpful! We will address these problems as
follows, please let us know if you have additional suggestions

- NOTICE is still incorrect
>
We will change  "2019 and onwards" to  "2019".

- I did notice a directory called "3rdparty/dlpack/apps/from_numpy” is this
> code from numpy?
>
No the code demonstrate how to convert data from numpy to the dlpack
format, the code is under ALv2 license as indicated by dlpack repo


> - This file [2] has two copyright lines is this correct?

We will fix the problem and keep on copyright file.


> - This license [3] notes some exceptions to the ALv2 license, this might
> be an issue and I suggest you ask on legal discuss if this is OK. I
> wouldn't let this hold up a release.
>

 The license [3] actually provides three licenses. The legacy section of
the license indicate that the file is also licensed under MIT and
University of Illinois/NCSA.
 We reported the file as MIT license as indicated in the source header. We
also agree to discuss the exemption on ASF legal

cma.c and cma/Makefile

The file belongs to kernel module(which our code base does not depend on)
but can be helpful when user builds a customized version of linux to run
the VTA driver.
Although the driver file itself is MIT, because linux kernel driver has a
policy that open source driver has to be dual licensed to GPL, the driver
declaration declared the binary module as GPL.
After looking it closely we agree that this poses a potential risk, and
will remove the file from the project (we will suggest the community to
host a separate repo for kernel driver plugins).


> 1. 3rdparty/cma//Makefile
> 2. 3rdparty/compiler-rt/builtin_fp16.h
> 3 ./licenses/LICENSE.builtin_fp16.txt
> 4. ./3rdparty/cma/cma.c
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Help Verify Apache(incubating) TVM Release RC

[Tianqi Chen]

 Thanks Justin for providing helpful feedbacks! and thanks Yizhi for making
the improvement and bringing another RC.
The community did another pass over the licenses and addressed Justin's
note and made a sweep of the codebase to remove all the un-necessary
copyright messages(including those that are not on Justin's list).

The community would like to hold the release to the highest possible
standard in our first release and these feedbacks are super valuable for
us.
It would be great to get further feedbacks from IPMC members to help us to
uphold that standard.

Please refer to the updated RC:
https://github.com/apache/incubator-tvm/releases/tag/0.6.0.rc1

Thank you!
TQ


On Sun, Nov 24, 2019 at 3:29 PM YiZhi Liu  wrote:

> Hi Justin,
>
> Many thanks to your help. We just addressed the issues and created
> another [RC](
> https://github.com/apache/incubator-tvm/releases/tag/0.6.0.rc1).
> Would you mind check whether it is in good shape?
>
> We highly appreciate your patience and guidance.
>
> Thanks,
> Yizhi
>
> On Sat, Nov 23, 2019 at 5:25 PM Justin Mclean 
> wrote:
> >
> > Hi,
> >
> > > Looks for copyrights inside the files, file with ASF header should
> have no copyright lines.
> >
> > Well ones donated to the ASF anyway.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> --
> Yizhi Liu
> Bay Area, the United States
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Help Verify Apache(incubating) TVM Release RC

[Tianqi Chen]

Re LLVM’s license issue. I believe MIT is a safer choice for compiler-rt
before we confirm with ASF.

Because strictly LLVM’s apache license comes with an exemption Clause which
needs to be reviewed. Given that the code is also dual licensed under MIT,
we should take that as a safer choice until we get official position from
the ASF wrt to the exemption

TQ

On Sat, Nov 23, 2019 at 4:39 PM YiZhi Liu  wrote:

> Hi Justin,
>
> for ./3rdparty/compiler-rt/builtin_fp16.h , from
> [here](
> https://github.com/llvm-mirror/compiler-rt/blob/master/LICENSE.TXT#L240-L241
> )
> it says it was dual licensed under University of Illinois and the MIT
> license, though the current LICENSE file declares ALv2. I believe the
> builtin_fp16.h file was collected before its license be changed to
> ALv2. Shall we say it is ALv2, or MIT?
>
> And would you mind advise what was wrong with the following files?
> 6. /nnvm/include/nnvm/op.h  - looks zlib is not used there?
> 7 ./src/schedule/bound.cc
>
> On Sat, Nov 23, 2019 at 2:54 PM YiZhi Liu  wrote:
> >
> > Thanks Justin for helping, we'll make modification accordingly.
> >
> > On Sat, Nov 23, 2019 at 2:15 PM Justin Mclean 
> wrote:
> > >
> > > Hi,
> > >
> > > I checked the release candidate further:
> > > - Signatures and hashes good
> > > - DISCLAIMER exists
> > > - LICENSE is missing a few things
> > > - NOTICE needs some minor adjustments
> > > - Some files are missing ASF headers e.g. [1][2][3][4][5] (+ others)
> > > - Some files incorrectly have an ASF headers or have ASF lines with a
> unneeded copyright line. e.g [6][7][8][9][10][11] and many many other files.
> > > - No unexpected binary files
> > >
> > > You'll need to remove all "Copyright (c)  by Contributors” where
> the files were donated to the ASF (and there’s signed ICLAS for everyone
> that worked on that file) so it clear what is a 3rd party file and what is
> not.
> > >
> > > Because of the above issue it impossible to work out what is missing
> in  LICENCE, this will be a subset:
> > > - Code zlib licensed in  [6]
> > > - BSD code in [9] (this is not ALv2 likened as mentioned the LICENSE
> file)
> > > - ASv2 licensed code in [11]
> > > - BSD code in [12]
> > >
> > > In NOTICE is incorrect to say “2017 and onwards”, it should just be
> 2019.
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. ./nnvm/tests/cpp/unittest.mk
> > > 2. ./nnvm/make/config.mk
> > > 3. ./ docs/_static/css/tvm_theme.css
> > > 4. apps/android_rpc/app/src/main/jni/Android.mk
> > > 5. apps/ios_rpc/tvmrpc/Base.lproj/LaunchScreen.storyboard
> > > 6. /nnvm/include/nnvm/op.h
> > > 7. ./src/schedule/bound.cc
> > > 8. ./src/schedule/bound.cc
> > > 9.  vi ./3rdparty/picojson/picojson.h
> > > 10. ./vta/src/de10nano/cma_api.cc
> > > 11. /3rdparty/compiler-rt/builtin_fp16.h
> > > 12. ./3rdparty/dmlc-core/include/dmlc/concurrentqueue.h
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@tvm.apache.org
> > > For additional commands, e-mail: dev-h...@tvm.apache.org
> > >
> >
> >
> > --
> > Yizhi Liu
>
>
>
> --
> Yizhi Liu
> Bay Area, the United States
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Help Verify Apache(incubating) TVM Release RC

[Tianqi Chen]

Thanks Justin! This is exactly kind of feedback we are looking for.

The community would like to hold the release to the highest possible
standard, which means we would like to make sure the release meet the
criteria of the standard disclaimer. We will look into the
compatibility issue of LLVM license.

TQ

On Sat, Nov 23, 2019 at 12:04 AM Justin Mclean 
wrote:

> Hi,
>
> I’ve not had an extensive look but I note this license in your license
> file:
> LLVM Release License
>
> While a BSD style license (I think) it not listen in Apaches list of
> compatible licenses. You’ll also note it include other 3rd party licensed
> buts of software, these would need to be checked if they are compatible
> with ALv2 and listed in the LICENSE file if your include any code under
> those licenses.
>
> I's also suggest you use the work in progress DISCLAIMER [1], as it more
> likely your first release will pass an IPMC votes if you do so.
>
> Thanks,
> Justin
>
> 1. https://incubator.apache.org/policy/incubation.html#disclaimers
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Help Verify Apache(incubating) TVM Release RC

[Tianqi Chen]

Dear IPMC:

I am sending this email to let you know that the Apache (incubating) TVM
community started a formal RFC for our first apache release.

Because this is our first ASF release, the community wanted to hold the
release to the highest standard possible, by starting an RFC to ask
everyone to verify the RC before the formal vote.

While we have already gone through the common checklist(such as licenses
and disclaimer), we would love to get help from IPMC members as well, if
possible, to help us check if there is anything that we might be missing.

Please refer to the following thread:

- RFC thread https://github.com/apache/incubator-tvm/issues/4406
- Mirrored dev@ thread about the same RFC:
https://lists.apache.org/thread.html/a5a4d6e43975809aebab46043d95ecd794a7d9235f078d732ab4e515@%3Cdev.tvm.apache.org%3E

Thank you!
TQ

Write Access to Wiki

[Tianqi Chen]

Hi:

Can someone give me write access to the incubator wiki? I need the
permission to migrate the podling report.
Wiki username: TianqiChen

Thank you!
Tianqi

Re: Prodling reports due 3rd April

[Tianqi Chen]

TVM PMC has finished the report and we are just waiting to get things on
the incubator wiki.

Tianqi

On Wed, Apr 3, 2019 at 2:23 PM Justin Mclean 
wrote:

> Hi,
>
> Podling reports are now due and we’re missing reports from:
> - Annotator
> - Gobblin
> - Milagro
> - MXNet
> - Spot
> - TVM
>
> I can see Annotator and MXnet are working on reports, please get them is
> as soon as you can. For other projects can the Mentors please remind your
> podling that their report is due. Any podling not submitting on time will
> be asked to report next month.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [Result][VOTE] Accept Apache TVM into the incubator

[Tianqi Chen]

Thank you, everyone.
I will follow up by cross-posting in the TVM community as well as give
a public roadmap regarding next steps together with the help from our
mentors.  I am traveling this week and will draft and cross-post the public
roadmap of incubator transition this weekend.

Tianqi

On Wed, Mar 6, 2019 at 1:47 PM Markus Weimer  wrote:

> The vote has concluded with 13 binding and 5 non-binding and 1 unclear +1
> votes,
> no other votes were cast. TVM has been accepted into the incubator. The
> voring
> tally is below
>
> Thanks!
>
> Markus
>
> Binding +1:
>
>
>   * Sebastian
>   * Gon
>   * Markus
>   * Henry
>   * Furkan
>   * Felix
>   * Timothy
>   * Willem
>   * Mohammad
>   * Sheng
>   * Vinayakumar
>   * Gosling
>   * Jason
>
>
> Non-Binding
>
>   * Sheng
>   * Kellen
>   * Cihad
>   * Huxing
>   * Tianqui
>
> Undeclared:
>
>   * Matt
>
>
> On Mon, Mar 4, 2019 at 12:18 AM Jason Dai  wrote:
> >
> > +1 (binding)
> >
> > Thanks,
> > -Jason
> >
> > On Mon, Mar 4, 2019 at 2:50 PM Gosling Von  wrote:
> >
> > > +1, binding
> > >
> > >
> > > Best Regards,
> > > Von Gosling
> > >
> > > > 在 2019年2月28日，下午12:44，Markus Weimer  写道：
> > > >
> > > > Hi everyone,
> > > >
> > > > we've discussed the proposal for the TVM project in [1]. The proposal
> > > itself can
> > > > be found on the wiki [2].
> > > >
> > > > According to the Incubator rules[3] I'd like to call a vote to accept
> > > the new
> > > > TVM project as a podling in the Apache Incubator.
> > > >
> > > > A vote for accepting a new Apache Incubator podling is a majority
> vote.
> > > Everyone
> > > > is welcome to vote, only Incubator PMC member votes are binding. It
> > > would be
> > > > helpful (but not required) if you could add a comment stating whether
> > > your vote
> > > > is binding or non-binding.
> > > >
> > > > This vote will run for at least 72 hours (but I expect to keep it
> open
> > > for
> > > > longer). Please VOTE as follows:
> > > >
> > > > [ ] +1 Accept TVM into the Apache Incubator
> > > > [ ] +0 Abstain
> > > > [ ] -1 Do not accept TVM into the Apache Incubator because ...
> > > >
> > > > Thank you for everyone who decided to join in in the past
> discussions!
> > > >
> > > > Markus
> > > >
> > > > [1]:
> > >
> https://lists.apache.org/thread.html/e2b1fe9ca76422ec80b146a6b120091f2419e2f1c27d57080f39cf6f@%3Cgeneral.incubator.apache.org%3E
> > > >
> > > > [2]: https://wiki.apache.org/incubator/TVMProposal
> > > >
> > > > [3]: https://incubator.apache.org/guides/proposal.html#the_vote
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Apache TVM into the incubator

[Tianqi Chen]

+1 (non-binding

On Thu, Feb 28, 2019 at 12:23 AM Cihad Guzel  wrote:

> +1 (non-binding)
>
> 28 Şub 2019 Per 11:08 tarihinde Felix Cheung  şunu
> yazdı:
>
> > +1 (binding)
> >
> > On Wed, Feb 27, 2019 at 10:17 PM kellen sunderland <
> > kellen.sunderl...@gmail.com> wrote:
> >
> > > +1 (non-binding)
> > >
> > > On Wed, Feb 27, 2019, 10:15 PM Furkan KAMACI 
> > > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > 28 Şub 2019 Per, saat 08:40 tarihinde Henry Saputra <
> > > > henry.sapu...@gmail.com>
> > > > şunu yazdı:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > On Wed, Feb 27, 2019 at 8:44 PM Markus Weimer 
> > > wrote:
> > > > >
> > > > > > Hi everyone,
> > > > > >
> > > > > > we've discussed the proposal for the TVM project in [1]. The
> > proposal
> > > > > > itself can
> > > > > > be found on the wiki [2].
> > > > > >
> > > > > > According to the Incubator rules[3] I'd like to call a vote to
> > accept
> > > > the
> > > > > > new
> > > > > > TVM project as a podling in the Apache Incubator.
> > > > > >
> > > > > > A vote for accepting a new Apache Incubator podling is a majority
> > > vote.
> > > > > > Everyone
> > > > > > is welcome to vote, only Incubator PMC member votes are binding.
> It
> > > > would
> > > > > > be
> > > > > > helpful (but not required) if you could add a comment stating
> > whether
> > > > > your
> > > > > > vote
> > > > > > is binding or non-binding.
> > > > > >
> > > > > > This vote will run for at least 72 hours (but I expect to keep it
> > > open
> > > > > for
> > > > > > longer). Please VOTE as follows:
> > > > > >
> > > > > > [ ] +1 Accept TVM into the Apache Incubator
> > > > > > [ ] +0 Abstain
> > > > > > [ ] -1 Do not accept TVM into the Apache Incubator because ...
> > > > > >
> > > > > > Thank you for everyone who decided to join in in the past
> > > discussions!
> > > > > >
> > > > > > Markus
> > > > > >
> > > > > > [1]:
> > > > > >
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/e2b1fe9ca76422ec80b146a6b120091f2419e2f1c27d57080f39cf6f@%3Cgeneral.incubator.apache.org%3E
> > > > > >
> > > > > > [2]: https://wiki.apache.org/incubator/TVMProposal
> > > > > >
> > > > > > [3]: https://incubator.apache.org/guides/proposal.html#the_vote
> > > > > >
> > > > > >
> > -
> > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > > For additional commands, e-mail:
> general-h...@incubator.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [Proposal] Apache TVM

[Tianqi Chen]

Thanks Henry!

On Thu, Feb 28, 2019 at 10:57 AM Henry Saputra 
wrote:

> Thanks, Markus.
>
> Hope you do not mind but I have edited the proposal to reflect the changes.
> Since the people did not actually change, I think we can continue with the
> VOTE
>
>
> - Henry
>
> On Thu, Feb 28, 2019 at 10:20 AM Markus Weimer  wrote:
>
> > On Thu, Feb 28, 2019 at 9:36 AM Henry Saputra 
> > wrote:
> >
> > > > What I can do instead is to restructure the proposal to have PPMC to
> > > > include mentors and the PMC members from TVM.
> > > > And the rest of committers from TVM will invited from VOTE from PPMC.
> > >
> >
> > Yes, that is what I should have done in the final edits of the Proposal,
> > but did not do. This is how all other incubator projects I've been in
> have
> > done it: PPMC is mentors + leaders / founders / members of the inbound
> > project. For TVM, the most appropriate thing is to have the PPMC be
> mentors
> > + TVM's current PMC.
> >
> > If we agree on that, I'd like to make the change in the proposal, and
> leave
> > the vote open.
> >
> > Thanks for spotting this, Henry!
> >
> > Markus
> >
>

Re: [Proposal] Apache TVM

[Tianqi Chen]

Hi Henry:

Because the TVM community already adopts Apache meritocracy and has a
separation of PMC and committers. Every new member(PMC and committers) are
formally discussed and we welcome each member in the community by
summarizing their contributions.
If possible,  we would like to keep the same structure during incubation.
The current PMC members are actively proposing new committers and PMC
members from different organizations in the past few months and will
continue doing so after the incubation.

Tianqi

On Wed, Feb 27, 2019 at 9:07 PM Henry Saputra 
wrote:

> Bit more clarifications, as new podling in Apache, the initial members of
> PPMC consist of mentors and initial commiters of the project.
>
> I understand TVM already work mirroring ASF meritoracy [1] but we need to
> change the proposal to follow Apache guidelines to help us cross check
> membership later for onboarding.
>
> If it is OK with you I will change the proposal to merge the "Initial PPMC
> Members" and "Initial Committers", minus the mentors from ASF, to be just
> Initial Committers.
>
> Thanks,
>
> - Henry
>
>
> [1] https://github.com/dmlc/tvm/blob/master/CONTRIBUTORS.md
>
> On Tue, Feb 26, 2019 at 9:56 AM Markus Weimer  wrote:
>
> > Thanks everyone for the discussion thus far. Based on it, I have uploaded
> > an updated proposal here:
> >
> > https://wiki.apache.org/incubator/TVMProposal
> >
> > The changes made are:
> >
> >1. Rectify the language around PMC vs. PMC member. Thanks Greg, for
> >pointing that out!
> >2. Adding Furkan, Timothy and Henry as additional mentors. We can use
> >all the help :)
> >
> > Assuming there are no further discussion points, I'd like to move forward
> > with a [VOTE]. I'll let this sit here and simmer for another 24h to make
> > sure we are done with the discussion phase.
> >
> > Thanks,
> >
> > Markus
> >
> >
> > On Mon, Feb 18, 2019 at 1:08 PM Tianqi Chen  wrote:
> >
> > > Thanks, everyone for helpful feedbacks. I would like to clarify a few
> > > points being raised so far on behalf of the current TVM PMC.
> > >
> > > > PMC vs PMC member
> > >
> > > Thanks for pointing it out. This is something we overlooked and will
> > update
> > > the proposal to make the change accordingly.
> > >
> > > > Champion
> > >
> > > Markus has been actively engaging with the TVM community and helped the
> > > community start the incubation process. These efforts include:
> > > - Introduce the Apache way to in the TVM conference last Dec
> > >-
> > >
> >
> https://sampl.cs.washington.edu/tvmconf/slides/Markus-Weimer-TVM-Apache.pdf
> > > - Help the community to start the incubation conversation(also Thanks
> to
> > > Sebastian and Gon)
> > >- https://github.com/dmlc/tvm/issues/2401
> > > - Watch the pre-incubation private list, and give helpful feedback
> > >
> > > While we do not expect our mentor to actively watch the community on
> the
> > > daily basis(many of our committers only contribute a few days in a
> week),
> > > he has been very responsive and helped us to shape the incubation
> > proposal
> > > and most importantly be a strong advocate of the Apache way. I
> personally
> > > think he is more than qualified as our champion:)
> > >
> > > > Hardware artifact
> > >
> > > INAL, however, given that Apache only releases source code and our
> source
> > > code is in the form of software source code (HLS C and we are moving to
> > > Chisel-(scala) ). Then anyone can take the software source code and
> > > generate unofficial hardware release.
> > >
> > > Tianqi
> > >
> > >
> > > On Mon, Feb 18, 2019 at 6:44 AM Bertrand Delacretaz <
> > > bdelacre...@codeconsult.ch> wrote:
> > >
> > > > Hi,
> > > >
> > > > On Mon, Feb 18, 2019 at 11:44 AM Justin Mclean <
> > jus...@classsoftware.com
> > > >
> > > > wrote:
> > > > > > If the Apache License works for those artifacts I think that's
> > > fine...
> > > > >
> > > > > It probably doesn’t, but it's complex and INAL, but I have touched
> on
> > > > this about this in IoT talks at previous ApacheCons...
> > > >
> > > > FWIW the prior discussions that I mentioned are linked below - from
> > > > board@ so accessible for ASF Memb

Re: [Proposal] Apache TVM

[Tianqi Chen]

Thanks, everyone for helpful feedbacks. I would like to clarify a few
points being raised so far on behalf of the current TVM PMC.

> PMC vs PMC member

Thanks for pointing it out. This is something we overlooked and will update
the proposal to make the change accordingly.

> Champion

Markus has been actively engaging with the TVM community and helped the
community start the incubation process. These efforts include:
- Introduce the Apache way to in the TVM conference last Dec
   -
https://sampl.cs.washington.edu/tvmconf/slides/Markus-Weimer-TVM-Apache.pdf
- Help the community to start the incubation conversation(also Thanks to
Sebastian and Gon)
   - https://github.com/dmlc/tvm/issues/2401
- Watch the pre-incubation private list, and give helpful feedback

While we do not expect our mentor to actively watch the community on the
daily basis(many of our committers only contribute a few days in a week),
he has been very responsive and helped us to shape the incubation proposal
and most importantly be a strong advocate of the Apache way. I personally
think he is more than qualified as our champion:)

> Hardware artifact

INAL, however, given that Apache only releases source code and our source
code is in the form of software source code (HLS C and we are moving to
Chisel-(scala) ). Then anyone can take the software source code and
generate unofficial hardware release.

Tianqi


On Mon, Feb 18, 2019 at 6:44 AM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi,
>
> On Mon, Feb 18, 2019 at 11:44 AM Justin Mclean 
> wrote:
> > > If the Apache License works for those artifacts I think that's fine...
> >
> > It probably doesn’t, but it's complex and INAL, but I have touched on
> this about this in IoT talks at previous ApacheCons...
>
> FWIW the prior discussions that I mentioned are linked below - from
> board@ so accessible for ASF Members of Officers only, but we can
> distill them as needed if a concrete need appears with TVM.
>
> We didn't go past the discussions stage at that time (2011) but if
> there's another case of hardware at the ASF I'm willing to help
> restart those discussions to move this forward. Either to define which
> additions to the Apache License are required, or to clarify that it's
> ok as is.
>
> So unless there are specific objections about accepting a project
> which includes hardware as a software artifact I'm in favor of
> accepting TVM and sorting out these things during incubation.
>
> -Bertrand
>
> Prior board@ discussions at https://s.apache.org/hw2011_1 and
> https://s.apache.org/hw2011_2
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc0

[Tianqi Chen]

Hi Justin, it would be great if we can clarify the policy the submodule
dependencies.

Strictly speaking, these dependencies are in the form of git submodule and
they are not part of the commit tree (instead, they are pointers to the
specific version of dependency).
If we just do git clone, or tag the release, the source content of
submodule dependencies will not be part of tarball, so in some sense, they
can be excluded as the part of the release, which might help us to make an
easier release.

Tianqi

On Wed, Jan 9, 2019 at 9:08 PM Justin Mclean 
wrote:

> Hi,
>
> I assume you realise this would be a lot easier if the dependancies were
> not copied into the git tree (as mentioned in the link you posted) , but I
> assume there a reason for doing this that I’m not aware of.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[RFC] Community Diversity and How to Encourage Collaboration

[Tianqi Chen]

Dear Incubator General:
I am writing this email to seek your experience on how do you try to
encourage diversity in your community and encourage collaboration among
contributors across organizations. One of the key driving force of Apache
is its neural nature which encourages collaboration among different
organizations. On the other hand, admittedly usually each community have
its majority organization.
As an Apache contributor, and while building another open source
projects. I always wonder how could we best encourage collaboration among
organizations.

   Recently I tried to propose a guideline to MXNet community to encourage
PMC members to propose committers that comes from different organizations
that they come from.

   There is certainly some is a controversy in this, and I would like to
see what is the opinions of the people here on whether this is an
appropriate thing to try in an Apache community.

Thanks!

Tianqi

Re: MXNet External Sources (was Re: [VOTE] Apache MXNet (incubating) 1.0.0 release RC1)

[Tianqi Chen]

Many of them are stand-alone project on their own that MXNet happens to
depend on. Major open source projects other than MXNet depend on these
projects(e.g. XGBoost depend on dmlc-core).  So, for now, they can be
viewed as external dependencies like boost.

DMLC have talked about migrating more major projects to ASF to build an
Apache deep learning stack and had the intention to do so. Which I feel
belong to a separate discussion thread.

Tianqi

On Fri, Dec 1, 2017 at 4:16 PM, John D. Ament  wrote:

> One question about the below.  We've noted that much of the source code for
> MXNet is coming from the external DMLC repos.  Are there plans to move
> those repos into the ASF?
>
> John
>
> On Fri, Dec 1, 2017 at 7:13 PM Hen  wrote:
>
> > +1.
> >
> > Items I note should happen post release are:
> >
> > * Move the various git submodules into third-party/ or similar so it's
> > simpler to see what is Apache original source when we review a release.
> > * Deal with the Copyright statements in perl-package (copyright holder
> has
> > approved doing this)
> > * Lots of whitespace on end of NOTICE
> > * Comment added to CODEOWNERS to explain the file so we don't cause
> > community problems
> > * There was a suggestion to simplify the LICENSE to not explicitly list
> > which packages are under each license. Something to consider.
> >
> > Hen
> >
> >
> >
> > On Thu, Nov 30, 2017 at 4:45 PM, Chris Olivier 
> > wrote:
> >
> > > Hello All,
> > >
> > >
> > > This is a call for releasing Apache MXNet (incubating) 1.0.0, release
> > > candidate 1.
> > >
> > >
> > > Apache MXNet community has voted and approved the release.
> > >
> > >
> > > *Vote thread:*
> > >
> > > https://lists.apache.org/thread.html/568bf0c9960f14640b753a5fb6766c
> > > 7b0074339d286f405c04ffec96@%3Cdev.mxnet.apache.org%3E
> > >
> > >
> > > *Result thread:*
> > >
> > > https://lists.apache.org/thread.html/558a60f4d0c16b0311c96afd059082
> > > ebde0f773c56a03cb9e00bc19f@%3Cdev.mxnet.apache.org%3E
> > >
> > >
> > > *The source tarball, including signatures, digests, etc. can be found
> > at:*
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.0.0.rc1/
> > >
> > >
> > >
> > > *The release tag can be found here: *
> > >
> > > https://github.com/apache/incubator-mxnet/tree/1.0.0.rc1
> > >
> > >
> > >
> > > *The release hash is *25720d0e3c29232a37e2650f3ba3a2454f9367bb* and
> can
> > be
> > > found here:*
> > >
> > >  > > 25720d0e3c29232a37e2650f3ba3a2454f9367bb>
> > >
> > >
> > >
> > > *Release artifacts are signed with the following key:*
> > >
> > > 16DD B2E2 FE0C 3925 CB13  38D7 21F3 F9AB C622 DF82
> > >
> > >
> > >
> > > *KEY files are available here:*
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> > >
> > >
> > >
> > > *For information about the contents of this release, see:*
> > >
> > >  > > Apache+MXNet+%28incubating%29+1.0+Release+Notes>
> > >
> > >
> > >
> > > The vote will be open for at least 72 hours.
> > >
> > >
> > > [ ] +1 Release this package as 1.0.0
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 Do not release this package because...
> > >
> > >
> > > Thanks,
> > >
> > >
> > > -Chris Olivier
> > >
> > > cjolivie...@apache.org
> > >
> >
>