Re: [VOTE] Release Apache Baremaps 0.8.1-rc2 (incubating)
Hi, In the NOTICE file, there is no need for the "product includes / copied files / derived files” sections. If you want to keep this content, put it in the README or similar. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Accept Hunter into the ASF Incubator
+1 (non-binding) We are using Hunter for regression testing of Kafka Streams, and it would be great if Hunter could become an ASF project by itself. -Matthias (Apache Kafka PCM member) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Answer (incubating) as a Top Level Project
+1 (binding) IPMC fanningpj On Mon, 25 Nov 2024 at 15:36, Christofer Dutz wrote: > > +1 (binding) IPMC cdutz > > I would like to support the graduation. > So far, their many releases have been almost spotless and they have been > successfully inviting new people into the PPMC as well as committers ranks. > > I have no doubt, that the project will live up to our standards. > > Chris > > Von: Ning Qi > Datum: Montag, 25. November 2024 um 04:55 > An: general@incubator.apache.org > Betreff: [VOTE] Graduate Apache Answer (incubating) as a Top Level Project > Hi everyone, > > Following the positive feedback received on the Answer Vote thread > [1](result[2]), I would like to initiate an official Incubator Vote thread > now. > > Here're some facts and project highlights during incubation and the draft > resolution are pasted as below. > - 9 Apache releases.[3] > - 15 language translations. > - 4 release managers have helped with the release and updated release file. > - 4 new committers and 1 PPMC member. > - 104 contributors and 144 translators. > - 193 issues resolved and 323 pull requests merged during incubation. > - We’ve built a diverse community representing 10 nations and various types > of contributions, showcasing active development and community involvement. > - All criteria in maturity assessment for Apache Answer have been met.[4] > > Please vote on the resolution below to graduate Apache Answer from the > Incubator to the Top Level Project. > > +1: Graduate Apache Answer as a TLP > +0: No opinion > -1: Don't graduate Apache Answer because ... > > This vote will open for at least 72 hours. > > We extend our sincere gratitude to everyone who has contributed to the > Apache Answer community, including the Apache Incubator community, the > Apache Infrastructure team, and the ASF community. > > Thank you for your participation in Apache Answer's journey. > > [1] https://lists.apache.org/thread/pwrlbhypjnq9nwd2l6f5406ohp8x9dv4 > [2] https://lists.apache.org/thread/pdwgzd4qnlhotn06z19z0vxhhnfcdrnm > [3] https://github.com/apache/incubator-answer/releases > [4] > https://github.com/apache/incubator-answer/wiki/Podling-Maturity-Assessment-for-Apache-Answer > > --- > Establish the Apache Answer 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 Q-and-A platform software for teams at any scales. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache Answer Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache Answer Project be and hereby is responsible > for the creation and maintenance of software related to A Q-and-A > platform software for teams at any scales; and be it further > > RESOLVED, that the office of "Vice President, Apache Answer" 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 Answer > Project, and to have primary responsibility for management of the > projects within the scope of responsibility of the Apache Answer > 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 Answer Project: > > * Anne Zhu > * Christofer Dutz > * Enxin Xie > * Feng Dong > * Fengjun Lv > * Guangfu Yang > * Justin Mclean > * Luffy > * Nadia Jiang > * Ning Qi > * Shuailing Li > * Willem Ning Jiang > * Yubin Ren > * Zili Chen > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ning Qi be appointed to the > office of Vice President, Apache Answer, 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 Answer Project be and hereby is tasked with > the migration and rationalization of the Apache Incubator Answer > podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > Answer podling encumbered upon the Apache Incubator PMC are hereafter > discharged. > --- > > Thank you. > > Best Regards, > Ning - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Baremaps 0.8.1-rc2 (incubating)
On Mon, Nov 25, 2024 at 6:25 PM Bertil Chapuis wrote: > Hello Calvin, > > Are you referring to the following email? I struggled to find a reference > to Netty in the dev mailing-list, but this one related to Hadoop seems to > be the most closely related. > https://lists.apache.org/thread/h8bbvwm5l9c5n9gzs4prhkrcmj9q5js1 > > As mentioned, I’ve observed different practices among top-level Apache > projects. For example, Hadoop and Spark include LICENSE, LICENSE-binary, > NOTICE, and NOTICE-binary files, as well as license and > license-binarydirectories. While we could introduce similar directories in > Baremaps, I’m concerned that they might quickly become outdated, given that > we lack the same level of resources as these large projects. Moreover, even > in Hadoop’s case, these files and directories haven’t been updated for four > to five years. > Yes, but that's something you have to do when releasing binary versions. I'm not sure if providing a link to indicate the license source in the LICENSE file would be acceptable. For example, with the MIT License: "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." I don't think providing just a link would work, but perhaps you could check with the ASF legal team. > On the other hand, other top-level projects that depend on Hadoop and > Spark (e.g., Drill, Sedona, etc.) seem to follow a simpler approach similar > to ours: a LICENSE file listing the dependencies and their licenses. Their > NOTICE files also don’t appear to include additional information (though I > could be overlooking something). > Not all practices of top-level projects are necessarily correct. I haven't kept up with Sedona, but I raised this issue with Drill last year[2]. [1]https://infra.apache.org/licensing-howto.html#binary [2]https://issues.apache.org/jira/projects/DRILL/issues/DRILL-8475 > > I’d prefer to stick with the simple approach (which is already quite > time-consuming :-) as it aligns with what many other projects are doing. If > this approach isn’t sufficient, I’d really appreciate gathering broader > input so we can define something actionable and maintainable for this > release and future ones. > > Best regards, > > Bertil > > > > > > On 25 Nov 2024, at 04:41, Calvin Kirs wrote: > > > > Hi Bertil, > > > > In addition to what Justin mentioned, I brought up in the dev mailing > list > > that the binary release is missing the NOTICE section (at least we > omitted > > the NOTICE for Netty). > > The LICENSE file is also missing and needs to be addressed in the next RC > > version. > > > > On Sun, Nov 24, 2024 at 10:40 PM Bertil Chapuis > wrote: > > > >> Hello Justin, > >> > >> I believe I now have enough information to release a new candidate. I’m > >> closing this vote and will start a new one early next week. > >> > >> Here is a summary of the corrections I made: > >> - Removed the unlicensed fuji.png file and fixed the related tests. > >> - Added a missing license header to scripts/generate-flageobuf.sh. > >> - Revised the notice file to ensure all paths are correct. > >> - Configured Spotless to ignore third-party files and added original > >> license headers. > >> - Created a licenses directory and added copies of third-party licenses. > >> - Replaced the URLs in the LICENSE file with pointers to these local > files. > >> - Included these new files in the assembly configuration. > >> > >> These changes are listed here (I will probably squash them into a single > >> release commit): > >> https://github.com/apache/incubator-baremaps/pull/905/files > >> > >> Thank you very much for helping with these changes. Please don't > hesitate > >> to provide additional feedback if needed. > >> > >> Best regards, > >> > >> Bertil > >> > >>> On 23 Nov 2024, at 22:50, Justin Mclean > >> wrote: > >>> > >>> HI, > >>> > According to the documentation [1], what’s currently missing in our > >> LICENSE file are pointers (“For details, see deps/flatgeobuf”). I > suggest > >> to modify the third party section as follow, so we have pointers for > >> everything. > > THIRD PARTY LICENSES: > > Code and data produced outside the ASF that is included in the > distribution of this product is subject to the following > additional license terms: > > - FlatGeobuf, BSD-2-Clause license, see > >> https://github.com/flatgeobuf/flatgeobuf. > - GeoPackage Java, MIT License, see > >> https://github.com/ngageoint/geopackage-java. > - OSMPBF, MIT License, see > >> https://github.com/openstreetmap/OSM-binary/pull/35. > - OSM Test Data, Public domain, see > >> https://github.com/osmcode/osm-testdata. > - Mapbox Vector Tile, Creative Commons Public License, see > >> https://github.com/mapbox/vector-tile-spec. > - Palantir Streams, Apache License 2.0, see > >> https://github.com/palantir/streams. > - Planetiler, Apache License 2.0, see >
Re: [VOTE] Release Apache Baremaps 0.8.1-rc2 (incubating)
This discussion might be clearer.[1] [1] https://issues.apache.org/jira/browse/LEGAL-323 On Mon, Nov 25, 2024 at 7:18 PM Calvin Kirs wrote: > > > On Mon, Nov 25, 2024 at 6:25 PM Bertil Chapuis wrote: > >> Hello Calvin, >> >> Are you referring to the following email? I struggled to find a reference >> to Netty in the dev mailing-list, but this one related to Hadoop seems to >> be the most closely related. >> https://lists.apache.org/thread/h8bbvwm5l9c5n9gzs4prhkrcmj9q5js1 >> >> As mentioned, I’ve observed different practices among top-level Apache >> projects. For example, Hadoop and Spark include LICENSE, LICENSE-binary, >> NOTICE, and NOTICE-binary files, as well as license and >> license-binarydirectories. While we could introduce similar directories in >> Baremaps, I’m concerned that they might quickly become outdated, given that >> we lack the same level of resources as these large projects. Moreover, even >> in Hadoop’s case, these files and directories haven’t been updated for four >> to five years. >> > Yes, but that's something you have to do when releasing binary versions. > I'm not sure if providing a link to indicate the license source in the > LICENSE file would be acceptable. For example, with the MIT License: "The > above copyright notice and this permission notice shall be included in all > copies or substantial portions of the Software." I don't think providing > just a link would work, but perhaps you could check with the ASF legal > team. > > > >> On the other hand, other top-level projects that depend on Hadoop and >> Spark (e.g., Drill, Sedona, etc.) seem to follow a simpler approach similar >> to ours: a LICENSE file listing the dependencies and their licenses. Their >> NOTICE files also don’t appear to include additional information (though I >> could be overlooking something). >> > > Not all practices of top-level projects are necessarily correct. I haven't > kept up with Sedona, but I raised this issue with Drill last year[2]. > > [1]https://infra.apache.org/licensing-howto.html#binary > [2]https://issues.apache.org/jira/projects/DRILL/issues/DRILL-8475 > >> >> I’d prefer to stick with the simple approach (which is already quite >> time-consuming :-) as it aligns with what many other projects are doing. If >> this approach isn’t sufficient, I’d really appreciate gathering broader >> input so we can define something actionable and maintainable for this >> release and future ones. >> >> Best regards, >> >> Bertil >> >> >> >> >> > On 25 Nov 2024, at 04:41, Calvin Kirs wrote: >> > >> > Hi Bertil, >> > >> > In addition to what Justin mentioned, I brought up in the dev mailing >> list >> > that the binary release is missing the NOTICE section (at least we >> omitted >> > the NOTICE for Netty). >> > The LICENSE file is also missing and needs to be addressed in the next >> RC >> > version. >> > >> > On Sun, Nov 24, 2024 at 10:40 PM Bertil Chapuis >> wrote: >> > >> >> Hello Justin, >> >> >> >> I believe I now have enough information to release a new candidate. I’m >> >> closing this vote and will start a new one early next week. >> >> >> >> Here is a summary of the corrections I made: >> >> - Removed the unlicensed fuji.png file and fixed the related tests. >> >> - Added a missing license header to scripts/generate-flageobuf.sh. >> >> - Revised the notice file to ensure all paths are correct. >> >> - Configured Spotless to ignore third-party files and added original >> >> license headers. >> >> - Created a licenses directory and added copies of third-party >> licenses. >> >> - Replaced the URLs in the LICENSE file with pointers to these local >> files. >> >> - Included these new files in the assembly configuration. >> >> >> >> These changes are listed here (I will probably squash them into a >> single >> >> release commit): >> >> https://github.com/apache/incubator-baremaps/pull/905/files >> >> >> >> Thank you very much for helping with these changes. Please don't >> hesitate >> >> to provide additional feedback if needed. >> >> >> >> Best regards, >> >> >> >> Bertil >> >> >> >>> On 23 Nov 2024, at 22:50, Justin Mclean >> >> wrote: >> >>> >> >>> HI, >> >>> >> According to the documentation [1], what’s currently missing in our >> >> LICENSE file are pointers (“For details, see deps/flatgeobuf”). I >> suggest >> >> to modify the third party section as follow, so we have pointers for >> >> everything. >> >> THIRD PARTY LICENSES: >> >> Code and data produced outside the ASF that is included in the >> distribution of this product is subject to the following >> additional license terms: >> >> - FlatGeobuf, BSD-2-Clause license, see >> >> https://github.com/flatgeobuf/flatgeobuf. >> - GeoPackage Java, MIT License, see >> >> https://github.com/ngageoint/geopackage-java. >> - OSMPBF, MIT License, see >> >> https://github.com/openstreetmap/OSM-binary/pull/35. >> - OSM Test Data, Public domain, see >> >> https://github.
Re: [VOTE] Release Apache Baremaps 0.8.1-rc2 (incubating)
Hello Calvin, Are you referring to the following email? I struggled to find a reference to Netty in the dev mailing-list, but this one related to Hadoop seems to be the most closely related. https://lists.apache.org/thread/h8bbvwm5l9c5n9gzs4prhkrcmj9q5js1 As mentioned, I’ve observed different practices among top-level Apache projects. For example, Hadoop and Spark include LICENSE, LICENSE-binary, NOTICE, and NOTICE-binary files, as well as license and license-binarydirectories. While we could introduce similar directories in Baremaps, I’m concerned that they might quickly become outdated, given that we lack the same level of resources as these large projects. Moreover, even in Hadoop’s case, these files and directories haven’t been updated for four to five years. On the other hand, other top-level projects that depend on Hadoop and Spark (e.g., Drill, Sedona, etc.) seem to follow a simpler approach similar to ours: a LICENSE file listing the dependencies and their licenses. Their NOTICE files also don’t appear to include additional information (though I could be overlooking something). I’d prefer to stick with the simple approach (which is already quite time-consuming :-) as it aligns with what many other projects are doing. If this approach isn’t sufficient, I’d really appreciate gathering broader input so we can define something actionable and maintainable for this release and future ones. Best regards, Bertil > On 25 Nov 2024, at 04:41, Calvin Kirs wrote: > > Hi Bertil, > > In addition to what Justin mentioned, I brought up in the dev mailing list > that the binary release is missing the NOTICE section (at least we omitted > the NOTICE for Netty). > The LICENSE file is also missing and needs to be addressed in the next RC > version. > > On Sun, Nov 24, 2024 at 10:40 PM Bertil Chapuis wrote: > >> Hello Justin, >> >> I believe I now have enough information to release a new candidate. I’m >> closing this vote and will start a new one early next week. >> >> Here is a summary of the corrections I made: >> - Removed the unlicensed fuji.png file and fixed the related tests. >> - Added a missing license header to scripts/generate-flageobuf.sh. >> - Revised the notice file to ensure all paths are correct. >> - Configured Spotless to ignore third-party files and added original >> license headers. >> - Created a licenses directory and added copies of third-party licenses. >> - Replaced the URLs in the LICENSE file with pointers to these local files. >> - Included these new files in the assembly configuration. >> >> These changes are listed here (I will probably squash them into a single >> release commit): >> https://github.com/apache/incubator-baremaps/pull/905/files >> >> Thank you very much for helping with these changes. Please don't hesitate >> to provide additional feedback if needed. >> >> Best regards, >> >> Bertil >> >>> On 23 Nov 2024, at 22:50, Justin Mclean >> wrote: >>> >>> HI, >>> According to the documentation [1], what’s currently missing in our >> LICENSE file are pointers (“For details, see deps/flatgeobuf”). I suggest >> to modify the third party section as follow, so we have pointers for >> everything. THIRD PARTY LICENSES: Code and data produced outside the ASF that is included in the distribution of this product is subject to the following additional license terms: - FlatGeobuf, BSD-2-Clause license, see >> https://github.com/flatgeobuf/flatgeobuf. - GeoPackage Java, MIT License, see >> https://github.com/ngageoint/geopackage-java. - OSMPBF, MIT License, see >> https://github.com/openstreetmap/OSM-binary/pull/35. - OSM Test Data, Public domain, see >> https://github.com/osmcode/osm-testdata. - Mapbox Vector Tile, Creative Commons Public License, see >> https://github.com/mapbox/vector-tile-spec. - Palantir Streams, Apache License 2.0, see >> https://github.com/palantir/streams. - Planetiler, Apache License 2.0, see >> https://github.com/onthegomap/planetiler. - PMTiles, BSD-3-Clause license, see >> https://github.com/protomaps/PMTiles. - pyosmium, BSD 2-Clause "Simplified" License, see >> https://github.com/osmcode/pyosmium. >>> >>> While knowing where the files come from is useful (and it would be best >> to keep that info), the “pointers” mentioned need to be to local files >> containing the license text in full, not to a URL whose content may change. >> This is usually a condition of the license that you need to include its >> text when distributing it. >>> The reason for the notice file is that we never “bundled” a whole >> project into baremaps. Instead, we derived and adapted a couple of files >> from third party projects and included them in our sources. This is the >> reason why we found useful to tell more about it in the NOTICE file. >>> >>> Even if you bundle a single file or a single function from a 3rd party
Re: [VOTE] Release Apache Baremaps 0.8.1-rc2 (incubating)
Hello Calvin, > Yes, but that's something you have to do when releasing binary versions. > I'm not sure if providing a link to indicate the license source in the > LICENSE file would be acceptable. For example, with the MIT License: "The > above copyright notice and this permission notice shall be included in all > copies or substantial portions of the Software." I don't think providing > just a link would work, but perhaps you could check with the ASF legal > team. I silenced my brain and created additional directories (licenses-binary, notices-binary). I manually fetched all the license and notice files for the dependencies declared in the managed dependencies section of our pom.xml file (the Maven License Plugin is rarely able to download the actual licenses). https://github.com/apache/incubator-baremaps/pull/905/commits/f86ca06dbc57bccf29134482cb3fc57b72575a42#diff-cca02cc6d280041610f60091acaf62720f8db3242e3e82dcfb682ef1ce57ce0c Please, let me know if this is sufficient. > Not all practices of top-level projects are necessarily correct. I haven't > kept up with Sedona, but I raised this issue with Drill last year[2]. > > [1]https://infra.apache.org/licensing-howto.html#binary > [2]https://issues.apache.org/jira/projects/DRILL/issues/DRILL-8475 I’m quite sympathetic to the projects that succeed with a simpler approach, and I think I understand why they try to avoid going down this rabbit hole… ;-) Best, Bertil - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Baremaps 0.8.1-rc2 (incubating)
> In the NOTICE file, there is no need for the "product includes / copied files > / derived files” sections. If you want to keep this content, put it in the > README or similar. Ok, I simply removed this content as it is not required: https://github.com/apache/incubator-baremaps/pull/905/commits/af6e40a9860c0b0ce3ea1f670cd180f5bd4f8ca7 Thanks, Bertil - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
AW: [VOTE] Graduate Apache Answer (incubating) as a Top Level Project
+1 (binding) IPMC cdutz I would like to support the graduation. So far, their many releases have been almost spotless and they have been successfully inviting new people into the PPMC as well as committers ranks. I have no doubt, that the project will live up to our standards. Chris Von: Ning Qi Datum: Montag, 25. November 2024 um 04:55 An: general@incubator.apache.org Betreff: [VOTE] Graduate Apache Answer (incubating) as a Top Level Project Hi everyone, Following the positive feedback received on the Answer Vote thread [1](result[2]), I would like to initiate an official Incubator Vote thread now. Here're some facts and project highlights during incubation and the draft resolution are pasted as below. - 9 Apache releases.[3] - 15 language translations. - 4 release managers have helped with the release and updated release file. - 4 new committers and 1 PPMC member. - 104 contributors and 144 translators. - 193 issues resolved and 323 pull requests merged during incubation. - We’ve built a diverse community representing 10 nations and various types of contributions, showcasing active development and community involvement. - All criteria in maturity assessment for Apache Answer have been met.[4] Please vote on the resolution below to graduate Apache Answer from the Incubator to the Top Level Project. +1: Graduate Apache Answer as a TLP +0: No opinion -1: Don't graduate Apache Answer because ... This vote will open for at least 72 hours. We extend our sincere gratitude to everyone who has contributed to the Apache Answer community, including the Apache Incubator community, the Apache Infrastructure team, and the ASF community. Thank you for your participation in Apache Answer's journey. [1] https://lists.apache.org/thread/pwrlbhypjnq9nwd2l6f5406ohp8x9dv4 [2] https://lists.apache.org/thread/pdwgzd4qnlhotn06z19z0vxhhnfcdrnm [3] https://github.com/apache/incubator-answer/releases [4] https://github.com/apache/incubator-answer/wiki/Podling-Maturity-Assessment-for-Apache-Answer --- Establish the Apache Answer 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 Q-and-A platform software for teams at any scales. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Answer Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Answer Project be and hereby is responsible for the creation and maintenance of software related to A Q-and-A platform software for teams at any scales; and be it further RESOLVED, that the office of "Vice President, Apache Answer" 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 Answer Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Answer 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 Answer Project: * Anne Zhu * Christofer Dutz * Enxin Xie * Feng Dong * Fengjun Lv * Guangfu Yang * Justin Mclean * Luffy * Nadia Jiang * Ning Qi * Shuailing Li * Willem Ning Jiang * Yubin Ren * Zili Chen NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ning Qi be appointed to the office of Vice President, Apache Answer, 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 Answer Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Answer podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Answer podling encumbered upon the Apache Incubator PMC are hereafter discharged. --- Thank you. Best Regards, Ning
Re: [VOTE] Graduate Apache Answer (incubating) as a Top Level Project
HI, +1 (binding) jmclean (IPMC) Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Baremaps 0.8.1-rc2 (incubating)
Hi, > Ok, I simply removed this content as it is not required: > https://github.com/apache/incubator-baremaps/pull/905/commits/af6e40a9860c0b0ce3ea1f670cd180f5bd4f8ca7 Thanks, that looks good to me. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Answer (incubating) as a Top Level Project
+1（binding） Good luck On Tue, Nov 26, 2024 at 7:23 AM Justin Mclean wrote: > HI, > > +1 (binding) jmclean (IPMC) > > Kind Regards, > Justin > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
