Re: [RESULT][VOTE] Release Apache DevLake (Incubating) v0.14.0-rc1
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 >> >>
Re: [VOTE] Release Apache NuttX (Incubating) 11.0.0
+1 (binding) Checked sigs and sums: Matched LICENSE and NOTICE: Looks fine （run RAT to generate many warnings, most warnings seems to addressed in LICENSE, suggest to create a exclude file to depress annoying warnings） DISCLAIMER: In place Thanks, Junping Jean-Baptiste Onofré 于2022年10月8日周六 12:50写道： > +1 (binding) > > I checked: > - incubating is in the name > - ASF headers are present > - Signature and hash are OK > - LICENSE, NOTICE and DISCLAIMER look good > - No binary in the source distribution > > Regards > JB > > On Fri, Oct 7, 2022 at 7:00 PM TimH wrote: > > > > +1 (non-binding) > > > > Built for out-of-tree custom board and successfully got a working nuttx > > shell. > > > > > > > From: Alin Jerpelea > > > Sent: 22 September 2022 13:26 > > > To: general@incubator.apache.org > > > Subject: [VOTE] Release Apache NuttX (Incubating) 11.0.0 > > > > > > This is a call for a vote to release Apache NuttX (Incubating) version > > > 11.0.0. > > > > > > - > > 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
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. 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. > > > > > > > > I don't remember having seen new active contributions on the mailing > > > > list, and very limited on source code. > > > > > > > > If you really think we can have a team, that would be great, and I > > > > still agree to support. But it has to be concrete. > > > > > > > > Let's see what the other IPMC members are thinking, but IMHO, I doubt > > > > we will have Livy back to life in the short term. > > > > > > > > Regards > > > > JB > > > > > > > > On Thu, Oct 6, 2022 at 5:29 PM larry mccay > wrote: > > > > > > > > > > Folks, > > > > > > > > > > As I mentioned in a previous thread [1], I would like to help avoid > > > > sending > > > > > a well regarded, actively consumed and mature product to the attic. > > > There > > > > > have been discussions internally at my employer and we have also > > > > struggled > > > > > getting our contributions committed. The original group of > committers > > > > seem > > > > > to have all moved on, and this is the core challenge for those > that are > > > > > trying to contribute, but are not committers. This doesn’t > represent a > > > > > lack of interest in doing so and I think there are others in this > > > > position. > > > > > > > > > > We are interested in trying to reboot with additional PPMC > leadership > > > and > > > > > investing in contributors that we would like to install as new > > > > committers. > > > > > > > > > > I’d like to hear what the incubator would think about a Reproposal > for > > > > the > > > > > Livy project that would be open to existing PMC members and > committers > > > as > > > > > well as new contributors with a vested interest in this project > and the > > > > >
Re: [RESULT][VOTE] Release Apache DevLake (Incubating) v0.14.0-rc1
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 > >
Re: [VOTE] Accept Baremaps into the Apache Incubator
+ 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 Chapuis, who agrees to transfer > > them to the Apache Software Foundation unconditionally upon request. > > > > Orphaned Products > > > > There is a risk of being orphaned due to the small number of > > committers. Even if the main contributor has no plan to leave the > > project, this is a problem we need to address
Re: [VOTE] Accept Baremaps into the Apache Incubator
+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 Chapuis, who agrees to transfer > them to the Apache Software Foundation unconditionally upon request. > > Orphaned Products > > There is a risk of being orphaned due to the small number of > committers. Even if the main contributor has no plan to leave the > project, this is a problem we need to address in the future. > > Inexperience with open source > > The initial committers contributed to open source projects in the past > but have only a few experiences with the governance of open source > projects in a Foundation such as Apache. > > Length of incubation > > We expect to achieve most of the initial goals within one year.
[ANNOUNCE] Apache Tuweni (incubating) 2.3.0 released
The Apache Tuweni team is proud to announce the release of Apache Tuweni (incubating) 2.3.0. Apache Tuweni is a set of libraries and other tools to aid development of blockchain and other decentralized software in Java and other JVM languages. It includes a low-level bytes library, serialization and deserialization codecs (e.g. RLP), various cryptography functions and primatives, and lots of other helpful utilities. Tuweni is developed for JDK 11 or higher, and depends on various other FOSS libraries. Source and binary distributions can be downloaded from: https://tuweni.apache.org/download Release notes are at: https://github.com/apache/incubator-tuweni/releases/tag/v2.3.0-incubating A big thank you to all the contributors in this milestone release! To learn more about Tuweni and get started: http://tuweni.apache.org/ Thanks! The Apache Tuweni Team Disclaimer: Apache Tuweni is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
