Thank you Florian for considering my suggestions. Reg#1: I am glad to hear that it is automated. I didn't know that. (Some Apache projects still add these metrics to their board reports for some reason but I agree that it is not required in our report)
Reg #3 Discord provides some insights out of the box but only server Admins/Owners can view that. Some examples are highlighted in https://discord.com/moderation/1500000179521-341:-Understanding-Your-Community-Through-Insights. Discord is another medium via which users of Apache TinkerPop communicate with the community and we also highlight it very prominently at the homepage. Hence, metrics from discord server will be as relevant as the metrics from user mailing lists. Reg#4 Ack. Reg#5 I agree with your suggested approach. We should have a discussion first to identify known pain points and later on decide whether to add it to the report or not. I will start a thread with an initial list soon. Regards, Divij Vaidya On Wed, Apr 6, 2022 at 1:26 PM Florian Hockmann <[email protected]> wrote: > Hey Divij, > > Thanks a lot for your feedback. I'll respond to your suggestions > individually. > > > One of the aims of this report (correct me if I am wrong here) is to > represent the "health" of the project. > > Sure, that is also how it's described in our dev docs: > https://tinkerpop.apache.org/docs/current/dev/developer/#_board_reports > <discuss general project health, project direction, community > growth/activity, etc.> > > > Now to your specific suggestions: > > > 1. Mailing list activity compared to the previous quarter. > > 2. PRs compared to the previous quarter. > > These are of course interesting stats. These are however already covered > for the board by the automatic reporting tool used by the ASF. It generates > stats about project activity in the following areas: > - mailing list > - JIRA issues > - Commits > - PRs > Unfortunately, these stats seem to be private, but since we're talking > about the report for the ASF board here, I think they cover this already > sufficiently. > > > > 3. Discord activity compared to the previous quarter. > > We could of course add statistics about Discord, but I don't know how to > obtain them and what exactly we want to measure there. Stephen mentioned in > the last board report that the number of users on our server has grown to > over 250. Now we seem to be already at over 400. I could add that > information to the report. Would you consider that an interesting metric > for the board? If you have another concrete suggestion regarding Discord, > then I can of course also add that. > > > > 4. Any new notable projects / provider which started using TinkerPop? > > This is something that we always include in the board reports but I'm > simply not aware of any such project or provider which started using > TinkerPop in the last quarter. If I just missed it, then I'm happy to add > it to the report. > > > > 5. Top 5 problems that users of the project complain about and how are > we planning to address them. > > Now this is something that I would like to have myself, completely > independent of this board report. I think this could also already be a bit > too detailed for the ASF board, but very interesting for ourselves. > TinkerPop is of course a project completely driven by the community where > every contributor can contribute whatever they like, irrespective of > whether it's a feature requested by many users or just something they would > like to improve for themselves. But many contributors would probably like > to know what the biggest pain points for users are so they can concentrate > their efforts on areas that have a high impact. If we know what the biggest > pain points are, then we can of course discuss as a next step how we want > to address them. But first we need to find a way to determine what these > pain points are and I'm not sure yet how we could solve this. Votes on JIRA > issues might be a first thing to look into, but they have the disadvantage > that the entry bar to create an account for the ASF JIRA just to vote on an > issue is probably too high for many users. (The issues with most votes that > are currently open just have 2 votes at the moment [1].) > Divij, how about we first try to determine what these top problems / > biggest pain points are and then we can afterwards decide whether that is > something that we would like to add to the board report? I think we should > discuss this topic then in a separate thread. Feel free to start a thread > here on the dev list if you agree. > > Regards, > Florian > > [1]: > https://issues.apache.org/jira/browse/TINKERPOP-942?jql=project%20%3D%20TINKERPOP%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20votes%20DESC%2C%20priority%20DESC%2C%20updated%20DESC > > -----Ursprüngliche Nachricht----- > Von: Divij Vaidya <[email protected]> > Gesendet: Mittwoch, 6. April 2022 12:25 > An: [email protected] > Betreff: Re: [DISCUSS] Draft ASF Board Report - April 2022 > > Hey Florian > > Couple of thoughts/ideas for your consideration. > > One of the aims of this report (correct me if I am wrong here) is to > represent the "health" of the project. In light of the same, can we > consider adding the following to the report: > 1. Mailing list activity compared to the previous quarter. > 2. PRs compared to the previous quarter. > 3. Discord activity compared to the previous quarter. > 4. Any new notable projects / provider which started using TinkerPop? > 5. Top 5 problems that users of the project complain about and how are we > planning to address them. > > Regards, > Divij Vaidya > > > > On Wed, Apr 6, 2022 at 11:53 AM Florian Hockmann <[email protected]> > wrote: > > > Here is the attached draft of our board report for this quarter - > > please let me know if there is anything to add or edit. > > > > > > > > ---------------------------------------------------------------------- > > ---- > > > > > > > > ## Description: > > > > Apache TinkerPop is a graph computing framework for both graph > > databases > > > > (OLTP) and graph analytic systems (OLAP). > > > > > > > > ## Activity: > > > > TinkerPop is currently in the process of releasing 3.5.3 and 3.6.0. > > Version > > 3.5.3 is mostly a maintenance release. 3.6.0 represents a major > > release with breaking changes and a variety of new features, including > > support for regular expressions directly in Gremlin and better support > > for commonly used upsert-like functionality. > > > > The default logging implementation in the distributions of Gremlin > > Server and Gremlin Console will also be changed in 3.6.0 from log4j > > 1.2.x to logback due to the vulnerability CVE-2019-17571 [1]. > > > > > > > > These releases will be accompanied by the first pre-release versions > > of gremlin-go, making Gremlin natively available in Go which has been > > the mostly requested programming language for which we did not offer a > > Gremlin Language Variant (GLV)[2] yet by users over the last years. > > > > Notable about this new GLV is also that it has not been developed by a > > single contributor but by a group of contributors who collaborated on > > this, an effort that was mostly led by committer Lyndon Bauto. > > > > > > > > We have welcomed Mike Personick as a new committer who has already > > contributed great improvements around core aspects of Gremlin. > > > > > > > > ## Issues: > > > > There are no issues requiring board attention at this time. > > > > > > > > ## Releases: > > > > - 3.4.13 (January 10, 2022) > > > > - 3.5.2 (January 10, 2022) > > > > > > > > ## PMC/Committer: > > > > - Last PMC addition was Kelvin Lawrence/Josh Shinavier - June 2021 > > > > - Last committer addition was Mike Personick - March 2022 > > > > > > > > ## Links > > > > [1] https://nvd.nist.gov/vuln/detail/CVE-2019-17571 > > > > [2] > > https://tinkerpop.apache.org/docs/3.5.2/reference/#gremlin-drivers-var > > iants > > > > > >
