Re: [DISCUSS] Graduate Apache SDAP (Incubating) as a Top Level Project
t; > > - Stepheny Perez > > > - Wai Linn Phyo > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Nga Thien Chung > > > be appointed to the office of Vice President, Apache SDAP, 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 SDAP Project be and hereby is tasked with > > > the migration and rationalization of the Apache Incubator SDAP > > > podling; and be it further > > > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > > SDAP podling encumbered upon the Apache Incubator PMC are hereafter > > > discharged. > > > > > > [1] https://lists.apache.org/thread/vjwjmp0h2f22dv423h262cvdg5x7jl03 > > > [2] https://lists.apache.org/thread/m9vqwv23jdsofwgmhgxg25f5l1v2j7nz > > > [3] https://lists.apache.org/thread/4o1qjsk2cly2ppxcsmm2swzd6pcg3lxj > > > [4] https://lists.apache.org/thread/qtxlxl4gj6n33wvm164vdxxnwdlppttl > > > [5] https://lists.apache.org/thread/rr74c35fojc7ythmcgnoplyjllhbslj4 > > > [6] > > > https://github.com/apache/incubator-sdap-website/blob/asf-site/maturity.md > > > > > > - > > > 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 > > > > > -- Byung-Gon Chun
Re: [MENTORS] Late podling reports and missing signoffs
Yes. I just noticed. To be fair, not submitting a report in time is my fault, not the fault of the community. I guess the lack of support for graduation might have decreased activities. The community is addressing work items. On Mon, Mar 13, 2023 at 2:47 PM Calvin Kirs wrote: > On Mon, Mar 13, 2023 at 1:28 PM Byung-Gon Chun wrote: > > > > Hi, > > > > Nemo will report next month. > > Hi, thanks for your reply. but the shepherd has some comments [1], do > you notice? > > [1]https://cwiki.apache.org/confluence/display/INCUBATOR/March2023#nemo > > > > -Gon > > > > > > On Wed, Mar 8, 2023 at 2:23 PM Calvin Kirs wrote: > > > > > Hi, > > > > > > We are missing reports from: > > > - Baremaps > > > - Nemo > > > - PageSpeed > > > - Spot > > > - Toree > > > - Training > > > - Uniffle > > > > > > We are missing mentor sign-off on: > > > - Wayang > > > > > > -- > > > Best wishes！ > > > CalvinKirs > > > > > > ----- > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > -- > > Byung-Gon Chun > > > > -- > Best wishes！ > CalvinKirs > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: [MENTORS] Late podling reports and missing signoffs
Hi, Nemo will report next month. -Gon On Wed, Mar 8, 2023 at 2:23 PM Calvin Kirs wrote: > Hi, > > We are missing reports from: > - Baremaps > - Nemo > - PageSpeed > - Spot > - Toree > - Training > - Uniffle > > We are missing mentor sign-off on: > - Wayang > > -- > Best wishes！ > CalvinKirs > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: [DISCUSS] Graduate NEMO to TLP
We have some concerns from William and Calvin. How should we proceed? Thanks. -Gon On Thu, Nov 17, 2022 at 12:45 PM Willem Jiang wrote: > I just checked the contribution of the Nemo project[1] and the traffic > of d...@nemo.apache.org[2]. > It looks like the project was quiet for two years. I have a concern > if this project can still be active after graduation. > > I think we need to provide more evidence that the project already > builds up the community. > > [1]https://github.com/apache/incubator-nemo/graphs/contributors > [2]https://lists.apache.org/list?d...@nemo.apache.org > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Nov 14, 2022 at 6:33 PM Won Wook SONG wrote: > > > > Hi, > > > > Do we have additional opinions or feedback on what we have to do in order > > to proceed to our further steps, or are we ready to go? > > > > Best, > > Wonook > > > > > > 2022년 11월 11일 (금) 오후 4:01, Byung-Gon Chun 님이 작성: > > > > > Hi, > > > > > > The Nemo codebase has been well established. It's one of Apache Beam > > > runners, and it can be used in Google dataproc. Its batch processing is > > > mature, and the community has been working on stream processing. > > > The current committers will be added to PMC. > > > I think the Nemo project should have graduated. > > > > > > Best, > > > Gon > > > > > > > > > On Wed, Nov 9, 2022 at 3:06 PM Won Wook SONG > wrote: > > > > > > > Hi! > > > > > > > > Thanks for your feedback :) I've solved the issues related to our > > > website. > > > > As for the activity level, our system has initially gone over a > thorough > > > > development period at first. Now that essential features are already > > > > developed, we have been adding more specific features like dynamic > task > > > > offloading, hierarchical aggregation, dynamic skew detection, and > > > extending > > > > our data plane to special file systems. Such development had been > done in > > > > units of projects, and their PRs are quite large in terms of size, > and > > > > could have been reflected as an inactiveness in the Nemo project, but > > > this > > > > is actually not the case. > > > > I'll try to gently push our mentors for additional feedbacks. > > > > If you have any additional questions or concerns, please let us know! > > > > > > > > Thank you! > > > > > > > > Wonook > > > > > > > > On Nov 7, 2022, at 5:14 PM, Calvin Kirs wrote: > > > > > > > > On Mon, Nov 7, 2022 at 4:09 PM Calvin Kirs wrote: > > > > > > > > > > > > Hi, > > > > > > > > Nemo's activity level has been low for the past year or so, so I'm > not > > > > sure it's the right time to graduate, the last PPMC elected was in > > > > September 2021. > > > > > > > > and also there is only one mentor involved in your graduation > > > > discussion, and I would like to hear the thoughts of other mentors. > > > > > > > > Here are some issues that need to be addressed. > > > > > > > > The website has some issues, please refer to [1]. > > > > > > > > It is not recommended to list affiliation( in [2], as it can confuse > > > > people. > > > > > > > > Checking google search, I can see a lot of Nemo software products, > I'm > > > > not sure if the branding issue is addressed, but I see [3]， maybe > it's > > > > fine. (I'm not familiar with Nemo). > > > > > > > > [1]: https://whimsy.apache.org/pods/project/nemo > > > > [2]https://nemo.apache.org/pages/team/ > > > > [3]https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-139 > > > > > > > > > > > > There are still some PPMCs not subscribe private@nemo.a.o. > > > > > > > > > > > > On Mon, Nov 7, 2022 at 12:39 PM Won Wook SONG > wrote: > > > > > > > > > > > > Hi all, > > > > > > > > The Apache Nemo podling has discussed[0] > > > > <https://lists.apache.org/thread/hv196tfg6jzltsjxnj28q572y6p3lvq2> > and > > > > voted > > > > upon[1] < > > > https://lists.apache.org/thread/dzfq12xdwbtmsn1l527o56kh56kz31mh>
Re: [DISCUSS] Graduate NEMO to TLP
Hi, The Nemo codebase has been well established. It's one of Apache Beam runners, and it can be used in Google dataproc. Its batch processing is mature, and the community has been working on stream processing. The current committers will be added to PMC. I think the Nemo project should have graduated. Best, Gon On Wed, Nov 9, 2022 at 3:06 PM Won Wook SONG wrote: > Hi! > > Thanks for your feedback :) I've solved the issues related to our website. > As for the activity level, our system has initially gone over a thorough > development period at first. Now that essential features are already > developed, we have been adding more specific features like dynamic task > offloading, hierarchical aggregation, dynamic skew detection, and extending > our data plane to special file systems. Such development had been done in > units of projects, and their PRs are quite large in terms of size, and > could have been reflected as an inactiveness in the Nemo project, but this > is actually not the case. > I'll try to gently push our mentors for additional feedbacks. > If you have any additional questions or concerns, please let us know! > > Thank you! > > Wonook > > On Nov 7, 2022, at 5:14 PM, Calvin Kirs wrote: > > On Mon, Nov 7, 2022 at 4:09 PM Calvin Kirs wrote: > > > Hi, > > Nemo's activity level has been low for the past year or so, so I'm not > sure it's the right time to graduate, the last PPMC elected was in > September 2021. > > and also there is only one mentor involved in your graduation > discussion, and I would like to hear the thoughts of other mentors. > > Here are some issues that need to be addressed. > > The website has some issues, please refer to [1]. > > It is not recommended to list affiliation( in [2], as it can confuse > people. > > Checking google search, I can see a lot of Nemo software products, I'm > not sure if the branding issue is addressed, but I see [3]， maybe it's > fine. (I'm not familiar with Nemo). > > [1]: https://whimsy.apache.org/pods/project/nemo > [2]https://nemo.apache.org/pages/team/ > [3]https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-139 > > > There are still some PPMCs not subscribe private@nemo.a.o. > > > On Mon, Nov 7, 2022 at 12:39 PM Won Wook SONG wrote: > > > Hi all, > > The Apache Nemo podling has discussed[0] > <https://lists.apache.org/thread/hv196tfg6jzltsjxnj28q572y6p3lvq2> and > voted > upon[1] <https://lists.apache.org/thread/dzfq12xdwbtmsn1l527o56kh56kz31mh> > graduation as a TLP. Following the incubation guide[2] > <https://incubator.apache.org/guides/graduation.html>, we now ask for > feedback on our graduation. > > Thanks to everyone who helped this project to get this far! > > Best, > Wonook > > [0]: https://lists.apache.org/thread/hv196tfg6jzltsjxnj28q572y6p3lvq2 > [1]: https://lists.apache.org/thread/dzfq12xdwbtmsn1l527o56kh56kz31mh > [2]: https://incubator.apache.org/guides/graduation.html > > > -- > X. Establish the Apache Nemo 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 application development on top of > >resource managers. > > > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management > >Committee (PMC), to be known as the "Apache Nemo Project", > >be and hereby is established pursuant to Bylaws of the > >Foundation; and be it further > > > >RESOLVED, that the Apache Nemo Project be and hereby is > >responsible for the creation and maintenance of a software > >framework for application development on top of resource > >managers; and be it further > > > >RESOLVED, that the office of "Vice President, Apache Nemo" > >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 Nemo Project, and to have primary > >responsibility for management of the projects within the scope > >of responsibility of the Apache Nemo 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 Nemo
Re: [DISCUSS] Incubating Proposal for Datark
Thanks for the interesting proposal! Another related Apache project is Nemo: https://nemo.apache.org/. -Gon On Mon, Sep 26, 2022 at 1:01 AM li gang wrote: > Glad to see this proposal, it's an interesting project,good luck. > > Yu Li 于2022年9月22日周四 11:45写道： > > > Hi All, > > > > I would like to propose Datark [1] as a new apache incubator project, and > > you can find the proposal [2] of Datark for more details. > > > > Datark is an intermediate (shuffle and spilled) data service for big data > > compute engines (Apache Spark, Apache Flink, Apache Hive, etc.) to boost > > performance, stability, and flexibility. It aims at enabling computing > > engines to fully embrace the disaggregated architecture. In a lot of > cases, > > intermediate data depends on large local disks, and is often a major > cause > > of inefficiency, instability, and inflexibility in the lifecycle of a > > distributed job. Datark solves the problems through the following core > > designs: > > > > 1. Push-based shuffle plus partition data aggregation to turn random IO > > access into sequential access. > > 2. FileSystem-like API to support writing spilled data. > > 3. Hierarchical storage from memory to DFS/object store to enable fast > > cache and massive storage space. > > 4. Engine-irrelevant APIs for easy integrating to various engines. > > 5. Extended fault tolerance and data replication to increase reliability > > > > Datark is currently adopted in the production environment at both Alibaba > > and many other companies, serving petabytes of data per day. Beyond that, > > it has more open source users including Shopee, NetEase, Bilibily, BOSS, > > and Synnex. Most of these users have made contributions to the project, > > forming an active community with dozens of developers. > > > > The proposed initial committers are interested in joining ASF to > reinforce > > extensive collaboration and build a more vibrant community. We believe > the > > Datark project will provide tremendous value for the community if it is > > introduced into the Apache incubator. > > > > I will help this project as the champion and many thanks to our four > other > > mentors: > > > > * Becket Qin (j...@apache.org) > > * Duo Zhang (zhang...@apache.org) > > * Lidong Dai (lidong...@apache.org) > > * Willem Jiang (ningji...@apache.org) > > > > FWIW, although with different solutions, the issues Datark aims to > resolve > > have some overlap with Apache Uniffle (incubating) [3]. Actually we > noticed > > this during the discussion phase of Uniffle incubation (when we were also > > preparing for the incubation) and had some open and friendly discussion > to > > see whether there could be a joint force [4], and finally decided to > > develop independently for the time being [5]. > > > > Look forward to your feedback. Thanks. > > > > Best Regards, > > Yu > > > > [1] https://github.com/alibaba/RemoteShuffleService > > [2] https://cwiki.apache.org/confluence/display/INCUBATOR/DatarkProposal > > [3] https://uniffle.apache.org/ > > [4] https://lists.apache.org/thread/1w74z5f0pb7bhslhzcl5x7rdj9s9objz > > [5] https://lists.apache.org/thread/pg8lzhzc1794x3yloqp169j0mdzqs3yw > > > > > -- > > > -- > Best Regards > > DolphinScheduler PMC > Gang Li 李岗 > > lgcar...@apache.org > -- Byung-Gon Chun
Re: [MENTORS] Late podling reports and missing signoffs
Hi, Nemo reported on time this month. Thanks! -Gon On Sun, Sep 11, 2022 at 11:40 PM Calvin Kirs wrote: > Hi, > > We are missing reports from: > - Flagon* > - Livy* > - Marvin-AI* > - Nemo > - PonyMail* > - SDAP* > - Spot* > - Teaclave* > - Toree* > - Training* > > We are missing mentor sign-off on:(Mentor signoff due by end of days > is Tue Sep 13th) > - Datalab > - StreamPipes > > * Also did not report last month > > -- > Best wishes！ > CalvinKirs > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: [MENTORS] Podling reports due today
Hi Justin, Thanks for the reminder. Nemo reported last month. I suggested that we skip the report this month. Thanks. -Gon On Wed, Jun 1, 2022 at 1:31 PM Justin Mclean wrote: > Hi, > > The podling report are due today and we are missing: > BRCP > Hivemall > Kvrocks > Kyuubi* > Livy > Marvin-AI > Nemo > PonyMail > SDAP > Spot > Wayang > > If you are a mentor of one of the above projects could you please > encourage them to submit a report as soon as they can. > > Kind Regards, > Justin > > * Has a draft/work in progress > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: Re: [VOTE] Graduate Apache InLong(Incubating) as a TLP
; > > > > > invitation > > >> > > > > > > > > > >> > > > > > > > [13]. > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > [1] > https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro > > >> > > > > > > > > > >> > > > > > > > [2] > https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20 > > >> > > > > > > > > > >> > > > > > > > [3] > https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9 > > >> > > > > > > > > > >> > > > > > > > [4] > https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t > > >> > > > > > > > > > >> > > > > > > > [5] https://inlong.apache.org/download/main/ > > >> > > > > > > > > > >> > > > > > > > [6] https://whimsy.apache.org/roster/ppmc/inlong > > >> > > > > > > > > > >> > > > > > > > [7] > https://github.com/apache/incubator-inlong/graphs/contributors > > >> > > > > > > > > > >> > > > > > > > [8] > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed > > >> > > > > > > > > > >> > > > > > > > [9] > https://github.com/apache/incubator-inlong/tree/master/licenses > > >> > > > > > > > > > >> > > > > > > > [10] > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG&title=Maturity+Assessment+for+InLong > > >> > > > > > > > > > >> > > > > > > > [11] > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List > > >> > > > > > > > > > >> > > > > > > > [12] https://inlong.apache.org/docs/next/introduction > > >> > > > > > > > > > >> > > > > > > > [13] > > >> > > > > > https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > -- > > >> > > > > > > > > > >> > > > > > > > Establish the Apache InLong 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 one-stop data integration framework that > provides > > >> > > > > > > > > > >> > > > > > > > automatic, secure, and reliable data transmission > capabilities. > > >> > > > > InLong > > >> > > > > > > > > > >> > > > > > > > supports both batch and stream data processing at the > same time, > > >> > > > > which > > >> > > > > > > > > > >> > > > > > > > offers great power to build data analysis, modeling, > and other > > >> > > > > > real-time > > >> > > > > > > > > > >> > > > > > > > applications based on streaming data. > > >> > > > > > > > > > >> > > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project > Management Committee > > >> > > > > > > > > > >> > > > > > > > (PMC), to be known as the "Apache InLong Project", be > and hereby is > > >> > > > > > > > > > >> > > > > > > > established pursuant to Bylaws of the Foundation; and > be it further > > >> > > > > > > > > > >> > > > > > > > RESOLVED, that the Apache InLong Project be and hereby > is responsible > > >> > > > > > > > > > >> > > > > > > > for the creation and maintenance of software related to > a one-stop > > >> > > > > data > > >> > > > > > > > > > >> > > > > > > > integration framework that provides automatic, secure, > and reliable > > >> > > > > > data > > >> > > > > > > > > > >> > > > > > > > transmission capabilities. InLong supports both batch > and stream data > > >> > > > > > > > > > >> > > > > > > > processing at the same time, which offers great power > to build data > > >> > > > > > > > > > >> > > > > > > > analysis, modeling, and other real-time applications > based on > > >> > > > > streaming > > >> > > > > > > > > > >> > > > > > > > data; and be it further > > >> > > > > > > > > > >> > > > > > > > RESOLVED, that the office of "Vice President, Apache > InLong" 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 InLong > > >> > > > > > > > > > >> > > > > > > > Project, and to have primary responsibility for > management of the > > >> > > > > > > > > > >> > > > > > > > projects within the scope of responsibility of the > Apache InLong > > >> > > > > > > > > > >> > > > > > > > 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 > InLong > > >> > > > > Project: > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > * Aloys Zhang > > >> > > > > > > > > > >> > > > > > > > * Charles Zhang > > >> > > > > > > > > > >> > > > > > > > * Guangxu Cheng > > >> > > > > > > > > > >> > > > > > > > * Guocheng Zhang > > >> > > > > > > > > > >> > > > > > > > * Heal Chow > > >> > > > > > > > > > >> > > > > > > > * Jean-Baptiste Onofré > > >> > > > > > > > > > >> > > > > > > > * Jerry Shao > > >> > > > > > > > > > >> > > > > > > > * Junjie Chen > > >> > > > > > > > > > >> > > > > > > > * Junping Du > > >> > > > > > > > > > >> > > > > > > > * Justin Mclean > > >> > > > > > > > > > >> > > > > > > > * Lamber Liu > > >> > > > > > > > > > >> > > > > > > > * Osgoo Li > > >> > > > > > > > > > >> > > > > > > > * Peng Chen > > >> > > > > > > > > > >> > > > > > > > * Zak Wu > > >> > > > > > > > > > >> > > > > > > > * ZhongBo Wu > > >> > > > > > > > > > >> > > > > > > > * Zili Chen > > >> > > > > > > > > > >> > > > > > > > * Daniel Li > > >> > > > > > > > > > >> > > > > > > > * Guo Jiwei > > >> > > > > > > > > > >> > > > > > > > * Haiji Li > > >> > > > > > > > > > >> > > > > > > > * Lizhen > > >> > > > > > > > > > >> > > > > > > > * Yuanbo Liu > > >> > > > > > > > > > >> > > > > > > > * Yuanhao Ji > > >> > > > > > > > > > >> > > > > > > > * Zijie Lu > > >> > > > > > > > > > >> > > > > > > > * Zirui Peng > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Charles > Zhang be > > >> > > > > appointed > > >> > > > > > > > > > >> > > > > > > > to the office of Vice President, Apache InLong, 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 InLong Project be and hereby > is tasked with > > >> > > > > > > > > > >> > > > > > > > the migration and rationalization of the Apache > Incubator InLong > > >> > > > > > > > > > >> > > > > > > > podling; and be it further > > >> > > > > > > > > > >> > > > > > > > RESOLVED, that all responsibilities pertaining to the > Apache > > >> > > > > Incubator > > >> > > > > > > > > > >> > > > > > > > InLong podling encumbered upon the Apache Incubator PMC > are hereafter > > >> > > > > > > > > > >> > > > > > > > discharged. > > >> > > > > > > > > > >> > > > > > > > -- > > >> > > > > > > > Best wishes, > > >> > > > > > > > Charles Zhang > > >> > > > > > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > >> > > > - > > >> > > 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 > > >> > > > > > >- > > >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 > > -- Byung-Gon Chun
Re: [MENTORS] Podling reports due June 1st
Hi Justin, Nemo also reported last month. Can we skip this month? Thanks. -Gon On Mon, May 23, 2022 at 10:56 PM 谭中意 wrote: > Hi， Justin， > brpc has submit pod report last month. > https://cwiki.apache.org/confluence/display/INCUBATOR/May2022#brpc > so can we skip this month? > > Thanks. > > > On Mon, May 23, 2022 at 1:37 PM Justin Mclean > wrote: > > > Hi, > > > > Please submit your podling reports here [1] > > > > Reporting timeline is: > > Wed June 1st -- Podling reports due by end of day > > Sun June 5th -- Shepherd reviews due by end of day > > Sun June 5th -- Summary due by end of day > > Tue June 7th -- Mentor signoff due by end of day > > Wed June 8th -- Report submitted to Board > > Wed June 15th -- Board meeting > > > > Expected to report are: > > > > BBRPC > > Crail > > Hivemall > > Kvrocks > > Kyuubi > > Livy > > Marvin-AI > > Nemo > > Pegasus > > PonyMail > > SDAP > > Spot > > StreamPipes > > Wayang > > > > Kind Regards, > > Justin > > > > 1. https://cwiki.apache.org/confluence/display/INCUBATOR/June2022 > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- Byung-Gon Chun
Re: [VOTE] Graduate Apache AGE (Incubating) as a TLP
is responsible for > > > > > > the creation and maintenance of software related to a multi-model > > > > > > database that enables graph and relational models built on PostgreSQL; > > > > > > and be it further > > > > > > RESOLVED, that the office of "Vice President, Apache AGE" 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 AGE Project, and to > > > > > > have primary responsibility for management of the projects within the > > > > > > scope of responsibility of the Apache AGE 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 AGE Project: > > > > > > * Alex Kwak > > > > > > * Dehowe Feng > > > > > > * Eya Badal > > > > > > * Felix Cheung > > > > > > * Jasper Blues > > > > > > * John Gemignani > > > > > > * Josh Innis > > > > > > * Juan Pan > > > > > > * Kevin Ratnasekera > > > > > > * Nick Sorrell > > > > > > * Pieterjan De Potter > > > > > > * Von Gosling > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eya Badal be appointed to > > > > > > the office of Vice President, Apache AGE, 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 AGE Project be and hereby is tasked with the > > > > > > migration and rationalization of the Apache Incubator AGE podling; and > > > > > > be it further > > > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > > > > > AGE podling encumbered upon the Apache Incubator PMC are hereafter > > > > > > discharged. > > > > > > > > > * > > > * Thank you, > > > Eya Badal on behalf of the Apache AGE (incubating) community > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- Byung-Gon Chun
Re: Re: [DISCUSS] Graduate Apache DolphinScheduler (incubating) as a TLP
gt; > > distributed and extensible workflow scheduler platform with powerful > > > DAG > > > > > visual interfaces.; and be it further > > > > > > > > > > RESOLVED, that the office of "Vice President, Apache > > DolphinScheduler" > > > > > 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 > > > > > DolphinScheduler Project, and to have primary responsibility for > > > > > management of the projects within the scope of responsibility of the > > > > > Apache DolphinScheduler 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 > > > DolphinScheduler > > > > > Project: > > > > > > > > > > * Furkan Kamaci > > > > > * Gang Li > > > > > * Guo Jiwei > > > > > * Guo William > > > > > * Jun Gao > > > > > * Kevin Ratnasekera > > > > > * Leon Bao > > > > > * Liang Chen > > > > > * Lidong Dai > > > > > * Qiao Zhanwei > > > > > * Shao Feng Shi > > > > > * Sheng Wu > > > > > * Wu Baoqi > > > > > * Xiaochun Liu > > > > > * ZijJian Gong > > > > > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lidong Dai be appointed > > to > > > > > the office of Vice President, Apache DolphinScheduler, 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 DolphinScheduler Project be and hereby is > > > > > tasked with the migration and rationalization of the Apache Incubator > > > > > DolphinScheduler podling; and be it further > > > > > > > > > > RESOLVED, that all responsibilities pertaining to the Apache > > Incubator > > > > > DolphinScheduler podling encumbered upon the Apache Incubator PMC are > > > > > hereafter discharged. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Best Regards > > > > > > > > > > -- > > > > > DolphinScheduler(Incubator) PPMC > > > > > Gang Li 李岗 > > > > > > > > > > lgcar...@apache.org > > > > > > > > > > > > > > > > > > > > > > -- > > > Thanks, > > > Ming Wen, Apache APISIX PMC Chair > > > Twitter: _WenMing > > > > > > > -- Byung-Gon Chun - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Ratis as TLP Project
neru[Hadoop, Ozone PMC, > >> Incubator Committer] > >> * Jie Wang [Incubator, Ozone > >> Committer] > >> * Jing Zhao [Hadoop PMC, Incubator > >> Committer] > >> * Jitendra Nath Pandey [ASF Member, Hadoop, Ozone, > >> Incubator PMC and also PMC in ambari, atlas, tez] > >> * Josh Elser [ASF Member, HBase, Incubator > >> PMC, and also PMC in accumulo, calcite, fluo, phoenix, rya] > >> * Lokesh Jain [Hadoop, Ozone PMC, Incubator > >> Committer] > >> * Marton Elek[Hadoop, Ozone PMC, Incubator > >> Committer] > >> * Mingliang Liu [Hadoop PMC, Incubator > >> Committer] > >> * Mukul Kumar Singh [Hadoop, Ozone PMC, Incubator > >> Committer] > >> * Shashikant Banerjee [Hadoop, Ozone PMC, > >> Incubator Committer] > >> * Siddharth Wagle[Ambari, Ozone PMC, Hadoop, > >> Incubator Committer] > >> * Tsz-wo Sze [ASF Member, Hadoop, Ozone > >> PMC, Incubator Committer] > >> * Uma Maheswara Rao G [ASF Member, Hadoop, Ozone, > >> Incubator PMC and PMC in bookkeeper, carbondata] > >> * Xiaoyu Yao [Hadoop, Ozone PMC, Incubator > >> Committer] > >> > >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tsz-wo Sze be appointed to > >> the office of Vice President, Apache Ratis, 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 Ratis Project be and hereby is tasked with the > >> migration and rationalization of the Apache Incubator Ratis podling; and > >> be it further > >> > >> RESOLVED, that all responsibilities pertaining to the Apache Incubator > >> Ratis podling encumbered upon the Apache Incubator PMC are hereafter > >> discharged. > >> > >> > >> [1] Incubator General list: > >> > >> https://lists.apache.org/thread.html/r316caa8cff9982b5ca168a69c62b12076287ee7ebc7d95eb7ceb3e9e%40%3Cgeneral.incubator.apache.org%3E > >> < > >> https://lists.apache.org/thread.html/r316caa8cff9982b5ca168a69c62b12076287ee7ebc7d95eb7ceb3e9e%40%3Cgeneral.incubator.apache.org%3E > >>> > >> > >> [2] private list vote: > >> > >> https://lists.apache.org/thread.html/r2fc43d73ef22e210652e088c03074c30072c35e5adb9bda7cd893ae9%40%3Cprivate.ratis.apache.org%3E > >> > >> [3] private list Discuss: > >> > >> https://lists.apache.org/thread.html/red1f547c841c04daee40e6ec6fd9906124a54f524e7c9a2470c60b41%40%3Cprivate.ratis.apache.org%3E > >> > >> [4] community Dev list: > >> > >> https://lists.apache.org/thread.html/re57bc4c8e38a8e28c7b2b2f96342a93c65276fee88d8d0ef59468a54%40%3Cdev.ratis.apache.org%3E > >> > >> [5] Resolution Text: > >> > >> https://cwiki.apache.org/confluence/display/RATIS/Apache+Ratis+as+TLP+-+Board+resolution+text > >> > >> > >> Regards, > >> Uma > >> > > > > - > > 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 > -- Byung-Gon Chun - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Wayang into the Apache Incubator
hat > > > the Apache brand and community process will significantly help us in > > > building such a community and to establish the project in the > long-term. > > We > > > simply believe that ASF is the right home for Wayang to achieve this. > > > > > > === Documentation === > > > > > > Further details, documentation, and publications related to Wayang can > be > > > found at https://docs.rheem.io/rheem/ > > > > > > === Initial Source === > > > > > > The current source code of Wayang resides in Github: > > > https://github.com/rheem-ecosystem/rheem > > > > > > === External Dependencies === > > > > > > Wayang depends on the following Apache projects: > > > > > > * Maven > > > * HDFS > > > * Hadoop > > > * Spark > > > > > > Wayang depends on the following other open source projects organized by > > > license: > > > > > > org.json.json: Json (http://json.org/license.html) > > > SnakeYAML: Apache 2.0 > > > Java Unified Expression Language API (Juel): Apache 2.0 > > > ProfileDB Instrumentation: Apache 2.0 > > > Gson: Apache 2.0 > > > Hadoop: Apache 2.0 > > > Scala: Apache 2.0 > > > Antlr 4: BSD > > > Jackson: Apache 2.0 > > > Junit 5: EPL 2.0 > > > Mockito: MIT > > > Assertj: Apache 2.0 > > > logback-classic: EPL 1.0 LGPL 2.1 > > > slf4j: MIT > > > GNU Trove: LGPL 2.1 > > > graphchi: Apache 2.0 > > > SQLite JDBC: Apache 2.0 > > > PostgreSQL: BSD 2-clause > > > jcommander: Apache 2.0 > > > Koloboke Collections API: Apache 2.0 > > > Snappy Java: Apache 2.0 > > > Apache Spark: Apache 2.0 > > > HyperSQL Database: BSD Modified ( > http://hsqldb.org/web/hsqlLicense.html) > > > Apache Giraph: Apache 2.0 > > > Apache Flink: Apache 2.0 > > > Apache Commons IO: Apache 2.0 > > > Apache Commons Lang: Apache 2.0 > > > Apache Maven: Apache 2.0 > > > > > > === Cryptography === > > > > > > (not applicable) > > > > > > === Required Resources === > > > > > > ** Mailing Lists ** > > > > > > * mailto:priv...@wayang.incubator.apache.org > > > * mailto:d...@wayang.incubator.apache.org > > > * mailto:comm...@wayang.incubator.apache.org > > > > > > ** Git repositories ** > > > > > > git://git.apache.org/repos/asf/incubator/wayang > > > > > > ** Issue tracking ** > > > > > > https://issues.apache.org/jira/browse/RHEEM > > > > > > === Initial Committers === > > > > > > The following list gives the planned initial committers (in > alphabetical > > > order): > > > > > > * Bertty Contreras-Rojas http://scalytics.io> > > > * Rodrigo Pardo-Meza http://scalytics.io> > > > * Alexander Alten-Lorenz http://scalytics.io> > > > * Zoi Kaoudi http://tu-berlin.de> > > > * Haralampos Gavriilidis http://tu-berlin.de> > > > * Jorge-Arnulfo Quiane-Ruiz http://tu-berlin.de> > > > * Anis Troudi http://hbku.edu.qa> > > > * Wenceslao Palma-Muñoz http://pucv.cl> > > > > > > ** Affiliations ** > > > > > > * Scalytics Inc. > > > ** Bertty Contreras-Rojas > > > ** Rodrigo Pardo-Meza > > > ** Alexander Alten-Lorenz > > > * Berlin Institute of Technology (TU Berlin) > > > ** Zoi Kaoudi > > > ** Haralampos Gavriilidis > > > ** Jorge-Arnulfo Quiane-Ruiz > > > * Hamad Bin Khalifa University (HBKU) > > > ** Anis Troudi > > > * Pontifical Catholic University of Valparaiso, Chile (PUCV) > > > ** Wenceslao Palma-Muñoz > > > > > > === Sponsors === > > > > > > ** Champion ** > > > > > > * Christofer Dutz (christofer.dutz at c-ware dot de) > > > > > > ** Mentors ** > > > > > > . (cdutz) Christofer Dutz > > > . (larsgeorge) Lars George > > > . (berndf) Fondermann > > > . (jbonofre) Jean-Baptiste Onofré > > > > > > ** Sponsoring Entity ** > > > > > > The Apache Incubator > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > -- > > Dan Widdis > > > -- Byung-Gon Chun
Re: [VOTE] Release Apache Nemo (incubating) version 0.3.rc1
+1 (binding) Carried over from the dev list. -Gon On Wed, Dec 2, 2020 at 2:00 AM Markus Weimer wrote: > +1 (binding) > > Carried over from the dev list. > > Markus > > On Tue, Dec 1, 2020 at 12:30 AM Won Wook SONG wrote: > > > > Dear Community, > > > > This is a call for a releasing Apache Nemo (incubating) 0.3, release > > candidate 1. > > > > Apache Nemo (incubating) community has voted and approved the release. > > > > Vote thread: > > https://www.mail-archive.com/dev@nemo.apache.org/msg02360.html > > > > Result thread: > > https://www.mail-archive.com/dev@nemo.apache.org/msg02371.html > > > > The source tarball, including signatures, digests, etc. can be found at: > > > > https://dist.apache.org/repos/dist/dev/incubator/nemo/0.3-incubating > > > > if not > > > > https://dist.apache.org/repos/dist/release/incubator/nemo/0.3-incubating > > > > > > The tag to be voted upon is 0.3.rc1: > > https://github.com/apache/incubator-nemo/releases/tag/v0.3-rc1 > > > > The release hash is d77b95437c056e9235a615b03a17c455623833f3: > > > https://github.com/apache/incubator-nemo/commit/d77b95437c056e9235a615b03a17c455623833f3 > > > > KEYS file available: > > https://dist.apache.org/repos/dist/release/incubator/nemo/KEYS > > > > For information about the contents of this release, see: > > > > https://issues.apache.org/jira/projects/NEMO/versions/12346999 > > > > > > The fingerprint of key to sign release artifacts: > > > > 0A4DB8B636C0A71F8D6045F5AED6EC66324E678D > > > > which is publicly available at: > > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x0a4db8b636c0a71f8d6045f5aed6ec66324e678d > > > > > > The vote will be open for 72 hours. > > > > [ ] +1 release this package as 0.3 > > [ ] +0 no opinion > > [ ] -1 do not release this package because... > > > > Best regards, > > Wonook > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: [VOTE] Graduation of Apache DataSketches Project to TLP
+1 (binding) -Gon On Thu, Nov 26, 2020 at 10:24 AM Justin Mclean wrote: > Hi, > > +1 (binding) All the best! > > Thanks, > Justin > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: [RESULT][VOTE] Graduate Apache TVM as TLP
Congrats to the Apache TVM community! Well deserved! -Gon On Tue, Oct 27, 2020 at 8:21 AM Tianqi Chen wrote: > 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 > -- Byung-Gon Chun
Re: [VOTE] Graduate Apache TVM as TLP
s 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.apache.org/thread.html/r30929c68769ccb9fb67710e12f82f05f2141957cc52238dc02d12337%40%3Cgeneral.incubator.apache.org%3E > > > > > > > > > > > - [2] > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/r215d3ecbd9bbf4db20dcaffa4fa2ec00e49e71fdcec7fa954d75f84a%40%3Cgeneral.incubator.apache.org%3E > > > > > < > > > > > > > > > > > https://lists.apache.org/thread.html/r215d3ecbd9bbf4db20dcaffa4fa2ec00e49e71fdcec7fa954d75f84a%40%3Cgeneral.incubator.apache.org%3E > > > > > > > > > > > - [3] > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/r91b8f469c6a54769869bb2435b7334a28bcff885ae078ab5612dae00%40%3Cdev > > > > > . > > > > > tvm.apache.org%3E > > > > > - [4] > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/rd5b8eefe49af09a2d0913758a5e5737b3fdb9072bc0becf4a2b2c7ee%40%3Cdev > > > > > . > > > > > tvm.apache.org%3E > > > > > - [5] > > > > > > > > > > > > > > > > https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing > > > > > < > > > > > > > > > > > https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing > > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > -- Byung-Gon Chun
Re: [DISCUSS] Graduate Apache TVM as a TLP
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: [VOTE] Release Apache TVM (incubating) v0.7.0.rc0
+1 (binding), carrying over my vote on the dev list -Gon On Fri, Oct 9, 2020 at 2:34 PM Henry Saputra wrote: > NOTICE file looks good > LICENSE file looks good > DISCLAIMER file exists and looks good > Signature file looks good > Hash file looks good > No binary files in source artifact > License header exist in files > > +1 (binding) > > On Wed, Oct 7, 2020 at 11:29 AM Markus Weimer wrote: > > > +1 (binding) , carrying over my vote on the dev list > > > > Markus > > > > On Wed, Oct 7, 2020 at 10:51 AM Yizhi Liu wrote: > > > > > > +1 > > > > > > On Wed, Oct 7, 2020 at 6:02 AM Tianqi Chen wrote: > > > > > > > > +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 > > > > > > > > > > > > > > > > > -- > > > Yizhi Liu > > > > > > -- > > > Yizhi Liu > > > > > > - > > > 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 > > > > > -- Byung-Gon Chun
Re: [VOTE] Graduate Apache IoTDB as TLP
ion in the > Apache IoTDB Project; and be it further > > RESOLVED, that the Apache IoTDB Project be and hereby > is tasked with the migration and rationalization of the Apache > Incubator IoTDB podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache > Incubator IoTDB podling encumbered upon the Apache Incubator > Project are hereafter discharged. > > [0] https://iotdb.apache.org > [1] > > https://lists.apache.org/thread.html/r83af02254859c88f2555778e59a5a6fc72a1d9bb4c30c52a82065353%40%3Cgeneral.incubator.apache.org%3E > [2] > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148645763 > [3] > > https://lists.apache.org/thread.html/r5fe46923c8625601a25e51340f1df6a2b6472e52dfa2648df116f618%40%3Cdev.iotdb.apache.org%3E > [4] > > https://lists.apache.org/thread.html/rd99752552f6ecacaebd4ae4b27b4223c7899aabfa3ea22540a8f0924%40%3Cdev.iotdb.apache.org%3E > [5] > > https://lists.apache.org/thread.html/ra072c0f047c25a439088d12a3fca9e38f67870e71a430772b242343c%40%3Cdev.iotdb.apache.org%3E > [6] > > https://lists.apache.org/thread.html/r884906a2fb1f7e1b6538f9c444d763f2ea6964bbbc707b2a832f8c7c%40%3Cdev.iotdb.apache.org%3E > [7] > > https://lists.apache.org/thread.html/r768dace1874ac9e1eed6ed138ae1a686b381a9775ba648d0fa5cef22%40%3Cdev.iotdb.apache.org%3E > [8] > > https://lists.apache.org/thread.html/r8eb35e50f7b6728af1e9662c750b04d06677950238c04cb2d2044c9e%40%3Cgeneral.incubator.apache.org%3E > > Thanks, > Xiangdong Huang > On Behalf of Apache IoTDB PPMC > -- Byung-Gon Chun
Re: [VOTE] Graduate Apache TVM as TLP
+1 (binding) The TVM (incubating) project is young. However, I think the community is really well set up. I have no doubt that the project will be successful and will follow the Apache way after graduation. I'm particularly impressed by the vibrant community and all the exciting contributions made (e.g., Ansor, uTVM to name a few). Best, Gon On Fri, Aug 28, 2020 at 6:42 AM Sebastian wrote: > +1 > > Best, > Sebastian (one of the TVM mentors) > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: [VOTE] Release Apache TVM (incubating) v0.6.1.rc1
+1 (binding) - I checked the signature and hash. - DISCLAIMER, LICENSE, and NOTICE look good - No unexpected binary files - The code compiles and runs Thanks. -Gon On Wed, Jul 1, 2020 at 3:28 PM YiZhi Liu wrote: > Dear community, > > This is a call for a vote to release Apache TVM (incubating) version > 0.6.1. This is a maintenance release incorporating important bug > fixes. All users of Apache TVM (incubating) 0.6.0 are advised to > upgrade. > > Apache TVM (incubating) community has voted and approved the release, > with four +1 votes from IPMC members (Tianqi Chen, Markus Weimer, > Henry Saputra, and Furkan KAMACI). > > Vote thread: > > https://lists.apache.org/thread.html/r4aaf1e5eb82c2706b82657eddfd9a7d753272a91066a1ee0ae1af60c%40%3Cdev.tvm.apache.org%3E > > Result thread: > > https://lists.apache.org/thread.html/r341a8a77638a0c216d8ace5f401ad1c19dcc572e5a84bc6dcb6f92c5%40%3Cdev.tvm.apache.org%3E > > 1) Link to release notes: > https://github.com/apache/incubator-tvm/releases/tag/v0.6.1.rc1 > > 2) Link to release candidate: > https://dist.apache.org/repos/dist/dev/incubator/tvm/tvm-v0.6.1-rc1 > > The vote will be open for at least 72 hours. > > +1 = approve > +0 = no opinion > -1 = disapprove (provide reason) > > Thanks, > > -- > Yizhi Liu > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: [VOTE] Accept Pegasus into the Apache incubation
+1 (binding) Best, Gon On Thu, Jun 18, 2020 at 10:58 AM Gosling Von wrote: > +1, binding > > > Best Regards, > Von Gosling > > > On Jun 16, 2020, at 5:41 PM, Tao Wu > wrote: > > > > Hi, > > > > After [the discussion of Pegasus proposal]( > > > https://lists.apache.org/thread.html/d2dc725389e1e6d0b525f85201c6219973a568ed075837601fd6bd0b%40%3Cgeneral.incubator.apache.org%3E > ), > > I would like to call a vote to accept this project into the Apache > > Incubator. > > > > The proposal is here: > > https://cwiki.apache.org/confluence/display/INCUBATOR/PegasusProposal > > > > Please cast your vote: > > > > [ ] +1, bring Pegasus into Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring Pegasus into Incubator, because... > > > > The vote will open for at least 72 hours and only votes from the IPMC > > members are considered binding, but other votes are welcome! > > > > Thanks, > > Wu Tao > > > --------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: Re: [VOTE] Graduate Apache ShardingSphere (incubating)
ppointed 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 > > > > > > > > > > > > > > > > > > -- > > Thanks, > > Xin > > > -- Byung-Gon Chun
Re: [VOTE] Release Apache Nemo (incubating) version 0.2-rc5
Hi Woo Yeon, +1 (binding) I checked the checksum and signature. I tested the release on my mac with jdk 1.11. Great job! Best, Gon On Tue, Mar 3, 2020 at 4:41 PM Woo-Yeon Lee wrote: > Dear incubator community, > > This is a call for a releasing Apache Nemo (incubating) 0.2, release > candidate 5. > > Please refer to the information below to vote on this release, and vote: > > [ ] +1 Release this package as Apache Nemo (incubating) 0.2.0 > [ ] 0 I don't feel strongly about it, but the release seems okay. > [ ] -1 Please do not release this package because... > > > 1. Vote thread: > https://lists.apache.org/thread.html/re2f5cd075b697957cf89c41b218c8c8595c32f73283090e16f935d07%40%3Cdev.nemo.apache.org%3E > > 2. Result thread: > https://lists.apache.org/thread.html/r848812ed8f8f7e69069bb3ed03f30d240df34a85db364f09ce75ae4c%40%3Cdev.nemo.apache.org%3E > > 3. Source release > files: > https://dist.apache.org/repos/dist/dev/incubator/nemo/0.2-incubating/ > > 4. The tag to be voted upon is > v0.2:https://github.com/apache/incubator-nemo/releases/tag/v0.2 > > 5. The release hash is > 33f638ee0253731d787c1652b300d27c13afff66: > https://github.com/apache/incubator-nemo/commit/33f638ee0253731d787c1652b300d27c13afff66 > > 6. The KEYS file: > https://dist.apache.org/repos/dist/dev/incubator/nemo/KEYS > (fingerprint: 5719958759C2A835015BBAB81DA67C172CEC34AD) > > > The vote will be open for 72 hours. > > > Best regards, > WooYeon > -- Byung-Gon Chun
Re: [VOTE] Accept NLPCraft into Apache Incubator
+1 (binding) -Gon On Mon, Feb 10, 2020 at 6:54 AM Konstantin Boudnik wrote: > Hello. > > As the discussion of NLPCraft proposal [1] has been wrapped up [2] I would > like > to call a VOTE to accept this project into the Apache Incubator. > > Please cast your vote: > > [ ] +1, bring NLPCraft into Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring NLPCraft into Incubator, because... > > The vote will open for at least 72 hours until midnight PDT Wednesday, Feb > 13, > 2020. As a reminder: only votes from the IPMC members are considered > binding, > but other votes are welcome! > > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/NLPCraftProposal > [2] https://s.apache.org/me4ut > > Thank you, > Cos > > > -- Byung-Gon Chun
Re: [VOTE] Accept YuniKorn into Apache Incubator
+1 (binding) - Byung-Gon Chun On Sun, Jan 12, 2020 at 1:00 PM Kevin Ratnasekera wrote: > +1 (binding) > > On Sun, Jan 12, 2020 at 6:50 AM Sheng Wu > wrote: > > > +1 binding > > > > good luck > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Michael Wall 于2020年1月12日周日 上午8:03写道： > > > > > +1 binding > > > > > > Good luck > > > > > > Mike > > > > > > On Sat, Jan 11, 2020 at 1:31 PM Furkan KAMACI > > > wrote: > > > > > > > Hi, > > > > > > > > +1 (binding) > > > > > > > > Kind Regards, > > > > Furkan KAMACI > > > > > > > > 11 Oca 2020 Cmt, saat 20:50 tarihinde Dave Meikle < > dmei...@apache.org> > > > > şunu > > > > yazdı: > > > > > > > > > +1 (binding) > > > > > > > > > > All the best, > > > > > Dave > > > > > > > > > > On Fri, 10 Jan 2020 at 17:47, Vinod Kumar Vavilapalli < > > > > vino...@apache.org> > > > > > wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > I'd like to call a vote on accepting YuniKorn into the Apache > > > > Incubator. > > > > > > > > > > > > Please see the discussion thread [1]. > > > > > > > > > > > > Please see the full proposal: > > > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/YuniKornProposal > > > > > > > > > > > > Please cast your vote > > > > > > > > > > > > [ ] +1 Accept YuniKorn into the Incubator > > > > > > [ ] +0 Indifferent to the acceptance of YuniKorn > > > > > > [ ] -1 Do not accept YuniKorn because … > > > > > > > > > > > > The vote will be open at least for 72 hours. > > > > > > > > > > > > Incubator PMC member votes are binding. Everyone else is welcomed > > to > > > > vote > > > > > > too (mark them as non-binding if you can)! > > > > > > > > > > > > Thanks > > > > > > +Vinod > > > > > > > > > > > > [1] [DISCUSS] YuniKorn Proposal > > > > > > > > > > > > > > > > > > > > > https://lists.apache.org/thread.html/59a3fc019119352f06e75a2bae5c25cd1b652282d7a59b85ed2188cf%40%3Cgeneral.incubator.apache.org%3E > > > > > > > > - > > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > > > For additional commands, e-mail: > general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Byung-Gon Chun
Re: [VOTE] Accept NuttX into the Apache Incubator
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 target incubation period of 2 years > > or > > > >> > less, > > > >> > knowing that every Incubator project incurs a certain cost in > terms > > of > > > >> > ASF > > > >> > infrastructure and volunteer time. > > > >> > > > > >> > > > > >> > ==Inexperience with Open Source== > > > >> > > > > >> > None of the initial committers are Apache members and we will need > > > some > > > >> > help in learning the Apache Way. > > > >> > > > > >> > > > > >> > ==Salaried Developers== > > > >> > > > > >> > It is expected that NuttX development will occur primarily on > > > volunteer > > > >> > time, after hours. One initial committer will be paid by Xiaomi. > > All > > > >> > initial committers are all equally passionate about the project. > > > >> > > > > >> > > > > >> > =Relationships with Other Apache Products= > > > >> > > > > >> > There is no relationship between NuttX and any other Apache > > Products. > > > >> > There were discussions with the Mynewt project in the past > > concerning > > > >> > use > > > >> > of some Mynewt IoT components within NuttX. There is some > > possibility > > > >> > that > > > >> > those conversations could continue once NuttX has Apache licensing > > as > > > >> > well. > > > >> > > > > >> > > > > >> > =Required Resources= > > > >> > > > > >> > ==Mailing lists== > > > >> > > > > >> > * d...@nuttx.incubator.apache.org > > > >> > > > > >> > * comm...@nuttx.incubator.apache.org > > > >> > > > > >> > * priv...@nuttx.incubator.apache.org > > > >> > > > > >> > The podling may also create a user mailing list, if needed. > > > >> > > > > >> > > > > >> > ==Source Control and Issue Tracking== > > > >> > > > > >> > NuttX current uses the Bitbucket infrastructure for development. > It > > > is > > > >> > likely that the NuttX podling would switch to GitHub and would use > > > >> > Apache’s > > > >> > gitbox integration to sync between GitHub and Apache > infrastructure. > > > >> > The > > > >> > podling would use GitHub issues and pull requests for community > > > >> > engagement. > > > >> > > > > >> > Current Resources > > > >> > > > > >> > * Initial source: https://bitbucket.org/nuttx/ > > > >> > > > > >> > * Wiki Page: http://www.nuttx.org/ > > > >> > > > > >> > * Google Group: https://groups.google.com/forum/#!forum/nuttx > > > >> > > > > >> > > > > >> > =Source and Intellectual Property Submission Plan= > > > >> > > > > >> > The NuttX source code in Bitbucket is currently licensed under > the > > > BSD > > > >> > 3-clause license and the most copyrights are assigned to the > author, > > > >> > Gregory Nutt. If NuttX becomes an Incubator project at the ASF, > the > > > >> > project > > > >> > will transfer the source code and trademark ownership to the > Apache > > > >> > Software Foundation via a Software Grant Agreement. > > > >> > > > > >> > > > > >> > =External Dependencies= > > > >> > > > > >> > None. A small number of files within NuttX follow slightly > > different, > > > >> > but > > > >> > compatible licenses including BSD 2- and 4-clause, MIT, ISC, and > > > Public > > > >> > Domain. > > > >> > > > > >> > > > > >> > =Cryptography= > > > >> > > > > >> > NuttX has negligible cryptographic capabilities at present. This > > is, > > > >> > however, and are where there will be extensive future growth. > > > >> > > > > >> > > > > >> > =Initial Committers= > > > >> > > > > >> > * Gregory Nutt gn...@nuttx.org > > > >> > > > > >> > * Xiao Xiang xiaoxi...@xiaomi.com > > > >> > > > > >> > * Anthony Merlino anth...@vergeaero.com > > > >> > > > > >> > * Alin Jerpelea alin.jerpe...@sony.com > > > >> > > > > >> > * David Sidrane david.sidr...@nscdg.com > > > >> > > > > >> > * Alan Carvalho de Assis acas...@gmail.com > > > >> > > > > >> > * Nathan Hartman hartman.nat...@gmail.com > > > >> > > > > >> > * Abdelatif GUETTOUCHE abdelatif.guettou...@gmail.com > > > >> > > > > >> > =Sponsors= > > > >> > > > > >> > * Champion and mentor: Junping Du junping...@apache.org > > > >> > > > > >> > * Mentor: Justin Mclean jmcl...@apache.org > > > >> > > > > >> > * Mentor: Mohammad Asif Siddiqui asifdxtr...@apache.org > > > >> > > > > >> > * Mentor: Flavio Paiva Junqueira f...@apache.org > > > >> > > > > >> > > > > >> > =Sponsoring Entity= > > > >> > > > > >> > * The Apache Incubator > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > [1] > > > https://cwiki.apache.org/confluence/display/INCUBATOR/NuttXProposal > > > >> > > > > >> > > > > >> > Thanks, > > > >> > > > > >> > > > > >> > Junping > > > >> > > > > >> > > > - > > > >> > 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 > > > > > > > > > -- Byung-Gon Chun
Re: [Discuss] Graduate Apache SINGA (incubating) as a TLP
If SIGNA started as a university project, which is likely, I think the university should sign SGA. I'm a mentor of Nemo (donated from a university project). I helped the Nemo community file SGA. Best, Gon On Wed, Sep 4, 2019 at 5:51 AM Alan Gates wrote: > If I understand correctly, anytime software is brought into Apache as part > of the incubating process there must be documentation from the previous > owner of that software stating that they are donating it to Apache. > Without that Apache's ownership of the code is not clear. Justin, Dave, > others, please correct me if this understanding is wrong. > > And clearly there was code imported into Apache when Singa entered the > incubator, since an existing github link (now defunct) is referenced in > Singa's incubator proposal[1]. > > So I don't believe that an affirmation from PPMC that no docs are necessary > is sufficient. I believe we need a code grant from whoever owned that code > previously. > > Alan. > > 1. https://cwiki.apache.org/confluence/display/INCUBATOR/SingaProposal see > the section on initial source. > > On Mon, Sep 2, 2019 at 12:29 AM Justin Mclean wrote: > > > Hi, > > > > > The PPMC reached a conclusion on the discussion [1] that there is no > need > > > for SGA. > > > > The link referred to doesn't give a reason why one is not required. Why > > was it decided that it wasn’t needed? Even if it not required (which I’m > > not 100% sure that is the case), would it be difficult to get one? If so > > why is that? > > > > Thanks, > > Justin > > --------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- Byung-Gon Chun
Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator
ing Apache Maven, none of > the external libraries need to be packaged in a source distribution. > > Most of dependencies have Apache compatible licenses，and the detail as > follows: > > Most of dependencies have Apache compatible licenses，and the core > dependencies are as follows: > Backend Dependency > Dependency > License > Comments > bonecp-0.8.0.RELEASE.jar Apache v2.0 > byte-buddy-1.9.10.jar Apache V2.0 > c3p0-0.9.1.1.jar GNU LESSER GENERAL PUBLIC LICENSE will remove > curator-*-2.12.0.jar Apache V2.0 > druid-1.1.14.jar Apache V2.0 > fastjson-1.2.29.jar Apache V2.0 > fastutil-6.5.6.jar Apache V2.0 > grpc-*-1.9.0.jar Apache V2.0 > gson-2.8.5.jar Apache V2.0 > guava-20.0.jar Apache V2.0 > guice-*3.0.jar Apache V2.0 > hadoop-*-2.7.3.jar Apache V2.0 > hbase-*-1.1.1.jar Apache V2.0 > hive-*-2.1.0.jar Apache V2.0 > instrumentation-api-0.4.3.jar Apache V2.0 > jackson-*-2.9.8.jar Apache V2.0 > jackson-jaxrs-1.8.3.jar LGPL Version 2.1 Apache V2.0 will remove > jackson-xc-1.8.3.jar LGPL Version 2.1 Apache V2.0 will remove > javax.activation-api-1.2.0.jar CDDL/GPLv2+CE will remove > javax.annotation-api-1.3.2.jar CDDL + GPLv2 with classpath exception will > remove > javax.servlet-api-3.1.0.jar CDDL + GPLv2 with classpath exception will > remove > jaxb-*.jar (CDDL 1.1) (GPL2 w/ CPE) will remove > jersey-*-1.9.jar CDDL+GPLv2 will remove > jetty-*-9.4.14.v20181114.jar Apache V2.0，EPL 1.0 > jna-4.5.2.jar Apache V2.0，LGPL 2.1 will remove > jna-platform-4.5.2.jar Apache V2.0，LGPL 2.1 will remove > jsp-api-2.x.jar CDDL，GPL 2.0 will remove > log4j-1.2.17.jar Apache V2.0 > log4j-*-2.11.2.jar Apache V2.0 > logback-x.jar dual-license EPL 1.0,LGPL 2.1 > mail-1.4.5.jar CDDL+GPLv2 will remove > mybatis-3.5.1.jar Apache V2.0 > mybatis-spring-*2.0.1.jar Apache V2.0 > mysql-connector-java-5.1.34.jar GPL 2.0 will remove > netty-*-4.1.33.Final.jar Apache V2.0 > oshi-core-3.5.0.jar EPL 1.0 > parquet-hadoop-bundle-1.8.1.jar Apache V2.0 > postgresql-42.1.4.jar BSD 2-clause > protobuf-java-*3.5.1.jar BSD 3-clause > quartz-2.2.3.jar Apache V2.0 > quartz-jobs-2.2.3.jar Apache V2.0 > slf4j-api-1.7.5.jar MIT > spring-*-5.1.5.RELEASE.jar Apache V2.0 > spring-beans-5.1.5.RELEASE.jar Apache V2.0 > spring-boot-*2.1.3.RELEASE.jar Apache V2.0 > springfox-*-2.9.2.jar Apache V2.0 > stringtemplate-3.2.1.jar BSD > swagger-annotations-1.5.20.jar Apache V2.0 > swagger-bootstrap-ui-1.9.3.jar Apache V2.0 > swagger-models-1.5.20.jar Apache V2.0 > zookeeper-3.4.8.jar Apache > > The front-end UI currently relies on many components, and the core > dependencies are as follows: > UI Dependency > Dependency > License > Comments > autoprefixer MIT > babel-core MIT > babel-eslint MIT > babel-helper-* MIT > babel-helpers MIT > babel-loader MIT > babel-plugin-syntax-* MIT > babel-plugin-transform-* MIT > babel-preset-env MIT > babel-runtime MIT > bootstrap MIT > canvg MIT > clipboard MIT > codemirror MIT > copy-webpack-plugin MIT > cross-env MIT > css-loader MIT > cssnano MIT > cyclist MIT > d3 BSD-3-Clause > dayjs MIT > echarts Apache V2.0 > env-parse ISC > extract-text-webpack-plugin MIT > file-loader MIT > globby MIT > html-loader MIT > html-webpack-ext-plugin MIT > html-webpack-plugin MIT > html2canvas MIT > jsplumb (MIT OR GPL-2.0) > lodash MIT > node-sass MIT > optimize-css-assets-webpack-plugin MIT > postcss-loader MIT > rimraf ISC > sass-loader MIT > uglifyjs-webpack-plugin MIT > url-loader MIT > util.promisify MIT > vue MIT > vue-loader MIT > vue-style-loader MIT > vue-template-compiler MIT > vuex-router-sync MIT > watchpack MIT > webpack MIT > webpack-dev-server MIT > webpack-merge MIT > xmldom MIT,LGPL will remove > > Required ResourcesGit Repositories > >- https://github.com/analysys/EasyScheduler.git >- https://github.com/analysys/easyscheduler_docs.git >- https://github.com/analysys/easyscheduler_docs_cn.git > > Issue Tracking > > The community would like to continue using GitHub Issues. > Continuous Integration tool > > Jenkins > Mailing Lists > >- DolphinScheduler-dev: for development discussions >- DolphinScheduler-private: for PPMC discussions >- DolphinScheduler-notifications: for users notifications > > > Initial Committers > >- William-GuoWei(guowei...@outlook.com) >- Lidong Dai(lidong@outlook.com) >- Zhanwei Qiao(qiaozhan...@outlook.com) >- Liang Bao(baoliang.l...@gmail.com) >- Gang Li(lgcareer2...@outlook.com) >- Zijian Gong(quanqua...@gmail.com) >- Jun Gao(gaojun2...@gmail.com) >- Baoqi Wu(wuba...@gmail.com) > > Affiliations > >- > >Analysys Inc: William-GuoWei，Zhanwei Qiao，Liang Bao，Gang Li，Jun >Gao，Lidong Dai >- > >Hydee Inc: Zijian Gong >- > >Guandata Inc: Baoqi Wu > > SponsorsChampion > >- Sheng Wu ( Apache Incubator PMC, wush...@apache.org) > > Mentors > >- > >Sheng Wu ( Apache Incubator PMC, wush...@apache.org) >- > >ShaoFeng Shi ( Apache Incubator PMC, shaofeng...@apache.org >) >- > >Liang Chen ( Apache Incubator PMC, Apache member, > chenliang...@apache.org >) >- Furkan KAMACI ( Apache Incubator PMC, kam...@apache.org) >- Kevin Ratnasekera ( Apache Incubator PMC, Apache member, >djkevi...@apache.org) > > Sponsoring Entity > > We are expecting the Apache Incubator could sponsor this project. > > Sheng Wu 吴晟 > > Apache SkyWalking, ShardingSphere, Zipkin > Twitter, wusheng1108 > -- Byung-Gon Chun
Re: [VOTE] Accept MesaTEE into Apache Incubator
, 0.8.0, sha2 > * spin, 0.5.0, MIT > * syn, 0.11.11, MIT > * syn, 0.15.39, MIT > * synom, 0.11.3, MIT/Apache-2.0 > * termcolor, 1.0.5, Unlicense > * thread_local, 0.3.6, Apache-2.0/MIT > * tiff, 0.3.1, MIT > * toml, 0.5.1, MIT/Apache-2.0 > * typetag, 0.1.3, MIT > * typetag-impl, 0.1.3, MIT > * ucd-util, 0.1.3, MIT/Apache-2.0 > * unicode-xid, 0.0.4, MIT/Apache-2.0 > * unicode-xid, 0.1.0, MIT/Apache-2.0 > * utf8-ranges, 1.0.3, Unlicense/MIT > * uuid, 0.7.4, Apache-2.0 > * wabt, 0.6.0, Apache-2.0 > * wasmi, 0.5.0, MIT/Apache-2.0 > * wasmi-validation, 0.1.0, MIT/Apache-2.0 > * webpki, 0.19.1, ISC-style > * webpki-roots, 0.16.0, MPL-2.0 > * winapi, 0.3.7, MIT/Apache-2.0 > * winapi-i686-pc-windows-gnu, 0.4.0, MIT/Apache-2.0 > * winapi-util, 0.1.2, Unlicense/MIT > * winapi-x86_64-pc-windows-gnu, 0.4.0, MIT/Apache-2.0 > * wincolor, 1.0.1, Unlicense/MIT > * yasna, 0.3.1, MIT/Apache-2.0 > > Note that this is not an exhaustive dependency list and only direct > dependencies > of MesaTEE's trusted libs are included. > > == Cryptography == > > MesaTEE uses following cryptographic libraries: > > * ring (https://github.com/briansmith/ring): a Rust crypto library > based on BoringSSL > * rustls: a Rust TLS library > * sgx_tcrypto in Intel SGX SDK (https://software.intel.com/en-us/sgx/sdk > ) > > = Required Resources = > > == Mailing lists == > > * priv...@mesatee.incubator.apache.org (with moderated subscriptions) > * d...@mesatee.incubator.apache.org > * comm...@mesatee.incubator.apache.org > * u...@mesatee.incubator.apache.org > > == Git Repositories == > > Upon entering incubation, we want to transfer the existing repos from > https://github.com/mesalock-linux/mesatee and > https://github.com/baidu/rust-sgx-sdk to Apache organization in GitHub > like: > > * https://github.com/apache/incubator-mesatee > * https://github.com/apache/incubator-mesatee-rust-sgx-sdk > > == Issue Tracking == > > MesaTEE currently uses GitHub to track issues. Would like to continue doing > so. > > == Continuous Integration Service == > > MesaTEE currently uses self-hosted continuous integration (CI) service > which can > help developers to automatically test commits. The CI service involves > several > nodes which support Intel SGX. We would like to continue doing so. > > = Initial Committers = > > The list is sorted alphabetically: > > * Mingshen Sun > * Pei Wang > * Rundong Zhou > * Tao Wei > * Tongxin Li > * Yiming Jing > * Yu Ding > * Yulong Zhang > * Zhaofeng Chen > > = Sponsors = > > == Champion == > > * Zhijie Shen > > == Nominated Mentors == > > * Jianyong Dai > * Luciano Resende > * Matt Sicker > * Furkan Kamaci > > == Sponsoring Entity == > > The Incubator PMC > -- Byung-Gon Chun
Re: [VOTE] Accept DataSketches into the Apache Incubator
+1 (binding) On Fri, Mar 15, 2019 at 6:34 PM Furkan KAMACI wrote: > +1 (binding) > > 15 Mar 2019 Cum, saat 07:08 tarihinde Kevin A. McGrail < > kmcgr...@apache.org> > şunu yazdı: > > > I'd like to vote -1 since you made me look up the word "stochastic" and > > that feels like homework but I will vote +1 (binding). Please don't > > make me do any math. > > > > On 3/14/2019 5:23 PM, Kenneth Knowles wrote: > > > Hi all, > > > > > > We've discussed the proposal for the DataSketches project in [1] and > [2]. > > > The > > > proposal itself has been put on the wiki [3]. > > > > > > Per incubator rules [4] I'd like to call a vote to accept the new > > > "DataSketches" 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 DataSketches into the Apache Incubator > > > [ ] +0 Abstain > > > [ ] -1 Do not accept DataSketches into the Apache Incubator because ... > > > > > > Thanks to everyone who contributed to the proposal and discussions. > > > > > > Kenn > > > > > > [1] > > > > > > https://lists.apache.org/thread.html/329354bd6a463dab56c2539972cfa2d6c6da7c75900216d785db4e3b@%3Cgeneral.incubator.apache.org%3E > > > [2] > > > > > > https://lists.apache.org/thread.html/c9873cd4fcdc6367bcf530d8fa1ef09f3035f38e7c435e1a79a93885@%3Cgeneral.incubator.apache.org%3E > > > [3] https://wiki.apache.org/incubator/DataSketchesProposal > > > [4] https://incubator.apache.org/guides/proposal.html#the_vote > > > > > > > -- > > Kevin A. McGrail > > Member, Apache Software Foundation > > Chair Emeritus Apache SpamAssassin Project > > https://www.linkedin.com/in/kmcgrail - 703.798.0171 > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- Byung-Gon Chun
Re: [VOTE] Accept Apache TVM into the incubator
+1 (binding) On Thu, Feb 28, 2019 at 1: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 > > -- Byung-Gon Chun
Re: [Cava] Suitable name search - choosing a name
; >>>>>> > >>>>>> Here are the names: > >>>>>> - Rainbow (after the name of my kid’s favorite toy, and in line with > >> the crypto community unicorn punk theme [2]. > >>>>>> - Winch (a mechanical device used to wind up or wind out wires > >> (Wikipedia) , in the chain theme) > >>>>>> - Sprocket (a profiled wheel with teeth, or cogs, that mesh with a > >> chain, track or other perforated or indented material. (Wikipedia), in > the > >> chain theme as well) > >>>>>> - “Jal”, in reference to Indra’s net (or Indra jal) (with a quote > >> from [3]: "Imagine a multidimensional spider's web in the early morning > >> covered with dew drops. And every dew drop contains the reflection of > all > >> the other dew drops. > >>>>>> And, in each reflected dew drop, the reflections of all the other > dew > >> drops in that reflection. And so ad infinitum. That is the Buddhist > >> conception of the universe in an image." –Alan Watts) > >>>>>> > >>>>>> In this thread, please indicate the one name you like most. Please > >> feel free to justify your choice. > >>>>>> Based on your input, the project will adopt the name. In absence of > a > >> strong contender, I'll work with the Champion (Jim Jagielski) to pick a > >> name. > >>>>>> > >>>>>> I'll keep the thread open for 72 hours - that gives us until Tuesday > >> afternoon PST time. > >>>>>> > >>>>>> Cheers, > >>>>>> > >>>>>> Antoine > >>>>>> > >>>>>> [0]: > >> > https://lists.apache.org/thread.html/5634b8f24cf552da4cba12ab4b59647bfa6800b7380833d8131331e9@%3Cgeneral.incubator.apache.org%3E > >>>>>> [1]: > >> > https://lists.apache.org/thread.html/8d8014f53f140a3ccdd517c3c303de1d45cc04afdaee5961ac43e7fc@%3Cgeneral.incubator.apache.org%3E > >>>>>> [2]: https://www.urbandictionary.com/define.php?term=unicorn%20punk > >>>>>> [3]: https://en.wikipedia.org/wiki/Indra%27s_net > >>>>>> > - > >>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >>>>>> For additional commands, e-mail: general-h...@incubator.apache.org > >>>>>> > >>>>> -- > >>>>> Jean-Baptiste Onofré > >>>>> jbono...@apache.org > >>>>> http://blog.nanthrax.net > >>>>> Talend - http://www.talend.com > >>>>> > >>>>> - > >>>>> 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 > >>>> > >>> > >>> -- > >>> Kevin A. McGrail > >>> Member, Apache Software Foundation > >>> Chair Emeritus Apache SpamAssassin Project > >>> https://www.linkedin.com/in/kmcgrail - 703.798.0171 > >>> > >> > >> > >> - > >> 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 > > -- Byung-Gon Chun
Re: [VOTE] Accept Cava into the Apache Incubator
+1 (binding) On Thu, Feb 21, 2019 at 5:20 AM Dave Fisher wrote: > +1 (binding) > > Looking forward to this podling! > > Regards, > Dave > > Sent from my iPhone > > > On Feb 20, 2019, at 11:50 AM, Antoine Toulme > wrote: > > > > Hi everyone, > > > > we've discussed the proposal for the Cava project in [1] and [2]. The > > proposal itself can be found on the wiki[3]. > > > > We discussed how to go about finding a suitable name for the project in > [2]. > > I will kick off a vote to pick a name based on the proposals made there. > > > > According to the Incubator rules[4] I'd like to call a vote to accept the > > new "Cava" 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 Cava into the Apache Incubator > > [ ] +0 Abstain > > [ ] -1 Do not accept Cava into the Apache Incubator because ... > > > > Thank you for everyone who decided to join in in the past discussions! > > Antoine > > > > [1]: > https://lists.apache.org/thread.html/5a7f6a218b11a1cac61fbd53f4c995fd7716f8ad3751cf9f171ebd57@%3Cgeneral.incubator.apache.org%3E > > [2]: > https://lists.apache.org/thread.html/8d8014f53f140a3ccdd517c3c303de1d45cc04afdaee5961ac43e7fc@%3Cgeneral.incubator.apache.org%3E > > [3]: https://wiki.apache.org/incubator/CavaProposal?action=recall&rev=14 > > [4]: 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 > > -- Byung-Gon Chun
Re: [Proposal] Apache TVM
e > > PMCs followed a principle to *only* nominate committers outside > > their own > > organizations. > > > > > > === Reliance on Salaried Developers === > > > > Most of the current committers are volunteers. > > > > === Relationships with Other Apache Products === > > > > TVM can serve as a fundamental compiler stack for deep learning and > > machine > > learning in general. We expect it can benefit projects like MXNet, > > Spark, Flink, > > Mahout, and SystemML. > > > > === Documentation === > > > > See https://tvm.ai/ > > > > === Initial Source === > > > > https://github.com/dmlc/tvm > > > > We plan to move our repository to > > https://github.com/apache/incubator-tvm > > > > > > === Source and Intellectual Property Submission Plan === > > > > TVM source code is available under Apache V2 license. We will work > > with the > > committers to get ICLAs signed. > > > > === External Dependencies === > > > > We put all the source level dependencies under > > https://github.com/dmlc/tvm/tree/master/3rdparty > > > > - dmlc-core (Apache2): https://github.com/dmlc/dmlc-core > > - dlpack (Apache2): https://github.com/dmlc/dlpack > > - HalideIR (MIT): https://github.com/dmlc/HalideIR > > - range(Unlicense): https://github.com/agauniyal/rang > > - Compiler-RT (BSD) > > - LLVM > > > > All of the current he dependencies are stable, which means that the > > current TVM > > repo is standalone and main development activities only happen at > > the TVM repo. > > The dependencies are periodically updated in the rate about once a > > month when > > necessary. For source level dependencies, we will always point to a > > stable > > release version for software release in the future. > > > > > > === External Dependencies on DMLC projects === > > > > There are three dependencies to dmlc projects in the 3rdparty. The > > current > > proposal is to keep the current dependencies in the 3rdparty. We > > elaborate on > > the background of these dependencies below: > > > > - dmlc-core: is a minimum module for logging and memory > > serialization. It is > > currently used by projects including ApacheMXNet, TVM, and XGBoost. > The > > project is relatively stable, with around one change a week(most > recent > > changes comes from XGBoost project). TVM’s dependency on dmlc-core > > is minimum > > and only uses its feature for logging. > > - dlpack: is a minimum consensus standard for in-memory Tensor > > format. It is > > currently used by PyTorch, ApacheMXNet, Chainer, and a few other > > projects. > > - HalideIR: is a minimum IR data structure that is isolated from a > > fork of > > Halide project. We keep the license to be MIT to respect the > > original license > > and its origin. A common consensus in the TVM project is that we > > keep the old > > derived code in HalideIR (which are stable), and all new > > developments happen > > in the TVM repo. > > > > The main reason to propose keep these dependencies are: > > - Each of the dependencies has the user and developer community of > > its own > > which is larger than the TVM community or different license > > options(MIT in > > HalideIR) > > - These dependencies are stable and update at a monthly rate. > > > > While it is possible to fork the code in the tvm repo, given that > > the current > > tvm repo is self-contained, and community development is > > stand-alone, we feel > > that there are have enough justifications to treat these as 3rdparty > > dependencies. > > > > > > === Required Resources === > > > > Mailing List: > > The usual mailing lists are expected to be set up when entering > > incubation: > > > > * priv...@tvm.apache.org <mailto:priv...@tvm.apache.org> > > * d...@tvm.apache.org <mailto:d...@tvm.apache.org> , subscribe github > > issues. > > * discuss-arch...@tvm.apache.org > > <mailto:discuss-arch...@tvm.apache.org>, Archive the discuss content > > of the > > discourse user forum > > > &
Re: [VOTE] Release Apache Nemo (Incubating) 0.1
+1 (binding) I checked name, signature and hashes, NOTICE and LICENSE, and source headers. The code compiles from the source. Thanks. -Gon On Fri, Dec 28, 2018 at 3:16 AM Davor Bonaci wrote: > +1, binding, carried from dev@ > > On Thu, Dec 27, 2018 at 12:52 AM David Meikle wrote: > > > +1 (binding). I checked; name, sig and hashes (only checked sha512), > > notice, license, source headers, compiles from source (Ubuntu). > > > > As Justin says, you can remove the MD5 file. > > > > Cheers, > > Dave > > > > > On 27 Dec 2018, at 01:57, Joo Yeon Kim wrote: > > > > > > Please refer to the information below to vote on this release, and > vote: > > > (Please mark your vote as binding if so) > > > [ ] +1 Release this package as Apache Nemo (incubating) 0.1 > > > [ ] 0 I don't feel strongly about it, but the release seems okay. > > > [ ] -1 Please do not release this package because... > > > > > -- Byung-Gon Chun
Re: [VOTE] Accept the brpc Project into the Apache Incubator.
+1 (binding) On Sun, Nov 11, 2018 at 6:29 AM Justin Mclean wrote: > Hi, > > +1 (binding) > > Thanks, > Justin > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: [VOTE] Accept Zipkin into the Apache Incubator
ation on their own > > >> time and have done so for a lengthy period. Given the current stream > > >> of development requests and the committers' sense of ownership of the > > >> Zipkin code, this arrangement is expected to continue with Zipkin' > > >> induction into the ASF. > > >> > > >> === Relationships with Other Apache Products === > > >> Zipkin, Apache Incubator Skywalking and Apache Incubator HTrace > > >> address similiar use cases. Most similarities are between Zipkin and > > >> HTrace: Zipkin hopes to help serve the community formerly served by > > >> HTrace, but understands the data services focus of HTrace may require > > >> different tooling. SkyWalking addresses more feature surface than > > >> Zipkin. For example, metrics collection is not a goal of Zipkin, yet > > >> it is a goal of SkyWalking. SkyWalking accepts Zipkin formats and can > > >> be used as a replacement server. SkyWalking PPMC member, Sheng Wu, > > >> has been a routine member of Zipkin design discussions and has > > >> offered to help Zipkin through ASF process. > > >> > > >> While Zipkin does not directly rely upon any Apache project, zipkin > > >> supports several Apache projects. Apache CXF, Apache Camel, Apache > > >> Incubator SkyWalking, Apache Incubator Dubbo, Apache Incubator > > >> ServiceComb and Apache Incubator HTrace all utilize Zipkin APIs in > > >> their core repositories. Many more do via community extensions. > > >> Apache Maven is primarily use by Zipkin, and can be used by projects > > >> who build upon Zipkin projects. > > >> > > >> === A Excessive Fascination with the Apache Brand === > > >> Zipkin recognizes the fortitude of the Apache brand, but the > > >> motivation for becoming an Apache project is to strengthen and expand > > >> the Zipkin community and its user base. While the Zipkin community > > >> has seen steady growth over the past several years, association with > > >> the ASF is expected to expedite this pattern of growth. Development > > >> is expected to continue on Zipkin under the Apache license whether or > > >> not it is supported by the ASF. > > >> > > >> == Documentation == > > >> The Zipkin project documentation is publicly available at the > > >> following sites: > > >> > > >>* https://zipkin.io: project overview > > >>* http://zipkin.io/zipkin-api/#/: swagger specification > > >>* https://github.com/openzipkin/b3-propagation: header formats > > >>* https://zipkin.io/zipkin/: Javadocs for the Zipkin server > > >> > > >> == Initial Source == > > >> The initial source is located on GitHub in the following repositories: > > >> > > >>* git://github.com/OpenZipkin/zipkin.git > > >>* git://github.com/OpenZipkin/zipkin-dependencies.git > > >>* git://github.com/OpenZipkin/zipkin-api.git > > >>* git://github.com/OpenZipkin/b3-propagation.git > > >>* git://github.com/OpenZipkin/docker-zipkin.git > > >>* git://github.com/OpenZipkin/docker-zipkin-dependencies.git > > >>* git://github.com/openzipkin/zipkin-reporter-java > > >>* git://github.com/openzipkin/brave > > >>* git://github.com/openzipkin/zipkin-aws > > >>* git://github.com/openzipkin/docker-zipkin-aws > > >>* git://github.com/openzipkin/zipkin-azure > > >>* git://github.com/openzipkin/docker-zipkin-azure > > >>* git://github.com/openzipkin/zipkin-gcp > > >>* git://github.com/openzipkin/docker-zipkin-gcp > > >>* git://github.com/openzipkin/brave-cassandra > > >>* git://github.com/openzipkin/docker-jre-full > > >>* git://github.com/openzipkin/brave-karaf > > >> > > >> Depending on community progress, other repositories may be moved as > well > > >> > > >> == Source and Intellectual Property Submission Plan == > > >> Zipkin's initial source is licensed under the Apache License, Version > > >> 2.0. https://github.com/openzipkin/zipkin/blob/master/LICENSE > > >> > > >> All source code is copyrighted to 'The OpenZipkin Authors', to which > > >> the existing core community(members list in Initial Committers) has > > >> the rights to re-assign to the ASF. > > >> > > >> == External Dependencies == > > >> This is a listing of Maven coordinates for all of the external > > >> dependencies Zipkin uses. All of the dependencies are in Sonatype and > > >> their licenses should be accessible. > > >> > > >> == Cryptography == > > >> Zipkin contains no cryptographic algorithms. > > >> > > >> = Required Resources = > > >> == Mailing Lists == > > >>* Zipkin-dev: for development discussions > > >>* Zipkin-user: for community discussions > > >>* Zipkin-private: for PPMC discussions > > >>* Zipkin-commits: for code changes > > >> > > >> == Git Repositories == > > >> The Zipkin team is experienced in git and requests to transfer GitHub > > >> repositories(list in Initial Source) to Apache. > > >> > > >> == Issue Tracking == > > >> The community would like to continue using GitHub Issues. > > >> > > >> = Initial Committers = > > >>* Zoltán Nagy > > >>* Adrian Cole, Pivotal > > >>* Bas van Beek > > >>* Brian Devins > > >>* Eirik Sletteberg > > >>* Jeanneret Pierre-Hugues > > >>* Jordi Polo Carres > > >>* José Carlos Chávez > > >>* Kristof Adriaenssens > > >>* Lance Linder > > >>* Mick Semb Wever, > > >>* Tommy Ludwig > > >> > > >> = Champion = > > >> * Michael Semb Wever, m...@apache.org > > >> > > >> = Mentors = > > >> * Michael Semb Wever, m...@apache.org > > >> * Andriy Redko, r...@apache.org > > >> * John D. Ament, johndam...@apache.org > > >> * Willem Ning Jiang, ningji...@apache.org > > >> > > >> = Sponsoring Entity = > > >> We are requesting the Apache Incubator to sponsor this project. > > >> > > >> - > > >> 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 > > > > > -- Byung-Gon Chun
Re: [PROPOSAL] Zipkin for Apache Incubator
community members to come together in person and discuss ideas. > > > > > > === Homogenous Developers === > > > At the time of the writing, OpenZipkin's core 12 developers all work > > > at different companies around the globe. Most operate their own > > > tracing sites, but some no longer operate sites at all: staying for > > > the community we've built. Our ASF champion, Mick Semb Wever, is both > > > a committer and an experienced ASF member. > > > > > > The Zipkin developers thrive upon the diversity of the community. The > > > Zipkin gitter channel is always active, and the developers often > > > collaborate on fixes and changes in the code. They are always happy to > > > answer users' questions as well. > > > > > > Zipkin is interested in continuing to expand and strengthen its > > > network of developers and community members through the ASF. > > > > > > === Reliance on Salaried Developers === > > > Zipkin has one full time salaried developer, Adrian Cole. Though some > > > of the developers are paid by their employer to contribute to Zipkin, > > > many Zipkin developers contribute code and documentation on their own > > > time and have done so for a lengthy period. Given the current stream > > > of development requests and the committers' sense of ownership of the > > > Zipkin code, this arrangement is expected to continue with Zipkin' > > > induction into the ASF. > > > > > > === Relationships with Other Apache Products === > > > Zipkin, Apache Incubator Skywalking and Apache Incubator HTrace > > > address similiar use cases. Most similarities are between Zipkin and > > > HTrace: Zipkin hopes to help serve the community formerly served by > > > HTrace, but understands the data services focus of HTrace may require > > > different tooling. SkyWalking addresses more feature surface than > > > Zipkin. For example, metrics collection is not a goal of Zipkin, yet > > > it is a goal of SkyWalking. SkyWalking accepts Zipkin formats and can > > > be used as a replacement server. SkyWalking PPMC member, Sheng Wu, has > > > been a routine member of Zipkin design discussions and has offered to > > > help Zipkin through ASF process. > > > > > > While Zipkin does not directly rely upon any Apache project, zipkin > > > supports several Apache projects. Apache CXF, Apache Camel, Apache > > > Incubator SkyWalking, Apache Incubator Dubbo, Apache Incubator > > > ServiceComb and Apache Incubator HTrace all utilize Zipkin APIs in > > > their core repositories. Many more do via community extensions. Apache > > > Maven is primarily use by Zipkin, and can be used by projects who > > > build upon Zipkin projects. > > > > > > === A Excessive Fascination with the Apache Brand === > > > Zipkin recognizes the fortitude of the Apache brand, but the > > > motivation for becoming an Apache project is to strengthen and expand > > > the Zipkin community and its user base. While the Zipkin community has > > > seen steady growth over the past several years, association with the > > > ASF is expected to expedite this pattern of growth. Development is > > > expected to continue on Zipkin under the Apache license whether or not > > > it is supported by the ASF. > > > > > > == Documentation == > > > The Zipkin project documentation is publicly available at the following > > > sites: > > > > > > * https://zipkin.io: project overview > > > * http://zipkin.io/zipkin-api/#/: swagger specification > > > * https://github.com/openzipkin/b3-propagation: header formats > > > * https://zipkin.io/zipkin/: Javadocs for the Zipkin server > > > > > > == Initial Source == > > > The initial source is located on GitHub in the following repositories: > > > > > > * git://github.com/OpenZipkin/zipkin.git > > > * git://github.com/OpenZipkin/zipkin-dependencies.git > > > * git://github.com/OpenZipkin/zipkin-api.git > > > * git://github.com/OpenZipkin/b3-propagation.git > > > * git://github.com/OpenZipkin/docker-zipkin.git > > > * git://github.com/OpenZipkin/docker-zipkin-dependencies.git > > > * git://github.com/openzipkin/zipkin-reporter-java > > > * git://github.com/openzipkin/brave > > > * git://github.com/openzipkin/zipkin-aws > > > * git://github.com/openzipkin/docker-zipkin-aws > > > * git://github.com/openzipkin/zipkin-azure > > > * git://github.com/openzipkin/docker-zipkin-azure > > > * git://github.com/openzipkin/zipkin-gcp > > > * git://github.com/openzipkin/docker-zipkin-gcp > > > * git://github.com/openzipkin/brave-cassandra > > > * git://github.com/openzipkin/docker-jre-full > > > * git://github.com/openzipkin/brave-karaf > > > > > > Depending on community progress, other repositories may be moved as > well > > > > > > == Source and Intellectual Property Submission Plan == > > > Zipkin's initial source is licensed under the Apache License, Version > > > 2.0. https://github.com/openzipkin/zipkin/blob/master/LICENSE > > > > > > All source code is copyrighted to 'The OpenZipkin Authors', to which > > > the existing core community(members list in Initial Committers) has > > > the rights to re-assign to the ASF. > > > > > > == External Dependencies == > > > This is a listing of Maven coordinates for all of the external > > > dependencies Zipkin uses. All of the dependencies are in Sonatype and > > > their licenses should be accessible. > > > > > > == Cryptography == > > > Zipkin contains no cryptographic algorithms. > > > > > > = Required Resources = > > > == Mailing Lists == > > > * Zipkin-dev: for development discussions > > > * Zipkin-user: for community discussions > > > * Zipkin-private: for PPMC discussions > > > * Zipkin-commits: for code changes > > > > > > == Git Repositories == > > > The Zipkin team is experienced in git and requests to transfer GitHub > > > repositories(list in Initial Source) to Apache. > > > > > > == Issue Tracking == > > > The community would like to continue using GitHub Issues. > > > > > > = Initial Committers = > > > * Zoltán Nagy > > > * Adrian Cole, Pivotal > > > * Bas van Beek > > > * Brian Devins > > > * Eirik Sletteberg > > > * Jeanneret Pierre-Hugues > > > * Jordi Polo Carres > > > * José Carlos Chávez > > > * Kristof Adriaenssens > > > * Lance Linder > > > * Mick Semb Wever, > > > * Tommy Ludwig > > > > > > = Champion = > > > * Michael Semb Wever, m...@apache.org > > > > > > = Mentors = > > > * Michael Semb Wever, m...@apache.org > > > * Andriy Redko, r...@apache.org > > > > > > = Sponsoring Entity = > > > We are requesting the Apache Incubator to sponsor this project. > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > -- Byung-Gon Chun
Re: [RESULT] [VOTE] Accept Coral into the Apache Incubator
Hi, There's a name conflict with a project hosted at Mozilla foundation. The new project name is Nemo. It's approved by Podling Suitable Name Search. ( https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-139?filter=allissues ) Accordingly, I renamed the page CoralProposal to NemoProposal. https://wiki.apache.org/incubator/NemoProposal I'll continue the on-boarding process. Thanks! -Gon On Mon, Feb 5, 2018 at 6:10 AM, Byung-Gon Chun wrote: > Hi, > > 72 hours has passed and the vote for accepting Coral into the Apache > Incubator has passed with: > > 9 binding "+1" votes, 1 non-binding "+1" votes, and no "-1” votes. > > Binding votes: > Kevin A. McGrail > Davor Bonaci > Dave Fisher > Hyunsik Choi > Leif Hedstrom > Jean-Baptiste Onofré > Romain Manni-Bucau > Mark Struberg > Byung-Gon Chun > > Non-binding votes: > Clebert Suconic > > Thanks to everyone who voted. > > On Thu, Feb 1, 2018 at 11:07 PM, Byung-Gon Chun wrote: > >> Hi all, >> >> I would like to start a VOTE to propose the Coral project as a podling >> into the Apache Incubator. >> >> The ASF voting rules are described at https://www.apache.org/foundation/ >> voting.html >> >> A vote for accepting a new Apache Incubator podling is a majority vote >> for which only Incubator PMC member votes are binding. >> >> This vote will run for at least 72 hours. Please VOTE as follows. >> [] +1 Accept Coral into the Apache Incubator >> [] +0 Abstain >> [] -1 Do not accept Coral into the Apache Incubator because ... >> >> The proposal is listed below, but you can also access it on the wiki: >> https://wiki.apache.org/incubator/CoralProposal >> >> = CoralProposal = >> >> == Abstract == >> Coral is a data processing system for flexible employment with different >> execution scenarios for various deployment characteristics on clusters. >> >> == Proposal == >> Today, there is a wide variety of data processing systems with different >> designs for better performance and datacenter efficiency. They include >> processing data on specific resource environments and running jobs with >> specific attributes. Although each system successfully solves the problems >> it targets, most systems are designed in the way that runtime behaviors are >> built tightly inside the system core to hide the complexity of distributed >> computing. This makes it hard for a single system to support different >> deployment characteristics with different runtime behaviors without >> substantial effort. >> >> Coral is a data processing system that aims to flexibly control the runtime >> behaviors of a job to adapt to varying deployment characteristics. Moreover, >> it provides a means of extending the system’s capabilities and incorporating >> the extensions to the flexible job execution. >> >> In order to be able to easily modify runtime behaviors to adapt to varying >> deployment characteristics, Coral exposes runtime behaviors to be flexibly >> configured and modified at both compile-time and runtime through a set of >> high-level graph pass interfaces. >> >> We hope to contribute to the big data processing community by enabling more >> flexibility and extensibility in job executions. Furthermore, we can benefit >> more together as a community when we work together as a community to mature >> the system with more use cases and understanding of diverse deployment >> characteristics. The Apache Software Foundation is the perfect place to >> achieve these aspirations. >> >> == Background == >> Many data processing systems have distinctive runtime behaviors optimized >> and configured for specific deployment characteristics like different >> resource environments and for handling special job attributes. >> >> For example, much research have been conducted to overcome the challenge of >> running data processing jobs on cheap, unreliable transient resources. >> Likewise, techniques for disaggregating different types of resources, like >> memory, CPU and GPU, are being actively developed to use datacenter >> resources more efficiently. Many researchers are also working to run data >> processing jobs in even more diverse environments, such as across distant >> datacenters. Similarly, for special job attributes, many works take >> different approaches, such as runtime optimization, to solve problems like >> data skew, and to optimize systems for data processing jobs with small-scale >> input data. >> >> Al
Re: [RESULT] [VOTE] Accept Coral into the Apache Incubator
Done. Thanks! -Gon On Mon, Feb 5, 2018 at 2:26 PM, Craig Russell wrote: > Please add the proposal to the official incubator proposal wiki list > > https://wiki.apache.org/incubator/ProjectProposals > > Craig > > > On Feb 4, 2018, at 1:10 PM, Byung-Gon Chun wrote: > > > > Hi, > > > > 72 hours has passed and the vote for accepting Coral into the Apache > > Incubator has passed with: > > > > 9 binding "+1" votes, 1 non-binding "+1" votes, and no "-1” votes. > > > > Binding votes: > > Kevin A. McGrail > > Davor Bonaci > > Dave Fisher > > Hyunsik Choi > > Leif Hedstrom > > Jean-Baptiste Onofré > > Romain Manni-Bucau > > Mark Struberg > > Byung-Gon Chun > > > > Non-binding votes: > > Clebert Suconic > > > > Thanks to everyone who voted. > > > > On Thu, Feb 1, 2018 at 11:07 PM, Byung-Gon Chun > wrote: > > > >> Hi all, > >> > >> I would like to start a VOTE to propose the Coral project as a podling > >> into the Apache Incubator. > >> > >> The ASF voting rules are described at https://www.apache.org/ > foundation/ > >> voting.html > >> > >> A vote for accepting a new Apache Incubator podling is a majority vote > for > >> which only Incubator PMC member votes are binding. > >> > >> This vote will run for at least 72 hours. Please VOTE as follows. > >> [] +1 Accept Coral into the Apache Incubator > >> [] +0 Abstain > >> [] -1 Do not accept Coral into the Apache Incubator because ... > >> > >> The proposal is listed below, but you can also access it on the wiki: > >> https://wiki.apache.org/incubator/CoralProposal > >> > >> = CoralProposal = > >> > >> == Abstract == > >> Coral is a data processing system for flexible employment with > different execution scenarios for various deployment characteristics on > clusters. > >> > >> == Proposal == > >> Today, there is a wide variety of data processing systems with > different designs for better performance and datacenter efficiency. They > include processing data on specific resource environments and running jobs > with specific attributes. Although each system successfully solves the > problems it targets, most systems are designed in the way that runtime > behaviors are built tightly inside the system core to hide the complexity > of distributed computing. This makes it hard for a single system to support > different deployment characteristics with different runtime behaviors > without substantial effort. > >> > >> Coral is a data processing system that aims to flexibly control the > runtime behaviors of a job to adapt to varying deployment characteristics. > Moreover, it provides a means of extending the system’s capabilities and > incorporating the extensions to the flexible job execution. > >> > >> In order to be able to easily modify runtime behaviors to adapt to > varying deployment characteristics, Coral exposes runtime behaviors to be > flexibly configured and modified at both compile-time and runtime through a > set of high-level graph pass interfaces. > >> > >> We hope to contribute to the big data processing community by enabling > more flexibility and extensibility in job executions. Furthermore, we can > benefit more together as a community when we work together as a community > to mature the system with more use cases and understanding of diverse > deployment characteristics. The Apache Software Foundation is the perfect > place to achieve these aspirations. > >> > >> == Background == > >> Many data processing systems have distinctive runtime behaviors > optimized and configured for specific deployment characteristics like > different resource environments and for handling special job attributes. > >> > >> For example, much research have been conducted to overcome the > challenge of running data processing jobs on cheap, unreliable transient > resources. Likewise, techniques for disaggregating different types of > resources, like memory, CPU and GPU, are being actively developed to use > datacenter resources more efficiently. Many researchers are also working to > run data processing jobs in even more diverse environments, such as across > distant datacenters. Similarly, for special job attributes, many works take > different approaches, such as runtime optimization, to solve problems like > data skew, and to optimize systems for data processing jobs with > small-scale input data. > >> > >> Although e
[RESULT] [VOTE] Accept Coral into the Apache Incubator
Hi, 72 hours has passed and the vote for accepting Coral into the Apache Incubator has passed with: 9 binding "+1" votes, 1 non-binding "+1" votes, and no "-1” votes. Binding votes: Kevin A. McGrail Davor Bonaci Dave Fisher Hyunsik Choi Leif Hedstrom Jean-Baptiste Onofré Romain Manni-Bucau Mark Struberg Byung-Gon Chun Non-binding votes: Clebert Suconic Thanks to everyone who voted. On Thu, Feb 1, 2018 at 11:07 PM, Byung-Gon Chun wrote: > Hi all, > > I would like to start a VOTE to propose the Coral project as a podling > into the Apache Incubator. > > The ASF voting rules are described at https://www.apache.org/foundation/ > voting.html > > A vote for accepting a new Apache Incubator podling is a majority vote for > which only Incubator PMC member votes are binding. > > This vote will run for at least 72 hours. Please VOTE as follows. > [] +1 Accept Coral into the Apache Incubator > [] +0 Abstain > [] -1 Do not accept Coral into the Apache Incubator because ... > > The proposal is listed below, but you can also access it on the wiki: > https://wiki.apache.org/incubator/CoralProposal > > = CoralProposal = > > == Abstract == > Coral is a data processing system for flexible employment with different > execution scenarios for various deployment characteristics on clusters. > > == Proposal == > Today, there is a wide variety of data processing systems with different > designs for better performance and datacenter efficiency. They include > processing data on specific resource environments and running jobs with > specific attributes. Although each system successfully solves the problems it > targets, most systems are designed in the way that runtime behaviors are > built tightly inside the system core to hide the complexity of distributed > computing. This makes it hard for a single system to support different > deployment characteristics with different runtime behaviors without > substantial effort. > > Coral is a data processing system that aims to flexibly control the runtime > behaviors of a job to adapt to varying deployment characteristics. Moreover, > it provides a means of extending the system’s capabilities and incorporating > the extensions to the flexible job execution. > > In order to be able to easily modify runtime behaviors to adapt to varying > deployment characteristics, Coral exposes runtime behaviors to be flexibly > configured and modified at both compile-time and runtime through a set of > high-level graph pass interfaces. > > We hope to contribute to the big data processing community by enabling more > flexibility and extensibility in job executions. Furthermore, we can benefit > more together as a community when we work together as a community to mature > the system with more use cases and understanding of diverse deployment > characteristics. The Apache Software Foundation is the perfect place to > achieve these aspirations. > > == Background == > Many data processing systems have distinctive runtime behaviors optimized and > configured for specific deployment characteristics like different resource > environments and for handling special job attributes. > > For example, much research have been conducted to overcome the challenge of > running data processing jobs on cheap, unreliable transient resources. > Likewise, techniques for disaggregating different types of resources, like > memory, CPU and GPU, are being actively developed to use datacenter resources > more efficiently. Many researchers are also working to run data processing > jobs in even more diverse environments, such as across distant datacenters. > Similarly, for special job attributes, many works take different approaches, > such as runtime optimization, to solve problems like data skew, and to > optimize systems for data processing jobs with small-scale input data. > > Although each of the systems performs well with the jobs and in the > environments they target, they perform poorly with unconsidered cases, and do > not consider supporting multiple deployment characteristics on a single > system in their designs. > > For an application writer to optimize an application to perform well on a > certain system engraved with its underlying behaviors, it requires a deep > understanding of the system itself, which is an overhead that often requires > a lot of time and effort. Moreover, for a developer to modify such system > behaviors, it requires modifications of the system core, which requires an > even deeper understanding of the system itself. > > With this background, Coral is designed to represent all of its jobs as an > Intermediate Representation (IR) DAG. In the Coral compiler, user > applications from
Re: [VOTE] Accept Coral into the Apache Incubator
+1 binding -Gon On Fri, Feb 2, 2018 at 7:30 PM, Mark Struberg wrote: > +1 binding > > LieGrue, > strub > > > Am 01.02.2018 um 15:07 schrieb Byung-Gon Chun : > > > > Hi all, > > > > I would like to start a VOTE to propose the Coral project as a podling > into > > the Apache Incubator. > > > > The ASF voting rules are described at https://www.apache.org/foundation/ > > voting.html > > > > A vote for accepting a new Apache Incubator podling is a majority vote > for > > which only Incubator PMC member votes are binding. > > > > This vote will run for at least 72 hours. Please VOTE as follows. > > [] +1 Accept Coral into the Apache Incubator > > [] +0 Abstain > > [] -1 Do not accept Coral into the Apache Incubator because ... > > > > The proposal is listed below, but you can also access it on the wiki: > > https://wiki.apache.org/incubator/CoralProposal > > > > = CoralProposal = > > > > == Abstract == > > Coral is a data processing system for flexible employment with > > different execution scenarios for various deployment characteristics > > on clusters. > > > > == Proposal == > > Today, there is a wide variety of data processing systems with > > different designs for better performance and datacenter efficiency. > > They include processing data on specific resource environments and > > running jobs with specific attributes. Although each system > > successfully solves the problems it targets, most systems are designed > > in the way that runtime behaviors are built tightly inside the system > > core to hide the complexity of distributed computing. This makes it > > hard for a single system to support different deployment > > characteristics with different runtime behaviors without substantial > > effort. > > > > Coral is a data processing system that aims to flexibly control the > > runtime behaviors of a job to adapt to varying deployment > > characteristics. Moreover, it provides a means of extending the > > system’s capabilities and incorporating the extensions to the flexible > > job execution. > > > > In order to be able to easily modify runtime behaviors to adapt to > > varying deployment characteristics, Coral exposes runtime behaviors to > > be flexibly configured and modified at both compile-time and runtime > > through a set of high-level graph pass interfaces. > > > > We hope to contribute to the big data processing community by enabling > > more flexibility and extensibility in job executions. Furthermore, we > > can benefit more together as a community when we work together as a > > community to mature the system with more use cases and understanding > > of diverse deployment characteristics. The Apache Software Foundation > > is the perfect place to achieve these aspirations. > > > > == Background == > > Many data processing systems have distinctive runtime behaviors > > optimized and configured for specific deployment characteristics like > > different resource environments and for handling special job > > attributes. > > > > For example, much research have been conducted to overcome the > > challenge of running data processing jobs on cheap, unreliable > > transient resources. Likewise, techniques for disaggregating different > > types of resources, like memory, CPU and GPU, are being actively > > developed to use datacenter resources more efficiently. Many > > researchers are also working to run data processing jobs in even more > > diverse environments, such as across distant datacenters. Similarly, > > for special job attributes, many works take different approaches, such > > as runtime optimization, to solve problems like data skew, and to > > optimize systems for data processing jobs with small-scale input data. > > > > Although each of the systems performs well with the jobs and in the > > environments they target, they perform poorly with unconsidered cases, > > and do not consider supporting multiple deployment characteristics on > > a single system in their designs. > > > > For an application writer to optimize an application to perform well > > on a certain system engraved with its underlying behaviors, it > > requires a deep understanding of the system itself, which is an > > overhead that often requires a lot of time and effort. Moreover, for a > > developer to modify such system behaviors, it requires modifications > > of the system core, which requires an even deeper understanding of the > > system itself. > > > > With this back
Re: [VOTE] Accept Coral into the Apache Incubator
Thanks, Davor! I will add you to the mentor list of Coral. On Fri, Feb 2, 2018 at 4:23 AM, Davor Bonaci wrote: > +1 (binding) > > Also, happy to help, mentor, or be a connection with the Beam PMC, as > appropriate. > > On Thu, Feb 1, 2018 at 9:54 AM, Kevin A. McGrail > wrote: > >> +1 Binding >> >> >> On 2/1/2018 9:07 AM, Byung-Gon Chun wrote: >> >>> Hi all, >>> >>> I would like to start a VOTE to propose the Coral project as a podling >>> into >>> the Apache Incubator. >>> >>> The ASF voting rules are described at https://www.apache.org/foundation/ >>> voting.html >>> >>> A vote for accepting a new Apache Incubator podling is a majority vote >>> for >>> which only Incubator PMC member votes are binding. >>> >>> This vote will run for at least 72 hours. Please VOTE as follows. >>> [] +1 Accept Coral into the Apache Incubator >>> [] +0 Abstain >>> [] -1 Do not accept Coral into the Apache Incubator because ... >>> >>> The proposal is listed below, but you can also access it on the wiki: >>> https://wiki.apache.org/incubator/CoralProposal >>> >>> = CoralProposal = >>> >>> == Abstract == >>> Coral is a data processing system for flexible employment with >>> different execution scenarios for various deployment characteristics >>> on clusters. >>> >>> == Proposal == >>> Today, there is a wide variety of data processing systems with >>> different designs for better performance and datacenter efficiency. >>> They include processing data on specific resource environments and >>> running jobs with specific attributes. Although each system >>> successfully solves the problems it targets, most systems are designed >>> in the way that runtime behaviors are built tightly inside the system >>> core to hide the complexity of distributed computing. This makes it >>> hard for a single system to support different deployment >>> characteristics with different runtime behaviors without substantial >>> effort. >>> >>> Coral is a data processing system that aims to flexibly control the >>> runtime behaviors of a job to adapt to varying deployment >>> characteristics. Moreover, it provides a means of extending the >>> system’s capabilities and incorporating the extensions to the flexible >>> job execution. >>> >>> In order to be able to easily modify runtime behaviors to adapt to >>> varying deployment characteristics, Coral exposes runtime behaviors to >>> be flexibly configured and modified at both compile-time and runtime >>> through a set of high-level graph pass interfaces. >>> >>> We hope to contribute to the big data processing community by enabling >>> more flexibility and extensibility in job executions. Furthermore, we >>> can benefit more together as a community when we work together as a >>> community to mature the system with more use cases and understanding >>> of diverse deployment characteristics. The Apache Software Foundation >>> is the perfect place to achieve these aspirations. >>> >>> == Background == >>> Many data processing systems have distinctive runtime behaviors >>> optimized and configured for specific deployment characteristics like >>> different resource environments and for handling special job >>> attributes. >>> >>> For example, much research have been conducted to overcome the >>> challenge of running data processing jobs on cheap, unreliable >>> transient resources. Likewise, techniques for disaggregating different >>> types of resources, like memory, CPU and GPU, are being actively >>> developed to use datacenter resources more efficiently. Many >>> researchers are also working to run data processing jobs in even more >>> diverse environments, such as across distant datacenters. Similarly, >>> for special job attributes, many works take different approaches, such >>> as runtime optimization, to solve problems like data skew, and to >>> optimize systems for data processing jobs with small-scale input data. >>> >>> Although each of the systems performs well with the jobs and in the >>> environments they target, they perform poorly with unconsidered cases, >>> and do not consider supporting multiple deployment characteristics on >>> a single system in their designs. >>> >>> For an application writer to optimize an applicati
Re: [PROPOSAL] Onyx - proposal for Apache Incubation
Thanks for the question, Liang. The performance of Coral (previously named as Onyx) depends on deployment scenarios. We haven't done extensive experiments with Coral+Spark yet. However, in several deployment scenarios we've been looking at, Coral+Beam outperforms direct Spark even though the Coral runtime still misses a few optimizations the Spark runtime has. If you're interested in more details, please sign up coral@dev once Coral's in apache incubation. Thanks. -Gon On Fri, Feb 2, 2018 at 12:36 AM, Liang Chen wrote: > Hi > > Looks a nice project, very interested in checking more detail. > > How about the performance? Onyx+spark in comparison to directly using > spark, > whether reduce performance ,or not ? > > Regards > Liang > > > Byung-Gon Chun wrote > > Dear Apache Incubator Community, > > > > Please accept the following proposal for presentation and discussion: > > https://wiki.apache.org/incubator/OnyxProposal > > > > Onyx is a data processing system that aims to flexibly control the > runtime > > behaviors of a job to adapt to varying deployment characteristics (e.g., > > harnessing transient resources in datacenters, cross-datacenter > > deployment, > > changing runtime based on job characteristics, etc.). Onyx provides ways > > to > > extend the system’s capabilities and incorporate the extensions to the > > flexible job execution. > > Onyx translates a user program (e.g., Apache Beam, Apache Spark) into an > > Intermediate Representation (IR) DAG, which Onyx optimizes and deploys > > based on a deployment policy. > > > > I've attached the proposal below. > > > > Best regards, > > Byung-Gon Chun > > > > = OnyxProposal = > > > > == Abstract == > > Onyx is a data processing system for flexible employment with > > different execution scenarios for various deployment characteristics > > on clusters. > > > > == Proposal == > > Today, there is a wide variety of data processing systems with > > different designs for better performance and datacenter efficiency. > > They include processing data on specific resource environments and > > running jobs with specific attributes. Although each system > > successfully solves the problems it targets, most systems are designed > > in the way that runtime behaviors are built tightly inside the system > > core to hide the complexity of distributed computing. This makes it > > hard for a single system to support different deployment > > characteristics with different runtime behaviors without substantial > > effort. > > > > Onyx is a data processing system that aims to flexibly control the > > runtime behaviors of a job to adapt to varying deployment > > characteristics. Moreover, it provides a means of extending the > > system’s capabilities and incorporating the extensions to the flexible > > job execution. > > > > In order to be able to easily modify runtime behaviors to adapt to > > varying deployment characteristics, Onyx exposes runtime behaviors to > > be flexibly configured and modified at both compile-time and runtime > > through a set of high-level graph pass interfaces. > > > > We hope to contribute to the big data processing community by enabling > > more flexibility and extensibility in job executions. Furthermore, we > > can benefit more together as a community when we work together as a > > community to mature the system with more use cases and understanding > > of diverse deployment characteristics. The Apache Software Foundation > > is the perfect place to achieve these aspirations. > > > > == Background == > > Many data processing systems have distinctive runtime behaviors > > optimized and configured for specific deployment characteristics like > > different resource environments and for handling special job > > attributes. > > > > For example, much research have been conducted to overcome the > > challenge of running data processing jobs on cheap, unreliable > > transient resources. Likewise, techniques for disaggregating different > > types of resources, like memory, CPU and GPU, are being actively > > developed to use datacenter resources more efficiently. Many > > researchers are also working to run data processing jobs in even more > > diverse environments, such as across distant datacenters. Similarly, > > for special job attributes, many works take different approaches, such > > as runtime optimization, to solve problems like data skew, and to > > optimize systems for data processing jobs with small-scale input data. > >
[VOTE] Accept Coral into the Apache Incubator
, Apache Log4J, and multiple Apache Commons components. Coral supports the Apache Beam programming model for user applications. We are currently working on supporting the Apache Spark programming APIs as well. === An Excessive Fascination with the Apache Brand === We hope to make Coral a powerful system for data processing, meeting various needs for different deployment characteristics, under a more variety of environments. We see the limitations of simply putting code on GitHub, and we believe the Apache community will help the growth of Coral for the project to become a positively impactful and innovative open source software. We believe Coral is a great fit for the Apache Software Foundation due to the collaboration it aims to achieve from the big data processing community. == Documentation == The current documentation for Coral is at https://snuspl.github.io/coral/. == Initial Source == The Coral codebase is currently hosted at https://github.com/snuspl/coral. == External Dependencies == To the best of our knowledge, all Coral dependencies are distributed under Apache compatible licenses. Upon acceptance to the incubator, we would begin a thorough analysis of all transitive dependencies to verify this fact and further introduce license checking into the build and release process. == Cryptography == Not applicable. == Required Resources == === Mailing Lists === We will operate two mailing lists as follows: * Coral PMC discussions: priv...@coral.incubator.apache.org * Coral developers: d...@coral.incubator.apache.org === Git Repositories === Upon incubation: https://github.com/apache/incubator-coral. After the incubation, we would like to move the existing repo https://github.com/snuspl/coral to the Apache infrastructure === Issue Tracking === Coral currently tracks its issues using the Github issue tracker: https://github.com/snuspl/coral/issues. We plan to migrate to Apache JIRA. == Initial Committers == * Byung-Gon Chun * Jeongyoon Eo * Geon-Woo Kim * Joo Yeon Kim * Gyewon Lee * Jung-Gil Lee * Sanha Lee * Wooyeon Lee * Yunseong Lee * JangHo Seo * Won Wook Song * Taegeon Um * Youngseok Yang == Affiliations == * SNU (Seoul National University) * Byung-Gon Chun * Jeongyoon Eo * Geon-Woo Kim * Gyewon Lee * Sanha Lee * Wooyeon Lee * Yunseong Lee * JangHo Seo * Won Wook Song * Taegeon Um * Youngseok Yang * LG * Jung-Gil Lee * Samsung * Joo Yeon Kim * Viva Republica * Geon-Woo Kim == Sponsors == === Champions === Byung-Gon Chun === Mentors === * Hyunsik Choi * Byung-Gon Chun * Jean-Baptiste Onofré * Markus Weimer * Reynold Xin === Sponsoring Entity === The Apache Incubator Thanks! Byung-Gon Chun
Re: [PROPOSAL] Onyx - proposal for Apache Incubation
Thank you all for the feedback. We changed the project name to Coral. You can find the proposal at https://wiki.apache.org/incubator/CoralProposal . I will soon send out a voting email. Thanks. -Gon On Wed, Jan 31, 2018 at 11:54 PM, Jean-Baptiste Onofré wrote: > Thanks, much appreciated ! > > Regards > JB > > On 01/31/2018 09:50 AM, Byung-Gon Chun wrote: > > On Wed, Jan 31, 2018 at 4:04 PM, Jean-Baptiste Onofré > > wrote: > > > >> Hi, > >> > >> Coral is a good name ! > >> > > > > Thanks! > > > > > >> > >> Does the code belong to Seoul National University ? In that case, in > >> addition of > >> your ICLA, we would need a SGA (it's not blocker for the project > >> bootstrapping > >> or code donation, but we, at least, will need it later for graduation). > On > >> the > >> other hand, if the committers are all part on the university, you can > also > >> sign > >> a CCLA. > >> > > > > I will figure this out. > > > > > >> > >> Happy to be mentor on the project if you want me ! ;) > >> > >> > > Thanks! I will add you to the mentor list. > > > > -Gon > > > > > >> Thanks, > >> Regards > >> JB > >> > >> On 01/30/2018 10:17 AM, Byung-Gon Chun wrote: > >>> Thanks for the comments, JB! > >>> My replies are inlined below. > >>> > >>> On Tue, Jan 30, 2018 at 5:52 PM, Jean-Baptiste Onofré > > >>> wrote: > >>> > >>>> Hi, > >>>> > >>>> sorry to be a little bit late on this. > >>>> > >>>> It's a very interesting proposal. It sounds pretty close to the > >> portability > >>>> layer we want to add in Apache Beam. I would love to see interaction > >>>> between the > >>>> two communities. > >>>> > >>>> I have two minor questions: > >>>> > >>>> 1. about the name: Onyx sounds very generic and the name is used in > >> other > >>>> technologies. Maybe another unique name would be more accurate. > >>>> > >>> > >>> We proposed Coral instead. How does this sound? > >>> > >>> > >>>> 2. the Onyx code is on github right now, under the Apache 2.0 license. > >>>> Does this > >>>> code has any affiliation with companies ? Meaning that we would need a > >> SGA > >>>> for > >>>> the code donation. > >>>> > >>>> It does not. The developers are affiliated with Seoul National > >> University. > >>> In this case, do we still need a SGA? > >>> > >>> > >>>> If you need any help for the incubation, I would be more than happy to > >>>> help ! > >>>> > >>>> > >>> Thanks for the offer. Would you be interested in being a mentor of the > >>> project? > >>> > >>> Thanks. > >>> -Gon > >>> > >>> > >>> > >>>> Regards > >>>> JB > >>>> > >>>> On 01/26/2018 12:28 AM, Byung-Gon Chun wrote: > >>>>> Dear Apache Incubator Community, > >>>>> > >>>>> Please accept the following proposal for presentation and discussion: > >>>>> https://wiki.apache.org/incubator/OnyxProposal > >>>>> > >>>>> Onyx is a data processing system that aims to flexibly control the > >>>> runtime > >>>>> behaviors of a job to adapt to varying deployment characteristics > >> (e.g., > >>>>> harnessing transient resources in datacenters, cross-datacenter > >>>> deployment, > >>>>> changing runtime based on job characteristics, etc.). Onyx provides > >> ways > >>>> to > >>>>> extend the system’s capabilities and incorporate the extensions to > the > >>>>> flexible job execution. > >>>>> Onyx translates a user program (e.g., Apache Beam, Apache Spark) into > >> an > >>>>> Intermediate Representation (IR) DAG, which Onyx optimizes and > deploys > >>>>> based on a deployment policy. > >>>>> > >>>>> I've attached the proposal below. > >>>>> > >>&g
Re: [PROPOSAL] Onyx - proposal for Apache Incubation
Thanks for the information, John!
On Wed, Jan 31, 2018 at 9:50 PM, John D. Ament
wrote:
> Sorry for mid-posting.
>
> This isn't the list to determine if a project name is suitable. There's a
> JIRA project dedicated to that, and if you need a quick answer better to
> email trademarks@ to get a more precise answer.
>
> The question is really going to be, is "Apache Onyx" going to be easily
> confused with something else.
>
> John
>
> On Sun, Jan 28, 2018 at 4:50 AM Byung-Gon Chun wrote:
>
> > Thank you for all the information! It looks like Surf doesn't work.
> >
> > If possible, we'd like to keep Onyx.
> > Another name we came up with is Coral.
> >
> > Thanks!
> > -Gon
> >
> >
> > On Sun, Jan 28, 2018 at 4:21 AM, Leif Hedstrom wrote:
> >
> > > Did we rule out Onyx for sure? Just because some other project might
> use
> > > it on say github doesn’t necessarily exclude us from having an Apache
> > Onyx?
> > >
> > > FWIW, I agree that surf is too similar in pronunciation to Apache serf.
> > :)
> > >
> > > Cheers,
> > >
> > > — Leif
> > >
> > > > On Jan 27, 2018, at 07:31, Dave Fisher
> wrote:
> > > >
> > > > Checking “Serf Software” which sounds the same.
> > > >
> > > > (1) there is already Apache Serf
> > > > (2) Serf is a product from Hashicorp at https://www.serf.io/. This
> > > would definitely confuse as it is apparently comparable to ZooKeeper.
> > > >
> > > > Regards,
> > > > Dave
> > > >
> > > > Sent from my iPhone
> > > >
> > > >> On Jan 27, 2018, at 3:12 AM, sebb wrote:
> > > >>
> > > >> A brief search for 'Surf Software' shows quite a few hits.
> > > >> I have not looked to see if they would be likely to be confused with
> > > >> this project or cause problems for others.
> > > >>
> > > >> But it as though there might be a problem:
> > > >> Surfer - Golden Software
> > > >> surf @ sourceforge
> > > >> Surf Software company
> > > >>
> > > >>
> > > >>> On 27 January 2018 at 08:03, Byung-Gon Chun
> > wrote:
> > > >>> Since we cannot use the name Onyx, we would like to change the
> > project
> > > name
> > > >>> to Surf.
> > > >>> I hope that this name works.
> > > >>>
> > > >>> -Gon
> > > >>>
> > > >>> ---
> > > >>> Byung-Gon Chun
> > > >>>
> > > >>>
> > > >>>> On Sat, Jan 27, 2018 at 4:57 AM, Byung-Gon Chun >
> > > wrote:
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>> On Sat, Jan 27, 2018 at 4:09 AM, Davor Bonaci
> > > wrote:
> > > >>>>>
> > > >>>>> Great work -- I think this technology has a lot of promise, and
> I'd
> > > love
> > > >>>>> to
> > > >>>>> see its evolution inside the Foundation.
> > > >>>>>
> > > >>>>>
> > > >>>> Thanks, Davor!
> > > >>>>
> > > >>>>
> > > >>>>> Parts of it, like the Onyx Intermediate Representation [1],
> overlap
> > > with
> > > >>>>> the work-in-progress inside the Apache Beam project
> > ("portability").
> > > We'd
> > > >>>>> love to work together on this -- would you be open to such
> > > collaboration?
> > > >>>>> If so, it may not be necessary to start from scratch, and
> leverage
> > > the
> > > >>>>> work
> > > >>>>> already done.
> > > >>>>>
> > > >>>>>
> > > >>>> Sure. We're open to collaboration.
> > > >>>>
> > > >>>>
> > > >>>>> Regarding the name, Onyx would likely have to be renamed, due to
> a
> > > >>>>> conflict
> > > >>>>> with a related technology [2].
> > > >>>>>
> > > >>>>>
> > > >>>> Thanks for pointing it out. It's difficult to co
Re: [PROPOSAL] Onyx - proposal for Apache Incubation
On Wed, Jan 31, 2018 at 4:04 PM, Jean-Baptiste Onofré wrote: > Hi, > > Coral is a good name ! > Thanks! > > Does the code belong to Seoul National University ? In that case, in > addition of > your ICLA, we would need a SGA (it's not blocker for the project > bootstrapping > or code donation, but we, at least, will need it later for graduation). On > the > other hand, if the committers are all part on the university, you can also > sign > a CCLA. > I will figure this out. > > Happy to be mentor on the project if you want me ! ;) > > Thanks! I will add you to the mentor list. -Gon > Thanks, > Regards > JB > > On 01/30/2018 10:17 AM, Byung-Gon Chun wrote: > > Thanks for the comments, JB! > > My replies are inlined below. > > > > On Tue, Jan 30, 2018 at 5:52 PM, Jean-Baptiste Onofré > > wrote: > > > >> Hi, > >> > >> sorry to be a little bit late on this. > >> > >> It's a very interesting proposal. It sounds pretty close to the > portability > >> layer we want to add in Apache Beam. I would love to see interaction > >> between the > >> two communities. > >> > >> I have two minor questions: > >> > >> 1. about the name: Onyx sounds very generic and the name is used in > other > >> technologies. Maybe another unique name would be more accurate. > >> > > > > We proposed Coral instead. How does this sound? > > > > > >> 2. the Onyx code is on github right now, under the Apache 2.0 license. > >> Does this > >> code has any affiliation with companies ? Meaning that we would need a > SGA > >> for > >> the code donation. > >> > >> It does not. The developers are affiliated with Seoul National > University. > > In this case, do we still need a SGA? > > > > > >> If you need any help for the incubation, I would be more than happy to > >> help ! > >> > >> > > Thanks for the offer. Would you be interested in being a mentor of the > > project? > > > > Thanks. > > -Gon > > > > > > > >> Regards > >> JB > >> > >> On 01/26/2018 12:28 AM, Byung-Gon Chun wrote: > >>> Dear Apache Incubator Community, > >>> > >>> Please accept the following proposal for presentation and discussion: > >>> https://wiki.apache.org/incubator/OnyxProposal > >>> > >>> Onyx is a data processing system that aims to flexibly control the > >> runtime > >>> behaviors of a job to adapt to varying deployment characteristics > (e.g., > >>> harnessing transient resources in datacenters, cross-datacenter > >> deployment, > >>> changing runtime based on job characteristics, etc.). Onyx provides > ways > >> to > >>> extend the system’s capabilities and incorporate the extensions to the > >>> flexible job execution. > >>> Onyx translates a user program (e.g., Apache Beam, Apache Spark) into > an > >>> Intermediate Representation (IR) DAG, which Onyx optimizes and deploys > >>> based on a deployment policy. > >>> > >>> I've attached the proposal below. > >>> > >>> Best regards, > >>> Byung-Gon Chun > >>> > >>> = OnyxProposal = > >>> > >>> == Abstract == > >>> Onyx is a data processing system for flexible employment with > >>> different execution scenarios for various deployment characteristics > >>> on clusters. > >>> > >>> == Proposal == > >>> Today, there is a wide variety of data processing systems with > >>> different designs for better performance and datacenter efficiency. > >>> They include processing data on specific resource environments and > >>> running jobs with specific attributes. Although each system > >>> successfully solves the problems it targets, most systems are designed > >>> in the way that runtime behaviors are built tightly inside the system > >>> core to hide the complexity of distributed computing. This makes it > >>> hard for a single system to support different deployment > >>> characteristics with different runtime behaviors without substantial > >>> effort. > >>> > >>> Onyx is a data processing system that aims to flexibly control the > >>> runtime behaviors of a job to adapt to varying deployment > >>> characteristics.
Re: [PROPOSAL] Onyx - proposal for Apache Incubation
If Coral as our project name is fine, I will start voting in a couple of days. Let me know if you have any concern. Thanks. -Gon On Tue, Jan 30, 2018 at 6:17 PM, Byung-Gon Chun wrote: > Thanks for the comments, JB! > My replies are inlined below. > > On Tue, Jan 30, 2018 at 5:52 PM, Jean-Baptiste Onofré > wrote: > >> Hi, >> >> sorry to be a little bit late on this. >> >> It's a very interesting proposal. It sounds pretty close to the >> portability >> layer we want to add in Apache Beam. I would love to see interaction >> between the >> two communities. >> >> I have two minor questions: >> >> 1. about the name: Onyx sounds very generic and the name is used in other >> technologies. Maybe another unique name would be more accurate. >> > > We proposed Coral instead. How does this sound? > > >> 2. the Onyx code is on github right now, under the Apache 2.0 license. >> Does this >> code has any affiliation with companies ? Meaning that we would need a >> SGA for >> the code donation. >> >> It does not. The developers are affiliated with Seoul National > University. > In this case, do we still need a SGA? > > >> If you need any help for the incubation, I would be more than happy to >> help ! >> >> > Thanks for the offer. Would you be interested in being a mentor of the > project? > > Thanks. > -Gon > > > >> Regards >> JB >> >> On 01/26/2018 12:28 AM, Byung-Gon Chun wrote: >> > Dear Apache Incubator Community, >> > >> > Please accept the following proposal for presentation and discussion: >> > https://wiki.apache.org/incubator/OnyxProposal >> > >> > Onyx is a data processing system that aims to flexibly control the >> runtime >> > behaviors of a job to adapt to varying deployment characteristics (e.g., >> > harnessing transient resources in datacenters, cross-datacenter >> deployment, >> > changing runtime based on job characteristics, etc.). Onyx provides >> ways to >> > extend the system’s capabilities and incorporate the extensions to the >> > flexible job execution. >> > Onyx translates a user program (e.g., Apache Beam, Apache Spark) into an >> > Intermediate Representation (IR) DAG, which Onyx optimizes and deploys >> > based on a deployment policy. >> > >> > I've attached the proposal below. >> > >> > Best regards, >> > Byung-Gon Chun >> > >> > = OnyxProposal = >> > >> > == Abstract == >> > Onyx is a data processing system for flexible employment with >> > different execution scenarios for various deployment characteristics >> > on clusters. >> > >> > == Proposal == >> > Today, there is a wide variety of data processing systems with >> > different designs for better performance and datacenter efficiency. >> > They include processing data on specific resource environments and >> > running jobs with specific attributes. Although each system >> > successfully solves the problems it targets, most systems are designed >> > in the way that runtime behaviors are built tightly inside the system >> > core to hide the complexity of distributed computing. This makes it >> > hard for a single system to support different deployment >> > characteristics with different runtime behaviors without substantial >> > effort. >> > >> > Onyx is a data processing system that aims to flexibly control the >> > runtime behaviors of a job to adapt to varying deployment >> > characteristics. Moreover, it provides a means of extending the >> > system’s capabilities and incorporating the extensions to the flexible >> > job execution. >> > >> > In order to be able to easily modify runtime behaviors to adapt to >> > varying deployment characteristics, Onyx exposes runtime behaviors to >> > be flexibly configured and modified at both compile-time and runtime >> > through a set of high-level graph pass interfaces. >> > >> > We hope to contribute to the big data processing community by enabling >> > more flexibility and extensibility in job executions. Furthermore, we >> > can benefit more together as a community when we work together as a >> > community to mature the system with more use cases and understanding >> > of diverse deployment characteristics. The Apache Software Foundation >> > is the perfect place to achieve these aspirations. >> > >> >
Re: [PROPOSAL] Onyx - proposal for Apache Incubation
Thanks for the comments, JB! My replies are inlined below. On Tue, Jan 30, 2018 at 5:52 PM, Jean-Baptiste Onofré wrote: > Hi, > > sorry to be a little bit late on this. > > It's a very interesting proposal. It sounds pretty close to the portability > layer we want to add in Apache Beam. I would love to see interaction > between the > two communities. > > I have two minor questions: > > 1. about the name: Onyx sounds very generic and the name is used in other > technologies. Maybe another unique name would be more accurate. > We proposed Coral instead. How does this sound? > 2. the Onyx code is on github right now, under the Apache 2.0 license. > Does this > code has any affiliation with companies ? Meaning that we would need a SGA > for > the code donation. > > It does not. The developers are affiliated with Seoul National University. In this case, do we still need a SGA? > If you need any help for the incubation, I would be more than happy to > help ! > > Thanks for the offer. Would you be interested in being a mentor of the project? Thanks. -Gon > Regards > JB > > On 01/26/2018 12:28 AM, Byung-Gon Chun wrote: > > Dear Apache Incubator Community, > > > > Please accept the following proposal for presentation and discussion: > > https://wiki.apache.org/incubator/OnyxProposal > > > > Onyx is a data processing system that aims to flexibly control the > runtime > > behaviors of a job to adapt to varying deployment characteristics (e.g., > > harnessing transient resources in datacenters, cross-datacenter > deployment, > > changing runtime based on job characteristics, etc.). Onyx provides ways > to > > extend the system’s capabilities and incorporate the extensions to the > > flexible job execution. > > Onyx translates a user program (e.g., Apache Beam, Apache Spark) into an > > Intermediate Representation (IR) DAG, which Onyx optimizes and deploys > > based on a deployment policy. > > > > I've attached the proposal below. > > > > Best regards, > > Byung-Gon Chun > > > > = OnyxProposal = > > > > == Abstract == > > Onyx is a data processing system for flexible employment with > > different execution scenarios for various deployment characteristics > > on clusters. > > > > == Proposal == > > Today, there is a wide variety of data processing systems with > > different designs for better performance and datacenter efficiency. > > They include processing data on specific resource environments and > > running jobs with specific attributes. Although each system > > successfully solves the problems it targets, most systems are designed > > in the way that runtime behaviors are built tightly inside the system > > core to hide the complexity of distributed computing. This makes it > > hard for a single system to support different deployment > > characteristics with different runtime behaviors without substantial > > effort. > > > > Onyx is a data processing system that aims to flexibly control the > > runtime behaviors of a job to adapt to varying deployment > > characteristics. Moreover, it provides a means of extending the > > system’s capabilities and incorporating the extensions to the flexible > > job execution. > > > > In order to be able to easily modify runtime behaviors to adapt to > > varying deployment characteristics, Onyx exposes runtime behaviors to > > be flexibly configured and modified at both compile-time and runtime > > through a set of high-level graph pass interfaces. > > > > We hope to contribute to the big data processing community by enabling > > more flexibility and extensibility in job executions. Furthermore, we > > can benefit more together as a community when we work together as a > > community to mature the system with more use cases and understanding > > of diverse deployment characteristics. The Apache Software Foundation > > is the perfect place to achieve these aspirations. > > > > == Background == > > Many data processing systems have distinctive runtime behaviors > > optimized and configured for specific deployment characteristics like > > different resource environments and for handling special job > > attributes. > > > > For example, much research have been conducted to overcome the > > challenge of running data processing jobs on cheap, unreliable > > transient resources. Likewise, techniques for disaggregating different > > types of resources, like memory, CPU and GPU, are being actively > > developed to use datacenter resources more efficiently. Many > > r
Re: [PROPOSAL] Onyx - proposal for Apache Incubation
Thank you for all the information! It looks like Surf doesn't work.
If possible, we'd like to keep Onyx.
Another name we came up with is Coral.
Thanks!
-Gon
On Sun, Jan 28, 2018 at 4:21 AM, Leif Hedstrom wrote:
> Did we rule out Onyx for sure? Just because some other project might use
> it on say github doesn’t necessarily exclude us from having an Apache Onyx?
>
> FWIW, I agree that surf is too similar in pronunciation to Apache serf. :)
>
> Cheers,
>
> — Leif
>
> > On Jan 27, 2018, at 07:31, Dave Fisher wrote:
> >
> > Checking “Serf Software” which sounds the same.
> >
> > (1) there is already Apache Serf
> > (2) Serf is a product from Hashicorp at https://www.serf.io/. This
> would definitely confuse as it is apparently comparable to ZooKeeper.
> >
> > Regards,
> > Dave
> >
> > Sent from my iPhone
> >
> >> On Jan 27, 2018, at 3:12 AM, sebb wrote:
> >>
> >> A brief search for 'Surf Software' shows quite a few hits.
> >> I have not looked to see if they would be likely to be confused with
> >> this project or cause problems for others.
> >>
> >> But it as though there might be a problem:
> >> Surfer - Golden Software
> >> surf @ sourceforge
> >> Surf Software company
> >>
> >>
> >>> On 27 January 2018 at 08:03, Byung-Gon Chun wrote:
> >>> Since we cannot use the name Onyx, we would like to change the project
> name
> >>> to Surf.
> >>> I hope that this name works.
> >>>
> >>> -Gon
> >>>
> >>> ---
> >>> Byung-Gon Chun
> >>>
> >>>
> >>>> On Sat, Jan 27, 2018 at 4:57 AM, Byung-Gon Chun
> wrote:
> >>>>
> >>>>
> >>>>
> >>>>> On Sat, Jan 27, 2018 at 4:09 AM, Davor Bonaci
> wrote:
> >>>>>
> >>>>> Great work -- I think this technology has a lot of promise, and I'd
> love
> >>>>> to
> >>>>> see its evolution inside the Foundation.
> >>>>>
> >>>>>
> >>>> Thanks, Davor!
> >>>>
> >>>>
> >>>>> Parts of it, like the Onyx Intermediate Representation [1], overlap
> with
> >>>>> the work-in-progress inside the Apache Beam project ("portability").
> We'd
> >>>>> love to work together on this -- would you be open to such
> collaboration?
> >>>>> If so, it may not be necessary to start from scratch, and leverage
> the
> >>>>> work
> >>>>> already done.
> >>>>>
> >>>>>
> >>>> Sure. We're open to collaboration.
> >>>>
> >>>>
> >>>>> Regarding the name, Onyx would likely have to be renamed, due to a
> >>>>> conflict
> >>>>> with a related technology [2].
> >>>>>
> >>>>>
> >>>> Thanks for pointing it out. It's difficult to come up with a good
> short
> >>>> name. :)
> >>>> Do you have any suggestion?
> >>>>
> >>>> Thanks!
> >>>> -Gon
> >>>>
> >>>> ---
> >>>> Byung-Gon Chun
> >>>>
> >>>>
> >>>>
> >>>>> Davor
> >>>>>
> >>>>> [1] https://snuspl.github.io/onyx/docs/ir/
> >>>>> [2] http://www.onyxplatform.org/
> >>>>>
> >>>>>> On Thu, Jan 25, 2018 at 3:28 PM, Byung-Gon Chun
> wrote:
> >>>>>>
> >>>>>> Dear Apache Incubator Community,
> >>>>>>
> >>>>>> Please accept the following proposal for presentation and
> discussion:
> >>>>>> https://wiki.apache.org/incubator/OnyxProposal
> >>>>>>
> >>>>>> Onyx is a data processing system that aims to flexibly control the
> >>>>> runtime
> >>>>>> behaviors of a job to adapt to varying deployment characteristics
> (e.g.,
> >>>>>> harnessing transient resources in datacenters, cross-datacenter
> >>>>> deployment,
> >>>>>> changing runtime based on job characteristics, etc.). Onyx provides
> >>>>> ways to
> >>>>>> extend the system’s capabilities and incorporate the extensions to
> the
> &
Re: [PROPOSAL] Onyx - proposal for Apache Incubation
Since we cannot use the name Onyx, we would like to change the project name
to Surf.
I hope that this name works.
-Gon
---
Byung-Gon Chun
On Sat, Jan 27, 2018 at 4:57 AM, Byung-Gon Chun wrote:
>
>
> On Sat, Jan 27, 2018 at 4:09 AM, Davor Bonaci wrote:
>
>> Great work -- I think this technology has a lot of promise, and I'd love
>> to
>> see its evolution inside the Foundation.
>>
>>
> Thanks, Davor!
>
>
>> Parts of it, like the Onyx Intermediate Representation [1], overlap with
>> the work-in-progress inside the Apache Beam project ("portability"). We'd
>> love to work together on this -- would you be open to such collaboration?
>> If so, it may not be necessary to start from scratch, and leverage the
>> work
>> already done.
>>
>>
> Sure. We're open to collaboration.
>
>
>> Regarding the name, Onyx would likely have to be renamed, due to a
>> conflict
>> with a related technology [2].
>>
>>
> Thanks for pointing it out. It's difficult to come up with a good short
> name. :)
> Do you have any suggestion?
>
> Thanks!
> -Gon
>
> ---
> Byung-Gon Chun
>
>
>
>> Davor
>>
>> [1] https://snuspl.github.io/onyx/docs/ir/
>> [2] http://www.onyxplatform.org/
>>
>> On Thu, Jan 25, 2018 at 3:28 PM, Byung-Gon Chun wrote:
>>
>> > Dear Apache Incubator Community,
>> >
>> > Please accept the following proposal for presentation and discussion:
>> > https://wiki.apache.org/incubator/OnyxProposal
>> >
>> > Onyx is a data processing system that aims to flexibly control the
>> runtime
>> > behaviors of a job to adapt to varying deployment characteristics (e.g.,
>> > harnessing transient resources in datacenters, cross-datacenter
>> deployment,
>> > changing runtime based on job characteristics, etc.). Onyx provides
>> ways to
>> > extend the system’s capabilities and incorporate the extensions to the
>> > flexible job execution.
>> > Onyx translates a user program (e.g., Apache Beam, Apache Spark) into an
>> > Intermediate Representation (IR) DAG, which Onyx optimizes and deploys
>> > based on a deployment policy.
>> >
>> > I've attached the proposal below.
>> >
>> > Best regards,
>> > Byung-Gon Chun
>> >
>> > = OnyxProposal =
>> >
>> > == Abstract ==
>> > Onyx is a data processing system for flexible employment with
>> > different execution scenarios for various deployment characteristics
>> > on clusters.
>> >
>> > == Proposal ==
>> > Today, there is a wide variety of data processing systems with
>> > different designs for better performance and datacenter efficiency.
>> > They include processing data on specific resource environments and
>> > running jobs with specific attributes. Although each system
>> > successfully solves the problems it targets, most systems are designed
>> > in the way that runtime behaviors are built tightly inside the system
>> > core to hide the complexity of distributed computing. This makes it
>> > hard for a single system to support different deployment
>> > characteristics with different runtime behaviors without substantial
>> > effort.
>> >
>> > Onyx is a data processing system that aims to flexibly control the
>> > runtime behaviors of a job to adapt to varying deployment
>> > characteristics. Moreover, it provides a means of extending the
>> > system’s capabilities and incorporating the extensions to the flexible
>> > job execution.
>> >
>> > In order to be able to easily modify runtime behaviors to adapt to
>> > varying deployment characteristics, Onyx exposes runtime behaviors to
>> > be flexibly configured and modified at both compile-time and runtime
>> > through a set of high-level graph pass interfaces.
>> >
>> > We hope to contribute to the big data processing community by enabling
>> > more flexibility and extensibility in job executions. Furthermore, we
>> > can benefit more together as a community when we work together as a
>> > community to mature the system with more use cases and understanding
>> > of diverse deployment characteristics. The Apache Software Foundation
>> > is the perfect place to achieve these aspirations.
>> >
>> > == Background ==
>> > Many data processing systems have distinctive runtime behaviors
>> > optimized and configured for specific deployment charact
Re: [PROPOSAL] Onyx - proposal for Apache Incubation
On Sat, Jan 27, 2018 at 5:41 AM, Romain Manni-Bucau
wrote:
> Why not doing a beam subproject? Any blocker?
>
>
Thanks for the question, Romain.
We have a flexible, efficient runtime that supports various user programs
(e.g., Beam and Spark programs).
We are taking advantage of Beam as a programming layer, but our focus is
more on optimizing execution on various deployment scenarios.
We also plan to support other programming layers.
> Otherwise +1 to have it @asf, makes a lot of sense.
>
>
Thanks for the support!
-Gon
> Le 26 janv. 2018 20:58, "Byung-Gon Chun" a écrit :
>
> > On Sat, Jan 27, 2018 at 4:09 AM, Davor Bonaci wrote:
> >
> > > Great work -- I think this technology has a lot of promise, and I'd
> love
> > to
> > > see its evolution inside the Foundation.
> > >
> > >
> > Thanks, Davor!
> >
> >
> > > Parts of it, like the Onyx Intermediate Representation [1], overlap
> with
> > > the work-in-progress inside the Apache Beam project ("portability").
> We'd
> > > love to work together on this -- would you be open to such
> collaboration?
> > > If so, it may not be necessary to start from scratch, and leverage the
> > work
> > > already done.
> > >
> > >
> > Sure. We're open to collaboration.
> >
> >
> > > Regarding the name, Onyx would likely have to be renamed, due to a
> > conflict
> > > with a related technology [2].
> > >
> > >
> > Thanks for pointing it out. It's difficult to come up with a good short
> > name. :)
> > Do you have any suggestion?
> >
> > Thanks!
> > -Gon
> >
> > ---
> > Byung-Gon Chun
> >
> >
> >
> > > Davor
> > >
> > > [1] https://snuspl.github.io/onyx/docs/ir/
> > > [2] http://www.onyxplatform.org/
> > >
> > > On Thu, Jan 25, 2018 at 3:28 PM, Byung-Gon Chun
> > wrote:
> > >
> > > > Dear Apache Incubator Community,
> > > >
> > > > Please accept the following proposal for presentation and discussion:
> > > > https://wiki.apache.org/incubator/OnyxProposal
> > > >
> > > > Onyx is a data processing system that aims to flexibly control the
> > > runtime
> > > > behaviors of a job to adapt to varying deployment characteristics
> > (e.g.,
> > > > harnessing transient resources in datacenters, cross-datacenter
> > > deployment,
> > > > changing runtime based on job characteristics, etc.). Onyx provides
> > ways
> > > to
> > > > extend the system’s capabilities and incorporate the extensions to
> the
> > > > flexible job execution.
> > > > Onyx translates a user program (e.g., Apache Beam, Apache Spark) into
> > an
> > > > Intermediate Representation (IR) DAG, which Onyx optimizes and
> deploys
> > > > based on a deployment policy.
> > > >
> > > > I've attached the proposal below.
> > > >
> > > > Best regards,
> > > > Byung-Gon Chun
> > > >
> > > > = OnyxProposal =
> > > >
> > > > == Abstract ==
> > > > Onyx is a data processing system for flexible employment with
> > > > different execution scenarios for various deployment characteristics
> > > > on clusters.
> > > >
> > > > == Proposal ==
> > > > Today, there is a wide variety of data processing systems with
> > > > different designs for better performance and datacenter efficiency.
> > > > They include processing data on specific resource environments and
> > > > running jobs with specific attributes. Although each system
> > > > successfully solves the problems it targets, most systems are
> designed
> > > > in the way that runtime behaviors are built tightly inside the system
> > > > core to hide the complexity of distributed computing. This makes it
> > > > hard for a single system to support different deployment
> > > > characteristics with different runtime behaviors without substantial
> > > > effort.
> > > >
> > > > Onyx is a data processing system that aims to flexibly control the
> > > > runtime behaviors of a job to adapt to varying deployment
> > > > characteristics. Moreover, it provides a means of extending the
> > > > system’s capabilities and incorporating the extensions to the
> flexible
> > > > job executio
Re: [PROPOSAL] Onyx - proposal for Apache Incubation
On Sat, Jan 27, 2018 at 4:09 AM, Davor Bonaci wrote:
> Great work -- I think this technology has a lot of promise, and I'd love to
> see its evolution inside the Foundation.
>
>
Thanks, Davor!
> Parts of it, like the Onyx Intermediate Representation [1], overlap with
> the work-in-progress inside the Apache Beam project ("portability"). We'd
> love to work together on this -- would you be open to such collaboration?
> If so, it may not be necessary to start from scratch, and leverage the work
> already done.
>
>
Sure. We're open to collaboration.
> Regarding the name, Onyx would likely have to be renamed, due to a conflict
> with a related technology [2].
>
>
Thanks for pointing it out. It's difficult to come up with a good short
name. :)
Do you have any suggestion?
Thanks!
-Gon
---
Byung-Gon Chun
> Davor
>
> [1] https://snuspl.github.io/onyx/docs/ir/
> [2] http://www.onyxplatform.org/
>
> On Thu, Jan 25, 2018 at 3:28 PM, Byung-Gon Chun wrote:
>
> > Dear Apache Incubator Community,
> >
> > Please accept the following proposal for presentation and discussion:
> > https://wiki.apache.org/incubator/OnyxProposal
> >
> > Onyx is a data processing system that aims to flexibly control the
> runtime
> > behaviors of a job to adapt to varying deployment characteristics (e.g.,
> > harnessing transient resources in datacenters, cross-datacenter
> deployment,
> > changing runtime based on job characteristics, etc.). Onyx provides ways
> to
> > extend the system’s capabilities and incorporate the extensions to the
> > flexible job execution.
> > Onyx translates a user program (e.g., Apache Beam, Apache Spark) into an
> > Intermediate Representation (IR) DAG, which Onyx optimizes and deploys
> > based on a deployment policy.
> >
> > I've attached the proposal below.
> >
> > Best regards,
> > Byung-Gon Chun
> >
> > = OnyxProposal =
> >
> > == Abstract ==
> > Onyx is a data processing system for flexible employment with
> > different execution scenarios for various deployment characteristics
> > on clusters.
> >
> > == Proposal ==
> > Today, there is a wide variety of data processing systems with
> > different designs for better performance and datacenter efficiency.
> > They include processing data on specific resource environments and
> > running jobs with specific attributes. Although each system
> > successfully solves the problems it targets, most systems are designed
> > in the way that runtime behaviors are built tightly inside the system
> > core to hide the complexity of distributed computing. This makes it
> > hard for a single system to support different deployment
> > characteristics with different runtime behaviors without substantial
> > effort.
> >
> > Onyx is a data processing system that aims to flexibly control the
> > runtime behaviors of a job to adapt to varying deployment
> > characteristics. Moreover, it provides a means of extending the
> > system’s capabilities and incorporating the extensions to the flexible
> > job execution.
> >
> > In order to be able to easily modify runtime behaviors to adapt to
> > varying deployment characteristics, Onyx exposes runtime behaviors to
> > be flexibly configured and modified at both compile-time and runtime
> > through a set of high-level graph pass interfaces.
> >
> > We hope to contribute to the big data processing community by enabling
> > more flexibility and extensibility in job executions. Furthermore, we
> > can benefit more together as a community when we work together as a
> > community to mature the system with more use cases and understanding
> > of diverse deployment characteristics. The Apache Software Foundation
> > is the perfect place to achieve these aspirations.
> >
> > == Background ==
> > Many data processing systems have distinctive runtime behaviors
> > optimized and configured for specific deployment characteristics like
> > different resource environments and for handling special job
> > attributes.
> >
> > For example, much research have been conducted to overcome the
> > challenge of running data processing jobs on cheap, unreliable
> > transient resources. Likewise, techniques for disaggregating different
> > types of resources, like memory, CPU and GPU, are being actively
> > developed to use datacenter resources more efficiently. Many
> > researchers are also working to run data processing jobs in even more
> > diverse environments, such as across distant datacenters. Similarly,
> > for sp
[PROPOSAL] Onyx - proposal for Apache Incubation
Dear Apache Incubator Community, Please accept the following proposal for presentation and discussion: https://wiki.apache.org/incubator/OnyxProposal Onyx is a data processing system that aims to flexibly control the runtime behaviors of a job to adapt to varying deployment characteristics (e.g., harnessing transient resources in datacenters, cross-datacenter deployment, changing runtime based on job characteristics, etc.). Onyx provides ways to extend the system’s capabilities and incorporate the extensions to the flexible job execution. Onyx translates a user program (e.g., Apache Beam, Apache Spark) into an Intermediate Representation (IR) DAG, which Onyx optimizes and deploys based on a deployment policy. I've attached the proposal below. Best regards, Byung-Gon Chun = OnyxProposal = == Abstract == Onyx is a data processing system for flexible employment with different execution scenarios for various deployment characteristics on clusters. == Proposal == Today, there is a wide variety of data processing systems with different designs for better performance and datacenter efficiency. They include processing data on specific resource environments and running jobs with specific attributes. Although each system successfully solves the problems it targets, most systems are designed in the way that runtime behaviors are built tightly inside the system core to hide the complexity of distributed computing. This makes it hard for a single system to support different deployment characteristics with different runtime behaviors without substantial effort. Onyx is a data processing system that aims to flexibly control the runtime behaviors of a job to adapt to varying deployment characteristics. Moreover, it provides a means of extending the system’s capabilities and incorporating the extensions to the flexible job execution. In order to be able to easily modify runtime behaviors to adapt to varying deployment characteristics, Onyx exposes runtime behaviors to be flexibly configured and modified at both compile-time and runtime through a set of high-level graph pass interfaces. We hope to contribute to the big data processing community by enabling more flexibility and extensibility in job executions. Furthermore, we can benefit more together as a community when we work together as a community to mature the system with more use cases and understanding of diverse deployment characteristics. The Apache Software Foundation is the perfect place to achieve these aspirations. == Background == Many data processing systems have distinctive runtime behaviors optimized and configured for specific deployment characteristics like different resource environments and for handling special job attributes. For example, much research have been conducted to overcome the challenge of running data processing jobs on cheap, unreliable transient resources. Likewise, techniques for disaggregating different types of resources, like memory, CPU and GPU, are being actively developed to use datacenter resources more efficiently. Many researchers are also working to run data processing jobs in even more diverse environments, such as across distant datacenters. Similarly, for special job attributes, many works take different approaches, such as runtime optimization, to solve problems like data skew, and to optimize systems for data processing jobs with small-scale input data. Although each of the systems performs well with the jobs and in the environments they target, they perform poorly with unconsidered cases, and do not consider supporting multiple deployment characteristics on a single system in their designs. For an application writer to optimize an application to perform well on a certain system engraved with its underlying behaviors, it requires a deep understanding of the system itself, which is an overhead that often requires a lot of time and effort. Moreover, for a developer to modify such system behaviors, it requires modifications of the system core, which requires an even deeper understanding of the system itself. With this background, Onyx is designed to represent all of its jobs as an Intermediate Representation (IR) DAG. In the Onyx compiler, user applications from various programming models (ex. Apache Beam) are submitted, transformed to an IR DAG, and optimized/customized for the deployment characteristics. In the IR DAG optimization phase, the DAG is modified through a series of compiler “passes” which reshape or annotate the DAG with an expression of the underlying runtime behaviors. The IR DAG is then submitted as an execution plan for the Onyx runtime. The runtime includes the unmodified parts of data processing in the backbone which is transparently integrated with configurable components exposed for further extension. == Rationale == Onyx’s vision lies in providing means for flexibly supporting a wide variety of job execution scenarios for users while facilitating system developers to exten
Re: [Request] Write access to the incubator wiki
John, thanks for the quick response! On Fri, Jan 26, 2018 at 7:04 AM, John D. Ament wrote: > I've added you, happy editing! > > On Thu, Jan 25, 2018 at 4:36 PM Byung-Gon Chun wrote: > > > Hi, > > > > Please grant me write access to the incubator wiki: > > https://wiki.apache.org/incubator. > > > > My user name is Byung-gonChun. > > > > Thanks! > > -Gon > > > > -- > > Byung-Gon Chun > > > -- Byung-Gon Chun
[Request] Write access to the incubator wiki
Hi, Please grant me write access to the incubator wiki: https://wiki.apache.org/incubator. My user name is Byung-gonChun. Thanks! -Gon -- Byung-Gon Chun
Re: [VOTE] Accept ECharts for Apache Incubation
After incubation, we want to move the existing repo from > github/ecomfe/echarts to Apache infrastructure. > > Issue Tracking: > > ECharts currently uses GitHub to track issues. there are more than 7k > issues. Would like to continue to do so while we discuss migration > possibilities with the ASF Infra committee. > > URL: > > Currently the website url is https://ecomfe.github.io/echar > ts-doc/public/en/index.html. It will be moved to > http://echarts.incubator.apache.org/ to follow incubator conventions. > > Initial Committers > > Lin Zhifeng (https://github.com/kener kener.linf...@gmail.com) > > Su Shuang (https://github.com/100pah sushuang0...@gmail.com) > > Shen Yi (https://github.com/pissang shenyi@gmail.com) > > Zhang Wenli (https://github.com/Ovilia m...@zhangwenli.com) > > Li Deqing (https://github.com/deqingli annong...@gmail.com) > Wang Junting > > Dong Rui (https://github.com/erik168 error...@gmail.com) > > Huang Houjin (https://github.com/chriswong w...@foxmail.com) > > Sponsors: > > Champion: > > Kevin A. McGrail > > Mentors: > > Daniel Gruno > > Kevin A. McGrail > Dave Fisher > John D. Ament > > Sponsoring Entity > We are requesting the Incubator to sponsor this project. > > -- > Kevin A. McGrail > Asst. Treasurer & VP Fundraising, Apache Software Foundation > Chair Emeritus Apache SpamAssassin Project > -- Byung-Gon Chun
Re: [VOTE] Retire Wave
+1 (binding) -Gon On Tue, Jan 9, 2018 at 3:56 AM, John D. Ament wrote: > All, > > This is a call to vote for the retirement of the Wave podling. > > The podling has positively voted to retire [1]. I now call upon the IPMC > to confirm this retirement. > > [ ] +1 to retire > [ ] +/- 0 to retire > [ ] -1 don't retire because... > > The podling is working on a migration plan, it seems they will move the > code to github somewhere, and will work on it as seen fit there. > > John > > [1]: > https://lists.apache.org/thread.html/fe4b7a240facbebeded29d7d9d8c73 > 3c0e5e624f07b7a110887c2f16@%3Cwave-dev.incubator.apache.org%3E > -- Byung-Gon Chun
Re: [VOTE] Graduate Apache Guacamole as TLP
+1 (binding) On Mon, Nov 13, 2017 at 10:10 PM, Jim Jagielski wrote: > +1 (binding) > > On Nov 10, 2017, at 2:51 PM, Mike Jumper wrote: > > > > Hello Incubator PMC, > > > > The Apache Guacamole community has discussed [1] [2], voted on, and > > approved a resolution to graduate to a top-level project. The draft > > resolution has since been given to the IPMC for review and discussion > [3], > > and with no further feedback, we would now like to call a VOTE to > graduate > > and establish Apache Guacamole as a top-level project. > > > > Apache Guacamole began incubation in February of 2016. Since entering the > > Incubator, the podling has gone through four releases [4], added three > > committers, and grown a healthy and active community on the mailing > lists. > > Our completed maturity evaluation can be found here: > > > > http://guacamole.incubator.apache.org/maturity-evaluation/ > > > > and the community graduation VOTE result can be found here: > > > > https://lists.apache.org/thread.html/0de2c49ee556b0e024d25be6092d40 > > 5ce8d1cccbb9df1823ba79713e@%3Cdev.guacamole.apache.org%3E > > > > The full text of the proposed resolution can be found below. > > > > Please review and vote: > > > > [ ] +1 Graduate Apache Guacamole podling from the Incubator > > [ ] +0 Don't care > > [ ] -1 Don't graduate Apache Guacamole from the Incubator because... > > > > This vote will be open for at least 72 hours. > > > > Thanks, > > > > - Mike > > > > [1] https://lists.apache.org/thread.html/0848dd53b6acc1a0edea2ed > > a1f385294eeb041a88c3d1f6221fa1ef2@%3Cdev.guacamole.apache.org%3E > > [2] https://lists.apache.org/thread.html/a5259173a8ef4a1d2bb7be2 > > d99d3cbc2ccf8856130ae6e3fe54e079e@%3Cdev.guacamole.apache.org%3E > > [3] https://lists.apache.org/thread.html/da03d479209b6f7a254a301de9bcd4 > > 07a6eaf65f632227e76395f32d@%3Cgeneral.incubator.apache.org%3E > > [4] http://guacamole.incubator.apache.org/releases/ > > > > -- > > > > Establish the Apache Guacamole 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 providing performant, browser-based remote access. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > (PMC), to be known as the "Apache Guacamole Project", be and hereby is > > established pursuant to Bylaws of the Foundation; and be it further > > > > RESOLVED, that the Apache Guacamole Project be and hereby is responsible > > for the creation and maintenance of software related to providing > > performant, browser-based remote access; and be it further > > > > RESOLVED, that the office of "Vice President, Apache Guacamole" 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 Guacamole > > Project, and to have primary responsibility for management of the > > projects within the scope of responsibility of the Apache Guacamole > > 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 Guacamole > > Project: > > > > * Carl Harris > > * Daniel Gruno > > * Frode Langelo > > * Greg Trasuk > > * James Muehlner > > * Jean-Baptiste Onofré > > * Jim Jagielski > > * Mike Jumper > > * Nick Couchman > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mike Jumper be appointed to > > the office of Vice President, Apache Guacamole, 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 Guacamole PMC be and hereby is tasked > > with the creation of a set of bylaws intended to encourage open > > development and increased participation in the Apache Guacamole Project; > > and be it further > > > > RESOLVED, that the Apache Guacamole Project be and hereby is tasked with > > the migration and rationalization of the Apache Incubator Guacamole > > podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > Guacamole 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 > > -- Byung-Gon Chun
Re: [VOTE] Resolution to graduate Apache Impala to TLP
+1 (binding) On Fri, Nov 10, 2017 at 7:31 AM, Carl Steinbach wrote: > +1 (binding) > > On Thu, Nov 9, 2017 at 10:04 AM, Todd Lipcon wrote: > > > +1 (binding) from me! > > > > Todd > > > > On Nov 8, 2017 8:28 PM, "Jim Apple" wrote: > > > > > The graduation of Impala to a TLP has been discussed[0] on dev@impala, > > > voted on[1] on dev@impala, and discussed[2] on general@incubator. All > > > threads were open 72 hours or more, and all seem to have quiesced. > > > > > > This is a call for a VOTE to graduate Impala to a TLP. The draft > > resolution > > > is below. Please select from: > > > > > > [ ] +1: Graduate Impala to a TLP > > > [ ] +-0: Neither graduate nor do not graduate Impala to a TLP > > > [ ] -1: Do NOT graduate Impala to a TLP, because ... > > > > > > > > > > > > [0]: < > > > https://lists.apache.org/thread.html/2f5db4788aff9b0557354b9106c032 > > > 8a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E > > > > > > > > > > [1]: < > > > https://lists.apache.org/thread.html/a5a7c6895b3e019347d6e4e4cf49d6 > > > 7d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E > > > > > > > > > > [2]: < > > > https://lists.apache.org/thread.html/6b8598408f76a472532923c5a7fc51 > > > 0470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E > > > > > > > > > > > > > > > > Establish the Apache Impala 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 high-performance distributed SQL engine. > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > (PMC), to be known as the "Apache Impala Project", be and hereby is > > > established pursuant to Bylaws of the Foundation; and be it further > > > > > > RESOLVED, that the Apache Impala Project be and hereby is responsible > > > for the creation and maintenance of software related to a > > > high-performance distributed SQL engine; and be it further > > > > > > RESOLVED, that the office of "Vice President, Apache Impala" 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 Impala > > > Project, and to have primary responsibility for management of the > > > projects within the scope of responsibility of the Apache Impala > > > 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 Impala Project: > > > > > > * Alex Behm > > > * Bharath Vissapragada > > > * Brock Noland > > > * Carl Steinbach > > > * Casey Ching > > > * Daniel Hecht > > > * Dimitris Tsirogiannis > > > * Henry Robinson > > > * Ishaan Joshi > > > * Jim Apple > > > * John Russell > > > * Juan Yu > > > * Lars Volker > > > * Lenni Kuff > > > * Marcel Kornacker > > > * Martin Grund > > > * Matthew Jacobs > > > * Michael Brown > > > * Michael Ho > > > * Sailesh Mukil > > > * Skye Wanderman-Milne > > > * Taras Bobrovytsky > > > * Tim Armstrong > > > * Todd Lipcon > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be appointed to > > > the office of Vice President, Apache Impala, 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 Impala PMC be and hereby is tasked > > > with the creation of a set of bylaws intended to encourage open > > > development and increased participation in the Apache Impala Project; > > > and be it further > > > > > > RESOLVED, that the Apache Impala Project be and hereby is tasked with > > > the migration and rationalization of the Apache Incubator Impala > > > podling; and be it further > > > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > > Impala podling encumbered upon the Apache Incubator PMC are hereafter > > > discharged. > > > > > > -- Byung-Gon Chun
Request to join IPMC
Hi, I am an Apache member and would like to join the IPMC. I'm a REEF PMC chair. Let me know what else you need from me. Thanks! -Gon -- Byung-Gon Chun
Re: [VOTE] Heron to enter Apache Incubator
ron.incubator.apache.org > * u...@heron.incubator.apache.org > > == Subversion Directory == > > Git is the preferred source control system: git://git.apache.org/heron > > == Issue Tracking == > > JIRA: Heron (HERON) > > == Initial Committers == > > * Andrew Jorgensen (andrew at andrewjorgensen dot com) > * Ashvin Agrawal (ashvin at apache dot org)* > * Avrilia Floratou (avrilia dot floratou at gmail dot com) > * Bill Graham (billgraham at apache dot org)* > * Brian Hatfield (bmhatfield at gmail dot com) > * Chris Kellogg (cckellogg at gmail dot com) > * Huijun Wu (huijun dot wu dot 2010 at gmail dot com) > * Karthik Ramasamy (karthik at gmail dot com) > * Maosong Fu (maosongfu at gmail dot com) > * Neng Lu(freeneng at gmail dot com) > * Runhang Li (obj dot runhang at gmail dot com) > * Sanjeev Kulkarni (sanjeevrk at gmail dot com) > * Supun Kamburugamuve (supun at apache dot org)* > * Thomas Sun (tom dot ssf at gmail dot com) > * Yaliang Wang (yaliang dot w dot wang at ieee dot org) > > == Affiliations == > > * Andrew Jorgensen (Google) > * Ashvin Agrawal (Microsoft) > * Avrilia Floratou (Microsoft) > * Bill Graham (Twitter) > * Brian Hatfield (Google) > * Chris Kellogg (Twitter) > * Huijun Wu (Twitter) > * Karthik Ramasamy (Streamlio) > * Maosong Fu (Twitter) > * Neng Lu (Twitter) > * Runhang Li (Twitter) > * Sanjeev Kulkarni (Streamlio) > * Supun Kamburugamuve (Indiana University) > * Thomas Sun (Twitter) > * Yaliang Wang (Twitter) > > = Sponsors = > > == Champion == > > * Julien Le Dem (julien at apache dot org) > > == Nominated Mentors == > > * Jake Farrell (jfarrell at apache dot org) > * Jacques Nadeau (jacques at apache dot org) > * Julien Le Dem (julien at apache dot org) > * P. Taylor Goetz (ptgoetz at apache dot org) > > == Sponsoring Entity == > > The Apache Incubator > > == Footnotes == > > * 1 - Papers detailing Heron are available at > http://dl.acm.org/citation.cfm?id=2742788 and > http://sites.computer.org/debull/A15dec/p15.pdf. > * 2 - http://home.apache.org/phonebook.html?uid=billgraham > * 3 - http://home.apache.org/phonebook.html?uid=ashvin > * 4 - http://home.apache.org/phonebook.html?uid=supun > -- Byung-Gon Chun
Re: [VOTE] MXNet to enter the Incubator
+1 (non-binding) On Sun, Jan 22, 2017 at 9:03 AM, Lieven Govaerts wrote: > On Tue, Jan 17, 2017 at 5:20 AM, Henri Yandell wrote: > > Hi Incubator folk, > > > >I would like to call a vote for accepting "MXNet" for incubation in > the > > Apache Incubator. > > > > The full proposal is available at this wiki link: > > > > https://wiki.apache.org/incubator/MXNetProposal?action=recall&rev=19 > > > > I will reply to this email with a copy of the proposal. > > > > MXNet already has a broad community, which I think is clear from the > > interest from many contributors in being a part of the project at Apache. > > There are four mentors signed up, along with 2 or 3 other Apache > committers > > looking to be involved in the project. > > > > Please cast your vote: > > > > [ ] +1, bring MXNet into the Incubator > > [ ] -1, MXNet should not enter the Incubator, because... > > > > The vote will be open for at least 72 hours, and only votes from the > > Incubator PMC are binding. > > > > As the proposer, I consider my vote already cast in favour (and binding > as > > I'm a PMC member). > > > > Thanks all, > > > > Hen > > > +1 > > Lieven > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: [RESTART] [VOTE] Graduate Apache Beam
+1 (non-binding) On Mon, Dec 5, 2016 at 3:30 PM, Davor Bonaci wrote: > Hi everyone, > Please vote on the draft resolution proposed by the Apache Beam PPMC below, > which establishes Apache Beam as a new top-level project at the Apache > Software Foundation, as follows: > > [ ] +1, Graduate Apache Beam from the Incubator. > [ ] +0, Don't care. > [ ] -1, Don't graduate Apache Beam from the Incubator because... > > Please note that this is a restarted vote, per John's request, to clarify > the alternatives. The old voting thread is archived [1]. > > Before voting, please see the full text of the draft resolution below and > the corresponding discussion thread [2], and vote only after you feel ready > to do so. The vote will be open for at least 72 hours. This is a procedural > vote [3]; it is adopted by a simple majority of qualified votes (with no > minimum). > > If approved by the Apache Incubator, the proposed resolution will be > submitted to the Board of Directors for their consideration. > > Thank you! > > Davor > > [1] > https://lists.apache.org/thread.html/a8e9cecfe93f0e464cc7c1774d2761 > ca14326df1101b7670ca8b1dc3@%3Cgeneral.incubator.apache.org%3E > [2] > https://lists.apache.org/thread.html/b9c1071b35558846836814575ada3c > dca61c72dc1e672ab994a9c936@%3Cgeneral.incubator.apache.org%3E > [3] http://apache.org/foundation/voting.html > > The full-text of the draft resolution proposed by the Apache Beam PPMC: > > X. Establish the Apache Beam 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 unified programming model for both >batch and streaming data processing, enabling efficient >execution across diverse distributed execution engines >and providing extensibility points for connecting to different >technologies and user communities. > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management >Committee (PMC), to be known as the "Apache Beam Project", >be and hereby is established pursuant to Bylaws of the >Foundation; and be it further > >RESOLVED, that the Apache Beam Project be and hereby is >responsible for the creation and maintenance of software >related to a unified programming model for both batch and >streaming data processing, enabling efficient execution across >diverse distributed execution engines and providing extensibility >points for connecting to different technologies and user >communities; and be it further > >RESOLVED, that the office of "Vice President, Apache Beam" 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 Beam Project, and to have primary responsibility >for management of the projects within the scope of >responsibility of the Apache Beam 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 Beam Project: > > * Tyler Akidau > * Davor Bonaci > * Robert Bradshaw > * Ben Chambers > * Luke Cwik > * Stephan Ewen > * Dan Halperin > * Kenneth Knowles > * Aljoscha Krettek > * Maximilian Michels > * Jean-Baptiste Onofré > * Frances Perry > * Amit Sela > * Josh Wills > >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Davor Bonaci >be appointed to the office of Vice President, Apache Beam, 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 Beam PMC be and hereby is >tasked with the creation of a set of bylaws intended to >encourage open development and increased participation in the >Apache Beam Project; and be it further > >RESOLVED, that the Apache Beam Project be and hereby >is tasked with the migration and rationalization of the Apache >Incubator Beam podling; and be it further > >RESOLVED, that all responsibilities pertaining to the Apache >Incubator Beam podling encumbered upon the Apache Incubator >Project are hereafter discharged. > -- Byung-Gon Chun
Re: [VOTE] Graduate Zeppelin from the Incubator
+1 (non-binding) On Sun, Apr 17, 2016 at 2:08 PM, Minho Kim wrote: > +1 (non binding). > Good luck! > > Regards, > Minho Kim > > 2016-04-17 7:41 GMT+09:00 John D. Ament : > > > +1 and good luck > > On Apr 16, 2016 05:01, "moon soo Lee" wrote: > > > > > Hi, > > > > > > Apache Zeppelin started incubating about a year and 4 months ago > > > (2014-12-23) and the members of the community think that it is ready to > > > graduate from the incubator to be a TLP. > > > > > > Since it's inception, Zeppelin community has made 3 releases, > recruited 4 > > > PPMC and resolved 500+ issues [1] with 90+ contributors [2]. Now, > > community > > > is very open, active and continuously growing. > > > > > > The Apache Zeppelin community has discussed and voted on graduation to > > > top level > > > project. > > > The vote passed with 22 +1 votes (9 binding) and no 0 or -1 votes. > > > > > > Incubation Status: > > > http://incubator.apache.org/projects/zeppelin.html > > > Maturity Assessment: > > > > > > > > > https://cwiki.apache.org/confluence/display/ZEPPELIN/Apache+Zeppelin+Project+Maturity+Model > > > Discussion: > > > https://s.apache.org/gLi0 > > > https://s.apache.org/GhqY (continue) > > > Vote: > > > https://s.apache.org/7hCK > > > Result: > > > https://s.apache.org/1rJD > > > > > > Please vote on the resolution pasted below to graduate Apache Zeppelin > > > from the incubator to top level project. > > > > > > [ ] +1 Graduate Apache Zeppelin from the Incubator. > > > [ ] +0 Don't care. > > > [ ] -1 Don't graduate Apache Zeppelin from the Incubator because > > > > > > This vote will be open for at least 72 hours. > > > Many thanks to our mentors and everyone else for the support, > > > > > > [1] https://s.apache.org/eswD > > > [2] https://s.apache.org/gi3o > > > > > > Apache Zeppelin top-level project resolution: > > > > > > > > > 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 collaborative data analytics and > > > visualization tool for general-purpose data processing systems. > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > > Committee (PMC), to be known as the "Apache Zeppelin Project", > > > be and hereby is established pursuant to Bylaws of the > > > Foundation; and be it further > > > > > > RESOLVED, that the Apache Zeppelin Project be and hereby is > > > responsible for the creation and maintenance of software > > > related to a collaborative data analytics and > > > visualization tool for general-purpose data processing systems; and be > it > > > further > > > > > > RESOLVED, that the office of "Vice President, Apache Zeppelin" 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 Zeppelin Project, and to have primary responsibility > > > for management of the projects within the scope of > > > responsibility of the Apache Zeppelin 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 Zeppelin Project: > > > > > > * Alexander Bezzubov > > > * Anthony Corbacho > > > * Damien Corneau > > > * Felix Cheung > > > * Jongyoul Lee > > > * Kevin Sangwoo Kim > > > * Lee Moon Soo > > > * Mina Lee > > > * Prabhjyot Singh > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lee Moon Soo > > > be appointed to the office of Vice President, Apache Zeppelin, 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 Zeppelin PMC be and hereby is > > > tasked with the creation of a set of bylaws intended to > > > encourage open development and increased participation in the > > > Apache Zeppelin Project; and be it further > > > > > > RESOLVED, that the Apache Zeppelin Project be and hereby > > > is tasked with the migration and rationalization of the Apache > > > Incubator Zeppelin podling; and be it further > > > > > > RESOLVED, that all responsibilities pertaining to the Apache > > > Incubator Zeppelin podling encumbered upon the Apache Incubator > > > Project are hereafter discharge. > > > > > > -- Byung-Gon Chun
Re: [VOTE] Accept Beam into the Apache Incubator
presently used by several organizations, from > >>> small > >>>>>> startups to Fortune 100 companies, to construct production pipelines > >>>>>> which are executed in Google Cloud Dataflow. Google has a long-term > >>>>>> commitment to advance the Dataflow SDK; moreover, Dataflow is seeing > >>>>>> increasing interest, development, and adoption from organizations > >>>>>> outside of Google. > >>>>>> > >>>>>> === Inexperience with Open Source === > >>>>>> > >>>>>> Google believes strongly in open source and the exchange of > >>> information > >>>>>> to advance new ideas and work. Examples of this commitment are > >>>>>>active > >>>>>> OSS projects such as Chromium (https://www.chromium.org) and > >>>> Kubernetes > >>>>>> (http://kubernetes.io/). With Dataflow, we have tried to be > >>>> increasingly > >>>>>> open and forward-looking; we have published a paper in the VLDB > >>>>>> conference describing the Dataflow model > >>>>>> (http://www.vldb.org/pvldb/vol8/p1792-Akidau.pdf) and were quick to > >>>>>> release the Dataflow SDK as open source software with the launch of > >>>>>> Cloud Dataflow. Our submission to the Apache Software Foundation is > >>>>>>a > >>>>>> logical extension of our commitment to open source software. > >>>>>> > >>>>>> === Homogeneous Developers === > >>>>>> > >>>>>> The majority of committers in this proposal belong to Google due to > >>> the > >>>>>> fact that Dataflow has emerged from several internal Google > >>>>>>projects. > >>>>>> This proposal also includes committers outside of Google who are > >>>>>> actively involved with other Apache projects, such as Hadoop, Flink, > >>>> and > >>>>>> Spark. We expect our entry into incubation will allow us to expand > >>> the > >>>>>> number of individuals and organizations participating in Dataflow > >>>>>> development. Additionally, separation of the Dataflow SDK from > >>>>>>Google > >>>>>> Cloud Dataflow allows us to focus on the open source SDK and model > >>> and > >>>>>> do what is best for this project. > >>>>>> > >>>>>> === Reliance on Salaried Developers === > >>>>>> > >>>>>> The Dataflow SDK and Dataflow runners have been developed primarily > >>> by > >>>>>> salaried developers supporting the Google Cloud Dataflow project. > >>> While > >>>>>> the Dataflow SDK and Cloud Dataflow have been developed by different > >>>>>> teams (and this proposal would reinforce that separation) we expect > >>> our > >>>>>> initial set of developers will still primarily be salaried. > >>>> Contribution > >>>>>> has not been exclusively from salaried developers, however. For > >>>> example, > >>>>>> the contrib directory of the Dataflow SDK > >>>>>> ( > >>>>>> > >>>>> > >>>> > >>> > >>> > https://github.com/GoogleCloudPlatform/DataflowJavaSDK/tree/master/contr > >>>ib > >>>>>> ) > >>>>>> contains items from free-time contributors. Moreover, seperate > >>>> projects, > >>>>>> such as ScalaFlow (https://github.com/darkjh/scalaflow) have been > >>>>>> created around the Dataflow model and SDK. We expect our reliance on > >>>>>> salaried developers will decrease over time during incubation. > >>>>>> > >>>>>> === Relationship with other Apache products === > >>>>>> > >>>>>> Dataflow directly interoperates with or utilizes several existing > >>>> Apache > >>>>>> projects. > >>>>>> > >>>>>> * Build > >>>>>> * Apache Maven > >>>>>> * Data I/O, Libraries > >>>>>> * Apache Avro > >>>>>> * Apache Co
Re: [DISCUSS] Apache Dataflow Incubator Proposal
This looks very interesting. I'm interested in contributing. Thanks. -Gon --- Byung-Gon Chun On Thu, Jan 21, 2016 at 1:32 AM, James Malone < jamesmal...@google.com.invalid> wrote: > Hello everyone, > > Attached to this message is a proposed new project - Apache Dataflow, a > unified programming model for data processing and integration. > > The text of the proposal is included below. Additionally, the proposal is > in draft form on the wiki where we will make any required changes: > > https://wiki.apache.org/incubator/DataflowProposal > > We look forward to your feedback and input. > > Best, > > James > > > > = Apache Dataflow = > > == Abstract == > > Dataflow is an open source, unified model and set of language-specific SDKs > for defining and executing data processing workflows, and also data > ingestion and integration flows, supporting Enterprise Integration Patterns > (EIPs) and Domain Specific Languages (DSLs). Dataflow pipelines simplify > the mechanics of large-scale batch and streaming data processing and can > run on a number of runtimes like Apache Flink, Apache Spark, and Google > Cloud Dataflow (a cloud service). Dataflow also brings DSL in different > languages, allowing users to easily implement their data integration > processes. > > == Proposal == > > Dataflow is a simple, flexible, and powerful system for distributed data > processing at any scale. Dataflow provides a unified programming model, a > software development kit to define and construct data processing pipelines, > and runners to execute Dataflow pipelines in several runtime engines, like > Apache Spark, Apache Flink, or Google Cloud Dataflow. Dataflow can be used > for a variety of streaming or batch data processing goals including ETL, > stream analysis, and aggregate computation. The underlying programming > model for Dataflow provides MapReduce-like parallelism, combined with > support for powerful data windowing, and fine-grained correctness control. > > == Background == > > Dataflow started as a set of Google projects focused on making data > processing easier, faster, and less costly. The Dataflow model is a > successor to MapReduce, FlumeJava, and Millwheel inside Google and is > focused on providing a unified solution for batch and stream processing. > These projects on which Dataflow is based have been published in several > papers made available to the public: > > * MapReduce - http://research.google.com/archive/mapreduce.html > > * Dataflow model - http://www.vldb.org/pvldb/vol8/p1792-Akidau.pdf > > * FlumeJava - http://notes.stephenholiday.com/FlumeJava.pdf > > * MillWheel - http://research.google.com/pubs/pub41378.html > > Dataflow was designed from the start to provide a portable programming > layer. When you define a data processing pipeline with the Dataflow model, > you are creating a job which is capable of being processed by any number of > Dataflow processing engines. Several engines have been developed to run > Dataflow pipelines in other open source runtimes, including a Dataflow > runner for Apache Flink and Apache Spark. There is also a “direct runner”, > for execution on the developer machine (mainly for dev/debug purposes). > Another runner allows a Dataflow program to run on a managed service, > Google Cloud Dataflow, in Google Cloud Platform. The Dataflow Java SDK is > already available on GitHub, and independent from the Google Cloud Dataflow > service. Another Python SDK is currently in active development. > > In this proposal, the Dataflow SDKs, model, and a set of runners will be > submitted as an OSS project under the ASF. The runners which are a part of > this proposal include those for Spark (from Cloudera), Flink (from data > Artisans), and local development (from Google); the Google Cloud Dataflow > service runner is not included in this proposal. Further references to > Dataflow will refer to the Dataflow model, SDKs, and runners which are a > part of this proposal (Apache Dataflow) only. The initial submission will > contain the already-released Java SDK; Google intends to submit the Python > SDK later in the incubation process. The Google Cloud Dataflow service will > continue to be one of many runners for Dataflow, built on Google Cloud > Platform, to run Dataflow pipelines. Necessarily, Cloud Dataflow will > develop against the Apache project additions, updates, and changes. Google > Cloud Dataflow will become one user of Apache Dataflow and will participate > in the project openly and publicly. > > The Dataflow programming model has been designed with simplicity, > scalability, and speed as key tenants. In the Dataflow model, you only need > to think about four top-level concepts wh
Re: [VOTE] Accept S2Graph into Apache Incubation
onboard individuals with Apache open source experience to the > > > > project. > > > > > > > > === Homogenous Developers === > > > > Most committers in this proposal belong to the same institution > > > > (Kakao). The engagement of these committers goes well beyond the > > > > necessary development to support research, and all committers work on > > > > S2Graph full time. Several people from other institutions are working > > > > on and are familiar with the S2Graph codebase. We will work to > attract > > > > them as future committers during the incubation phase, following a > > > > merit-based approach. > > > > > > > > === Reliance on Salaried Developers === > > > > Kakao invested in S2Graph as the distributed graph database solution > > > > on top of HBase and some of its key engineers are working full time > on > > > > the project. We look forward to other Apache developers and > > > > researchers contributing to the project. Also key to addressing the > > > > risk associated with relying on Salaried developers from a single > > > > entity is to increase the diversity of the contributors and actively > > > > lobby for Domain experts in the graph database space to contribute. > > > > Apache S2Graph intends to do this. > > > > > > > > === Relationships with Other Apache Products === > > > > S2Graph has a strong relationship and dependency with Apache HBase > and > > > > Apache Spark. Being part of Apache’s Incubation community, could help > > > > with a closer collaboration among these two projects and as well as > > > > others. > > > > > > > > In terms of graph processing frameworks, S2Graph and Apache Giraph > > > > look similar. However, their goals are apparently different to each > > > > other. Giraph aims at analytical batch processing on immutable graph > > > > data sets. In contrast, S2Graph is designed for OLTP-like workloads > on > > > > graph data sets, and S2Graph provides INSERT/UPDATE operations too. > > > > > > > > > > > > === An Excessive Fascination with the Apache Brand === > > > > S2Graph is proposing to enter incubation at Apache in order to help > > > > efforts to diversify the committer-base, not so much to capitalize on > > > > the Apache brand. The S2Graph project is in production use already > > > > inside Kakao, but is not expected to be a Kakao product for external > > > > customers. As such, the S2Graph project is not seeking to use the > > > > Apache brand as a marketing tool. > > > > > > > > == Documentation == > > > > Information about S2Graph can be found at > > > > https://github.com/kakao/s2graph. The following links provide more > > > > information about S2Graph in open source: > > > > * S2Graph web site: > > https://steamshon.gitbooks.io/s2graph-book/content/ > > > > * Codebase at Github: https://github.com/kakao/s2graph > > > > * Issue Tracking: https://github.com/kakao/s2graph/issues > > > > * User community: https://groups.google.com/forum/#!forum/s2graph > > > > > > > > == Initial Source == > > > > > > > > The S2Graph codebase is currently hosted on Github: > > > > https://github.com/kakao/s2graph. > > > > > > > > === Source and Intellectual Property Submission Plan === > > > > > > > > Currently, the S2Graph codebase is distributed under the Apache 2.0 > > > > License. > > > > > > > > == External Dependencies == > > > > > > > > Beyond relying on Apache HBase, S2Graph has the following external > > > > dependencies: > > > > * Asynchbase (BSD) > > > > * Play Framework (Apache 2.0 license) > > > > * Scala (http://www.scala-lang.org/license.html) > > > > * Spark (Apache 2.0 license) > > > > * Kafka (Apache 2.0 license) > > > > > > > > == Required Resources == > > > > > > > > === Mailing list === > > > > > > > > We will migrate our mailing lists to the following: > > > > * us...@s2graph.incubator.apache.org > > > > * d...@s2graph.incubator.apache.org > > > > * priv...@s2graph.incubator.apache.org > > > > * comm...@s2graph.incubator.apache.org > > > > > > > > === Source control === > > > > > > > > The S2Graph team would like to use Git for source code control, due > to > > > > our current use of Git. We request a writeable Git repo for S2Graph, > > > > and mirroring to be set up to Github through INFRA. > > > > > > > > === Issue Tracking === > > > > > > > > S2Graph currently uses the github issue tracking system associated > > > > with its github repo (https://github.com/kakao/s2graph/issues). We > > > > will migrate to the Apache JIRA > > > > (http://issues.apache.org/jira/browse/S2Graph). > > > > > > > > === Other Resources === > > > > > > > > * Jenkins/Hudson for builds and test running. > > > > * Wiki for documentation purposes. > > > > * Blog to improve project dissemination. > > > > > > > > == Initial Committers == > > > > > > > > * Doyung Yoon > > > > * Daewon Jeong > > > > * Jaesang Kim > > > > * Hwansung Yu > > > > * Min-Seok Kim > > > > * Chul Kang > > > > * Luke Han > > > > * Alexander Bezzubov > > > > > > > > == Affiliations == > > > > > > > > * Doyung Yoon, Kakao > > > > * Daewon Jeong, Kakao > > > > * Jaesang Kim, Kakao > > > > * Hwansung Yu, Kakao > > > > * Min-Seok Kim, Kakao > > > > * Chul Kang, Kakao, > > > > * Luke Han, Ebay Inc. > > > > * Alexander Bezzubov, NFLabs > > > > > > > > == Sponsors == > > > > > > > > === Champion === > > > > Hyunsik Choi > > > > > > > > === Nominated Mentors === > > > > * Andrew Purtell - Apache Member, Salesforce > > > > * Sergio Fernández - Apache Member, Redlink > > > > * Hyunsik Choi - Apache Member, Gruter Inc. > > > > * Seetharam Venkatesh - IPMC, Hortonworks Inc. > > > > > > > > === Sponsoring Entity === > > > > > > > > * The Apache Incubator > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > > > > > > > -- > > Regards, > > > > *Bin Mahone | 马洪宾* > > Apache Kylin: http://kylin.io > > Github: https://github.com/binmahone > > > -- Byung-Gon Chun
Re: [DISCUSS] S2Graph Incubator Proposal
The proposal looks interesting. I'd love to help as a mentor but I can't since I'm not an IPMC member. -Gon --- Byung-Gon Chun On Fri, Nov 13, 2015 at 1:55 PM, Atri Sharma wrote: > Really happy to see this proposal. > > I am glad to help in any way I can. > On 13 Nov 2015 10:25, "Hyunsik Choi" wrote: > > > @Sergio, > > I totally agree with you. > > > > @Luke Han, > > I put your name on the initial committer list. > > > > I'll call a vote for incubation within few days. > > > > Best regards, > > Hyunsik > > > > On Thu, Nov 12, 2015 at 12:45 AM, Luke Han wrote: > > > Hi Hyunsik, > > > I'm happy to help, GraphDB is interesting to me to analysis > > qualitative > > > data beyond quantitative data:) > > > > > > Thanks. > > > Luke > > > > > > > > > Best Regards! > > > - > > > > > > Luke Han > > > > > > On Thu, Nov 12, 2015 at 9:47 AM, Hyunsik Choi > > wrote: > > > > > >> Hi Luke, > > >> > > >> Thank you for your interest in S2Graph project. If you don't mind, > > >> we'd like to add you to the initial committer list. I think that your > > >> experience and skills about HBase would be very helpful to S2Graph > > >> project. > > >> > > >> Best regards, > > >> Hyunsik > > >> > > >> On Mon, Nov 9, 2015 at 6:58 PM, Luke Han wrote: > > >> > I'm very interesting about this project, would love to help but I'm > > not > > >> > IPMC member. > > >> > > > >> > Please let me know if there's anything I could help on. > > >> > > > >> > Thanks. > > >> > > > >> > > > >> > Best Regards! > > >> > - > > >> > > > >> > Luke Han > > >> > > > >> > On Tue, Nov 10, 2015 at 9:03 AM, Hyunsik Choi > > >> wrote: > > >> > > > >> >> Hi Seetharam, > > >> >> > > >> >> Thank you for your volunteering! I've added your name to the mentor > > >> list. > > >> >> > > >> >> I also updated the initial committer list and affiliations via > google > > >> >> search. > > >> >> If I wrote wrong affiliations, please let me know. > > >> >> > > >> >> Best regards, > > >> >> Hyunsik > > >> >> > > >> >> > > >> >> On Mon, Nov 9, 2015 at 4:21 PM, Seetharam Venkatesh > > >> >> wrote: > > >> >> > Hi Hyunsik, > > >> >> > > > >> >> > If you are still looking for mentors, let me volunteer as one. > > >> >> > > > >> >> > Thanks! > > >> >> > > > >> >> > On Mon, Nov 9, 2015 at 3:45 PM Hyunsik Choi > > >> wrote: > > >> >> > > > >> >> >> Thank you all guys I just put you names on the nominated mentor > > >> list. > > >> >> >> > > >> >> >> @Andrew, > > >> >> >> > > >> >> >> I agree with you. S2Graph already has good relationships with > > other > > >> >> >> ASF projects, such as HBase and Spark, In addition, they have a > > plan > > >> >> >> to expand its relationship to Apache incubator TinkerPop, which > > is a > > >> >> >> graph computing framework. I'm looking forward to their > > combinations. > > >> >> >> > > >> >> >> @Sergio, > > >> >> >> > > >> >> >> Thank you for attending the talk and joining the S2Graph > mentors. > > >> That > > >> >> >> was Doyung Yoon, one of the S2Graph creators. He had a talk at > the > > >> >> >> last ApacheCon. > > >> >> >> > > >> >> >> On Mon, Nov 9, 2015 at 11:58 AM, Sergio Fernández < > > wik...@apache.org > > >> > > > >> >> >> wrote: > > >> >> >> > Hi Hyunsik, I attended your talk at the last ApacheCon, and I > > >> think S2 > > >> >>
[RESULT] [VOTE] Release Apache REEF 0.10.0-incubating
The release vote passes with 3 +1 binding votes from Justin, Alan, and Chris and no -1 vote. We already addressed the comments about DISCLAIMER and NOTICE in our master branch for our next release. Thanks to everyone involved in making this release happen! On Thu, Jan 15, 2015 at 8:53 AM, Chris Douglas wrote: > +1 > > Checksum and signature match, RAT OK, source tarball builds cleanly. > LICENSE/NOTICE lgtm, and I agree with Marvin w.r.t. the missing > DISCLAIMER (can be fixed in subsequent releases). -C > > On Sat, Jan 10, 2015 at 7:14 PM, Byung-Gon Chun wrote: > > The Apache REEF PPMC has voted to release Apache REEF 0.10.0-incubating > > based on the release candidate described below. Now it is the IPMC's turn > > to vote. > > > > Here's the PPMC voting result (five binding +1 votes): > > > http://mail-archives.apache.org/mod_mbox/incubator-reef-dev/201501.mbox/%3CCADq0cj7YNbVLYX5dUZtd0U4Cafi%3DDRB-%3DfxoiufHSOHcBdzCDQ%40mail.gmail.com%3E > > > > The source tarball, including signatures, digests, etc can be found at: > > http://people.apache.org/~bgchun/apache-reef-0.10.0-incubating-rc1/ > > > > The Git tag is release-0.10.0-incubating-rc1 > > The Git commit ID is 76147ea7a4a7b6114bee9d1b8b4d1d588b4f0ce2 > > > https://git-wip-us.apache.org/repos/asf?p=incubator-reef.git;a=commit;h=76147ea7a4a7b6114bee9d1b8b4d1d588b4f0ce2 > > > > Checksums of apache-reef-0.10.0-incubating-rc1.tar.gz: > > MD5: e112edbfe15a67710ad697ab529c4816 > > SHA1: 654dc4b7a386ed17e1a8084aa45682ac6c17f159 > > SHA512: > > > a92a9f6eb4c6c25a3a83843bcd39da462107a10d573705e977744afa498a25a8e0c508d97480661b5ddb5724edc39ea4c84c555c2154c323acd25d74f36bcb51 > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/bgchun.asc > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/incubator/reef/KEYS > > > > Test binaries have been published to Maven's staging repository, and > > are available here: > > https://repository.apache.org/content/repositories/orgapachereef-1000 > > > > 41 issues were closed/resolved for this release: > > > https://issues.apache.org/jira/browse/REEF-84?jql=project%20%3D%20REEF%20AND%20(status%3Dclosed%20OR%20status%3Dresolved) > > > > The vote will be open for 72 hours. > > > > [ ] +1 Release this package as Apache REEF 0.10.0-incubating > > [ ] +0 no opinion > > [ ] -1 Do not release this package because ... > > > > > > Thanks, > > Gon > > > > -- > > Byung-Gon Chun > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: [VOTE] Release Apache REEF 0.10.0-incubating
Dear IPMC members, We have received 2 +1 binding votes so far. We'd really appreciate it if some of you can check the release and cast a vote for us to make progress. Please first check my response to Alan's email in case you have questions on the release. Thanks! - Gon On Mon, Jan 12, 2015 at 2:38 PM, Byung-Gon Chun wrote: > Hi Alan, > > Thank you for your comments. > > I mistakenly copied and pasted digest values in my email. :( > > My further comments are inlined. > > On Mon, Jan 12, 2015 at 2:02 PM, Alan D. Cabrera > wrote: > >> >> > On Jan 10, 2015, at 7:14 PM, Byung-Gon Chun wrote: >> > >> > The Apache REEF PPMC has voted to release Apache REEF 0.10.0-incubating >> > based on the release candidate described below. Now it is the IPMC's >> turn >> > to vote. >> > >> > Here's the PPMC voting result (five binding +1 votes): >> > >> http://mail-archives.apache.org/mod_mbox/incubator-reef-dev/201501.mbox/%3CCADq0cj7YNbVLYX5dUZtd0U4Cafi%3DDRB-%3DfxoiufHSOHcBdzCDQ%40mail.gmail.com%3E >> > >> > The source tarball, including signatures, digests, etc can be found at: >> > http://people.apache.org/~bgchun/apache-reef-0.10.0-incubating-rc1/ < >> http://people.apache.org/~bgchun/apache-reef-0.10.0-incubating-rc1/> >> >> The source does not build unless you have protobufs installed. Not a big >> deal but something you may want to add this fact to your README.md for the >> next subsequent release. >> >> Source builds and tests fine after protobufs is installed. >> >> > Thanks for catching it. We will add this fact for the next release. > > >> mvn rat:check does not pass but they are just false positives; the PPMC >> vote thread seems to say that it passes. Not a big deal. >> >> > PPMC members did not have this problem. > > >> > The Git tag is release-0.10.0-incubating-rc1 >> > The Git commit ID is 76147ea7a4a7b6114bee9d1b8b4d1d588b4f0ce2 >> > >> https://git-wip-us.apache.org/repos/asf?p=incubator-reef.git;a=commit;h=76147ea7a4a7b6114bee9d1b8b4d1d588b4f0ce2 >> > >> > Checksums of apache-reef-0.10.0-incubating-rc1.tar.gz: >> > MD5: e112edbfe15a67710ad697ab529c4816 >> > SHA1: 654dc4b7a386ed17e1a8084aa45682ac6c17f159 >> > SHA512: >> > >> a92a9f6eb4c6c25a3a83843bcd39da462107a10d573705e977744afa498a25a8e0c508d97480661b5ddb5724edc39ea4c84c555c2154c323acd25d74f36bcb51 >> >> My checksums don’t match what’s in this email, nor the email in the PPMC >> vote, but they do match what’s in >> >> http://people.apache.org/~bgchun/apache-reef-0.10.0-incubating-rc1 < >> http://people.apache.org/~bgchun/apache-reef-0.10.0-incubating-rc1> >> >> MD5: fa0de47ab4916a950a077d253a9be783 >> SHA1: 3b5abfb3447ac9787014211e736be10aa3219d1c >> SHA512: >> 25a913a5f6ce1e76c145fbf703e49b1716669df7876bead9a025e9d9e26a745ef47ec9d8b2eae072829215017a6c3cc4d8126160e0b7c63613b83989253af03b >> >> IMO, the above public declaration is good enough though others >> participates of this vote, and PPMC vote, will probably have to re-confirm >> the checksums that they actually voted on. >> > > I mistakenly copied and pasted digest values from my prior email. > As you mentioned, digests under > http://people.apache.org/~bgchun/apache-reef-0.10.0-incubating-rc1 are > correct ones. > > Thanks! > -Gon > > >> >> > Release artifacts are signed with the following key: >> > https://people.apache.org/keys/committer/bgchun.asc >> > >> > KEYS file available here: >> > https://dist.apache.org/repos/dist/release/incubator/reef/KEYS >> > >> > Test binaries have been published to Maven's staging repository, and >> > are available here: >> > https://repository.apache.org/content/repositories/orgapachereef-1000 < >> https://repository.apache.org/content/repositories/orgapachereef-1000> >> >> Signatures verified. >> >> > 41 issues were closed/resolved for this release: >> > >> https://issues.apache.org/jira/browse/REEF-84?jql=project%20%3D%20REEF%20AND%20(status%3Dclosed%20OR%20status%3Dresolved) >> > >> > The vote will be open for 72 hours. >> > >> > [ ] +1 Release this package as Apache REEF 0.10.0-incubating >> > [ ] +0 no opinion >> > [ ] -1 Do not release this package because … >> >> >> +1 - binding >> >> >> Regards, >> Alan >> >> > > > -- > Byung-Gon Chun > -- Byung-Gon Chun
Re: [VOTE] Release Apache REEF 0.10.0-incubating
Hi Alan, Thank you for your comments. I mistakenly copied and pasted digest values in my email. :( My further comments are inlined. On Mon, Jan 12, 2015 at 2:02 PM, Alan D. Cabrera wrote: > > > On Jan 10, 2015, at 7:14 PM, Byung-Gon Chun wrote: > > > > The Apache REEF PPMC has voted to release Apache REEF 0.10.0-incubating > > based on the release candidate described below. Now it is the IPMC's turn > > to vote. > > > > Here's the PPMC voting result (five binding +1 votes): > > > http://mail-archives.apache.org/mod_mbox/incubator-reef-dev/201501.mbox/%3CCADq0cj7YNbVLYX5dUZtd0U4Cafi%3DDRB-%3DfxoiufHSOHcBdzCDQ%40mail.gmail.com%3E > > > > The source tarball, including signatures, digests, etc can be found at: > > http://people.apache.org/~bgchun/apache-reef-0.10.0-incubating-rc1/ < > http://people.apache.org/~bgchun/apache-reef-0.10.0-incubating-rc1/> > > The source does not build unless you have protobufs installed. Not a big > deal but something you may want to add this fact to your README.md for the > next subsequent release. > > Source builds and tests fine after protobufs is installed. > > Thanks for catching it. We will add this fact for the next release. > mvn rat:check does not pass but they are just false positives; the PPMC > vote thread seems to say that it passes. Not a big deal. > > PPMC members did not have this problem. > > The Git tag is release-0.10.0-incubating-rc1 > > The Git commit ID is 76147ea7a4a7b6114bee9d1b8b4d1d588b4f0ce2 > > > https://git-wip-us.apache.org/repos/asf?p=incubator-reef.git;a=commit;h=76147ea7a4a7b6114bee9d1b8b4d1d588b4f0ce2 > > > > Checksums of apache-reef-0.10.0-incubating-rc1.tar.gz: > > MD5: e112edbfe15a67710ad697ab529c4816 > > SHA1: 654dc4b7a386ed17e1a8084aa45682ac6c17f159 > > SHA512: > > > a92a9f6eb4c6c25a3a83843bcd39da462107a10d573705e977744afa498a25a8e0c508d97480661b5ddb5724edc39ea4c84c555c2154c323acd25d74f36bcb51 > > My checksums don’t match what’s in this email, nor the email in the PPMC > vote, but they do match what’s in > > http://people.apache.org/~bgchun/apache-reef-0.10.0-incubating-rc1 < > http://people.apache.org/~bgchun/apache-reef-0.10.0-incubating-rc1> > > MD5: fa0de47ab4916a950a077d253a9be783 > SHA1: 3b5abfb3447ac9787014211e736be10aa3219d1c > SHA512: > 25a913a5f6ce1e76c145fbf703e49b1716669df7876bead9a025e9d9e26a745ef47ec9d8b2eae072829215017a6c3cc4d8126160e0b7c63613b83989253af03b > > IMO, the above public declaration is good enough though others > participates of this vote, and PPMC vote, will probably have to re-confirm > the checksums that they actually voted on. > I mistakenly copied and pasted digest values from my prior email. As you mentioned, digests under http://people.apache.org/~bgchun/apache-reef-0.10.0-incubating-rc1 are correct ones. Thanks! -Gon > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/bgchun.asc > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/incubator/reef/KEYS > > > > Test binaries have been published to Maven's staging repository, and > > are available here: > > https://repository.apache.org/content/repositories/orgapachereef-1000 < > https://repository.apache.org/content/repositories/orgapachereef-1000> > > Signatures verified. > > > 41 issues were closed/resolved for this release: > > > https://issues.apache.org/jira/browse/REEF-84?jql=project%20%3D%20REEF%20AND%20(status%3Dclosed%20OR%20status%3Dresolved) > > > > The vote will be open for 72 hours. > > > > [ ] +1 Release this package as Apache REEF 0.10.0-incubating > > [ ] +0 no opinion > > [ ] -1 Do not release this package because … > > > +1 - binding > > > Regards, > Alan > > -- Byung-Gon Chun
Re: [VOTE] Release Apache REEF 0.10.0-incubating
Hi Justin, I will wait. Thanks! -Gon On Mon, Jan 12, 2015 at 11:46 AM, Justin Mclean wrote: > HI, > > > I will add the DISCLAIMER, update the year in the NOTICE file, and delete > > the HEADER file. I will create a new RC and restart the vote. > > You may want to wait a little until other IPMC members reply, if other > people are fine with it and you fix it for the next release I'm happy to > vote +1. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: [VOTE] Release Apache REEF 0.10.0-incubating
Hi Justin, Thank you for the feedback. I will add the DISCLAIMER, update the year in the NOTICE file, and delete the HEADER file. I will create a new RC and restart the vote. I cced dev@reef. Thanks. -Gon On Sun, Jan 11, 2015 at 1:57 PM, Justin Mclean wrote: > Hi, > > The release is missing DISCLAIMER file [1][2] While the web site does > contain the incubating disclaimer and README mentions incubation it's > missing the full text so that needs to be fixed for the next release and > probably this one. What do other IPMC members think? > > Everything else looks good. Checked: > - incubating in release name > - signature and hash good > - LICENSE and NOTICE good > - no binary files in source (except 2 test files) > - all source files have correct headers > - can compile from source > > Other minor things: > - no need for HEADER file > - year in NOTICE is wrong (but oddly is correct in jars) > - place the RC in incubator area not on peopel.apache.org [3] > > Thanks, > Justin > > 1.http://incubator.apache.org/guides/releasemanagement.html#check-list > 2.http://incubator.apache.org/guides/branding.html#disclaimers > 3. > http://incubator.apache.org/guides/releasemanagement.html#glossary-podling-dist > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
[VOTE] Release Apache REEF 0.10.0-incubating
The Apache REEF PPMC has voted to release Apache REEF 0.10.0-incubating based on the release candidate described below. Now it is the IPMC's turn to vote. Here's the PPMC voting result (five binding +1 votes): http://mail-archives.apache.org/mod_mbox/incubator-reef-dev/201501.mbox/%3CCADq0cj7YNbVLYX5dUZtd0U4Cafi%3DDRB-%3DfxoiufHSOHcBdzCDQ%40mail.gmail.com%3E The source tarball, including signatures, digests, etc can be found at: http://people.apache.org/~bgchun/apache-reef-0.10.0-incubating-rc1/ The Git tag is release-0.10.0-incubating-rc1 The Git commit ID is 76147ea7a4a7b6114bee9d1b8b4d1d588b4f0ce2 https://git-wip-us.apache.org/repos/asf?p=incubator-reef.git;a=commit;h=76147ea7a4a7b6114bee9d1b8b4d1d588b4f0ce2 Checksums of apache-reef-0.10.0-incubating-rc1.tar.gz: MD5: e112edbfe15a67710ad697ab529c4816 SHA1: 654dc4b7a386ed17e1a8084aa45682ac6c17f159 SHA512: a92a9f6eb4c6c25a3a83843bcd39da462107a10d573705e977744afa498a25a8e0c508d97480661b5ddb5724edc39ea4c84c555c2154c323acd25d74f36bcb51 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/bgchun.asc KEYS file available here: https://dist.apache.org/repos/dist/release/incubator/reef/KEYS Test binaries have been published to Maven's staging repository, and are available here: https://repository.apache.org/content/repositories/orgapachereef-1000 41 issues were closed/resolved for this release: https://issues.apache.org/jira/browse/REEF-84?jql=project%20%3D%20REEF%20AND%20(status%3Dclosed%20OR%20status%3Dresolved) The vote will be open for 72 hours. [ ] +1 Release this package as Apache REEF 0.10.0-incubating [ ] +0 no opinion [ ] -1 Do not release this package because ... Thanks, Gon -- Byung-Gon Chun
[RESULT] [VOTE] Accept REEF into the Apache Incubator
Thanks everyone who voted! The vote has passed with 13 binding +1 votes and 2 non-binding +1 votes and no +0 or -1 votes. Binding (+1) Ross Gardler Till Westmann Alan D. Cabrera Konstantin Boudnik Bertrand Delacretaz Jakob Glen Homan Chris A Mattmann Andrew Purtell Owen O'Malley Jake Farrell Suresh Srinivas Roman Shaposhnik Chris Douglas Non-binding (+1) Hitesh Shah Jan Iversen We will follow the next steps under the guidance of our mentors. Thanks! - Gon --- Byung-Gon Chun On Sat, Aug 9, 2014 at 2:40 PM, Byung-Gon Chun wrote: > Hi, > > Thanks for participating in the proposal discussion on REEF. The > discussion has calmed. I would like to call a vote for acceptance of REEF > into the Apache Incubator. > > The proposal is attached below, and it is also available at > https://wiki.apache.org/incubator/ReefProposal > > Let's keep this vote open for three business days, closing the voting on > August 11, 11:59PM (PDT). > > [] +1 Accept REEF into the Incubator > [] 0 Don't care > [] -1 Don't accept REEF because... > > Thanks! > -Gon > > -- > Byung-Gon Chun > > > # REEFProposal - Incubator > > > # Abstract > > REEF (Retainable Evaluator Execution Framework) is a scale-out > computing fabric that eases the development of Big Data applications > on top of resource managers such as Apache YARN and Mesos. > > > # Proposal > > REEF is a Big Data system that makes it easy to implement scalable, > fault-tolerant runtime environments for a range of data processing > models (e.g., graph processing and machine learning) on top of > resource managers such as Apache YARN and Mesos. REEF provides > capabilities to run multiple heterogeneous frameworks and workflows of > those efficiently. > > Additionally, REEF contains two libraries that are of independent > value: Wake is an event-based-programming framework inspired by Rx and > SEDA. Tang is a dependency injection framework inspired by Google > Guice, but designed specifically for configuring distributed systems. > > > # Background > > The resource management layer such as Apache YARN and Mesos has > emerged as a critical layer in the new scale-out data processing > stack; resource managers assume the responsibility of multiplexing a > cluster of shared-nothing machines across heterogeneous > applications. They operate behind an interface for leasing containers > - a slice of a machine’s resources - to computations in an elastic > fashion. However, building data processing frameworks directly on this > layer comes at a high cost: each framework must tackle the same > challenges (e.g., fault-tolerance, task scheduling and coordination) > and reimplement common mechanisms (e.g., caching, bulk transfers). > > REEF provides a reusable control-plane for scheduling and coordinating > task-level work on cluster resource managers. The REEF design enables > sophisticated optimizations, such as container re-use and data > caching, and facilitates workflows that span multiple > frameworks. Examples include pipelining data between different > operators in a relational system, retaining state across iterations in > iterative or recursive data flow, and passing the result of a > MapReduce job to a Machine Learning computation. > > > # Rationale > > Since REEF is a library that makes it easy to write distributed > applications on top of Apache YARN or Mesos, the Apache Software > Foundation > is the perfect home for hosting REEF. > > > # Current Status > > REEF has been developed mostly by Microsoft, UCLA and the Seoul > National University. The REEF codebase is open-sourced under Apache > License 2.0 and is currently hosted in a public repository at > github.com. > > > # Meritocracy > > We plan to build a strong open community by following the Apache > meritocracy principles. We will work with those who contribute > significantly to the project and invite them to be its committers. > > > # Community > > REEF is currently being used internally at Microsoft. Also, SK > Telecom builds their data analytics infrastructure on top of REEF in > collaboration with Seoul National University. We hope to extend our > contributor base by becoming an Apache incubator project. REEF will > attract developers who are interested in creating common building > blocks for simplifying the development of large-scale big data > applications. > > > # Core Developers > > Core developers are engineers from Microsoft, Purestorage, UCB, UCLA, > UW and Seoul National University. > > > # Alignment > > REEF depends on many Apache projects and dependencies. REEF is built > on resource managers such as Apache YARN and Apache Mesos. REEF also
[VOTE] Accept REEF into the Apache Incubator
Hi, Thanks for participating in the proposal discussion on REEF. The discussion has calmed. I would like to call a vote for acceptance of REEF into the Apache Incubator. The proposal is attached below, and it is also available at https://wiki.apache.org/incubator/ReefProposal Let's keep this vote open for three business days, closing the voting on August 11, 11:59PM (PDT). [] +1 Accept REEF into the Incubator [] 0 Don't care [] -1 Don't accept REEF because... Thanks! -Gon -- Byung-Gon Chun # REEFProposal - Incubator # Abstract REEF (Retainable Evaluator Execution Framework) is a scale-out computing fabric that eases the development of Big Data applications on top of resource managers such as Apache YARN and Mesos. # Proposal REEF is a Big Data system that makes it easy to implement scalable, fault-tolerant runtime environments for a range of data processing models (e.g., graph processing and machine learning) on top of resource managers such as Apache YARN and Mesos. REEF provides capabilities to run multiple heterogeneous frameworks and workflows of those efficiently. Additionally, REEF contains two libraries that are of independent value: Wake is an event-based-programming framework inspired by Rx and SEDA. Tang is a dependency injection framework inspired by Google Guice, but designed specifically for configuring distributed systems. # Background The resource management layer such as Apache YARN and Mesos has emerged as a critical layer in the new scale-out data processing stack; resource managers assume the responsibility of multiplexing a cluster of shared-nothing machines across heterogeneous applications. They operate behind an interface for leasing containers - a slice of a machine’s resources - to computations in an elastic fashion. However, building data processing frameworks directly on this layer comes at a high cost: each framework must tackle the same challenges (e.g., fault-tolerance, task scheduling and coordination) and reimplement common mechanisms (e.g., caching, bulk transfers). REEF provides a reusable control-plane for scheduling and coordinating task-level work on cluster resource managers. The REEF design enables sophisticated optimizations, such as container re-use and data caching, and facilitates workflows that span multiple frameworks. Examples include pipelining data between different operators in a relational system, retaining state across iterations in iterative or recursive data flow, and passing the result of a MapReduce job to a Machine Learning computation. # Rationale Since REEF is a library that makes it easy to write distributed applications on top of Apache YARN or Mesos, the Apache Software Foundation is the perfect home for hosting REEF. # Current Status REEF has been developed mostly by Microsoft, UCLA and the Seoul National University. The REEF codebase is open-sourced under Apache License 2.0 and is currently hosted in a public repository at github.com. # Meritocracy We plan to build a strong open community by following the Apache meritocracy principles. We will work with those who contribute significantly to the project and invite them to be its committers. # Community REEF is currently being used internally at Microsoft. Also, SK Telecom builds their data analytics infrastructure on top of REEF in collaboration with Seoul National University. We hope to extend our contributor base by becoming an Apache incubator project. REEF will attract developers who are interested in creating common building blocks for simplifying the development of large-scale big data applications. # Core Developers Core developers are engineers from Microsoft, Purestorage, UCB, UCLA, UW and Seoul National University. # Alignment REEF depends on many Apache projects and dependencies. REEF is built on resource managers such as Apache YARN and Apache Mesos. REEF also uses HDFS as a distributed storage layer. # Known Risks ## Orphaned Products The risk of REEF being orphaned is small because Microsoft products are built on REEF. The core REEF developers continue to work on REEF at Microsoft, UCLA, and Seoul National University. The REEF project is gaining interest from other institutions to be used as their infrastructure. ## Inexperience with Open Source Several core developers have experience with open source development. REEF committers will be guided by the mentors with strong Apache open source project backgrounds. ## Homogeneous Developers The initial committers include developers from several institutions including Microsoft, Purestorage, UCB, UCLA, and Seoul National University. ## Reliance on Salaried Developers Developers from Microsoft are paid to work on REEF. Since the work is used internally at Microsoft, Microsoft will keep supporting the developers to work on REEF. There are also engineers and graduate students that contribute to REEF from UCLA, UCB, UW and Seoul National University. We plan to attract ac
Re: [PROPOSAL] REEF for the Apache Incubator
Hi Roman, I will send an email to start a vote soon. Thanks! -Gon On Sat, Aug 9, 2014 at 8:32 AM, Roman Shaposhnik wrote: > Looks like the feedback has been well received. > > Any reason not to start a vote? > > Thanks, > Roman. > > On Mon, Aug 4, 2014 at 11:12 PM, Byung-Gon Chun wrote: > > Hi Jake, > > > > Thank you for the comment. > > > > We had discussions on how to structure mailing lists with our mentors. > > We took our mentors' suggestions to start with a minimal set (two mailing > > lists) not to miss important discussions and to split them if there are > > demands. > > > > Thanks! > > -Gon > > > > --- > > Byung-Gon Chun > > > > > > > > > > > > > > On Tue, Aug 5, 2014 at 3:04 AM, Jake Farrell > wrote: > > > >> Would suggest you use the following format for the mailing lists (you > have > >> the older format listed) and also split the dev and commits. Also a lot > of > >> new projects have been also splitting out the jira issues from dev to > cut > >> down on noise on the dev list, would add issues@reef if you want to do > >> this. > >> > >> private@reef for private PMC discussions > >> dev@reef for technical discussions > >> commits@reef notification about commits > >> issues@reef jira notifications > >> > >> -Jake > >> > >> > >> > >> On Fri, Aug 1, 2014 at 3:14 AM, Byung-Gon Chun > wrote: > >> > >> > Hi everyone, > >> > > >> > I would like to propose REEF to be an Apache Incubator project. REEF > is a > >> > scale-out computing fabric that eases the development of Big Data > >> > applications on top of resource managers such as Apache YARN and > Mesos. > >> > > >> > The proposal is included in plain text below. I would also like to put > >> this > >> > on wiki but I don't have privileges to create wiki pages. > >> > > >> > I look forward to hearing everyone's thoughts and feedback! > >> > > >> > -Gon > >> > > >> > -- > >> > Byung-Gon Chun > >> > > >> > > >> > === > >> > > >> > # REEFProposal - Incubator > >> > > >> > > >> > # Abstract > >> > > >> > REEF (Retainable Evaluator Execution Framework) is a scale-out > >> > computing fabric that eases the development of Big Data applications > >> > on top of resource managers such as Apache YARN and Mesos. > >> > > >> > > >> > # Proposal > >> > > >> > REEF is a Big Data system that makes it easy to implement scalable, > >> > fault-tolerant runtime environments for a range of data processing > >> > models (e.g., graph processing and machine learning) on top of > >> > resource managers such as Apache YARN and Mesos. REEF provides > >> > capabilities to run multiple heterogeneous frameworks and workflows of > >> > those efficiently. > >> > > >> > Additionally, REEF contains two libraries that are of independent > >> > value: Wake is an event-based-programming framework inspired by Rx and > >> > SEDA. Tang is a dependency injection framework inspired by Google > >> > Guice, but designed specifically for configuring distributed systems. > >> > > >> > > >> > # Background > >> > > >> > The resource management layer such as Apache YARN and Mesos has > >> > emerged as a critical layer in the new scale-out data processing > >> > stack; resource managers assume the responsibility of multiplexing a > >> > cluster of shared-nothing machines across heterogeneous > >> > applications. They operate behind an interface for leasing containers > >> > - a slice of a machine’s resources - to computations in an elastic > >> > fashion. However, building data processing frameworks directly on this > >> > layer comes at a high cost: each framework must tackle the same > >> > challenges (e.g., fault-tolerance, task scheduling and coordination) > >> > and reimplement common mechanisms (e.g., caching, bulk transfers). > >> > > >> > REEF provides a reusable control-plane for scheduling and coordinating > >> > task-level work on cluster resource managers. The REEF design enables > >> > sophisticated optimizations, s
Re: Wiki access
Thanks, Nick! On Tue, Aug 5, 2014 at 5:59 PM, Nick Burch wrote: > On Tue, 5 Aug 2014, Byung-Gon Chun wrote: > >> I don't have write access to the wiki page: >> https://wiki.apache.org/incubator/ReefProposal. >> Could someone give me permission to update the page? >> >> My user name is "Byung-Gon Chun". >> > > Karma granted > > Nick > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: [PROPOSAL] REEF for the Apache Incubator
Hi Jake, Thank you for the comment. We had discussions on how to structure mailing lists with our mentors. We took our mentors' suggestions to start with a minimal set (two mailing lists) not to miss important discussions and to split them if there are demands. Thanks! -Gon --- Byung-Gon Chun On Tue, Aug 5, 2014 at 3:04 AM, Jake Farrell wrote: > Would suggest you use the following format for the mailing lists (you have > the older format listed) and also split the dev and commits. Also a lot of > new projects have been also splitting out the jira issues from dev to cut > down on noise on the dev list, would add issues@reef if you want to do > this. > > private@reef for private PMC discussions > dev@reef for technical discussions > commits@reef notification about commits > issues@reef jira notifications > > -Jake > > > > On Fri, Aug 1, 2014 at 3:14 AM, Byung-Gon Chun wrote: > > > Hi everyone, > > > > I would like to propose REEF to be an Apache Incubator project. REEF is a > > scale-out computing fabric that eases the development of Big Data > > applications on top of resource managers such as Apache YARN and Mesos. > > > > The proposal is included in plain text below. I would also like to put > this > > on wiki but I don't have privileges to create wiki pages. > > > > I look forward to hearing everyone's thoughts and feedback! > > > > -Gon > > > > -- > > Byung-Gon Chun > > > > > > === > > > > # REEFProposal - Incubator > > > > > > # Abstract > > > > REEF (Retainable Evaluator Execution Framework) is a scale-out > > computing fabric that eases the development of Big Data applications > > on top of resource managers such as Apache YARN and Mesos. > > > > > > # Proposal > > > > REEF is a Big Data system that makes it easy to implement scalable, > > fault-tolerant runtime environments for a range of data processing > > models (e.g., graph processing and machine learning) on top of > > resource managers such as Apache YARN and Mesos. REEF provides > > capabilities to run multiple heterogeneous frameworks and workflows of > > those efficiently. > > > > Additionally, REEF contains two libraries that are of independent > > value: Wake is an event-based-programming framework inspired by Rx and > > SEDA. Tang is a dependency injection framework inspired by Google > > Guice, but designed specifically for configuring distributed systems. > > > > > > # Background > > > > The resource management layer such as Apache YARN and Mesos has > > emerged as a critical layer in the new scale-out data processing > > stack; resource managers assume the responsibility of multiplexing a > > cluster of shared-nothing machines across heterogeneous > > applications. They operate behind an interface for leasing containers > > - a slice of a machine’s resources - to computations in an elastic > > fashion. However, building data processing frameworks directly on this > > layer comes at a high cost: each framework must tackle the same > > challenges (e.g., fault-tolerance, task scheduling and coordination) > > and reimplement common mechanisms (e.g., caching, bulk transfers). > > > > REEF provides a reusable control-plane for scheduling and coordinating > > task-level work on cluster resource managers. The REEF design enables > > sophisticated optimizations, such as container re-use and data > > caching, and facilitates workflows that span multiple > > frameworks. Examples include pipelining data between different > > operators in a relational system, retaining state across iterations in > > iterative or recursive data flow, and passing the result of a > > MapReduce job to a Machine Learning computation. > > > > > > # Rationale > > > > Since REEF is a library that makes it easy to write distributed > > applications on top of Apache YARN or Mesos, the Apache Software > Foundation > > is the perfect home for hosting REEF. > > > > > > # Current Status > > > > REEF has been developed mostly by Microsoft, UCLA and the Seoul > > National University. The REEF codebase is open-sourced under Apache > > License 2.0 and is currently hosted in a public repository at > > github.com. > > > > > > # Meritocracy > > > > We plan to build a strong open community by following the Apache > > meritocracy principles. We will work with those who contribute > > significantly to the project and invite them to be its committers. > > > >
Re: [PROPOSAL] REEF for the Apache Incubator
Hi Roman, Thank you for the comment. We will add the following description that covers Helix to the proposal page. Apache Helix automates application-wide management operations which require global knowledge and coordination, such as repartitioning of resources and scheduling of maintenance tasks. Helix separates global coordination concerns from the functional tasks of the application with a state machine abstraction. REEF's generic layer makes it easy to program the functional and management tasks, which may span small or large groups within the application. Helix can work hand-in-hand with REEF, by providing the global management component for REEF applications. Thanks! - Gon --- Byung-Gon Chun On Tue, Aug 5, 2014 at 1:59 AM, Roman Shaposhnik wrote: > Hi! > > On Fri, Aug 1, 2014 at 12:14 AM, Byung-Gon Chun wrote: > > Since REEF is a library that makes it easy to write distributed > > applications on top of Apache YARN or Mesos, the Apache Software > Foundation > > is the perfect home for hosting REEF. > > [ snip...snip...snip ] > > > ## Relationships with Other Apache Products > > Really appreciated the detailed review of potential relationships, > but was surprised not to see Apache Helix on the list of related > projects. > > Given the exec summary of the project -- there must be some > relationship. Or am I reading it incorrectly? > > Thanks, > Roman. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Byung-Gon Chun
Re: Wiki access
Hi again, I don't have write access to the wiki page: https://wiki.apache.org/incubator/ReefProposal. Could someone give me permission to update the page? Thanks. -Gon On Sat, Aug 2, 2014 at 10:43 AM, Byung-Gon Chun wrote: > Hello, > > Can I have access to the incubator wiki? I'd like to post the REEF > proposal on the wiki. My user name is "Byung-Gon Chun". > > Thanks! > - Gon > > -- > Byung-Gon Chun > -- Byung-Gon Chun
Re: [PROPOSAL] REEF for the Apache Incubator
John, Thank you for the feedback and the offer to help! On the mentors, I think that four mentors (including Chris Douglas) can cover REEF at this point. Thanks! -Gon --- Byung-Gon Chun On Sat, Aug 2, 2014 at 10:12 PM, John D. Ament wrote: > Byung-Gon > > It looks like a good proposal. There are some minor edit I'd recommend > you'd do: > > - Use the same github URL consistently. > - I just fixed the section of the proposal guide to include how to > reference a git repository. This should help you and future proposed > podlings get things going better. > > If you like - you already have 3 mentors, I'd be willing to step up and > help mentor REEF as well. > > John > > > > On Fri, Aug 1, 2014 at 3:14 AM, Byung-Gon Chun wrote: > > > Hi everyone, > > > > I would like to propose REEF to be an Apache Incubator project. REEF is a > > scale-out computing fabric that eases the development of Big Data > > applications on top of resource managers such as Apache YARN and Mesos. > > > > The proposal is included in plain text below. I would also like to put > this > > on wiki but I don't have privileges to create wiki pages. > > > > I look forward to hearing everyone's thoughts and feedback! > > > > -Gon > > > > -- > > Byung-Gon Chun > > > > > > === > > > > # REEFProposal - Incubator > > > > > > # Abstract > > > > REEF (Retainable Evaluator Execution Framework) is a scale-out > > computing fabric that eases the development of Big Data applications > > on top of resource managers such as Apache YARN and Mesos. > > > > > > # Proposal > > > > REEF is a Big Data system that makes it easy to implement scalable, > > fault-tolerant runtime environments for a range of data processing > > models (e.g., graph processing and machine learning) on top of > > resource managers such as Apache YARN and Mesos. REEF provides > > capabilities to run multiple heterogeneous frameworks and workflows of > > those efficiently. > > > > Additionally, REEF contains two libraries that are of independent > > value: Wake is an event-based-programming framework inspired by Rx and > > SEDA. Tang is a dependency injection framework inspired by Google > > Guice, but designed specifically for configuring distributed systems. > > > > > > # Background > > > > The resource management layer such as Apache YARN and Mesos has > > emerged as a critical layer in the new scale-out data processing > > stack; resource managers assume the responsibility of multiplexing a > > cluster of shared-nothing machines across heterogeneous > > applications. They operate behind an interface for leasing containers > > - a slice of a machine’s resources - to computations in an elastic > > fashion. However, building data processing frameworks directly on this > > layer comes at a high cost: each framework must tackle the same > > challenges (e.g., fault-tolerance, task scheduling and coordination) > > and reimplement common mechanisms (e.g., caching, bulk transfers). > > > > REEF provides a reusable control-plane for scheduling and coordinating > > task-level work on cluster resource managers. The REEF design enables > > sophisticated optimizations, such as container re-use and data > > caching, and facilitates workflows that span multiple > > frameworks. Examples include pipelining data between different > > operators in a relational system, retaining state across iterations in > > iterative or recursive data flow, and passing the result of a > > MapReduce job to a Machine Learning computation. > > > > > > # Rationale > > > > Since REEF is a library that makes it easy to write distributed > > applications on top of Apache YARN or Mesos, the Apache Software > Foundation > > is the perfect home for hosting REEF. > > > > > > # Current Status > > > > REEF has been developed mostly by Microsoft, UCLA and the Seoul > > National University. The REEF codebase is open-sourced under Apache > > License 2.0 and is currently hosted in a public repository at > > github.com. > > > > > > # Meritocracy > > > > We plan to build a strong open community by following the Apache > > meritocracy principles. We will work with those who contribute > > significantly to the project and invite them to be its committers. > > > > > > # Community > > > > REEF is currently being used internally at Microsoft. Also, SK > > Telecom builds their data analytics i
Re: [PROPOSAL] REEF for the Apache Incubator
Thank you! --- Byung-Gon Chun Sent from my phone 2014. 8. 2. 오전 11:08 작성: > I added the proposal to the Wiki at > http://wiki.apache.org/incubator/ReefProposal > > > > > > > Sent from Windows Mail > > > > > > From: bgc...@gmail.com > Sent: Friday, August 1, 2014 12:14 AM > To: general@incubator.apache.org > > > > > > Hi everyone, > > I would like to propose REEF to be an Apache Incubator project. REEF is a > scale-out computing fabric that eases the development of Big Data > applications on top of resource managers such as Apache YARN and Mesos. > > The proposal is included in plain text below. I would also like to put this > on wiki but I don't have privileges to create wiki pages. > > I look forward to hearing everyone's thoughts and feedback! > > -Gon > > -- > Byung-Gon Chun > > > === > > # REEFProposal - Incubator > > > # Abstract > > REEF (Retainable Evaluator Execution Framework) is a scale-out > computing fabric that eases the development of Big Data applications > on top of resource managers such as Apache YARN and Mesos. > > > # Proposal > > REEF is a Big Data system that makes it easy to implement scalable, > fault-tolerant runtime environments for a range of data processing > models (e.g., graph processing and machine learning) on top of > resource managers such as Apache YARN and Mesos. REEF provides > capabilities to run multiple heterogeneous frameworks and workflows of > those efficiently. > > Additionally, REEF contains two libraries that are of independent > value: Wake is an event-based-programming framework inspired by Rx and > SEDA. Tang is a dependency injection framework inspired by Google > Guice, but designed specifically for configuring distributed systems. > > > # Background > > The resource management layer such as Apache YARN and Mesos has > emerged as a critical layer in the new scale-out data processing > stack; resource managers assume the responsibility of multiplexing a > cluster of shared-nothing machines across heterogeneous > applications. They operate behind an interface for leasing containers > - a slice of a machine’s resources - to computations in an elastic > fashion. However, building data processing frameworks directly on this > layer comes at a high cost: each framework must tackle the same > challenges (e.g., fault-tolerance, task scheduling and coordination) > and reimplement common mechanisms (e.g., caching, bulk transfers). > > REEF provides a reusable control-plane for scheduling and coordinating > task-level work on cluster resource managers. The REEF design enables > sophisticated optimizations, such as container re-use and data > caching, and facilitates workflows that span multiple > frameworks. Examples include pipelining data between different > operators in a relational system, retaining state across iterations in > iterative or recursive data flow, and passing the result of a > MapReduce job to a Machine Learning computation. > > > # Rationale > > Since REEF is a library that makes it easy to write distributed > applications on top of Apache YARN or Mesos, the Apache Software Foundation > is the perfect home for hosting REEF. > > > # Current Status > > REEF has been developed mostly by Microsoft, UCLA and the Seoul > National University. The REEF codebase is open-sourced under Apache > License 2.0 and is currently hosted in a public repository at > github.com. > > > # Meritocracy > > We plan to build a strong open community by following the Apache > meritocracy principles. We will work with those who contribute > significantly to the project and invite them to be its committers. > > > # Community > > REEF is currently being used internally at Microsoft. Also, SK > Telecom builds their data analytics infrastructure on top of REEF in > collaboration with Seoul National University. We hope to extend our > contributor base by becoming an Apache incubator project. REEF will > attract developers who are interested in creating common building > blocks for simplifying the development of large-scale big data > applications. > > > # Core Developers > > Core developers are engineers from Microsoft, Purestorage, UCB, UCLA, > UW and Seoul National University. > > > # Alignment > > REEF depends on many Apache projects and dependencies. REEF is built > on resource managers such as Apache YARN and Apache Mesos. REEF also > uses HDFS as a distributed storage layer. > > > # Known Risks > ## Orphaned Products > > The risk of REEF being orphaned is small because Microsoft
Wiki access
Hello, Can I have access to the incubator wiki? I'd like to post the REEF proposal on the wiki. My user name is "Byung-Gon Chun". Thanks! - Gon -- Byung-Gon Chun
[PROPOSAL] REEF for the Apache Incubator
Hi everyone, I would like to propose REEF to be an Apache Incubator project. REEF is a scale-out computing fabric that eases the development of Big Data applications on top of resource managers such as Apache YARN and Mesos. The proposal is included in plain text below. I would also like to put this on wiki but I don't have privileges to create wiki pages. I look forward to hearing everyone's thoughts and feedback! -Gon -- Byung-Gon Chun === # REEFProposal - Incubator # Abstract REEF (Retainable Evaluator Execution Framework) is a scale-out computing fabric that eases the development of Big Data applications on top of resource managers such as Apache YARN and Mesos. # Proposal REEF is a Big Data system that makes it easy to implement scalable, fault-tolerant runtime environments for a range of data processing models (e.g., graph processing and machine learning) on top of resource managers such as Apache YARN and Mesos. REEF provides capabilities to run multiple heterogeneous frameworks and workflows of those efficiently. Additionally, REEF contains two libraries that are of independent value: Wake is an event-based-programming framework inspired by Rx and SEDA. Tang is a dependency injection framework inspired by Google Guice, but designed specifically for configuring distributed systems. # Background The resource management layer such as Apache YARN and Mesos has emerged as a critical layer in the new scale-out data processing stack; resource managers assume the responsibility of multiplexing a cluster of shared-nothing machines across heterogeneous applications. They operate behind an interface for leasing containers - a slice of a machine’s resources - to computations in an elastic fashion. However, building data processing frameworks directly on this layer comes at a high cost: each framework must tackle the same challenges (e.g., fault-tolerance, task scheduling and coordination) and reimplement common mechanisms (e.g., caching, bulk transfers). REEF provides a reusable control-plane for scheduling and coordinating task-level work on cluster resource managers. The REEF design enables sophisticated optimizations, such as container re-use and data caching, and facilitates workflows that span multiple frameworks. Examples include pipelining data between different operators in a relational system, retaining state across iterations in iterative or recursive data flow, and passing the result of a MapReduce job to a Machine Learning computation. # Rationale Since REEF is a library that makes it easy to write distributed applications on top of Apache YARN or Mesos, the Apache Software Foundation is the perfect home for hosting REEF. # Current Status REEF has been developed mostly by Microsoft, UCLA and the Seoul National University. The REEF codebase is open-sourced under Apache License 2.0 and is currently hosted in a public repository at github.com. # Meritocracy We plan to build a strong open community by following the Apache meritocracy principles. We will work with those who contribute significantly to the project and invite them to be its committers. # Community REEF is currently being used internally at Microsoft. Also, SK Telecom builds their data analytics infrastructure on top of REEF in collaboration with Seoul National University. We hope to extend our contributor base by becoming an Apache incubator project. REEF will attract developers who are interested in creating common building blocks for simplifying the development of large-scale big data applications. # Core Developers Core developers are engineers from Microsoft, Purestorage, UCB, UCLA, UW and Seoul National University. # Alignment REEF depends on many Apache projects and dependencies. REEF is built on resource managers such as Apache YARN and Apache Mesos. REEF also uses HDFS as a distributed storage layer. # Known Risks ## Orphaned Products The risk of REEF being orphaned is small because Microsoft products are built on REEF. The core REEF developers continue to work on REEF at Microsoft, UCLA, and Seoul National University. The REEF project is gaining interest from other institutions to be used as their infrastructure. ## Inexperience with Open Source Several core developers have experience with open source development. REEF committers will be guided by the mentors with strong Apache open source project backgrounds. ## Homogeneous Developers The initial committers include developers from several institutions including Microsoft, Purestorage, UCB, UCLA, and Seoul National University. ## Reliance on Salaried Developers Developers from Microsoft are paid to work on REEF. Since the work is used internally at Microsoft, Microsoft will keep supporting the developers to work on REEF. There are also engineers and graduate students that contribute to REEF from UCLA, UCB, UW and Seoul National University. We plan to attract active developers from other institutions. ## Relationships
