Re: Draft: board report for 2022 Q2
Thanks for the feedback. @Stamatis, I included the answer to this (minor) question in this quarter's report because after the last one I received an automatic email from the secretary (with priv...@calcite.apache.org in cc) mentioning the question and stating that "Comments that do not ask specific questions should be noted by the PMC and taken into consideration as appropriate for future board reports. Where a comment asks a specific question, it should be answered in your next board report unless otherwise stated in the comment."; so my understanding was that, for this specific case, it was simply required an answer in the following report. @Julian, I hesitated about that because technically the committer additions were effective on 2022-07-04, but the internal process started at the end of June. But I guess you are right, since it is something relevant which breaks an impasse in the committer list, I will update the "Membership Data" section with the new committers before submitting the final report (hopefully, for the Q3 report we will have newer additions to be mentioned :) Best, Ruben On Mon, Jul 4, 2022 at 9:15 PM Julian Hyde wrote: > +1 > > Thanks for getting this written on schedule. > > I know we try to only report what happened in the quarter (i.e. up to > June 30th) but since we have two new committers (yay!) I see no harm > in including them. > > Julian > > On Mon, Jul 4, 2022 at 12:49 PM Stamatis Zampetakis > wrote: > > > > Thanks for putting this together Ruben! LGTM, just a minor comment. > > > > When the board raises a comment/question we can reply by sending an email > > to the board@ list. We don't need to wait for the next quarter to put > this > > information in the board report. This was a minor remark and probably it > is > > fine even if we don't reply at all but for more serious matters they > expect > > timely answers. > > > > Best, > > Stamatis > > > > On Mon, Jul 4, 2022 at 9:00 PM Michael Mior wrote: > > > > > +1 Thanks Ruben! > > > -- > > > Michael Mior > > > mm...@apache.org > > > > > > > > > Le lun. 4 juil. 2022 à 07:52, Ruben Q L a écrit : > > > > > > > Hello, > > > > > > > > Below these lines you can find a draft of this quarter's board > report. I > > > > plan to submit it > > > > at the end of this week. > > > > Please let me know if you have any additions or corrections. Note > that > > > our > > > > last report got a question from the board, for which I include a > proposed > > > > answer in this report (cf "Issues" section). > > > > Best, > > > > Ruben > > > > > > > > > > > > > > > > ## Description: > > > > Apache Calcite is a highly customizable framework for parsing and > > > planning > > > > queries on data in a wide variety of formats. It allows database-like > > > > access, > > > > and in particular a SQL interface and advanced query optimization, > for > > > data > > > > not residing in a traditional database. > > > > > > > > Avatica is a sub-project within Calcite and provides a framework for > > > > building > > > > local and remote JDBC and ODBC database drivers. Avatica has an > > > independent > > > > release schedule and its own repository. > > > > > > > > > > > > ## Issues: > > > > There are no issues requiring board attention. > > > > > > > > The last report got one comment from the board: > > > > "It's certainly up to you all, but please remember that these > reports are > > > > published, publicly. Are you sure you want to have your names and > email > > > > addresses as part of this (public) report?". > > > > > > > > There is no problem from our side. This report has been pre-approved > by > > > the > > > > Calcite community and the section with names / emails has already > been > > > part > > > > of > > > > our reports in the "community health" section for a while. We > decided to > > > > add it some time ago to highlight the contributions from > non-committers > > > and > > > > the top reviewers, in order to encourage the members of the > community. > > > > > > > > > > > > ## Membership Data: > > > > Apache Calcite was founded 2015-10-22 (7 years ago) > > > > There are currently 56 committers and 25 PMC members in this project. > > > > The Committer-to-PMC ratio is roughly 7:4. > > > > > > > > Community changes, past quarter: > > > > - Chunwei Lei was added to the PMC on 2022-05-24 > > > > - Vladimir Ozerov was added to the PMC on 2022-05-24 > > > > - No new committers. Last addition was Alessandro Solimando on > > > 2021-12-17. > > > > > > > > > > > > ## Project Activity: > > > > Avatica 1.21.0 was released on 2022-05-08, it was a maintenance > release > > > > with > > > > dependency upgrades and added support for Oracle JDK 16 to 18. Of > > > > particular > > > > note is Log4j2 being upgrade to 2.16.0 and subsequently 2.17.0 and > 2.17.1 > > > > to > > > > address CVE-2021-44228, CVE-2021-45105 and CVE-2021-44832. > > > > > > > > There has not been any Calcite release in this quarter. Calcite > 1.31.0 > > > was > > > > planned for
Re: Draft: board report for 2022 Q2
+1 Thanks for getting this written on schedule. I know we try to only report what happened in the quarter (i.e. up to June 30th) but since we have two new committers (yay!) I see no harm in including them. Julian On Mon, Jul 4, 2022 at 12:49 PM Stamatis Zampetakis wrote: > > Thanks for putting this together Ruben! LGTM, just a minor comment. > > When the board raises a comment/question we can reply by sending an email > to the board@ list. We don't need to wait for the next quarter to put this > information in the board report. This was a minor remark and probably it is > fine even if we don't reply at all but for more serious matters they expect > timely answers. > > Best, > Stamatis > > On Mon, Jul 4, 2022 at 9:00 PM Michael Mior wrote: > > > +1 Thanks Ruben! > > -- > > Michael Mior > > mm...@apache.org > > > > > > Le lun. 4 juil. 2022 à 07:52, Ruben Q L a écrit : > > > > > Hello, > > > > > > Below these lines you can find a draft of this quarter's board report. I > > > plan to submit it > > > at the end of this week. > > > Please let me know if you have any additions or corrections. Note that > > our > > > last report got a question from the board, for which I include a proposed > > > answer in this report (cf "Issues" section). > > > Best, > > > Ruben > > > > > > > > > > > > ## Description: > > > Apache Calcite is a highly customizable framework for parsing and > > planning > > > queries on data in a wide variety of formats. It allows database-like > > > access, > > > and in particular a SQL interface and advanced query optimization, for > > data > > > not residing in a traditional database. > > > > > > Avatica is a sub-project within Calcite and provides a framework for > > > building > > > local and remote JDBC and ODBC database drivers. Avatica has an > > independent > > > release schedule and its own repository. > > > > > > > > > ## Issues: > > > There are no issues requiring board attention. > > > > > > The last report got one comment from the board: > > > "It's certainly up to you all, but please remember that these reports are > > > published, publicly. Are you sure you want to have your names and email > > > addresses as part of this (public) report?". > > > > > > There is no problem from our side. This report has been pre-approved by > > the > > > Calcite community and the section with names / emails has already been > > part > > > of > > > our reports in the "community health" section for a while. We decided to > > > add it some time ago to highlight the contributions from non-committers > > and > > > the top reviewers, in order to encourage the members of the community. > > > > > > > > > ## Membership Data: > > > Apache Calcite was founded 2015-10-22 (7 years ago) > > > There are currently 56 committers and 25 PMC members in this project. > > > The Committer-to-PMC ratio is roughly 7:4. > > > > > > Community changes, past quarter: > > > - Chunwei Lei was added to the PMC on 2022-05-24 > > > - Vladimir Ozerov was added to the PMC on 2022-05-24 > > > - No new committers. Last addition was Alessandro Solimando on > > 2021-12-17. > > > > > > > > > ## Project Activity: > > > Avatica 1.21.0 was released on 2022-05-08, it was a maintenance release > > > with > > > dependency upgrades and added support for Oracle JDK 16 to 18. Of > > > particular > > > note is Log4j2 being upgrade to 2.16.0 and subsequently 2.17.0 and 2.17.1 > > > to > > > address CVE-2021-44228, CVE-2021-45105 and CVE-2021-44832. > > > > > > There has not been any Calcite release in this quarter. Calcite 1.31.0 > > was > > > planned for mid-June, but it has suffered a small delay. It should be > > > released > > > during July. > > > > > > > > > ## Community Health: > > > The overall status of the community is healthy and stable. We are keeping > > > the > > > good momentum in terms of contributions and opened discussions to improve > > > the > > > project. This is reflected also on the statistics of Jira & GitHub > > > activity: > > > -1% issues opened, +9% issues closed, -9% commits, +18% code > > contributors, > > > -11% PRs opened, +21% PRs closed. > > > > > > As usual, we struggle a bit on the PRs reviews, with some of them being > > > opened > > > and blocked for a while due a lack of active reviewers. This fact has > > > triggered an interesting discussion in both the Apache Calcite and Apache > > > Flink communities about the pros and cons of forking Calcite by the > > latter. > > > Many voices from the Apache Calcite community advised against this idea, > > > due > > > to the elevated maintenance costs in the long term. Instead, we are > > > discussing > > > several ideas about how to improve our PR review situation, among them > > the > > > possibility of increasing the number of reviewers by granting Calcite > > > committership per request to people who are already ASF committers (in > > > other > > > projects) and have a proven record of working with Calcite (on a case by > > > case > > > basis to be approved
Re: [DISCUSS] How we choose a PMC chair
> Stamatis wrote: > > Assuming that multiple people are nominated, we should maybe agree > on how to proceed with the vote. Do we consider everyone and settle > on a majority vote or do we vote for the one who was nominated by > more people? I should probably have used the word "suggestions" rather than "nominations". The PMC should have a free discussion, reach consensus, and then vote to formalize the result. The decision is for the PMC alone to make, and the number of nominations a person receives should not affect the result. > If we say that PMC nominations matter the most then probably > we could move the whole discussion to the private list (including > the initial email) since there is no strong incentive for non-PMC > members to participate; it will not really affect the outcome. I was proposing that nominations and ensuing discussion go to private@ because a public discussion of candidates is unseemly and potentially divisive, but I wanted non-PMC members to have some input. Plus, the discussion is often kicked off by the 'state of the project' email, which is and should remain on dev@. But what you suggest is not unreasonable. > Another point worth clarifying is if we can nominate someone who > has already been a PMC chair in the past (including the current > chair). I agree that current and past chairs should be eligible. In other words, no term limits, but an election every year. Julian On Mon, Jul 4, 2022 at 12:31 PM Stamatis Zampetakis wrote: > > It makes perfect sense to send nominations to the private list. > > Assuming that multiple people are nominated, we should maybe agree on how > to proceed with the vote. Do we consider everyone and settle on a majority > vote or do we vote for the one who was nominated by more people? > > Both options are very similar but the difference may be significant if we > count nominations from PMC and non-PMC members the same way. > > If we say that PMC nominations matter the most then probably we could move > the whole discussion to the private list (including the initial email) > since there is no strong incentive for non-PMC members to participate; it > will not really affect the outcome. > > Another point worth clarifying is if we can nominate someone who has > already been a PMC chair in the past (including the current chair). Every > Calcite chair since Calcite's graduation from the incubation has served > exactly once and I think this is also part of the tradition. I like the > fact that new people are getting familiar with this role and it is > important for the future of the project but we shouldn't put this as a > strict requirement for the nomination process. > > Best, > Stamatis > > On Mon, Jul 4, 2022 at 9:00 PM Michael Mior wrote: > > > +1 from me as well. > > -- > > Michael Mior > > mm...@apache.org > > > > > > Le dim. 3 juil. 2022 à 19:46, Julian Hyde a écrit : > > > > > As you know, Calcite has a tradition of choosing a new PMC chair (VP) > > > each year, around the anniversary of the project's graduation[1][2]. I > > > think this is a great tradition, but I'd like to discuss an > > > improvement to that process. > > > > > > (I'm starting the conversation now - several months after the previous > > > vote, and several months before the next - so that it's clear that I > > > am not criticizing the process or the outcome or previous votes.) > > > > > > I've noticed that the outgoing chair sends an email on dev@ saying > > > words to the following effect: > > > > > > I think Xyz would be a great person to succeed me. > > > What do you all think? > > > > > > (I fear that I may have started this tradition when, at the end of my > > > tenure as first chair, I approached Jesus and asked him whether he'd > > > be prepared to do the job[3]. Mea culpa.) > > > > > > After such an outright endorsement, especially on a public list, it > > > would be churlish for someone to reply "Actually, I think Abc would be > > > better." As a result, it's rather difficult to have an open debate, > > > and the candidate selected by the outgoing chair tends to win > > > unopposed. > > > > > > I suggest that the outgoing chair says something like > > > > > > It's time to change the PMC chair. > > > Please send nominations to private@ and the PMC will discuss and vote. > > > > > > That would allow for several nominations, allow people to give reasons > > > why they prefer a candidate (without disparaging other candidates), > > > and lead to a more informed outcome. > > > > > > What do you think? Are there any other aspects of the election process > > > we should change? > > > > > > Julian > > > > > > [1] https://lists.apache.org/thread/rmj9qm9wlol3nb7z4phddoljbgvypkrt > > > [2] https://lists.apache.org/thread/5tzb8w655pj2vo9omz20th5jnbn9zww7 > > > [3] https://lists.apache.org/thread/y4wjdj5h1y3sypnlmhpoz9r6bkk3cv6o > > > > >
Re: Draft: board report for 2022 Q2
Thanks for putting this together Ruben! LGTM, just a minor comment. When the board raises a comment/question we can reply by sending an email to the board@ list. We don't need to wait for the next quarter to put this information in the board report. This was a minor remark and probably it is fine even if we don't reply at all but for more serious matters they expect timely answers. Best, Stamatis On Mon, Jul 4, 2022 at 9:00 PM Michael Mior wrote: > +1 Thanks Ruben! > -- > Michael Mior > mm...@apache.org > > > Le lun. 4 juil. 2022 à 07:52, Ruben Q L a écrit : > > > Hello, > > > > Below these lines you can find a draft of this quarter's board report. I > > plan to submit it > > at the end of this week. > > Please let me know if you have any additions or corrections. Note that > our > > last report got a question from the board, for which I include a proposed > > answer in this report (cf "Issues" section). > > Best, > > Ruben > > > > > > > > ## Description: > > Apache Calcite is a highly customizable framework for parsing and > planning > > queries on data in a wide variety of formats. It allows database-like > > access, > > and in particular a SQL interface and advanced query optimization, for > data > > not residing in a traditional database. > > > > Avatica is a sub-project within Calcite and provides a framework for > > building > > local and remote JDBC and ODBC database drivers. Avatica has an > independent > > release schedule and its own repository. > > > > > > ## Issues: > > There are no issues requiring board attention. > > > > The last report got one comment from the board: > > "It's certainly up to you all, but please remember that these reports are > > published, publicly. Are you sure you want to have your names and email > > addresses as part of this (public) report?". > > > > There is no problem from our side. This report has been pre-approved by > the > > Calcite community and the section with names / emails has already been > part > > of > > our reports in the "community health" section for a while. We decided to > > add it some time ago to highlight the contributions from non-committers > and > > the top reviewers, in order to encourage the members of the community. > > > > > > ## Membership Data: > > Apache Calcite was founded 2015-10-22 (7 years ago) > > There are currently 56 committers and 25 PMC members in this project. > > The Committer-to-PMC ratio is roughly 7:4. > > > > Community changes, past quarter: > > - Chunwei Lei was added to the PMC on 2022-05-24 > > - Vladimir Ozerov was added to the PMC on 2022-05-24 > > - No new committers. Last addition was Alessandro Solimando on > 2021-12-17. > > > > > > ## Project Activity: > > Avatica 1.21.0 was released on 2022-05-08, it was a maintenance release > > with > > dependency upgrades and added support for Oracle JDK 16 to 18. Of > > particular > > note is Log4j2 being upgrade to 2.16.0 and subsequently 2.17.0 and 2.17.1 > > to > > address CVE-2021-44228, CVE-2021-45105 and CVE-2021-44832. > > > > There has not been any Calcite release in this quarter. Calcite 1.31.0 > was > > planned for mid-June, but it has suffered a small delay. It should be > > released > > during July. > > > > > > ## Community Health: > > The overall status of the community is healthy and stable. We are keeping > > the > > good momentum in terms of contributions and opened discussions to improve > > the > > project. This is reflected also on the statistics of Jira & GitHub > > activity: > > -1% issues opened, +9% issues closed, -9% commits, +18% code > contributors, > > -11% PRs opened, +21% PRs closed. > > > > As usual, we struggle a bit on the PRs reviews, with some of them being > > opened > > and blocked for a while due a lack of active reviewers. This fact has > > triggered an interesting discussion in both the Apache Calcite and Apache > > Flink communities about the pros and cons of forking Calcite by the > latter. > > Many voices from the Apache Calcite community advised against this idea, > > due > > to the elevated maintenance costs in the long term. Instead, we are > > discussing > > several ideas about how to improve our PR review situation, among them > the > > possibility of increasing the number of reviewers by granting Calcite > > committership per request to people who are already ASF committers (in > > other > > projects) and have a proven record of working with Calcite (on a case by > > case > > basis to be approved by the Calcite PMC). > > > > The number of non-committer (contributor) commits per month: > > +-+-+-+ > > |year |month| contributor_commits | > > +-+-+-+ > > | 2022| 4 | 15 | > > | 2022| 5 | 13 | > > | 2022| 6 | 19 | > >
Re: [DISCUSS] How we choose a PMC chair
It makes perfect sense to send nominations to the private list. Assuming that multiple people are nominated, we should maybe agree on how to proceed with the vote. Do we consider everyone and settle on a majority vote or do we vote for the one who was nominated by more people? Both options are very similar but the difference may be significant if we count nominations from PMC and non-PMC members the same way. If we say that PMC nominations matter the most then probably we could move the whole discussion to the private list (including the initial email) since there is no strong incentive for non-PMC members to participate; it will not really affect the outcome. Another point worth clarifying is if we can nominate someone who has already been a PMC chair in the past (including the current chair). Every Calcite chair since Calcite's graduation from the incubation has served exactly once and I think this is also part of the tradition. I like the fact that new people are getting familiar with this role and it is important for the future of the project but we shouldn't put this as a strict requirement for the nomination process. Best, Stamatis On Mon, Jul 4, 2022 at 9:00 PM Michael Mior wrote: > +1 from me as well. > -- > Michael Mior > mm...@apache.org > > > Le dim. 3 juil. 2022 à 19:46, Julian Hyde a écrit : > > > As you know, Calcite has a tradition of choosing a new PMC chair (VP) > > each year, around the anniversary of the project's graduation[1][2]. I > > think this is a great tradition, but I'd like to discuss an > > improvement to that process. > > > > (I'm starting the conversation now - several months after the previous > > vote, and several months before the next - so that it's clear that I > > am not criticizing the process or the outcome or previous votes.) > > > > I've noticed that the outgoing chair sends an email on dev@ saying > > words to the following effect: > > > > I think Xyz would be a great person to succeed me. > > What do you all think? > > > > (I fear that I may have started this tradition when, at the end of my > > tenure as first chair, I approached Jesus and asked him whether he'd > > be prepared to do the job[3]. Mea culpa.) > > > > After such an outright endorsement, especially on a public list, it > > would be churlish for someone to reply "Actually, I think Abc would be > > better." As a result, it's rather difficult to have an open debate, > > and the candidate selected by the outgoing chair tends to win > > unopposed. > > > > I suggest that the outgoing chair says something like > > > > It's time to change the PMC chair. > > Please send nominations to private@ and the PMC will discuss and vote. > > > > That would allow for several nominations, allow people to give reasons > > why they prefer a candidate (without disparaging other candidates), > > and lead to a more informed outcome. > > > > What do you think? Are there any other aspects of the election process > > we should change? > > > > Julian > > > > [1] https://lists.apache.org/thread/rmj9qm9wlol3nb7z4phddoljbgvypkrt > > [2] https://lists.apache.org/thread/5tzb8w655pj2vo9omz20th5jnbn9zww7 > > [3] https://lists.apache.org/thread/y4wjdj5h1y3sypnlmhpoz9r6bkk3cv6o > > >
Re: Draft: board report for 2022 Q2
+1 Thanks Ruben! -- Michael Mior mm...@apache.org Le lun. 4 juil. 2022 à 07:52, Ruben Q L a écrit : > Hello, > > Below these lines you can find a draft of this quarter's board report. I > plan to submit it > at the end of this week. > Please let me know if you have any additions or corrections. Note that our > last report got a question from the board, for which I include a proposed > answer in this report (cf "Issues" section). > Best, > Ruben > > > > ## Description: > Apache Calcite is a highly customizable framework for parsing and planning > queries on data in a wide variety of formats. It allows database-like > access, > and in particular a SQL interface and advanced query optimization, for data > not residing in a traditional database. > > Avatica is a sub-project within Calcite and provides a framework for > building > local and remote JDBC and ODBC database drivers. Avatica has an independent > release schedule and its own repository. > > > ## Issues: > There are no issues requiring board attention. > > The last report got one comment from the board: > "It's certainly up to you all, but please remember that these reports are > published, publicly. Are you sure you want to have your names and email > addresses as part of this (public) report?". > > There is no problem from our side. This report has been pre-approved by the > Calcite community and the section with names / emails has already been part > of > our reports in the "community health" section for a while. We decided to > add it some time ago to highlight the contributions from non-committers and > the top reviewers, in order to encourage the members of the community. > > > ## Membership Data: > Apache Calcite was founded 2015-10-22 (7 years ago) > There are currently 56 committers and 25 PMC members in this project. > The Committer-to-PMC ratio is roughly 7:4. > > Community changes, past quarter: > - Chunwei Lei was added to the PMC on 2022-05-24 > - Vladimir Ozerov was added to the PMC on 2022-05-24 > - No new committers. Last addition was Alessandro Solimando on 2021-12-17. > > > ## Project Activity: > Avatica 1.21.0 was released on 2022-05-08, it was a maintenance release > with > dependency upgrades and added support for Oracle JDK 16 to 18. Of > particular > note is Log4j2 being upgrade to 2.16.0 and subsequently 2.17.0 and 2.17.1 > to > address CVE-2021-44228, CVE-2021-45105 and CVE-2021-44832. > > There has not been any Calcite release in this quarter. Calcite 1.31.0 was > planned for mid-June, but it has suffered a small delay. It should be > released > during July. > > > ## Community Health: > The overall status of the community is healthy and stable. We are keeping > the > good momentum in terms of contributions and opened discussions to improve > the > project. This is reflected also on the statistics of Jira & GitHub > activity: > -1% issues opened, +9% issues closed, -9% commits, +18% code contributors, > -11% PRs opened, +21% PRs closed. > > As usual, we struggle a bit on the PRs reviews, with some of them being > opened > and blocked for a while due a lack of active reviewers. This fact has > triggered an interesting discussion in both the Apache Calcite and Apache > Flink communities about the pros and cons of forking Calcite by the latter. > Many voices from the Apache Calcite community advised against this idea, > due > to the elevated maintenance costs in the long term. Instead, we are > discussing > several ideas about how to improve our PR review situation, among them the > possibility of increasing the number of reviewers by granting Calcite > committership per request to people who are already ASF committers (in > other > projects) and have a proven record of working with Calcite (on a case by > case > basis to be approved by the Calcite PMC). > > The number of non-committer (contributor) commits per month: > +-+-+-+ > |year |month| contributor_commits | > +-+-+-+ > | 2022| 4 | 15 | > | 2022| 5 | 13 | > | 2022| 6 | 19 | > +-+-+-+ > > The number of active reviewers per month: > +-+-+-+ > |year |month| active_reviewers | > +-+-+-+ > | 2022| 4 | 9 | > | 2022| 5 | 5 | > | 2022| 6 | 7 | > +-+-+-+ > > Top reviewers in the last 3 months: >
Re: [DISCUSS] How we choose a PMC chair
+1 from me as well. -- Michael Mior mm...@apache.org Le dim. 3 juil. 2022 à 19:46, Julian Hyde a écrit : > As you know, Calcite has a tradition of choosing a new PMC chair (VP) > each year, around the anniversary of the project's graduation[1][2]. I > think this is a great tradition, but I'd like to discuss an > improvement to that process. > > (I'm starting the conversation now - several months after the previous > vote, and several months before the next - so that it's clear that I > am not criticizing the process or the outcome or previous votes.) > > I've noticed that the outgoing chair sends an email on dev@ saying > words to the following effect: > > I think Xyz would be a great person to succeed me. > What do you all think? > > (I fear that I may have started this tradition when, at the end of my > tenure as first chair, I approached Jesus and asked him whether he'd > be prepared to do the job[3]. Mea culpa.) > > After such an outright endorsement, especially on a public list, it > would be churlish for someone to reply "Actually, I think Abc would be > better." As a result, it's rather difficult to have an open debate, > and the candidate selected by the outgoing chair tends to win > unopposed. > > I suggest that the outgoing chair says something like > > It's time to change the PMC chair. > Please send nominations to private@ and the PMC will discuss and vote. > > That would allow for several nominations, allow people to give reasons > why they prefer a candidate (without disparaging other candidates), > and lead to a more informed outcome. > > What do you think? Are there any other aspects of the election process > we should change? > > Julian > > [1] https://lists.apache.org/thread/rmj9qm9wlol3nb7z4phddoljbgvypkrt > [2] https://lists.apache.org/thread/5tzb8w655pj2vo9omz20th5jnbn9zww7 > [3] https://lists.apache.org/thread/y4wjdj5h1y3sypnlmhpoz9r6bkk3cv6o >
Re: [ANNOUNCE] New committer: Jing Zhang
Thanks everyone, Calcite is really an awesome project. It's my honour to be a committer of the Calcite community. I'm now working in the kuaishou company which serves to record and share videos taken by all users. Besides, I have been active in the Flink community for several years. In Apache Flink, we're currently heavily using Calcite, including SQL parser, validator and optimizer. I would like to contribute to further communication and collaboration between the Calcite and Flink communities. Best, Jing Zhang Alessandro Solimando 于2022年7月4日周一 14:43写道： > Congratulations, Jing! > > Best regards, > Alessandro > > On Mon, 4 Jul 2022 at 07:42, Chunwei Lei wrote: > > > Congratulations! > > > > > > > > Best, > > Chunwei > > > > > > On Mon, Jul 4, 2022 at 1:31 PM Forward Xu > wrote: > > > > > Congratulations! > > > > > > > > > Best, > > > > > > ForwardXu > > > > > > Benchao Li 于2022年7月4日周一 13:11写道： > > > > > > > Congratulations Jing! > > > > > > > > Francis Chuang 于2022年7月4日周一 10:43写道： > > > > > > > > > Congrats! > > > > > > > > > > On 4/07/2022 12:42 pm, Haisheng Yuan wrote: > > > > > > Apache Calcite's Project Management Committee (PMC) has invited > > Jing > > > > > Zhang > > > > > > to > > > > > > become a committer, and we are pleased to announce that she has > > > > accepted. > > > > > > > > > > > > Since Dec 2017, Jing has been an active and continuous > contributor > > to > > > > the > > > > > > Apache > > > > > > Calcite project. She has pushed high quality patches, fixing and > > > > > improving > > > > > > code > > > > > > around streaming plan. > > > > > > > > > > > > Jing, welcome, thank you for your contributions, and we look > > forward > > > to > > > > > your > > > > > > further interactions with the community! If you wish, please feel > > > free > > > > to > > > > > > tell > > > > > > us more about yourself and what you are working on. > > > > > > > > > > > > Haisheng (on behalf of the Apache Calcite PMC) > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Best, > > > > Benchao Li > > > > > > > > > >
Re: [ANNOUNCE] New committer: Benchao Li
Congratulations! Best, Jing Zhang Alessandro Solimando 于2022年7月4日周一 14:44写道： > Congratulations Benchao, well deserved! > > Best regards, > Alessandro > > On Mon, 4 Jul 2022 at 07:32, Forward Xu wrote: > > > Congratulations! > > > > > > Best, > > > > ForwardXu > > > > Francis Chuang 于2022年7月4日周一 10:21写道： > > > > > Congrats! > > > > > > On 4/07/2022 12:13 pm, Jiajun Xie wrote: > > > > Congrat Benchao Li, Well deserved! > > > > > > > > On Mon, 4 Jul 2022 at 09:21, Haisheng Yuan wrote: > > > > > > > >> Apache Calcite's Project Management Committee (PMC) has invited > > Benchao > > > Li > > > >> to > > > >> become a committer, and we are pleased to announce that he has > > accepted. > > > >> > > > >> Benchao has pushed a lot of high quality patches, fixing and > improving > > > code > > > >> around plan simplification and rules. Apart from code contributions, > > he > > > has > > > >> been regularly involved in the discussion and helping out others in > > the > > > >> mailing > > > >> list. > > > >> > > > >> Benchao, welcome, thank you for your contributions, and we look > > forward > > > to > > > >> your > > > >> further interactions with the community! If you wish, please feel > free > > > to > > > >> tell > > > >> us more about yourself and what you are working on. > > > >> > > > >> Haisheng (on behalf of the Apache Calcite PMC) > > > >> > > > > > > > > > >
Draft: board report for 2022 Q2
Hello, Below these lines you can find a draft of this quarter's board report. I plan to submit it at the end of this week. Please let me know if you have any additions or corrections. Note that our last report got a question from the board, for which I include a proposed answer in this report (cf "Issues" section). Best, Ruben ## Description: Apache Calcite is a highly customizable framework for parsing and planning queries on data in a wide variety of formats. It allows database-like access, and in particular a SQL interface and advanced query optimization, for data not residing in a traditional database. Avatica is a sub-project within Calcite and provides a framework for building local and remote JDBC and ODBC database drivers. Avatica has an independent release schedule and its own repository. ## Issues: There are no issues requiring board attention. The last report got one comment from the board: "It's certainly up to you all, but please remember that these reports are published, publicly. Are you sure you want to have your names and email addresses as part of this (public) report?". There is no problem from our side. This report has been pre-approved by the Calcite community and the section with names / emails has already been part of our reports in the "community health" section for a while. We decided to add it some time ago to highlight the contributions from non-committers and the top reviewers, in order to encourage the members of the community. ## Membership Data: Apache Calcite was founded 2015-10-22 (7 years ago) There are currently 56 committers and 25 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - Chunwei Lei was added to the PMC on 2022-05-24 - Vladimir Ozerov was added to the PMC on 2022-05-24 - No new committers. Last addition was Alessandro Solimando on 2021-12-17. ## Project Activity: Avatica 1.21.0 was released on 2022-05-08, it was a maintenance release with dependency upgrades and added support for Oracle JDK 16 to 18. Of particular note is Log4j2 being upgrade to 2.16.0 and subsequently 2.17.0 and 2.17.1 to address CVE-2021-44228, CVE-2021-45105 and CVE-2021-44832. There has not been any Calcite release in this quarter. Calcite 1.31.0 was planned for mid-June, but it has suffered a small delay. It should be released during July. ## Community Health: The overall status of the community is healthy and stable. We are keeping the good momentum in terms of contributions and opened discussions to improve the project. This is reflected also on the statistics of Jira & GitHub activity: -1% issues opened, +9% issues closed, -9% commits, +18% code contributors, -11% PRs opened, +21% PRs closed. As usual, we struggle a bit on the PRs reviews, with some of them being opened and blocked for a while due a lack of active reviewers. This fact has triggered an interesting discussion in both the Apache Calcite and Apache Flink communities about the pros and cons of forking Calcite by the latter. Many voices from the Apache Calcite community advised against this idea, due to the elevated maintenance costs in the long term. Instead, we are discussing several ideas about how to improve our PR review situation, among them the possibility of increasing the number of reviewers by granting Calcite committership per request to people who are already ASF committers (in other projects) and have a proven record of working with Calcite (on a case by case basis to be approved by the Calcite PMC). The number of non-committer (contributor) commits per month: +-+-+-+ |year |month| contributor_commits | +-+-+-+ | 2022| 4 | 15 | | 2022| 5 | 13 | | 2022| 6 | 19 | +-+-+-+ The number of active reviewers per month: +-+-+-+ |year |month| active_reviewers | +-+-+-+ | 2022| 4 | 9 | | 2022| 5 | 5 | | 2022| 6 | 7 | +-+-+-+ Top reviewers in the last 3 months: +--+-+ | committer | reviews | +--+-+ | Julian Hyde| 13 | | chunwei <37774589+chunwei...@users.noreply.github.com> | 13 | | rubenada
[jira] [Created] (CALCITE-5203) SQL: Support BOOLEAN datatype.
Andrey Mashenkov created CALCITE-5203: - Summary: SQL: Support BOOLEAN datatype. Key: CALCITE-5203 URL: https://issues.apache.org/jira/browse/CALCITE-5203 Project: Calcite Issue Type: Bug Reporter: Andrey Mashenkov For now, BOOLEAN column is not supported by storage. We could map the Bitset(1), but it is not supported as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] How we choose a PMC chair
+1 for the improvement. As the current chair until the end of the year, when do you think it would be a good time to send the email to the dev list with the message "It's time to change the PMC chair, please send nominations to private@ ..." to start this discussion? Around beginning of December? Best, Ruben On Mon, Jul 4, 2022 at 7:45 AM Alessandro Solimando < alessandro.solima...@gmail.com> wrote: > +1 from me too on adopting Julian's suggestion. > > Best regards, > Alessandro > > On Mon, 4 Jul 2022 at 07:37, Forward Xu wrote: > > > +1 > > > > Haisheng Yuan 于2022年7月4日周一 08:32写道： > > > > > +1 to the improvement. > > > > > > On 2022/07/04 00:13:58 Francis Chuang wrote: > > > > +1 I think this is a good idea. We have a lot of capable PMC members > > and > > > > it would be of great benefit to the project if all of them were > > > > considered during the PMC chair selection process. > > > > > > > > On 4/07/2022 9:46 am, Julian Hyde wrote: > > > > > As you know, Calcite has a tradition of choosing a new PMC chair > (VP) > > > > > each year, around the anniversary of the project's > graduation[1][2]. > > I > > > > > think this is a great tradition, but I'd like to discuss an > > > > > improvement to that process. > > > > > > > > > > (I'm starting the conversation now - several months after the > > previous > > > > > vote, and several months before the next - so that it's clear that > I > > > > > am not criticizing the process or the outcome or previous votes.) > > > > > > > > > > I've noticed that the outgoing chair sends an email on dev@ saying > > > > > words to the following effect: > > > > > > > > > >I think Xyz would be a great person to succeed me. > > > > >What do you all think? > > > > > > > > > > (I fear that I may have started this tradition when, at the end of > my > > > > > tenure as first chair, I approached Jesus and asked him whether > he'd > > > > > be prepared to do the job[3]. Mea culpa.) > > > > > > > > > > After such an outright endorsement, especially on a public list, it > > > > > would be churlish for someone to reply "Actually, I think Abc would > > be > > > > > better." As a result, it's rather difficult to have an open debate, > > > > > and the candidate selected by the outgoing chair tends to win > > > > > unopposed. > > > > > > > > > > I suggest that the outgoing chair says something like > > > > > > > > > >It's time to change the PMC chair. > > > > >Please send nominations to private@ and the PMC will discuss > and > > > vote. > > > > > > > > > > That would allow for several nominations, allow people to give > > reasons > > > > > why they prefer a candidate (without disparaging other candidates), > > > > > and lead to a more informed outcome. > > > > > > > > > > What do you think? Are there any other aspects of the election > > process > > > > > we should change? > > > > > > > > > > Julian > > > > > > > > > > [1] > https://lists.apache.org/thread/rmj9qm9wlol3nb7z4phddoljbgvypkrt > > > > > [2] > https://lists.apache.org/thread/5tzb8w655pj2vo9omz20th5jnbn9zww7 > > > > > [3] > https://lists.apache.org/thread/y4wjdj5h1y3sypnlmhpoz9r6bkk3cv6o > > > > > > > > > >
Re: [DISCUSS] How we choose a PMC chair
+1 from me too on adopting Julian's suggestion. Best regards, Alessandro On Mon, 4 Jul 2022 at 07:37, Forward Xu wrote: > +1 > > Haisheng Yuan 于2022年7月4日周一 08:32写道： > > > +1 to the improvement. > > > > On 2022/07/04 00:13:58 Francis Chuang wrote: > > > +1 I think this is a good idea. We have a lot of capable PMC members > and > > > it would be of great benefit to the project if all of them were > > > considered during the PMC chair selection process. > > > > > > On 4/07/2022 9:46 am, Julian Hyde wrote: > > > > As you know, Calcite has a tradition of choosing a new PMC chair (VP) > > > > each year, around the anniversary of the project's graduation[1][2]. > I > > > > think this is a great tradition, but I'd like to discuss an > > > > improvement to that process. > > > > > > > > (I'm starting the conversation now - several months after the > previous > > > > vote, and several months before the next - so that it's clear that I > > > > am not criticizing the process or the outcome or previous votes.) > > > > > > > > I've noticed that the outgoing chair sends an email on dev@ saying > > > > words to the following effect: > > > > > > > >I think Xyz would be a great person to succeed me. > > > >What do you all think? > > > > > > > > (I fear that I may have started this tradition when, at the end of my > > > > tenure as first chair, I approached Jesus and asked him whether he'd > > > > be prepared to do the job[3]. Mea culpa.) > > > > > > > > After such an outright endorsement, especially on a public list, it > > > > would be churlish for someone to reply "Actually, I think Abc would > be > > > > better." As a result, it's rather difficult to have an open debate, > > > > and the candidate selected by the outgoing chair tends to win > > > > unopposed. > > > > > > > > I suggest that the outgoing chair says something like > > > > > > > >It's time to change the PMC chair. > > > >Please send nominations to private@ and the PMC will discuss and > > vote. > > > > > > > > That would allow for several nominations, allow people to give > reasons > > > > why they prefer a candidate (without disparaging other candidates), > > > > and lead to a more informed outcome. > > > > > > > > What do you think? Are there any other aspects of the election > process > > > > we should change? > > > > > > > > Julian > > > > > > > > [1] https://lists.apache.org/thread/rmj9qm9wlol3nb7z4phddoljbgvypkrt > > > > [2] https://lists.apache.org/thread/5tzb8w655pj2vo9omz20th5jnbn9zww7 > > > > [3] https://lists.apache.org/thread/y4wjdj5h1y3sypnlmhpoz9r6bkk3cv6o > > > > > >
Re: [ANNOUNCE] New committer: Benchao Li
Congratulations Benchao, well deserved! Best regards, Alessandro On Mon, 4 Jul 2022 at 07:32, Forward Xu wrote: > Congratulations! > > > Best, > > ForwardXu > > Francis Chuang 于2022年7月4日周一 10:21写道： > > > Congrats! > > > > On 4/07/2022 12:13 pm, Jiajun Xie wrote: > > > Congrat Benchao Li, Well deserved! > > > > > > On Mon, 4 Jul 2022 at 09:21, Haisheng Yuan wrote: > > > > > >> Apache Calcite's Project Management Committee (PMC) has invited > Benchao > > Li > > >> to > > >> become a committer, and we are pleased to announce that he has > accepted. > > >> > > >> Benchao has pushed a lot of high quality patches, fixing and improving > > code > > >> around plan simplification and rules. Apart from code contributions, > he > > has > > >> been regularly involved in the discussion and helping out others in > the > > >> mailing > > >> list. > > >> > > >> Benchao, welcome, thank you for your contributions, and we look > forward > > to > > >> your > > >> further interactions with the community! If you wish, please feel free > > to > > >> tell > > >> us more about yourself and what you are working on. > > >> > > >> Haisheng (on behalf of the Apache Calcite PMC) > > >> > > > > > >
Re: [ANNOUNCE] New committer: Jing Zhang
Congratulations, Jing! Best regards, Alessandro On Mon, 4 Jul 2022 at 07:42, Chunwei Lei wrote: > Congratulations! > > > > Best, > Chunwei > > > On Mon, Jul 4, 2022 at 1:31 PM Forward Xu wrote: > > > Congratulations! > > > > > > Best, > > > > ForwardXu > > > > Benchao Li 于2022年7月4日周一 13:11写道： > > > > > Congratulations Jing! > > > > > > Francis Chuang 于2022年7月4日周一 10:43写道： > > > > > > > Congrats! > > > > > > > > On 4/07/2022 12:42 pm, Haisheng Yuan wrote: > > > > > Apache Calcite's Project Management Committee (PMC) has invited > Jing > > > > Zhang > > > > > to > > > > > become a committer, and we are pleased to announce that she has > > > accepted. > > > > > > > > > > Since Dec 2017, Jing has been an active and continuous contributor > to > > > the > > > > > Apache > > > > > Calcite project. She has pushed high quality patches, fixing and > > > > improving > > > > > code > > > > > around streaming plan. > > > > > > > > > > Jing, welcome, thank you for your contributions, and we look > forward > > to > > > > your > > > > > further interactions with the community! If you wish, please feel > > free > > > to > > > > > tell > > > > > us more about yourself and what you are working on. > > > > > > > > > > Haisheng (on behalf of the Apache Calcite PMC) > > > > > > > > > > > > > > > > > > -- > > > > > > Best, > > > Benchao Li > > > > > >
