[jira] [Updated] (INCUBATOR-274) Gives Orbit (orbit.love) access to GitHub repos
[ https://issues.apache.org/jira/browse/INCUBATOR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hezheng Yin updated INCUBATOR-274: -- Description: Dear Infra Team, I'm looking to set up Orbit (orbit.love, a community growth platform) for DevLake. I ran into a permission issue when I tried to give Orbit access to DevLake's repos as shown in this [screenshot|https://user-images.githubusercontent.com/2908155/206342490-32d84f00-15df-49d3-b3d4-0b758c4ed3ac.png]. Is there any workaround that may get this integration working? Thanks in advance for your guidance! was: Dear Infra Team, I'm looking to set up Orbit (orbit.love, a community growth platform) for DevLake. I ran into a permission issue when I tried to give Orbit access to DevLake's repos. Is there any workaround that may get this integration working? Thanks in advance for your guidance! > Gives Orbit (orbit.love) access to GitHub repos > --- > > Key: INCUBATOR-274 > URL: https://issues.apache.org/jira/browse/INCUBATOR-274 > Project: Incubator > Issue Type: Task > Components: git >Reporter: Hezheng Yin >Priority: Major > > Dear Infra Team, > > I'm looking to set up Orbit (orbit.love, a community growth platform) for > DevLake. I ran into a permission issue when I tried to give Orbit access to > DevLake's repos as shown in this > [screenshot|https://user-images.githubusercontent.com/2908155/206342490-32d84f00-15df-49d3-b3d4-0b758c4ed3ac.png]. > > Is there any workaround that may get this integration working? Thanks in > advance for your guidance! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-274) Gives Orbit (orbit.love) access to GitHub repos
[ https://issues.apache.org/jira/browse/INCUBATOR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hezheng Yin updated INCUBATOR-274: -- Description: Dear Infra Team, I'm looking to set up Orbit (orbit.love, a community growth platform) for DevLake. I ran into a permission issue when I tried to give Orbit access to DevLake's repos as shown below: Is there any workaround that may get this integration working? Thanks in advance for your guidance! was: Dear Infra Team, I'm looking to set up Orbit (orbit.love, a community growth platform) for DevLake. I ran into a permission issue when I tried to give Orbit access to DevLake's repos as shown below: !image-2022-12-07-18-31-47-181.png|width=950,height=1012! Is there any workaround that may get this integration working? Thanks in advance for your guidance! > Gives Orbit (orbit.love) access to GitHub repos > --- > > Key: INCUBATOR-274 > URL: https://issues.apache.org/jira/browse/INCUBATOR-274 > Project: Incubator > Issue Type: Task > Components: git >Reporter: Hezheng Yin >Priority: Major > > Dear Infra Team, > > I'm looking to set up Orbit (orbit.love, a community growth platform) for > DevLake. I ran into a permission issue when I tried to give Orbit access to > DevLake's repos as shown below: > > > > Is there any workaround that may get this integration working? Thanks in > advance for your guidance! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-274) Gives Orbit (orbit.love) access to GitHub repos
[ https://issues.apache.org/jira/browse/INCUBATOR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hezheng Yin updated INCUBATOR-274: -- Description: Dear Infra Team, I'm looking to set up Orbit (orbit.love, a community growth platform) for DevLake. I ran into a permission issue when I tried to give Orbit access to DevLake's repos. Is there any workaround that may get this integration working? Thanks in advance for your guidance! was: Dear Infra Team, I'm looking to set up Orbit (orbit.love, a community growth platform) for DevLake. I ran into a permission issue when I tried to give Orbit access to DevLake's repos as shown below: Is there any workaround that may get this integration working? Thanks in advance for your guidance! > Gives Orbit (orbit.love) access to GitHub repos > --- > > Key: INCUBATOR-274 > URL: https://issues.apache.org/jira/browse/INCUBATOR-274 > Project: Incubator > Issue Type: Task > Components: git >Reporter: Hezheng Yin >Priority: Major > > Dear Infra Team, > > I'm looking to set up Orbit (orbit.love, a community growth platform) for > DevLake. I ran into a permission issue when I tried to give Orbit access to > DevLake's repos. > > > > Is there any workaround that may get this integration working? Thanks in > advance for your guidance! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Updated] (INCUBATOR-274) Gives Orbit (orbit.love) access to GitHub repos
[ https://issues.apache.org/jira/browse/INCUBATOR-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hezheng Yin updated INCUBATOR-274: -- Description: Dear Infra Team, I'm looking to set up Orbit (orbit.love, a community growth platform) for DevLake. I ran into a permission issue when I tried to give Orbit access to DevLake's repos as shown below: !image-2022-12-07-18-31-47-181.png|width=950,height=1012! Is there any workaround that may get this integration working? Thanks in advance for your guidance! was: Dear Infra Team, I'm looking to set up Orbit (orbit.love, a community growth platform) for DevLake. I ran into a permission issue when I tried to give Orbit access to DevLake's repos as shown below: !image-2022-12-07-18-27-43-771.png|width=598,height=637! Is there any workaround that may get this integration working? Thanks in advance for your guidance! > Gives Orbit (orbit.love) access to GitHub repos > --- > > Key: INCUBATOR-274 > URL: https://issues.apache.org/jira/browse/INCUBATOR-274 > Project: Incubator > Issue Type: Task > Components: git >Reporter: Hezheng Yin >Priority: Major > > Dear Infra Team, > > I'm looking to set up Orbit (orbit.love, a community growth platform) for > DevLake. I ran into a permission issue when I tried to give Orbit access to > DevLake's repos as shown below: > > !image-2022-12-07-18-31-47-181.png|width=950,height=1012! > > Is there any workaround that may get this integration working? Thanks in > advance for your guidance! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-274) Gives Orbit (orbit.love) access to GitHub repos
Hezheng Yin created INCUBATOR-274: - Summary: Gives Orbit (orbit.love) access to GitHub repos Key: INCUBATOR-274 URL: https://issues.apache.org/jira/browse/INCUBATOR-274 Project: Incubator Issue Type: Task Components: git Reporter: Hezheng Yin Dear Infra Team, I'm looking to set up Orbit (orbit.love, a community growth platform) for DevLake. I ran into a permission issue when I tried to give Orbit access to DevLake's repos as shown below: !image-2022-12-07-18-27-43-771.png|width=598,height=637! Is there any workaround that may get this integration working? Thanks in advance for your guidance! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Uniffle (Incubating) 0.6.1-rc3
> What are the reason for these? btw, if this is from the Apache Spark > project you might need to attribute it in LICENSE. > > apache-uniffle-0.6.1-incubating-src/spark-patches/spark-3.1.2_dynamic_allocation_support.patch > apache-uniffle-0.6.1-incubating-src/spark-patches/spark-2.4.6_dynamic_allocation_support.patch > apache-uniffle-0.6.1-incubating-src/spark-patches/spark-3.2.1_dynamic_allocation_support.patch Thanks Felix for checking. These patches are not from Apache Spark. Instead, it is for our users to patch Apache Spark to enable more features of Uniffle. Kaijie - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Uniffle (Incubating) 0.6.1-rc3
+1 (binding) [x] incubating in name [x] signature and hash fine [x] DISCLAIMER is fine [x] LICENSE and NOTICE are fine [x] No unexpected binary files [x] All source files have ASF headers [x] Can be built from source Best, Jerry Felix Cheung 于2022年12月8日周四 09:05写道： > +1 (binding) > > - incubating in name > - signature and hash fine > - DISCLAIMER is fine > - LICENSE and NOTICE are fine > - No unexpected binary files > - All source files have ASF headers > > What are the reason for these? btw, if this is from the Apache Spark > project you might need to attribute it in LICENSE. > > > apache-uniffle-0.6.1-incubating-src/spark-patches/spark-3.1.2_dynamic_allocation_support.patch > > apache-uniffle-0.6.1-incubating-src/spark-patches/spark-2.4.6_dynamic_allocation_support.patch > > apache-uniffle-0.6.1-incubating-src/spark-patches/spark-3.2.1_dynamic_allocation_support.patch > > > On Wed, Dec 7, 2022 at 7:47 AM Xianjin YE wrote: > > > +1 from my side. > > - Download links are valid > > - Building and unit tests are ok. > > > > > On Dec 7, 2022, at 18:53, Charles Zhang > wrote: > > > > > > +1(non-binding) from me, and I checked the following items: > > > > > > - [X] Download links are valid. > > > - [X] Checksums and PGP signatures are valid. > > > - [X] All files have license headers if necessary. > > > - [X] No compiled archives bundled in the source archive. > > > - [X] Building is OK. > > > > > > Best wishes, > > > Charles Zhang > > > from Apache InLong > > > > > > > > > Kent Yao 于2022年12月7日周三 17:26写道： > > > > > >> +1(non-binding) > > >> > > >> - Download links are valid > > >> - Signatures are OK > > >> - Checksums are OK > > >> - LICENSE, NOTICE, and DISCLAIMER are OK > > >> - Successfully passes UT > > >> > > >> Kent Yao > > >> > > >> On 2022/12/07 02:19:36 He Qi wrote: > > >>> From my side > > >>> +1 > > >>> > > >>> I have checked > > >>> * Download links, checksums and PGP signatures are valid > > >>> * LICENSE, NOTICE and DISCLAIMER-WIP files are correct > > >>> * No unlicensed compiled archives bundled in source archive. > > >>> * UT passed. I use the command `mvn package -Pspark3 > > >>> > > >>> On 2022/12/06 05:56:13 Kaijie Chen wrote: > > Hello Incubator Community, > > > > This is a call for a vote to release Apache Uniffle (Incubating) > > version 0.6.1-rc3. > > > > The Apache Uniffle community has voted on and approved a proposal to > > release Apache Uniffle (Incubating) version 0.6.1-rc3. > > > > We now kindly request the Incubator PMC members review and vote on > > this > > incubator release. > > > > Uniffle community vote thread: > > https://lists.apache.org/thread/sorpwljxl2nssowhloswo662jng5qwr7 > > > > Vote result thread: > > https://lists.apache.org/thread/4k9v3n6fvtmd3y37jhof2t6kb90qjg36 > > > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.6.1-rc3/ > > > > Git tag for the release: > > https://github.com/apache/incubator-uniffle/tree/v0.6.1-rc3 > > > > Release notes: > > https://uniffle.apache.org/download/release-notes-0.6.1/ > > > > The artifacts signed with PGP key > > 3B8167D035D33A4C2D725FAA39A39E985C5EFBA4 > > corresponding to c...@apache.org, that can be found in keys file: > > https://dist.apache.org/repos/dist/dev/incubator/uniffle/KEYS > > > > The vote will be open for at least 72 hours or until the necessary > > number of votes are reached. > > > > Please vote accordingly: > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks, > > Kaijie Chen > > On behalf of Apache Uniffle (Incubating) community > > > > > - > > 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 > > > > >
Re: [VOTE] Release Apache Uniffle (Incubating) 0.6.1-rc3
+1 (binding) - incubating in name - signature and hash fine - DISCLAIMER is fine - LICENSE and NOTICE are fine - No unexpected binary files - All source files have ASF headers What are the reason for these? btw, if this is from the Apache Spark project you might need to attribute it in LICENSE. apache-uniffle-0.6.1-incubating-src/spark-patches/spark-3.1.2_dynamic_allocation_support.patch apache-uniffle-0.6.1-incubating-src/spark-patches/spark-2.4.6_dynamic_allocation_support.patch apache-uniffle-0.6.1-incubating-src/spark-patches/spark-3.2.1_dynamic_allocation_support.patch On Wed, Dec 7, 2022 at 7:47 AM Xianjin YE wrote: > +1 from my side. > - Download links are valid > - Building and unit tests are ok. > > > On Dec 7, 2022, at 18:53, Charles Zhang wrote: > > > > +1(non-binding) from me, and I checked the following items: > > > > - [X] Download links are valid. > > - [X] Checksums and PGP signatures are valid. > > - [X] All files have license headers if necessary. > > - [X] No compiled archives bundled in the source archive. > > - [X] Building is OK. > > > > Best wishes, > > Charles Zhang > > from Apache InLong > > > > > > Kent Yao 于2022年12月7日周三 17:26写道： > > > >> +1(non-binding) > >> > >> - Download links are valid > >> - Signatures are OK > >> - Checksums are OK > >> - LICENSE, NOTICE, and DISCLAIMER are OK > >> - Successfully passes UT > >> > >> Kent Yao > >> > >> On 2022/12/07 02:19:36 He Qi wrote: > >>> From my side > >>> +1 > >>> > >>> I have checked > >>> * Download links, checksums and PGP signatures are valid > >>> * LICENSE, NOTICE and DISCLAIMER-WIP files are correct > >>> * No unlicensed compiled archives bundled in source archive. > >>> * UT passed. I use the command `mvn package -Pspark3 > >>> > >>> On 2022/12/06 05:56:13 Kaijie Chen wrote: > Hello Incubator Community, > > This is a call for a vote to release Apache Uniffle (Incubating) > version 0.6.1-rc3. > > The Apache Uniffle community has voted on and approved a proposal to > release Apache Uniffle (Incubating) version 0.6.1-rc3. > > We now kindly request the Incubator PMC members review and vote on > this > incubator release. > > Uniffle community vote thread: > https://lists.apache.org/thread/sorpwljxl2nssowhloswo662jng5qwr7 > > Vote result thread: > https://lists.apache.org/thread/4k9v3n6fvtmd3y37jhof2t6kb90qjg36 > > The release candidate: > https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.6.1-rc3/ > > Git tag for the release: > https://github.com/apache/incubator-uniffle/tree/v0.6.1-rc3 > > Release notes: > https://uniffle.apache.org/download/release-notes-0.6.1/ > > The artifacts signed with PGP key > 3B8167D035D33A4C2D725FAA39A39E985C5EFBA4 > corresponding to c...@apache.org, that can be found in keys file: > https://dist.apache.org/repos/dist/dev/incubator/uniffle/KEYS > > The vote will be open for at least 72 hours or until the necessary > number of votes are reached. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > Kaijie Chen > On behalf of Apache Uniffle (Incubating) community > > - > 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 > >
Re: [VOTE] Apache Tuweni graduation
We have also recently seen long term incubating projects with considerable adoption falter. I consider the fact that they did not graduate early enough a contributing factor here. Nothing wrong with incubation but staying in the incubator and encountering attrition is different from TLP with some churn with new folks coming into an official TLP project while others can fall off in a healthy way. Again, having the community test and release 14 separate releases demonstrates contributors in the community even if they aren't all materially contributing code. On Wed, Dec 7, 2022 at 3:45 AM Christofer Dutz wrote: > Hi all, > > And in the last few months the ASF has sadly seen enough cases, in which > even big projects suffered from the lack of diversity. > So, I would also consider this to be a blocker. > > Community building isn’t something that happens or comes for free. > It’s actually hard work, but it needs to be done. > > Just my opinion on this topic. > > Chris > > From: Willem Jiang > Date: Wednesday, 7. December 2022 at 02:59 > To: general@incubator.apache.org > Subject: Re: [VOTE] Apache Tuweni graduation > It looks like we need a dedicated community leader[1] to build a > diverse community (just borrow a pattern from InnerSource Common[2]). > > " Communication takes up a significant percentage of a community > leader's daily work. At the same time, he or she will likely also have > to spearhead the initial development, too. In the face of limited > capacity, inexperienced leaders will tend to focus on development and > neglect communication. The barrier for potential contributors to make > their first contribution and to commit to the community will be much > higher if the community leader is hard to reach or is slow to respond > to feedback and questions for lack of time." > > [1] > https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/2-structured/dedicated-community-leader.md#forces > [2]https://innersourcecommons.org/ > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Dec 6, 2022 at 9:51 AM larry mccay wrote: > > > > I'm not so sure that I see this as a blocker for graduation. > > There was enough consensus and testing to spin and publish 14 releases. > > There has been healthy conversation about this very topic among the > mentors > > and contributors on the private list. > > > > The nature of this project is that the consumption of these libraries are > > going to get less traction while in incubation and a community may grow > > larger as a TLP as confidence is instilled by that status. > > > > The Tuweni community has demonstrated the ability to publish releases > > within that Apache Way and guidelines, has welcomed new contributors, > etc. > > The long term success will require a larger active community but I don't > > think that needs to block graduation as the incubation goals have been > met. > > > > My 2 cents. > > > > On Mon, Dec 5, 2022 at 7:41 PM Willem Jiang > wrote: > > > > > I agree with Gang Li. The Bus factor[1] of this project is relatively > high. > > > > > > [1]https://en.wikipedia.org/wiki/Bus_factor > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Mon, Dec 5, 2022 at 11:06 PM li gang wrote: > > > > > > > > I checked the contributions of the Tuweni project[1],the traffic of > the > > > > mail list d...@tuweni.apache.org[2] and the KEYS[3]. > > > > > > > > It looks like the project is mainly maintained by Antoine Toulme > self, > > > > I have a concern this is not comply with the diversity. > > > > > > > > [1]https://github.com/apache/incubator-tuweni/graphs/contributors > > > > [2]https://lists.apache.org/list?d...@tuweni.apache.org > > > > [3]https://downloads.apache.org/incubator/tuweni/KEYS > > > > > > > > Antoine Toulme 于2022年12月5日周一 15:14写道： > > > > > > > > > Dear Apache Incubator Community and IPMC members, > > > > > > > > > > We discussed the graduation for Tuweni in the Apache Incubator > > > > > Community [4], where no issues were raised and positive replies > were > > > > > received. > > > > > After having the graduation discussion in the Tuweni community > [1], we > > > > > have passed the vote within Tuweni community [2] and the vote > result > > > > > was published [3]. > > > > > > > > > > I would like to start this voting thread to request graduating > Apache > > > > > Tuweni(incubating) from Apache Incubator as a Top Level Project. > > > > > > > > > > Please provide your vote accordingly: > > > > > [ ] +1 Yes, I support Tuweni project to graduate from the Apache > > > Incubator. > > > > > [ ] +0 No opinion. > > > > > [ ] -1 No, the Tuweni project is not ready to graduate, because... > > > > > > > > > > Thank you for participating in the vote. This vote will stay open > for > > > at > > > > > least 72 hours. > > > > > > > > > > Here is an overview of the Apache Tuweni(incubating) to help with > the > > > > > vote. > > > > > > > > > > *Community* > > > > > > >
Re: [VOTE] Graduate Apache Sedona as an Apache Top Level Project
+1 (binding) Thanks Sunil On Mon, Dec 5, 2022 at 3:25 AM Jia Yu wrote: > Dear Apache Incubator Community, > > Apache Sedona has been incubating since 07-19-2020. For over 2 years, the > Sedona community has made great progress and grown rapidly under the > guidance of our mentors. We believe the Sedona project has met the > conditions for graduation. > > We then discussed the graduation of Sedona in the Apache Incubator > community [13]. The discussion received positive feedback and found no > issues. > > I would like to start this voting thread to request graduating Apache > Sedona (incubating) from Apache Incubator as a Top Level Project. > > Please provide your vote accordingly: > [ ] +1 Yes, I support Sedona project to graduate from the Apache Incubator. > [ ] +0 No opinion. > [ ] -1 No, the Sedona project is not ready to graduate, because... > > Thank you for participating in the vote. This vote will stay open for at > least 72 hours or until at least 3 +1 binding votes are received. > > Thanks, > Jia > > Here is an overview of the Apache Sedona to help with the vote. > > *** > > The incubation status of Sedona can be found in [1]. The Apache Sedona > community has a discussion thread of graduating Sedona to a TLP [2], passed > the community vote [3]. The vote result was announced [4]. The PPMC also > passed a vote [5] to nominate Jia as the chair of Sedona TLP, and the > result was also announced [6]. We had a discussion about Sedona graduation > in the incubator this September [12] and all issues have been fixed. > > The summary on the state of the community is listed below and the self > assessment (Apache Project Maturity Model) is in [7]. > > > Sedona joined the Apache Incubator on July 19 2020. As of Dec 2 2022: > > ** Community **: > > * number of contributions (commits) since incubation: 394 > - Overall: 1083 > - 36% of the commits were added since incubation. > > * number of contributors (and growth since incubation): 51 > - Overall: 86 > - 59% of the contributors joined since incubation > > * email discussions since incubation: 1214 threads on > d...@sedona.apache.org > > * Number of monthly downloads: grow from 200K per month to 800K per month. > > * Marked as critical project on PyPi as Sedona ranks among top 1% most > downloaded Python projects on PyPi. > > ** Project ** > > * releases: 7 > > * number of release managers: 3 (Jia Yu, Paweł Kociński, Kanchan Chowdhury) > > * Apache Sedona website (sedona.apache.org) is compliant with ASF > requirement [8]. The GitHub.com used in external resources are compliant > with ASF privacy requirement [9] > > ** Brands ,License, and Copyright ** > > * We submitted an application for the brand [10] and it has been > reviewed and approved. > > * Apache Sedona community maintains project code on GitHub, and all > modules > code is under Apache 2.0 license. We have reviewed all the > dependencies and ensured they do not bring any license issues [11]. All > the status files, license headers, and copyright are up to date. > > ** PPMC members > > * Please see the proposed board resolution below and let us know what you > think. The initial PMC members were passed by the vote [5] and the result > was also announced [6]. > > * affiliations of the current PPMC members of Sedona: 11 PPMC from 10 > different organizations > Adam Binford: Maxar > Kanchan Chowdhury: Arizona State University > Paweł Kociński: GetInData > Yitao Li: SafeGraph > Netanel Malka: Upstream Security > Mohamed Sarwat: Wherobots Inc. > Kengo Seki: NTT Data > Sachio Wakai: KDDI > Jinxuan Wu: Bloomberg LP > Jia Yu: Wherobots Inc. > Zongsi Zhang: Grab > > * new PPMC members since incubation: 5 > Adam Binford: Maxar > Kanchan Chowdhury: Arizona State University > Yitao Li: SafeGraph > Sachio Wakai: KDDI > Kengo Seki: NTT Data > > * Pending new PPMC members (due to pending CCLAs): 1 > Magdalena Wójciak: Billennium > > ** Graduation Resolution ** > > Establish the Apache Sedona 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 big geospatial data processing engine. It provides an easy > to use APIs for spatial data scientists to manage, wrangle, and process > geospatial data. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache Sedona Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache Sedona Project be and hereby is responsible > for the creation and maintenance of software related to a big geospatial > data processing engine. It provides an easy to use APIs for spatial data > scientists to manage, wrangle, and process geospatial data; and be it > further > > RESOLVED, that the
Re: [VOTE] Release Apache Uniffle (Incubating) 0.6.1-rc3
+1 from my side. - Download links are valid - Building and unit tests are ok. > On Dec 7, 2022, at 18:53, Charles Zhang wrote: > > +1(non-binding) from me, and I checked the following items: > > - [X] Download links are valid. > - [X] Checksums and PGP signatures are valid. > - [X] All files have license headers if necessary. > - [X] No compiled archives bundled in the source archive. > - [X] Building is OK. > > Best wishes, > Charles Zhang > from Apache InLong > > > Kent Yao 于2022年12月7日周三 17:26写道： > >> +1(non-binding) >> >> - Download links are valid >> - Signatures are OK >> - Checksums are OK >> - LICENSE, NOTICE, and DISCLAIMER are OK >> - Successfully passes UT >> >> Kent Yao >> >> On 2022/12/07 02:19:36 He Qi wrote: >>> From my side >>> +1 >>> >>> I have checked >>> * Download links, checksums and PGP signatures are valid >>> * LICENSE, NOTICE and DISCLAIMER-WIP files are correct >>> * No unlicensed compiled archives bundled in source archive. >>> * UT passed. I use the command `mvn package -Pspark3 >>> >>> On 2022/12/06 05:56:13 Kaijie Chen wrote: Hello Incubator Community, This is a call for a vote to release Apache Uniffle (Incubating) version 0.6.1-rc3. The Apache Uniffle community has voted on and approved a proposal to release Apache Uniffle (Incubating) version 0.6.1-rc3. We now kindly request the Incubator PMC members review and vote on this incubator release. Uniffle community vote thread: https://lists.apache.org/thread/sorpwljxl2nssowhloswo662jng5qwr7 Vote result thread: https://lists.apache.org/thread/4k9v3n6fvtmd3y37jhof2t6kb90qjg36 The release candidate: https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.6.1-rc3/ Git tag for the release: https://github.com/apache/incubator-uniffle/tree/v0.6.1-rc3 Release notes: https://uniffle.apache.org/download/release-notes-0.6.1/ The artifacts signed with PGP key 3B8167D035D33A4C2D725FAA39A39E985C5EFBA4 corresponding to c...@apache.org, that can be found in keys file: https://dist.apache.org/repos/dist/dev/incubator/uniffle/KEYS The vote will be open for at least 72 hours or until the necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Thanks, Kaijie Chen On behalf of Apache Uniffle (Incubating) community - 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
Re: [VOTE] Release Apache Uniffle (Incubating) 0.6.1-rc3
+1(non-binding) from me, and I checked the following items: - [X] Download links are valid. - [X] Checksums and PGP signatures are valid. - [X] All files have license headers if necessary. - [X] No compiled archives bundled in the source archive. - [X] Building is OK. Best wishes, Charles Zhang from Apache InLong Kent Yao 于2022年12月7日周三 17:26写道： > +1(non-binding) > > - Download links are valid > - Signatures are OK > - Checksums are OK > - LICENSE, NOTICE, and DISCLAIMER are OK > - Successfully passes UT > > Kent Yao > > On 2022/12/07 02:19:36 He Qi wrote: > > From my side > > +1 > > > > I have checked > > * Download links, checksums and PGP signatures are valid > > * LICENSE, NOTICE and DISCLAIMER-WIP files are correct > > * No unlicensed compiled archives bundled in source archive. > > * UT passed. I use the command `mvn package -Pspark3 > > > > On 2022/12/06 05:56:13 Kaijie Chen wrote: > > > Hello Incubator Community, > > > > > > This is a call for a vote to release Apache Uniffle (Incubating) > > > version 0.6.1-rc3. > > > > > > The Apache Uniffle community has voted on and approved a proposal to > > > release Apache Uniffle (Incubating) version 0.6.1-rc3. > > > > > > We now kindly request the Incubator PMC members review and vote on this > > > incubator release. > > > > > > Uniffle community vote thread: > > > https://lists.apache.org/thread/sorpwljxl2nssowhloswo662jng5qwr7 > > > > > > Vote result thread: > > > https://lists.apache.org/thread/4k9v3n6fvtmd3y37jhof2t6kb90qjg36 > > > > > > The release candidate: > > > https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.6.1-rc3/ > > > > > > Git tag for the release: > > > https://github.com/apache/incubator-uniffle/tree/v0.6.1-rc3 > > > > > > Release notes: > > > https://uniffle.apache.org/download/release-notes-0.6.1/ > > > > > > The artifacts signed with PGP key > > > 3B8167D035D33A4C2D725FAA39A39E985C5EFBA4 > > > corresponding to c...@apache.org, that can be found in keys file: > > > https://dist.apache.org/repos/dist/dev/incubator/uniffle/KEYS > > > > > > The vote will be open for at least 72 hours or until the necessary > > > number of votes are reached. > > > > > > Please vote accordingly: > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with the reason > > > > > > Thanks, > > > Kaijie Chen > > > On behalf of Apache Uniffle (Incubating) community > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Uniffle (Incubating) 0.6.1-rc3
+1(non-binding) - Download links are valid - Signatures are OK - Checksums are OK - LICENSE, NOTICE, and DISCLAIMER are OK - Successfully passes UT Kent Yao On 2022/12/07 02:19:36 He Qi wrote: > From my side > +1 > > I have checked > * Download links, checksums and PGP signatures are valid > * LICENSE, NOTICE and DISCLAIMER-WIP files are correct > * No unlicensed compiled archives bundled in source archive. > * UT passed. I use the command `mvn package -Pspark3 > > On 2022/12/06 05:56:13 Kaijie Chen wrote: > > Hello Incubator Community, > > > > This is a call for a vote to release Apache Uniffle (Incubating) > > version 0.6.1-rc3. > > > > The Apache Uniffle community has voted on and approved a proposal to > > release Apache Uniffle (Incubating) version 0.6.1-rc3. > > > > We now kindly request the Incubator PMC members review and vote on this > > incubator release. > > > > Uniffle community vote thread: > > https://lists.apache.org/thread/sorpwljxl2nssowhloswo662jng5qwr7 > > > > Vote result thread: > > https://lists.apache.org/thread/4k9v3n6fvtmd3y37jhof2t6kb90qjg36 > > > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.6.1-rc3/ > > > > Git tag for the release: > > https://github.com/apache/incubator-uniffle/tree/v0.6.1-rc3 > > > > Release notes: > > https://uniffle.apache.org/download/release-notes-0.6.1/ > > > > The artifacts signed with PGP key > > 3B8167D035D33A4C2D725FAA39A39E985C5EFBA4 > > corresponding to c...@apache.org, that can be found in keys file: > > https://dist.apache.org/repos/dist/dev/incubator/uniffle/KEYS > > > > The vote will be open for at least 72 hours or until the necessary > > number of votes are reached. > > > > Please vote accordingly: > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks, > > Kaijie Chen > > On behalf of Apache Uniffle (Incubating) community > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] KIE Proposal
Hi Jason, now this looks a lot more like something we can help support :-) And projects don’t necessarily have to be mono repos. Stuff like examples, project websites … that’s quite common to be in separate repositories. I guess the amount of additional work would not be that much … yeah … the reports have to be written, but most use templates for that and just fill in special things being noted. Writing the reports for a project usually doesn’t take much time. Regarding setting up of infra … I guess you would go a GitHub approach and not sign up for Jira and Confluence now that public user registrations are disabled. I would dare to say the amount of work to set this up for one project and multiple project would be identical. Chris From: Jason Porter Date: Tuesday, 6. December 2022 at 17:27 To: general@incubator.apache.org Subject: Re: [DISCUSS] KIE Proposal > On Dec 6, 2022, at 01:43, Christofer Dutz wrote: > > Hi Jason, > > Well, those numbers are a bit better than the initial ones. > Thing is: Mentors will not only have to help onboard people to Apache and > teach them how to do things, if they are doing their job correctly, they > should also really audit the releases being done and help get the codebase > into shape first. > > Even with 12 sub-projects, work-wise that would put a load on the mentors, as > if they signed up for mentoring 12 projects. > > So how about bringing in projects separately (where it makes sense)? There > each project could have their initial PPMC and committer lists and it would > spread out the load a bit. However I would expect staffing 12 projects with > enough work-willing mentors will still be challenging and I would assume not > all of them to find enough of them, but it could be one first step. > > Or is there an advantage of considering all projects as one unity? > > Chris > > [snip] That is part of a broader question. Some of those repos are things like examples for kogito, the website, etc. Things that are part of the projects themselves, but don’t have a life outside of the project to which they belong. I understand we’ll probably have to collapse the structures within Apache and have a single repo per project. What we’re really looking at as far as projects being donated: Kogito Drools jBPM Then there are the supporting repos for things like examples, docs, website, tooling, etc. Many of the people working on these projects work on all of them, so it would probably be the same group of people with very little deviation in the list of committers. Could they be different PPMCs, but they’d basically be the same group, just more work with the reports, setup, infra, etc. Jason Porter Software Engineer He/Him/His IBMB�CB��[��X��ܚX�KK[XZ[ ��[�\�[ ][��X��ܚX�P[��X�]܋�\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[ ��[�\�[ Z[ [��X�]܋�\X�K�ܙ�B
Re: [VOTE] Apache Tuweni graduation
Hi all, And in the last few months the ASF has sadly seen enough cases, in which even big projects suffered from the lack of diversity. So, I would also consider this to be a blocker. Community building isn’t something that happens or comes for free. It’s actually hard work, but it needs to be done. Just my opinion on this topic. Chris From: Willem Jiang Date: Wednesday, 7. December 2022 at 02:59 To: general@incubator.apache.org Subject: Re: [VOTE] Apache Tuweni graduation It looks like we need a dedicated community leader[1] to build a diverse community (just borrow a pattern from InnerSource Common[2]). " Communication takes up a significant percentage of a community leader's daily work. At the same time, he or she will likely also have to spearhead the initial development, too. In the face of limited capacity, inexperienced leaders will tend to focus on development and neglect communication. The barrier for potential contributors to make their first contribution and to commit to the community will be much higher if the community leader is hard to reach or is slow to respond to feedback and questions for lack of time." [1]https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/2-structured/dedicated-community-leader.md#forces [2]https://innersourcecommons.org/ Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Dec 6, 2022 at 9:51 AM larry mccay wrote: > > I'm not so sure that I see this as a blocker for graduation. > There was enough consensus and testing to spin and publish 14 releases. > There has been healthy conversation about this very topic among the mentors > and contributors on the private list. > > The nature of this project is that the consumption of these libraries are > going to get less traction while in incubation and a community may grow > larger as a TLP as confidence is instilled by that status. > > The Tuweni community has demonstrated the ability to publish releases > within that Apache Way and guidelines, has welcomed new contributors, etc. > The long term success will require a larger active community but I don't > think that needs to block graduation as the incubation goals have been met. > > My 2 cents. > > On Mon, Dec 5, 2022 at 7:41 PM Willem Jiang wrote: > > > I agree with Gang Li. The Bus factor[1] of this project is relatively high. > > > > [1]https://en.wikipedia.org/wiki/Bus_factor > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Mon, Dec 5, 2022 at 11:06 PM li gang wrote: > > > > > > I checked the contributions of the Tuweni project[1],the traffic of the > > > mail list d...@tuweni.apache.org[2] and the KEYS[3]. > > > > > > It looks like the project is mainly maintained by Antoine Toulme self, > > > I have a concern this is not comply with the diversity. > > > > > > [1]https://github.com/apache/incubator-tuweni/graphs/contributors > > > [2]https://lists.apache.org/list?d...@tuweni.apache.org > > > [3]https://downloads.apache.org/incubator/tuweni/KEYS > > > > > > Antoine Toulme 于2022年12月5日周一 15:14写道： > > > > > > > Dear Apache Incubator Community and IPMC members, > > > > > > > > We discussed the graduation for Tuweni in the Apache Incubator > > > > Community [4], where no issues were raised and positive replies were > > > > received. > > > > After having the graduation discussion in the Tuweni community [1], we > > > > have passed the vote within Tuweni community [2] and the vote result > > > > was published [3]. > > > > > > > > I would like to start this voting thread to request graduating Apache > > > > Tuweni(incubating) from Apache Incubator as a Top Level Project. > > > > > > > > Please provide your vote accordingly: > > > > [ ] +1 Yes, I support Tuweni project to graduate from the Apache > > Incubator. > > > > [ ] +0 No opinion. > > > > [ ] -1 No, the Tuweni project is not ready to graduate, because... > > > > > > > > Thank you for participating in the vote. This vote will stay open for > > at > > > > least 72 hours. > > > > > > > > Here is an overview of the Apache Tuweni(incubating) to help with the > > > > vote. > > > > > > > > *Community* > > > > > > > > ● The PPMC is active, with PMC members voting for graduation along with > > > > mentors. > > > > ● 6 new committers were added, bringing the total number of committers > > to > > > > 14 from 12 different > > > > organizations. > > > > ● The number of contributors is now 25 and growing. > > > > ● The dev@Tuweni mailing list currently has 33 subscribers [4]. > > > > > > > > *Project* > > > > > > > > ● Apache Tuweni (incubating) 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 > > > > primitives, and lots of other helpful utilities. Tuweni is developed > > for > > > > JDK 11 or higher. > > > >
