Re: [DISCUSS] Retire Livy podling
Thank you Larry. We are from Shopee, I lead the Spark team here. I have several team members participant in Livy development, but most finished feature are done by me and my colleague Jianzhen, information as follows: Xilang Yan, xilang@gmail.com, Shopee Jianzhen Wu, myjianz...@gmail.com, Shopee Thanks! larry mccay 于2022年10月10日周一 23:01写道： > Exciting to see interest growing! > I think rather than try and gather all of these things now, we follow up > the proposal with a roadmap discussion. > > Just as we often entertain new committers during the proposal consideration > we can do that then as well. > If you'd like to provide your names and affiliations here, I can add them > to the upcoming proposal. > If you'd like to wait to agree on the proposal first that would work too. > > Again, very good to see traction building here! > > --larry > > On Mon, Oct 10, 2022 at 8:56 AM 严细浪 wrote: > > > So glad to see there is new progress on Livy community. We have a huge > > Livy cluster on our prod environment with nearly one million Spark > > applications submitted everyday, currently we have to maintain Livy > > ourselves. > > Some common features we finished: > > Livy rest cluster, I engaged in the Livy rest cluster design but after > > that there is no progress so we implement it ourselves, although has a > > little difference with design > > Support multi Spark versions > > Implemented a metrics system for Livy > > Support customize batch/interactive session lifecycle event handler, > > default log event with log4j, very helpful for trouble shooting > > Optimize log to track which session id the log message came from, also > > very helpful for trouble shooting > > Support customize Spark config optimization rules, can be used to > optimize > > config for users’ job > > A sets of command line tool which can be used to replace Spark’s > > spark-submit, pyspark, spark-sql but actually submit application in Livy > > > > We are planning to implement a JDBC state store, and allow multi Livy > > Thrift session to share one backend Spark application in next few months. > > > > We can deliver our changes if it is in Livy’s plan. > > > > Thanks, > > Jeffrey > > > > > > On 2022/10/10 09:27:46 Jean-Baptiste Onofré wrote: > > > Hi, > > > > > > If you plan to contribute on Livy, you are welcome to be part of the > > > proposal imho. > > > > > > Regards > > > JB > > > > > > On Mon, Oct 10, 2022 at 7:19 AM Brahma Reddy Battula > > > wrote: > > > > > > > > Hi Larry, > > > > > > > > Nice to hear from you that you are planning propose new features and > > make > > > > active. > > > > > > > > We do use Livy in our prod clusters, any chance to include us in your > > > > proposal so that we can also contribute. > > > > > > > > > > > > > > > > On Mon, 10 Oct 2022 at 3:54 AM, larry mccay > wrote: > > > > > > > > > Sure. > > > > > Thanks, Craig. > > > > > > > > > > --larry > > > > > > > > > > On Sun, Oct 9, 2022, 5:38 PM Craig Russell > wrote: > > > > > > > > > > > Hi Larry, > > > > > > > > > > > > > On Oct 8, 2022, at 10:30, larry mccay > wrote: > > > > > > > > > > > > > > Good to hear, Jean-Baptiste! > > > > > > > We will send the proposal both here and to the Livy private > > list, I > > > > > > guess. > > > > > > > Once we come to an agreement and direction we can share with > the > > dev@ > > > > > > and > > > > > > > user@ lists. > > > > > > > > > > > > I support the effort to revive the Livy podling, but I'd advise > > against > > > > > > using the private list to discuss it. The incubator general list > is > > > > > public > > > > > > and the livy dev list is public, so these are the lists I'd > > suggest you > > > > > use > > > > > > for further discussion. > > > > > > > > > > > > Again, good luck with the effort, > > > > > > Craig > > > > > > > > > > > > > > Thanks again! > > > > > > > > > > > > > > --larry > > > > > > > > > > > > > > On Sat, Oct 8, 2022 at 12:49 AM Jean-Baptiste Onofré < > > jb...@nanthrax.net> > > > > > > > wrote: > > > > > > > > > > > > > >> Hi Larry, > > > > > > >> > > > > > > >> Agree with Claude: if we can have concrete proposal (in terms > of > > > > > > >> community and roadmap), it's OK. We are not in a rush, if we > > can have > > > > > > >> this in the commit weeks, it's fine. > > > > > > >> I would sent this on the Livy mailing list. > > > > > > >> > > > > > > >> Again, I would be more than happy to help and contribute on > > Livy. > > > > > > >> > > > > > > >> Regards > > > > > > >> JB > > > > > > >> > > > > > > >> On Fri, Oct 7, 2022 at 6:08 PM larry mccay > > wrote: > > > > > > >>> > > > > > > >>> I was hoping that we could bring a set of contributors as: > > > > > > >>> > > > > > > >>> * mentors - 1 or 2 plus whoever wants to remain > > > > > > >>> * PPMC/Committers - 2 or 3 plus whoever wants to remain > > > > > > >>> * election of a PPMC chair if needed > > > > > > >>> > > > > > > >>> Also open it up for folks to ask to join (as well as go > > emeritus) as > > > > > I > > > >
Re: [VOTE] Accept Baremaps into the Apache Incubator
+1 (binding) On Sat, Oct 8, 2022 at 8:47 AM Yu Xiao wrote: > + 1 > > Best wishes! > > Yu Xiao > Apache ShenYu > > li gang 于2022年10月8日周六 23:26写道： > > > > +1 (non-binding) > > Good luck. > > > > Bertrand Delacretaz 于2022年10月6日周四 20:53写道： > > > > > Hi, > > > > > > The [DISCUSS] thread on Baremaps [1] has slowed down, with no > > > objections AFAICS, so I'm calling a vote to accept Baremap into the > > > Apache incubator. > > > > > > The proposal is copied below and available at > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Baremaps+Proposal > > > > > > Please cast your vote: > > > > > > [ ] +1, bring Baremap into the Incubator > > > [ ] +0, I don't care either way > > > [ ] -1, do not bring Baremap into the Incubator, because... > > > > > > This majority vote is open for at least 72 hours. > > > > > > Only votes from Incubator PMC members are binding, but other votes are > > > welcome! > > > > > > -Bertrand > > > > > > [1] https://lists.apache.org/thread/wlqvf709oljv20qd3f44pstn4l8vt4n3 > > > > > > -- Baremaps Proposal -- > > > > > > Abstract > > > > > > Apache Baremaps is a toolkit and a set of infrastructure components > > > for creating, publishing, and operating online maps. > > > > > > Proposal > > > > > > Apache Baremaps is a toolkit and a set of infrastructure components > > > for creating, publishing, and operating online maps. It provides a > > > data pipeline enabling developers to build maps with different data > > > sources. It offers live reload capabilities that allow cartographers > > > to customize the content and the style of a map. It includes an > > > attribution-free map schema and style that stimulates derived work. > > > Finally, it provides services commonly used in online maps, such as > > > location search and IP to location. > > > > > > Background > > > > > > The infrastructure components required to publish and operate > > > large-scale online maps are often closed-source, heterogeneous, > > > complex, and expensive. For instance: the visualization of maps in Web > > > browsers or on mobile devices requires processing and tiling large > > > spatial datasets, such as OpenStreetMap; the location of users based > > > on their IP addresses requires aggregating and merging data from > > > network information centers; the ability to search in a map requires > > > indexing features based on text and spatial attributes in different > > > languages. > > > > > > Rationale > > > > > > Web mapping infrastructure is often managed by large teams of > > > developers (e.g., Google Maps, Apple Maps, Mapbox, etc.), which makes > > > it hard to customize and evolve. Apache Baremaps is a Web mapping > > > infrastructure for the rest of us: it enables individuals and small > > > teams of developers to regain control over spatial data and to develop > > > custom mapping experiences. As a result, Apache Baremaps facilitates > > > innovation in niche areas where resources are limited and > > > customization is needed (e.g., sustainable mobility, civil > > > engineering, urban planning, environment monitoring, startups, etc.). > > > > > > Initial Goals > > > > > > The primary goals are: > > > > > > to learn the Apache Way; > > > to release a customizable attribution-free map schema and style; > > > to publish a tiled world map in different formats (mvt, png, 3D Tiles > > > Next, etc.); > > > to grow the community and attract new contributors; > > > to release additional services and components (IP to location, > > > location search, etc.). > > > > > > Current Status > > > > > > Meritocracy > > > > > > Baremaps is a project initially developed by Bertil Chapuis. It has > > > already attracted outside contributors. Therefore, the process of > > > electing new committers and project management committee members > > > should be natural. > > > > > > Community > > > > > > The need for Web mapping infrastructure is great, hence a good > > > potential for a diverse community mixing developers and cartographers. > > > > > > Core Developers > > > > > > The contributors to Baremaps include developers from academia and > > > industry, mainly located in Europe. The contributions include > > > documentation, bug fixes, and new features. Most of the development > > > and communication currently takes place on GitHub. > > > > > > Alignment > > > > > > Many critical components used in the geospatial community are released > > > under LGPL (e.g., Geotools, Geotoolkit). We are strongly aligned with > > > the terms of the Apache license. Joining the geospatial community at > > > Apache will enable us to be less reliant on components with > > > contaminating licenses. For instance, Apache SIS seeks to become an > > > alternative to Geotools and Geotoolkit. > > > > > > Known Risks > > > > > > Project Name > > > > > > No trademark is associated with the Baremaps name, and the project is > > > already well referenced by search engines. The .com, .org, and .net > > > domains are the property of Bertil
Re: [DISCUSS] Retire Livy podling
Exciting to see interest growing! I think rather than try and gather all of these things now, we follow up the proposal with a roadmap discussion. Just as we often entertain new committers during the proposal consideration we can do that then as well. If you'd like to provide your names and affiliations here, I can add them to the upcoming proposal. If you'd like to wait to agree on the proposal first that would work too. Again, very good to see traction building here! --larry On Mon, Oct 10, 2022 at 8:56 AM 严细浪 wrote: > So glad to see there is new progress on Livy community. We have a huge > Livy cluster on our prod environment with nearly one million Spark > applications submitted everyday, currently we have to maintain Livy > ourselves. > Some common features we finished: > Livy rest cluster, I engaged in the Livy rest cluster design but after > that there is no progress so we implement it ourselves, although has a > little difference with design > Support multi Spark versions > Implemented a metrics system for Livy > Support customize batch/interactive session lifecycle event handler, > default log event with log4j, very helpful for trouble shooting > Optimize log to track which session id the log message came from, also > very helpful for trouble shooting > Support customize Spark config optimization rules, can be used to optimize > config for users’ job > A sets of command line tool which can be used to replace Spark’s > spark-submit, pyspark, spark-sql but actually submit application in Livy > > We are planning to implement a JDBC state store, and allow multi Livy > Thrift session to share one backend Spark application in next few months. > > We can deliver our changes if it is in Livy’s plan. > > Thanks, > Jeffrey > > > On 2022/10/10 09:27:46 Jean-Baptiste Onofré wrote: > > Hi, > > > > If you plan to contribute on Livy, you are welcome to be part of the > > proposal imho. > > > > Regards > > JB > > > > On Mon, Oct 10, 2022 at 7:19 AM Brahma Reddy Battula > wrote: > > > > > > Hi Larry, > > > > > > Nice to hear from you that you are planning propose new features and > make > > > active. > > > > > > We do use Livy in our prod clusters, any chance to include us in your > > > proposal so that we can also contribute. > > > > > > > > > > > > On Mon, 10 Oct 2022 at 3:54 AM, larry mccay wrote: > > > > > > > Sure. > > > > Thanks, Craig. > > > > > > > > --larry > > > > > > > > On Sun, Oct 9, 2022, 5:38 PM Craig Russell wrote: > > > > > > > > > Hi Larry, > > > > > > > > > > > On Oct 8, 2022, at 10:30, larry mccay wrote: > > > > > > > > > > > > Good to hear, Jean-Baptiste! > > > > > > We will send the proposal both here and to the Livy private > list, I > > > > > guess. > > > > > > Once we come to an agreement and direction we can share with the > dev@ > > > > > and > > > > > > user@ lists. > > > > > > > > > > I support the effort to revive the Livy podling, but I'd advise > against > > > > > using the private list to discuss it. The incubator general list is > > > > public > > > > > and the livy dev list is public, so these are the lists I'd > suggest you > > > > use > > > > > for further discussion. > > > > > > > > > > Again, good luck with the effort, > > > > > Craig > > > > > > > > > > > > Thanks again! > > > > > > > > > > > > --larry > > > > > > > > > > > > On Sat, Oct 8, 2022 at 12:49 AM Jean-Baptiste Onofré < > jb...@nanthrax.net> > > > > > > wrote: > > > > > > > > > > > >> Hi Larry, > > > > > >> > > > > > >> Agree with Claude: if we can have concrete proposal (in terms of > > > > > >> community and roadmap), it's OK. We are not in a rush, if we > can have > > > > > >> this in the commit weeks, it's fine. > > > > > >> I would sent this on the Livy mailing list. > > > > > >> > > > > > >> Again, I would be more than happy to help and contribute on > Livy. > > > > > >> > > > > > >> Regards > > > > > >> JB > > > > > >> > > > > > >> On Fri, Oct 7, 2022 at 6:08 PM larry mccay > wrote: > > > > > >>> > > > > > >>> I was hoping that we could bring a set of contributors as: > > > > > >>> > > > > > >>> * mentors - 1 or 2 plus whoever wants to remain > > > > > >>> * PPMC/Committers - 2 or 3 plus whoever wants to remain > > > > > >>> * election of a PPMC chair if needed > > > > > >>> > > > > > >>> Also open it up for folks to ask to join (as well as go > emeritus) as > > > > I > > > > > >> know > > > > > >>> there are others that have tried to contribute and have gotten > know > > > > > where > > > > > >>> or have long since decided it wasn't worth trying anymore. > > > > > >>> > > > > > >>> So, my thought was almost a new Proposal and solicitation for > > > > community > > > > > >>> bootstrap with a few seeds planted to help it grow. > > > > > >>> I was also considering a goal of getting it back off the > ground with > > > > > some > > > > > >>> number of releases and proof of health as a project to fast > track to > > > > a > > > > > >>> graduation discussion. > > > > > >>> A bit early to talk about
Re: [MENTORS] Late podling reports and missing signoffs
On 2022-10-10 03:19, Calvin Kirs wrote: Hi, EventMesh, Milagro, and PonyMail haven't been signed off by a mentor yet. Pony Mail hasn't had a mentor sign off for the last four reports. I think it's safe to say our mentor is not available right now :-). Having said that, I think we'll be fine without one for now. On Fri, Oct 7, 2022 at 6:06 AM Furkan KAMACI wrote: Hi, Exactly! Most of the mentors (including me) at ApacheCon. I think they will all take care of it before the deadline. Kind Regards, Furkan KAMACI On 6 Oct 2022 Thu at 10:09 Calvin Kirs wrote: On Thu, Oct 6, 2022 at 10:45 PM Daniel Gruno wrote: On 2022-10-06 07:15, Calvin Kirs wrote: Hi, We are missing reports from: - EventMesh - HugeGraph - MarvinAI - Nuttx - Spot - Teaclave - PonyMail We are missing mentor sign-off on:(Mentor signoff due by end of days is Tue Oct 9) - DataLab - Flagon - Milagro I suspect ApacheCon is causing some reports to be delayed for a couple of days... Yes, I know we have a lot of people who went to Apache Con, but it doesn't matter, we still have time to submit our reports. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best wishes！ CalvinKirs - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Retire Livy podling
So glad to see there is new progress on Livy community. We have a huge Livy cluster on our prod environment with nearly one million Spark applications submitted everyday, currently we have to maintain Livy ourselves. Some common features we finished: Livy rest cluster, I engaged in the Livy rest cluster design but after that there is no progress so we implement it ourselves, although has a little difference with design Support multi Spark versions Implemented a metrics system for Livy Support customize batch/interactive session lifecycle event handler, default log event with log4j, very helpful for trouble shooting Optimize log to track which session id the log message came from, also very helpful for trouble shooting Support customize Spark config optimization rules, can be used to optimize config for users’ job A sets of command line tool which can be used to replace Spark’s spark-submit, pyspark, spark-sql but actually submit application in Livy We are planning to implement a JDBC state store, and allow multi Livy Thrift session to share one backend Spark application in next few months. We can deliver our changes if it is in Livy’s plan. Thanks, Jeffrey On 2022/10/10 09:27:46 Jean-Baptiste Onofré wrote: > Hi, > > If you plan to contribute on Livy, you are welcome to be part of the > proposal imho. > > Regards > JB > > On Mon, Oct 10, 2022 at 7:19 AM Brahma Reddy Battula wrote: > > > > Hi Larry, > > > > Nice to hear from you that you are planning propose new features and make > > active. > > > > We do use Livy in our prod clusters, any chance to include us in your > > proposal so that we can also contribute. > > > > > > > > On Mon, 10 Oct 2022 at 3:54 AM, larry mccay wrote: > > > > > Sure. > > > Thanks, Craig. > > > > > > --larry > > > > > > On Sun, Oct 9, 2022, 5:38 PM Craig Russell wrote: > > > > > > > Hi Larry, > > > > > > > > > On Oct 8, 2022, at 10:30, larry mccay wrote: > > > > > > > > > > Good to hear, Jean-Baptiste! > > > > > We will send the proposal both here and to the Livy private list, I > > > > guess. > > > > > Once we come to an agreement and direction we can share with the dev@ > > > > and > > > > > user@ lists. > > > > > > > > I support the effort to revive the Livy podling, but I'd advise against > > > > using the private list to discuss it. The incubator general list is > > > public > > > > and the livy dev list is public, so these are the lists I'd suggest you > > > use > > > > for further discussion. > > > > > > > > Again, good luck with the effort, > > > > Craig > > > > > > > > > > Thanks again! > > > > > > > > > > --larry > > > > > > > > > > On Sat, Oct 8, 2022 at 12:49 AM Jean-Baptiste Onofré > > > > > > > > > > wrote: > > > > > > > > > >> Hi Larry, > > > > >> > > > > >> Agree with Claude: if we can have concrete proposal (in terms of > > > > >> community and roadmap), it's OK. We are not in a rush, if we can have > > > > >> this in the commit weeks, it's fine. > > > > >> I would sent this on the Livy mailing list. > > > > >> > > > > >> Again, I would be more than happy to help and contribute on Livy. > > > > >> > > > > >> Regards > > > > >> JB > > > > >> > > > > >> On Fri, Oct 7, 2022 at 6:08 PM larry mccay wrote: > > > > >>> > > > > >>> I was hoping that we could bring a set of contributors as: > > > > >>> > > > > >>> * mentors - 1 or 2 plus whoever wants to remain > > > > >>> * PPMC/Committers - 2 or 3 plus whoever wants to remain > > > > >>> * election of a PPMC chair if needed > > > > >>> > > > > >>> Also open it up for folks to ask to join (as well as go emeritus) as > > > I > > > > >> know > > > > >>> there are others that have tried to contribute and have gotten know > > > > where > > > > >>> or have long since decided it wasn't worth trying anymore. > > > > >>> > > > > >>> So, my thought was almost a new Proposal and solicitation for > > > community > > > > >>> bootstrap with a few seeds planted to help it grow. > > > > >>> I was also considering a goal of getting it back off the ground with > > > > some > > > > >>> number of releases and proof of health as a project to fast track to > > > a > > > > >>> graduation discussion. > > > > >>> A bit early to talk about that now but that was a detail that I > > > thought > > > > >>> would possibly go into such a reboot proposal. > > > > >>> > > > > >>> @Jean-Baptiste - we have compiled a list of features/improvements > > > that > > > > we > > > > >>> would be able to bring to the table with the reboot as well. > > > > >>> These are improvements that have been made internally due the sense > > > of > > > > >> not > > > > >>> being able to get them in. I lack the details around the attempts at > > > > this > > > > >>> time but we would be bringing source as well. > > > > >>> We could list these as part of the proposal/concrete plans. > > > > >>> > > > > >>> If you think this proposal can be done more casually, that's fine > > > too. > > > > I > > > > >>> just would like to make it clear that we would open
Re: [RESULT][VOTE] Accept Baremaps into the Apache Incubator
Le lun. 10 oct. 2022 à 11:30, Bertrand Delacretaz wrote: > ..The vote passes with more than 3 binding +1s, a few non-binding +1s > and no other votes... I should have included a link to the vote thread: https://lists.apache.org/thread/6qhbbdnvszpj2wwkcqb1xc05c81brw4r -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Accept Baremaps into the Apache Incubator
Le jeu. 6 oct. 2022 à 14:52, Bertrand Delacretaz wrote: > ...The [DISCUSS] thread on Baremaps [1] has slowed down, with no > objections AFAICS, so I'm calling a vote to accept Baremap into the > Apache incubator... The vote passes with more than 3 binding +1s, a few non-binding +1s and no other votes. Thanks to all who voted! I'll ask for the podling to be set up and mailing lists to be created as per https://incubator.apache.org/cookbook/#podling_infrastructure_setup and will report here when the dev@ list is ready. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Retire Livy podling
Hi, If you plan to contribute on Livy, you are welcome to be part of the proposal imho. Regards JB On Mon, Oct 10, 2022 at 7:19 AM Brahma Reddy Battula wrote: > > Hi Larry, > > Nice to hear from you that you are planning propose new features and make > active. > > We do use Livy in our prod clusters, any chance to include us in your > proposal so that we can also contribute. > > > > On Mon, 10 Oct 2022 at 3:54 AM, larry mccay wrote: > > > Sure. > > Thanks, Craig. > > > > --larry > > > > On Sun, Oct 9, 2022, 5:38 PM Craig Russell wrote: > > > > > Hi Larry, > > > > > > > On Oct 8, 2022, at 10:30, larry mccay wrote: > > > > > > > > Good to hear, Jean-Baptiste! > > > > We will send the proposal both here and to the Livy private list, I > > > guess. > > > > Once we come to an agreement and direction we can share with the dev@ > > > and > > > > user@ lists. > > > > > > I support the effort to revive the Livy podling, but I'd advise against > > > using the private list to discuss it. The incubator general list is > > public > > > and the livy dev list is public, so these are the lists I'd suggest you > > use > > > for further discussion. > > > > > > Again, good luck with the effort, > > > Craig > > > > > > > > Thanks again! > > > > > > > > --larry > > > > > > > > On Sat, Oct 8, 2022 at 12:49 AM Jean-Baptiste Onofré > > > > wrote: > > > > > > > >> Hi Larry, > > > >> > > > >> Agree with Claude: if we can have concrete proposal (in terms of > > > >> community and roadmap), it's OK. We are not in a rush, if we can have > > > >> this in the commit weeks, it's fine. > > > >> I would sent this on the Livy mailing list. > > > >> > > > >> Again, I would be more than happy to help and contribute on Livy. > > > >> > > > >> Regards > > > >> JB > > > >> > > > >> On Fri, Oct 7, 2022 at 6:08 PM larry mccay wrote: > > > >>> > > > >>> I was hoping that we could bring a set of contributors as: > > > >>> > > > >>> * mentors - 1 or 2 plus whoever wants to remain > > > >>> * PPMC/Committers - 2 or 3 plus whoever wants to remain > > > >>> * election of a PPMC chair if needed > > > >>> > > > >>> Also open it up for folks to ask to join (as well as go emeritus) as > > I > > > >> know > > > >>> there are others that have tried to contribute and have gotten know > > > where > > > >>> or have long since decided it wasn't worth trying anymore. > > > >>> > > > >>> So, my thought was almost a new Proposal and solicitation for > > community > > > >>> bootstrap with a few seeds planted to help it grow. > > > >>> I was also considering a goal of getting it back off the ground with > > > some > > > >>> number of releases and proof of health as a project to fast track to > > a > > > >>> graduation discussion. > > > >>> A bit early to talk about that now but that was a detail that I > > thought > > > >>> would possibly go into such a reboot proposal. > > > >>> > > > >>> @Jean-Baptiste - we have compiled a list of features/improvements > > that > > > we > > > >>> would be able to bring to the table with the reboot as well. > > > >>> These are improvements that have been made internally due the sense > > of > > > >> not > > > >>> being able to get them in. I lack the details around the attempts at > > > this > > > >>> time but we would be bringing source as well. > > > >>> We could list these as part of the proposal/concrete plans. > > > >>> > > > >>> If you think this proposal can be done more casually, that's fine > > too. > > > I > > > >>> just would like to make it clear that we would open it up to new > > folks > > > as > > > >>> well. > > > >>> > > > >>> However you'd like to see it done, we can have concrete commitments > > to > > > >> you > > > >>> within a week or so more than likely. > > > >>> > > > >>> BTW, I did note that Ambari was sent to the attic and then pulled > > back > > > >> out > > > >>> [1] back in June into July of this year. > > > >>> I would hope that we could avoid the administrative headache that > > seems > > > >> to > > > >>> have been involved in that reinstatement. > > > >>> > > > >>> 1. https://issues.apache.org/jira/browse/ATTIC-205 > > > >>> > > > >>> On Fri, Oct 7, 2022 at 11:04 AM Claude Warren, Jr > > > >>> wrote: > > > >>> > > > Larry et.al. > > > > > > I think we need concrete steps. So if Larry produced a list of new > > > committers could we get them added to the list and see if > > development > > > starts again? > > > > > > Mentors / Champion does that work for you? > > > > > > Larry, can you produce such a list? > > > > > > Is there an objection to proceeding along these lines? > > > > > > Claude > > > > > > On Fri 7 Oct 2022, 03:07 Jean-Baptiste Onofré, > > > >> wrote: > > > > > > > Hi Larry, > > > > > > > > I tried maybe 3 times to get Livy back to active, without success. > > > > I was a volunteer to contribute, but not alone, we need a community > > > around > > > > Livy. > > > > > >
Re: [RESULT][VOTE] Release Apache DevLake (Incubating) v0.14.0-rc1
Thanks to everyone that voted for Apache Devlake in such a short period, with your votes, we can prepare the release for the incoming hacktoberfest 2022 event, which would certainly help us grow. And thanks Liang Zhang for the quick follow-up. My gratitude to all of you. On 22/10/09 05:39AM, Liang Zhang wrote: > My apologies. I defaulted to non-binding when counting votes, will look > closer next time. > Thanks everyone for helping us get this release out so quickly! > > Best Regards! > Liang Zhang > > > 2022年10月9日 01:18，Felix Cheung 写道： > > > > Correction: my vote is binding > > > > > > On Fri, Oct 7, 2022 at 8:00 PM Liang Zhang > > wrote: > > > >> Hi all, > >> > >> The vote to Apache DevLake(Incubating) v0.14.0-rc1 is now closed. Thanks > >> for reviewing and voting. > >> > >> The release voting has passed with 4 binding votes and 2 non-binding > >> votes, no +0 or -1 votes. > >> > >> Binding: > >> > >> - Jean-Baptiste Onofré > >> - Madhawa Gunasekara > >> - David Zollo > >> - Willem Jiang > >> > >> > >> Non-binding: > >> - Felix Cheung > >> - Li Gang > >> > >> The voting thread is: > >> https://lists.apache.org/thread/lgfrsv0ymfk1c19ngnkkn46cspkf76lg > >> > >> Thank you to all those who have provided us with help, advice and > >> guidance. We will continue to finish the rest of the work. > >> > >> > >> Thanks > >> Liang Zhang > >> > >> > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] Late podling reports and missing signoffs
Hi, EventMesh, Milagro, and PonyMail haven't been signed off by a mentor yet. On Fri, Oct 7, 2022 at 6:06 AM Furkan KAMACI wrote: > > Hi, > > Exactly! Most of the mentors (including me) at ApacheCon. I think they will > all take care of it before the deadline. > > Kind Regards, > Furkan KAMACI > > On 6 Oct 2022 Thu at 10:09 Calvin Kirs wrote: > > > On Thu, Oct 6, 2022 at 10:45 PM Daniel Gruno wrote: > > > > > > On 2022-10-06 07:15, Calvin Kirs wrote: > > > > Hi, > > > > > > > > We are missing reports from: > > > > - EventMesh > > > > - HugeGraph > > > > - MarvinAI > > > > - Nuttx > > > > - Spot > > > > - Teaclave > > > > - PonyMail > > > > > > > > We are missing mentor sign-off on:(Mentor signoff due by end of days > > > > is Tue Oct 9) > > > > - DataLab > > > > - Flagon > > > > - Milagro > > > > > > > > > > I suspect ApacheCon is causing some reports to be delayed for a couple > > > of days... > > Yes, I know we have a lot of people who went to Apache Con, but it > > doesn't matter, we still have time to submit our reports. > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > -- > > Best wishes！ > > CalvinKirs > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > -- Best wishes！ CalvinKirs - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubating Proposal for Celeborn (was: [DISCUSS] Incubating Proposal for Datark)
Hi All, Thanks for the feedback, and great to know you like the new name :-) @Madhawa Thanks for the interest, as we already have enough mentors, maybe next time (smile). And you're warmly welcome to watch and join the project. Best Regards, Yu On Thu, 6 Oct 2022 at 07:39, Madhawa Gunasekara wrote: > Hi, > > The name of this project is interesting. Soon we will find some other > characters also in future podlings. I would like to become a mentor for > this podling. > > Thanks, > Madhawa > > > On Tue, Oct 4, 2022 at 6:06 PM Roman Shaposhnik > wrote: > > > At the risk of drawing the ire of the top-post police -- I have to > > top-post ;-) > > > > Kudos on a really cool name! > > > > Thanks, > > Roman. > > > > On Fri, Sep 30, 2022 at 6:10 PM keyong zhou > > wrote: > > > > > > Hi Yu, > > > > > > Yeah the name is from 《The Silmarillion》 and Celeborn is a seedling of > > the > > > tree Galathilion, which in turn had been made in image of Telperion[1]. > > > > > > We're glad that you like it :) > > > > > > Thanks. > > > > > > Best Regards, > > > Keyong > > > > > > [1] https://tolkiengateway.net/wiki/Celeborn_(White_Tree) > > > > > > Yu Xiao 于2022年9月30日周五 18:13写道： > > > > > > > Hi， > > > > > > > > Very happy to see the name , > > > > > > > > BTW, It refers to Telperion（silver tree）in Two Trees of Valinor? > > > > > > > > 《The Silmarillion》is my favorite stories. And now the TV of 《The > Rings > > > > of Power》in theaters. > > > > > > > > The name is really great, > > > > > > > > I think it's cool to introduce this fantasy tree to the Apache > world. > > > > > > > > > Celeborn is the name of the White Tree in J. R. R. Tolkien's > > fantasy > > > > stories. "Celeb" is the sindarin for "silver" > > > > > > > > Best wishes! > > > > > > > > Yu Xiao > > > > Apache ShenYu > > > > > > > > Yu Li 于2022年9月30日周五 17:39写道： > > > > > > > > > > Hi All, > > > > > > > > > > After more careful searching and legal consultation, we found the > > name > > > > > "Datark" may have some trademark conflicts and (after some > community > > > > > discussion) decided to rename the project to "Celeborn", and have > > updated > > > > > the proposal document accordingly [1]. > > > > > > > > > > Celeborn is the name of the White Tree in J. R. R. Tolkien's > fantasy > > > > > stories. "Celeb" is the sindarin for "silver", while "orn" is that > > for > > > > > "tree", and we think it's cool to introduce this fantasy tree to > the > > > > Apache > > > > > world. Hopefully people also like this new name. > > > > > > > > > > And we'd like to continue the discussion and look forward to more > > > > feedback > > > > > (and thanks for the existing ones). > > > > > > > > > > Thanks. > > > > > > > > > > Best Regards, > > > > > Yu > > > > > > > > > > [1] > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/CelebornProposal > > > > > > > > > > On Tue, 27 Sept 2022 at 17:07, Kaijie Chen wrote: > > > > > > > > > > > Hi Yu, > > > > > > > > > > > > Thanks for your explanation. Yes it makes sense. > > > > > > It's nice we can see the migration process in the community. > > > > > > And it will probably help create better docs for the project. > > > > > > > > > > > > Best, > > > > > > Kaijie > > > > > > > > > > > > On 2022/09/27 06:05:10 Yu Li wrote: > > > > > > > Hi BLAST and Kaijie, > > > > > > > > > > > > > > Yes, we've done quite some work on merging the two rss projects > > (or > > > > more > > > > > > > accurately, try to extract the high-level architecture and > > > > interfaces to > > > > > > > form a more general framework) but still not fully completed. > > > > However, on > > > > > > > second thought, we feel incubating the project first and > > involving > > > > more > > > > > > > community forces to discuss and complete the work together > might > > be a > > > > > > > better idea. I believe more information on this topic will be > > shared > > > > in > > > > > > the > > > > > > > community, and further discussion and the incubation process > > won't > > > > block > > > > > > > each other. Wdyt? > > > > > > > > > > > > > > @Gon > > > > > > > Apache Nemo is an interesting project and we will further > > > > investigate and > > > > > > > search for the cooperation between the two projects (smile). > > > > > > > > > > > > > > Best Regards, > > > > > > > Yu > > > > > > > > > > > > > > > > > > > > > On Tue, 27 Sept 2022 at 10:45, Kaijie Chen > > wrote: > > > > > > > > > > > > > > > Hi Yu, > > > > > > > > > > > > > > > > You mentioned you will merge RemoteShuffleService and > > > > > > flink-remote-shuffle > > > > > > > > previously in this thread: > > > > > > > > > > > > > > > > > > https://lists.apache.org/thread/1w74z5f0pb7bhslhzcl5x7rdj9s9objz > > > > > > > > > > > > > > > > > Our proposal is still not fully prepared because the merge > of > > > > the two > > > > > > > > projects > > > > > > > > > is still in progress > > > > > > > > > > > > > > > > Have you done the merge? Or is there a plan to merge them > > later?
