Re: [DISCUSS] Graduate Apache Sedona to a Top Level Project
Dear Calvin, Thank you for your feedback. We really appreciate it and will definitely fix the items you mentioned. Although we can wait until the next release, we'd like to take this opportunity to collect feedback from the incubator community. So we can make sure all issues are fixed. Hi everyone, please feel free to give us feedback so we can make everything right next time! Regards, Jia On Wed, Sep 14, 2022 at 6:26 PM Calvin Kirs wrote: > To sum up, > > I don't think this is the best time to graduate. > > At least we need a non-WIP-DISCLAIMER version. and we could confirm > that PPMC can check the release, and other issues can be resolved. > > Calvin Kirs 于2022年9月15日周四 09:15写道： > > > > Hi, > > > > The website still has some problems: > > [1]Should not include corporate affiliations of actual contributors. > > > > The homepage[2] should also not contain (Our users and code > > contributors are from) some third-party company logos. > > [1]https://sedona.apache.org/community/contributor/ > > [2]https://sedona.apache.org > > > > Jia Yu 于2022年9月15日周四 05:15写道： > > > > > > Dear Calvin, > > > > > > Thank you for your quick response. > > > > > > To your questions, > > > > > > 1. The DBI dependency in R is not mandatory. Our PPMC Yitao is working > on > > > the doc and will mark it as optional soon. > > > 2. As described in my email, the external resources are " > api.github.com" > > > which are used to get the number of stars and forks of our GitHub repo. > > > Based on ASF privacy policy [1], GitHub.com is considered fully > supports > > > GDPR. *Do you think we still should remove these api calls?* > > > 3. Yes, we admit that the voting information from PPMC should be > improved. > > > We will require all PPMCs to provide items they check from now on. But > I > > > believe our PPMCs already know how to check the release. The vote > guideline > > > was published on April 5 2022, which was 5 months ago. > > > 4. Our mentor George Percivall subscribed to the private channel using > > > perciv...@ogc.org but not his ASF email. But indeed he is not active > in our > > > community, we will remove him from our mentor list. Regarding the 4 > PPMC > > > who didn't link their GitHub account, they still actively participate > in > > > the community including voting and discussion (except Zongsi Zhang, who > > > will be removed in TLP PMC). They also create PRs on our GitHub and > then > > > other members merge the PRs. I have urged them to link their GitHub > account > > > ASAP. > > > 5. DISCLAIMER-WIP was used in our last release (1.2.1). We are now > using > > > the standard DISCLAIMER and it will be put in the next release. See our > > > commit [3] > > > > > > Hope my answers can address your concerns! > > > > > > Thanks, > > > Jia > > > > > > [1] Apache Software Foundation privacy policy: > > > https://privacy.apache.org/policies/privacy-policy-public.html > > > [2] Sedona community vote guideline first commit: > > > > https://github.com/apache/incubator-sedona/commit/6afe7785ae4fbbb2e18c272b0375458a10f2a61d > > > [3] Use standard DISCLAIMER commit: > > > > https://github.com/apache/incubator-sedona/commit/26d65d4e7f5add374c8089dfdf974d7cb830ee01 > > > > > > On Wed, Sep 14, 2022 at 12:16 AM Calvin Kirs wrote: > > > > > > > -1 （binding） > > > > > > > > As well as those mentioned above, the latest released version [1], > > > > did not use the standard disclaimer text. > > > > > > > > [1] > > > > > https://www.apache.org/dyn/closer.lua/incubator/sedona/1.2.1-incubating/apache-sedona-1.2.1-incubating-src.tar.gz > > > > > > > > Calvin Kirs 于2022年9月14日周三 13:15写道： > > > > > > > > > > Hi, > > > > > > > > > > I have a few questions: > > > > > > > > > > The first: a quick look [1] > > > > > > > > > > DBI (https://github.com/r-dbi/DBI): LGPL 2.1. Sedona R depends > on > > > > > this. But we do not deliver DBI in our source code and binary. > > > > > > > > > > Is this a mandatory dependency? > > > > > > > > > > Second: the website still has some small problems: [2] > > > > > > > > > > The third one: Check the recent version release voting [3]. There > is > > > > > basically no valid voting information in the community voting. Do > > > > > community members really know how to check the version release? The > > > > > documentation guidelines for version releases it was only recently > > > > > released. > > > > > > > > > > The last one: You have one mentor who has not subscribed to the > > > > > private mailing group, and four PPMCs who have not linked their > GitHub > > > > > accounts. How can they contribute? (maybe because of contributions > > > > > from other fields, I'm not surprised, but wanted to confirm) > > > > > > > > > > > > > > > [1]https://issues.apache.org/jira/browse/SEDONA-81 > > > > > [2]https://whimsy.apache.org/pods/project/sedona > > > > > [3] > https://lists.apache.org/thread/511gjndxmdxh4g2rzwyxppjc00orz3s3 > > > > > > > > > > Jia Yu 于2022年9月14日周三 10:40写道： > > > > > > > > > > > > Dear Apache
Re: [MENTORS] Late podling reports and missing signoffs
Thanks Calvin! I’ll alert mentors to the move! Joshua Poore > On Sep 14, 2022, at 8:39 PM, Calvin Kirs wrote: > > Joshua Poore 于2022年9月15日周四 08:21写道： >> >> Thanks Justin! >> >> I didn’t see a record for Flagon in the Sept report… OK to paste back in on >> my end? > > hi, I have copied the report from the OCT report. (I deleted the > previous record due to no submission due), thank you for your > submission. >> >> Josh >> >> Joshua Poore >> >> On Sep 14, 2022, at 6:24 PM, Justin Mclean wrote: >>> >>> Hi, >>> Apologies RE Flagon reporting. Just missed the window for SEPT. I have added a report for OCT and requested Mentor review earlier. >>> >>> You still have a couple of day in which you could submit it. >>> >>> Kind Regards, >>> Justin >>> - >>> 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 >> > > > -- > 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] Graduate Apache Sedona to a Top Level Project
To sum up, I don't think this is the best time to graduate. At least we need a non-WIP-DISCLAIMER version. and we could confirm that PPMC can check the release, and other issues can be resolved. Calvin Kirs 于2022年9月15日周四 09:15写道： > > Hi, > > The website still has some problems: > [1]Should not include corporate affiliations of actual contributors. > > The homepage[2] should also not contain (Our users and code > contributors are from) some third-party company logos. > [1]https://sedona.apache.org/community/contributor/ > [2]https://sedona.apache.org > > Jia Yu 于2022年9月15日周四 05:15写道： > > > > Dear Calvin, > > > > Thank you for your quick response. > > > > To your questions, > > > > 1. The DBI dependency in R is not mandatory. Our PPMC Yitao is working on > > the doc and will mark it as optional soon. > > 2. As described in my email, the external resources are "api.github.com" > > which are used to get the number of stars and forks of our GitHub repo. > > Based on ASF privacy policy [1], GitHub.com is considered fully supports > > GDPR. *Do you think we still should remove these api calls?* > > 3. Yes, we admit that the voting information from PPMC should be improved. > > We will require all PPMCs to provide items they check from now on. But I > > believe our PPMCs already know how to check the release. The vote guideline > > was published on April 5 2022, which was 5 months ago. > > 4. Our mentor George Percivall subscribed to the private channel using > > perciv...@ogc.org but not his ASF email. But indeed he is not active in our > > community, we will remove him from our mentor list. Regarding the 4 PPMC > > who didn't link their GitHub account, they still actively participate in > > the community including voting and discussion (except Zongsi Zhang, who > > will be removed in TLP PMC). They also create PRs on our GitHub and then > > other members merge the PRs. I have urged them to link their GitHub account > > ASAP. > > 5. DISCLAIMER-WIP was used in our last release (1.2.1). We are now using > > the standard DISCLAIMER and it will be put in the next release. See our > > commit [3] > > > > Hope my answers can address your concerns! > > > > Thanks, > > Jia > > > > [1] Apache Software Foundation privacy policy: > > https://privacy.apache.org/policies/privacy-policy-public.html > > [2] Sedona community vote guideline first commit: > > https://github.com/apache/incubator-sedona/commit/6afe7785ae4fbbb2e18c272b0375458a10f2a61d > > [3] Use standard DISCLAIMER commit: > > https://github.com/apache/incubator-sedona/commit/26d65d4e7f5add374c8089dfdf974d7cb830ee01 > > > > On Wed, Sep 14, 2022 at 12:16 AM Calvin Kirs wrote: > > > > > -1 （binding） > > > > > > As well as those mentioned above, the latest released version [1], > > > did not use the standard disclaimer text. > > > > > > [1] > > > https://www.apache.org/dyn/closer.lua/incubator/sedona/1.2.1-incubating/apache-sedona-1.2.1-incubating-src.tar.gz > > > > > > Calvin Kirs 于2022年9月14日周三 13:15写道： > > > > > > > > Hi, > > > > > > > > I have a few questions: > > > > > > > > The first: a quick look [1] > > > > > > > > DBI (https://github.com/r-dbi/DBI): LGPL 2.1. Sedona R depends on > > > > this. But we do not deliver DBI in our source code and binary. > > > > > > > > Is this a mandatory dependency? > > > > > > > > Second: the website still has some small problems: [2] > > > > > > > > The third one: Check the recent version release voting [3]. There is > > > > basically no valid voting information in the community voting. Do > > > > community members really know how to check the version release? The > > > > documentation guidelines for version releases it was only recently > > > > released. > > > > > > > > The last one: You have one mentor who has not subscribed to the > > > > private mailing group, and four PPMCs who have not linked their GitHub > > > > accounts. How can they contribute? (maybe because of contributions > > > > from other fields, I'm not surprised, but wanted to confirm) > > > > > > > > > > > > [1]https://issues.apache.org/jira/browse/SEDONA-81 > > > > [2]https://whimsy.apache.org/pods/project/sedona > > > > [3]https://lists.apache.org/thread/511gjndxmdxh4g2rzwyxppjc00orz3s3 > > > > > > > > Jia Yu 于2022年9月14日周三 10:40写道： > > > > > > > > > > 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'd like to start the discussion and > > > collect > > > > > feedback towards graduation. Please feel free to join the discussion. > > > > > > > > > > The discussion will remain open for at least 72 hours. > > > > > > > > > > Thanks, > > > > > Jia > > > > > > > > > > *** > > > > > > > > > > The incubation status of Sedona can be found in [1]. The Apache Sedona > > > > >
Re: [DISCUSS] Graduate Apache Sedona to a Top Level Project
Hi, The website still has some problems: [1]Should not include corporate affiliations of actual contributors. The homepage[2] should also not contain (Our users and code contributors are from) some third-party company logos. [1]https://sedona.apache.org/community/contributor/ [2]https://sedona.apache.org Jia Yu 于2022年9月15日周四 05:15写道： > > Dear Calvin, > > Thank you for your quick response. > > To your questions, > > 1. The DBI dependency in R is not mandatory. Our PPMC Yitao is working on > the doc and will mark it as optional soon. > 2. As described in my email, the external resources are "api.github.com" > which are used to get the number of stars and forks of our GitHub repo. > Based on ASF privacy policy [1], GitHub.com is considered fully supports > GDPR. *Do you think we still should remove these api calls?* > 3. Yes, we admit that the voting information from PPMC should be improved. > We will require all PPMCs to provide items they check from now on. But I > believe our PPMCs already know how to check the release. The vote guideline > was published on April 5 2022, which was 5 months ago. > 4. Our mentor George Percivall subscribed to the private channel using > perciv...@ogc.org but not his ASF email. But indeed he is not active in our > community, we will remove him from our mentor list. Regarding the 4 PPMC > who didn't link their GitHub account, they still actively participate in > the community including voting and discussion (except Zongsi Zhang, who > will be removed in TLP PMC). They also create PRs on our GitHub and then > other members merge the PRs. I have urged them to link their GitHub account > ASAP. > 5. DISCLAIMER-WIP was used in our last release (1.2.1). We are now using > the standard DISCLAIMER and it will be put in the next release. See our > commit [3] > > Hope my answers can address your concerns! > > Thanks, > Jia > > [1] Apache Software Foundation privacy policy: > https://privacy.apache.org/policies/privacy-policy-public.html > [2] Sedona community vote guideline first commit: > https://github.com/apache/incubator-sedona/commit/6afe7785ae4fbbb2e18c272b0375458a10f2a61d > [3] Use standard DISCLAIMER commit: > https://github.com/apache/incubator-sedona/commit/26d65d4e7f5add374c8089dfdf974d7cb830ee01 > > On Wed, Sep 14, 2022 at 12:16 AM Calvin Kirs wrote: > > > -1 （binding） > > > > As well as those mentioned above, the latest released version [1], > > did not use the standard disclaimer text. > > > > [1] > > https://www.apache.org/dyn/closer.lua/incubator/sedona/1.2.1-incubating/apache-sedona-1.2.1-incubating-src.tar.gz > > > > Calvin Kirs 于2022年9月14日周三 13:15写道： > > > > > > Hi, > > > > > > I have a few questions: > > > > > > The first: a quick look [1] > > > > > > DBI (https://github.com/r-dbi/DBI): LGPL 2.1. Sedona R depends on > > > this. But we do not deliver DBI in our source code and binary. > > > > > > Is this a mandatory dependency? > > > > > > Second: the website still has some small problems: [2] > > > > > > The third one: Check the recent version release voting [3]. There is > > > basically no valid voting information in the community voting. Do > > > community members really know how to check the version release? The > > > documentation guidelines for version releases it was only recently > > > released. > > > > > > The last one: You have one mentor who has not subscribed to the > > > private mailing group, and four PPMCs who have not linked their GitHub > > > accounts. How can they contribute? (maybe because of contributions > > > from other fields, I'm not surprised, but wanted to confirm) > > > > > > > > > [1]https://issues.apache.org/jira/browse/SEDONA-81 > > > [2]https://whimsy.apache.org/pods/project/sedona > > > [3]https://lists.apache.org/thread/511gjndxmdxh4g2rzwyxppjc00orz3s3 > > > > > > Jia Yu 于2022年9月14日周三 10:40写道： > > > > > > > > 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'd like to start the discussion and > > collect > > > > feedback towards graduation. Please feel free to join the discussion. > > > > > > > > The discussion will remain open for at least 72 hours. > > > > > > > > Thanks, > > > > Jia > > > > > > > > *** > > > > > > > > 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]. > > > > > > > > The summary on the state of the community is listed below and the self > > > > assessment (Apache Project Maturity Model) is in [7]. > > > > > > > > > > > > Sedona
Re: [VOTE] Heron Release 0.20.5-incubating Release Candidate 4
Hi Chao, The KEYS file is at https://dist.apache.org/repos/dist/dev/incubator/heron/KEYS On Sun, Sep 4, 2022 at 5:42 AM Chao Zhang wrote: > Hi, > > Where can I download the KEYS file? > > Best regards > Chao Zhang > > https://github.com/tokers > > On Fri, Sep 2, 2022 at 11:24 PM Nicholas Nezis > wrote: > > > > The Apache Heron community has voted and approved the proposal to release > > Apache Heron (Incubating) version 0.20.5-incubating Release Candidate > > 4. We request the Incubator PMC members to review and vote on this > > incubator release. To date, we only have 2 binded approvals as we have > > not heard from one of our mentors as of late. > > The results of the Release Candidate 1 votes are below: > > - Binded Approvals: 2 > >* Ming Wen > >* Kevin Ratnasekera > > > > Hello Heron Community, > > > > > > This is a call for a vote to the 4th release candidate for Apache Heron, > > > > version 0.20.5-incubating. > > > > We request project mentors (binded) as well as all contributors > (unbinded) > > > > and users to review and vote on this incubator release. > > > > > > * The tag to be voted upon: > > > > 12b8abc152f7a23e87ef19299ff92423a6ee1469 > > > > The full list of changes and release notes are available at: > > > > > https://github.com/apache/incubator-heron/releases/tag/0.20.5-incubating-rc4 > > > > Files can be found in dist.apache.org > > > > KEYS > > > > Source: > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-0.20.5-incubating-src.tar.gz > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-0.20.5-incubating-src.tar.gz.sha512 > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-0.20.5-incubating-src.tar.gz.asc > > > > > > Java Artifacts: > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/maven/heron-artifacts-0.20.5-incubating.tar.gz > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/maven/heron-artifacts-0.20.5-incubating.tar.gz.sha512 > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/maven/heron-artifacts-0.20.5-incubating.tar.gz.asc > > > > > > Centos 7 Installer: > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-install-0.20.5-incubating-centos7.sh.tar.gz > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-install-0.20.5-incubating-centos7.sh.tar.gz.sha512 > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-install-0.20.5-incubating-centos7.sh.tar.gz.asc > > > > > > Darwin Installer: > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-install-0.20.5-incubating-darwin.sh.tar.gz > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-install-0.20.5-incubating-darwin.sh.tar.gz.sha512 > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-install-0.20.5-incubating-darwin.sh.tar.gz.asc > > > > > > Debian 11 Installer: > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-install-0.20.5-incubating-debian11.sh.tar.gz > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-install-0.20.5-incubating-debian11.sh.tar.gz.sha512 > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-install-0.20.5-incubating-debian11.sh.tar.gz.asc > > > > > > Ubuntu 22.04 Installer: > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-install-0.20.5-incubating-ubuntu22.04.sh.tar.gz > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-install-0.20.5-incubating-ubuntu22.04.sh.tar.gz.sha512 > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heron-install-0.20.5-incubating-ubuntu22.04.sh.tar.gz.asc > > > > > > HeronPy: > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heronpy/heronpy-0.20.5rc4.tar.gz > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heronpy/heronpy-0.20.5rc4.tar.gz.sha512 > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heronpy/heronpy-0.20.5rc4.tar.gz.asc > > > > > > HeronPy Wheel: > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heronpy/heronpy-0.20.5rc4-py3-none-any.whl > > > > > https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.5-incubating-rc4/heronpy/heronpy-0.20.5rc4-py3-none-any.whl.sha512 > > > > >
Re: [MENTORS] Late podling reports and missing signoffs
Hi, By far, Marvin-AI, PonyMail and Flagon have no mentor signoff. Calvin Kirs 于2022年9月11日周日 22:40写道： > > Hi, > > We are missing reports from: > - Flagon* > - Livy* > - Marvin-AI* > - Nemo > - PonyMail* > - SDAP* > - Spot* > - Teaclave* > - Toree* > - Training* > > We are missing mentor sign-off on:(Mentor signoff due by end of days > is Tue Sep 13th) > - Datalab > - StreamPipes > > * Also did not report last month > > -- > Best wishes！ > CalvinKirs -- Best wishes！ CalvinKirs - 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
Joshua Poore 于2022年9月15日周四 08:21写道： > > Thanks Justin! > > I didn’t see a record for Flagon in the Sept report… OK to paste back in on > my end? hi, I have copied the report from the OCT report. (I deleted the previous record due to no submission due), thank you for your submission. > > Josh > > Joshua Poore > > > > On Sep 14, 2022, at 6:24 PM, Justin Mclean wrote: > > > > Hi, > > > >> Apologies RE Flagon reporting. Just missed the window for SEPT. I have > >> added a report for OCT and requested Mentor review earlier. > > > > You still have a couple of day in which you could submit it. > > > > Kind Regards, > > Justin > > - > > 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 > -- Best wishes！ CalvinKirs - 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
Thanks Justin! I didn’t see a record for Flagon in the Sept report… OK to paste back in on my end? Josh Joshua Poore > On Sep 14, 2022, at 6:24 PM, Justin Mclean wrote: > > Hi, > >> Apologies RE Flagon reporting. Just missed the window for SEPT. I have added >> a report for OCT and requested Mentor review earlier. > > You still have a couple of day in which you could submit it. > > Kind Regards, > Justin > - > 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: [MENTORS] Late podling reports and missing signoffs
Hi, > Apologies RE Flagon reporting. Just missed the window for SEPT. I have added > a report for OCT and requested Mentor review earlier. You still have a couple of day in which you could submit it. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept ICLA and Software Grant from UMD Into the Apache Flagon Podling
Hi John, Thanks for your response. I had a long thread with Calvin, Justin, and Craig Russell to clarify the process of onboarding new SW grants into existing podlings RE CCLA. The thread is on private@incubator, which I'm unable to grab a permalink for through lists... Bottom line up front: Suggestion was that formal votes through the incubator were not necessary in this case, but discussion and a vote on general level was encouraged to document consensus. Trying to adhere to good practice, but at this point a "consensus vote" on general is perfunctory. Respectfully, Josh (Flagon PPMC) On 2022/08/30 11:05:03 "John D. Ament" wrote: > Note that you're using public and private lists which is a big no-no. > > I'll be honest I don't understand what you're trying to get the IPMC to > vote on. You may need some help from mentors. I saw IP clearance and will > point out that [1] isn't for podlings. Likewise if this CCLA is new after > your proposal then likely [2] needs to be updated instead. After which your > mentors should be verifying the distribution rights. > > > [1]: https://incubator.apache.org/ip-clearance/index.html > [2]: https://incubator.apache.org/projects/flagon.html > > On Mon, Aug 29, 2022, 21:06 Joshua Poore wrote: > > > Hello General! > > > > Refreshing this 72 VOTE: > > > > I am looking for additional review and binding VOTEs from the Incubator > > regarding a recent SW grant (via CCLA) from UMD to the Flagon Podling. The > > Flagon community has VOTED to accept for reasons outlined below and > > Secretary has accepted the CCLA. We are seeking concurrence from the > > incubator. > > > > Details follow: > > > > > On Aug 19, 2022, at 9:32 PM, Joshua Poore wrote: > > > > > > Hello Incubator! > > > > > > I am continuing a 72 VOTE from the Flagon Community on Incubator General > > regarding the acceptance of an ICLA and Software Grant into the Apache > > Flagon (Incubating) Podling. > > > > > > The purpose of this VOTE is to establish consensus and transparency wrt > > to IP Clearance. > > > > > > We conducted a Community Discussion @ Flagon and a VOTE. > > > > > > VOTE Thread on Flagon Private: > > https://lists.apache.org/thread/t5gof3sj40xrv2ylrgntx6oz2vdcc37t > > > > > > VOTE Result on Flagon Private: > > https://lists.apache.org/thread/dvz7rtxl77pfqb3c3tgn36g1wbfgr54h > > > > > > [3] +1 (+2 Binding) > > > [0] 0 > > > [0] -1 > > > > > > Accepted Submission of ICLA to Secretary: > > https://lists.apache.org/thread/fz6v7x9gjcllr5dvsf5ho9hbt7ogrwvw > > > > > > > > > > > > Respectfully, > > > > > > Josh (Flagon PPMC) > > > > > > > > > Details on the Software Grant Follow (copied from original Flagon VOTE) > > below: > > > > > > > > > The Software Grant encompasses a refactor of the Apache Flagon Distill > > product, which has been deprecated for a few years now [1] > > > > > This Grant includes ~150 new commits and thousands of new insertions > > (and a lot of deletions) At UMD my team and I re-thought Distill as a > > Python Package (for distro through PyPI) [2] that allows users to: > > > > > - efficiently segment UserALE.js (or User Behavior Logs) data > > > > > - curate segments - transform segments with logical operations > > (intersection, union, etc.) > > > > > - filter log data extracted from segments > > > > > - apply analytics (e.g., statistical, graphs) to data extracted from > > segments > > > > > - support graph-based visualization (funnel, sankey) > > > > > Additionally: > > > > > - code is well documented [3] > > > > > - excellent working examples [4] > > > > > Distill also provides examples for dashboards to visualize segments > > using both Apache Superset and Plotly/Dash > > > > > The original Distill product was tethered to a front-end (Tap), relied > > on rudimentary (and error-prone) processing of segments within the client. > > This made Distill difficult to maintain and required users to adopt tap, > > limiting their analytical use-cases with UserALE.js and Distill. Overall, > > I think that Distill provides a far more scaleable product to engage (and > > expand) our development community. I think this will add real value to > > Apache Flagon. > > > > > > > Overhead/Actions prior to release: > > > > > - Documentation builds will need be adjusted for a new repo/branch > > > > > - Additional documentation for a few analytical functions (i.e., > > click-rate) > > > > > - Minor tweaks to simply code in a few functions (i.e., click-rate) > > > > > - Some restructuring of Repo to consolidate and organize examples > > > > > - a few additional README’s should be added (i.e., examples /dir) > > > > > IP Clearance The Software Grant is signed by Felicia Metz, esq. who is > > an Associate Director at the University of Maryland’s, UMD Ventures office, > > which has authority to release UMD IP. That makes accepting this grant > > significantly easier from an IP Clearance perspective. New Committers The > > UMD executed CCLA includes 5 new committers and
Re: [MENTORS] Late podling reports and missing signoffs
Apologies RE Flagon reporting. Just missed the window for SEPT. I have added a report for OCT and requested Mentor review earlier. Josh On 2022/09/11 14:40:22 Calvin Kirs wrote: > Hi, > > We are missing reports from: > - Flagon* > - Livy* > - Marvin-AI* > - Nemo > - PonyMail* > - SDAP* > - Spot* > - Teaclave* > - Toree* > - Training* > > We are missing mentor sign-off on:(Mentor signoff due by end of days > is Tue Sep 13th) > - Datalab > - StreamPipes > > * Also did not report last month > > -- > Best wishes！ > CalvinKirs > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache Sedona to a Top Level Project
Dear Calvin, Thank you for your quick response. To your questions, 1. The DBI dependency in R is not mandatory. Our PPMC Yitao is working on the doc and will mark it as optional soon. 2. As described in my email, the external resources are "api.github.com" which are used to get the number of stars and forks of our GitHub repo. Based on ASF privacy policy [1], GitHub.com is considered fully supports GDPR. *Do you think we still should remove these api calls?* 3. Yes, we admit that the voting information from PPMC should be improved. We will require all PPMCs to provide items they check from now on. But I believe our PPMCs already know how to check the release. The vote guideline was published on April 5 2022, which was 5 months ago. 4. Our mentor George Percivall subscribed to the private channel using perciv...@ogc.org but not his ASF email. But indeed he is not active in our community, we will remove him from our mentor list. Regarding the 4 PPMC who didn't link their GitHub account, they still actively participate in the community including voting and discussion (except Zongsi Zhang, who will be removed in TLP PMC). They also create PRs on our GitHub and then other members merge the PRs. I have urged them to link their GitHub account ASAP. 5. DISCLAIMER-WIP was used in our last release (1.2.1). We are now using the standard DISCLAIMER and it will be put in the next release. See our commit [3] Hope my answers can address your concerns! Thanks, Jia [1] Apache Software Foundation privacy policy: https://privacy.apache.org/policies/privacy-policy-public.html [2] Sedona community vote guideline first commit: https://github.com/apache/incubator-sedona/commit/6afe7785ae4fbbb2e18c272b0375458a10f2a61d [3] Use standard DISCLAIMER commit: https://github.com/apache/incubator-sedona/commit/26d65d4e7f5add374c8089dfdf974d7cb830ee01 On Wed, Sep 14, 2022 at 12:16 AM Calvin Kirs wrote: > -1 （binding） > > As well as those mentioned above, the latest released version [1], > did not use the standard disclaimer text. > > [1] > https://www.apache.org/dyn/closer.lua/incubator/sedona/1.2.1-incubating/apache-sedona-1.2.1-incubating-src.tar.gz > > Calvin Kirs 于2022年9月14日周三 13:15写道： > > > > Hi, > > > > I have a few questions: > > > > The first: a quick look [1] > > > > DBI (https://github.com/r-dbi/DBI): LGPL 2.1. Sedona R depends on > > this. But we do not deliver DBI in our source code and binary. > > > > Is this a mandatory dependency? > > > > Second: the website still has some small problems: [2] > > > > The third one: Check the recent version release voting [3]. There is > > basically no valid voting information in the community voting. Do > > community members really know how to check the version release? The > > documentation guidelines for version releases it was only recently > > released. > > > > The last one: You have one mentor who has not subscribed to the > > private mailing group, and four PPMCs who have not linked their GitHub > > accounts. How can they contribute? (maybe because of contributions > > from other fields, I'm not surprised, but wanted to confirm) > > > > > > [1]https://issues.apache.org/jira/browse/SEDONA-81 > > [2]https://whimsy.apache.org/pods/project/sedona > > [3]https://lists.apache.org/thread/511gjndxmdxh4g2rzwyxppjc00orz3s3 > > > > Jia Yu 于2022年9月14日周三 10:40写道： > > > > > > 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'd like to start the discussion and > collect > > > feedback towards graduation. Please feel free to join the discussion. > > > > > > The discussion will remain open for at least 72 hours. > > > > > > Thanks, > > > Jia > > > > > > *** > > > > > > 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]. > > > > > > 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 Sept 13 2022: > > > > > > ** Community **: > > > > > > * number of contributions (commits) since incubation: 349 > > > - Overall: 1038 > > > - 33% of the commits were added since incubation. > > > > > > * number of contributors (and growth since incubation): 47 > > > - Overall: 82 > > > - 57% of the contributors joined since incubation > > > > > > * email discussions since incubation: 1043 threads on > d...@sedona.apache.org > > > > > > * Number of monthly downloads: grow from 200K per month to 800K per >
Re: [DISCUSS] Graduate Apache Sedona to a Top Level Project
-1 （binding） As well as those mentioned above, the latest released version [1], did not use the standard disclaimer text. [1]https://www.apache.org/dyn/closer.lua/incubator/sedona/1.2.1-incubating/apache-sedona-1.2.1-incubating-src.tar.gz Calvin Kirs 于2022年9月14日周三 13:15写道： > > Hi, > > I have a few questions: > > The first: a quick look [1] > > DBI (https://github.com/r-dbi/DBI): LGPL 2.1. Sedona R depends on > this. But we do not deliver DBI in our source code and binary. > > Is this a mandatory dependency? > > Second: the website still has some small problems: [2] > > The third one: Check the recent version release voting [3]. There is > basically no valid voting information in the community voting. Do > community members really know how to check the version release? The > documentation guidelines for version releases it was only recently > released. > > The last one: You have one mentor who has not subscribed to the > private mailing group, and four PPMCs who have not linked their GitHub > accounts. How can they contribute? (maybe because of contributions > from other fields, I'm not surprised, but wanted to confirm) > > > [1]https://issues.apache.org/jira/browse/SEDONA-81 > [2]https://whimsy.apache.org/pods/project/sedona > [3]https://lists.apache.org/thread/511gjndxmdxh4g2rzwyxppjc00orz3s3 > > Jia Yu 于2022年9月14日周三 10:40写道： > > > > 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'd like to start the discussion and collect > > feedback towards graduation. Please feel free to join the discussion. > > > > The discussion will remain open for at least 72 hours. > > > > Thanks, > > Jia > > > > *** > > > > 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]. > > > > 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 Sept 13 2022: > > > > ** Community **: > > > > * number of contributions (commits) since incubation: 349 > > - Overall: 1038 > > - 33% of the commits were added since incubation. > > > > * number of contributors (and growth since incubation): 47 > > - Overall: 82 > > - 57% of the contributors joined since incubation > > > > * email discussions since incubation: 1043 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: 6 > > > > * 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: 10 PPMC from 9 > > different organizations > > Adam Binford: Maxar > > Kanchan Chowdhury: Arizona State University > > Paweł Kociński: GetInData > > Yitao Li: SafeGraph > > Netanel Malka: Upstream Security > > Mohame Sarwat: Wherobots Inc. > > Sachio Wakai: KDDI > > Jinxuan Wu: Bloomberg LP > > Jia Yu: Wherobots Inc. > > Zongsi Zhang: Grab > > > > * new PPMC members since incubation: 4 > > Adam Binford: Maxar > > Kanchan Chowdhury: Arizona State University > > Yitao Li: SafeGraph > > Sachio Wakai: KDDI > > > > * Pending new PPMC members (due to pending CCLAs): 2 > > Magdalena Wójciak: Billennium > > Kengo Seki: NTT Data > > > > > > ** 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
