Apache Ignite Board report, August, 2020

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Apache Ignite Board report, August, 2020

Dmitriy Pavlov-3
Dear Apache Ignite community,

PMC should submit the board report, not later than 12 August.

Previous board with drafted publicly with sharing with all developers
community. Let us try it one more time. Please share your thoughts on what
might be added to the board meeting agenda.

## Description:
The mission of Ignite is the creation and maintenance of software related
to
High-performance, integrated and distributed in-memory platform for
computing
and transacting on large-scale data sets in real-time

## Issues:
There are no issues requiring board attention. (hopefully)

## Membership Data:
Apache Ignite was founded 2015-08-19 (5 years ago)
There are currently 53 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- No new PMC members. Last addition was Maxim Muzafarov on 2020-04-28.
- Artem Budnikov was added as committer on 2020-07-14
- Sergey Chugunov was added as committer on 2020-06-12

## Project Activity:
Apache Ignite community is working on preparing release 2.9.0.
Release 3.0 discussion has been resurrected.
Project documentation migration from readme.io to the code started.

## Community Health:
There is a decrease in mailing list traffic comparing to the previous
quarter (-10-20%). Activity related to code commits remains stable.
The first committer was elected because of merit related to the non-code
contribution, but efforts in the documentation.
Apache Ignite users, developers, and PMC members continued to give talks
related to the product in C-19 situation mostly online. See also
https://ignite.apache.org/events.html

Sincerely,
Dmitriy Pavlov
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite Board report, August, 2020

dmagda
Hi Dmitry,

Thanks for sending the draft. I would suggest mentioning the following in
the project activity section:

   - Ignite Extensions project that decouples the core features from
   3rd-party integrations is being moved forward rapidly
   <https://samaitra.blogspot.com/2020/08/apache-ignite-extensions.html>.
   - Community members started the Virtual Apache Ignite Meetup
   <https://www.meetup.com/Apache-Ignite-Virtual-Meetup/> group that is
   envisioned as a place to meet and discuss Ignite best practices, internals,
   use cases, share experiences.
   - Ignite documentation is being migrated from the readme.io to the
   Ignite codebase. The first version is planned to be released with Ignite
   2.9 release.

Also, I would just put the definition of Ignite from the website in the
"description" section. That's what usually PMCs of other projects do in
their reports:

*Apache Ignite® is a horizontally scalable, fault-tolerant distributed
in-memory computing platform for building real-time applications that can
process terabytes of data with in-memory speed.*

-
Denis


On Mon, Aug 10, 2020 at 12:14 PM Dmitriy Pavlov <[hidden email]> wrote:

> Dear Apache Ignite community,
>
> PMC should submit the board report, not later than 12 August.
>
> Previous board with drafted publicly with sharing with all developers
> community. Let us try it one more time. Please share your thoughts on what
> might be added to the board meeting agenda.
>
> ## Description:
> The mission of Ignite is the creation and maintenance of software related
> to
> High-performance, integrated and distributed in-memory platform for
> computing
> and transacting on large-scale data sets in real-time
>
> ## Issues:
> There are no issues requiring board attention. (hopefully)
>
> ## Membership Data:
> Apache Ignite was founded 2015-08-19 (5 years ago)
> There are currently 53 committers and 34 PMC members in this project.
> The Committer-to-PMC ratio is roughly 7:5.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Maxim Muzafarov on 2020-04-28.
> - Artem Budnikov was added as committer on 2020-07-14
> - Sergey Chugunov was added as committer on 2020-06-12
>
> ## Project Activity:
> Apache Ignite community is working on preparing release 2.9.0.
> Release 3.0 discussion has been resurrected.
> Project documentation migration from readme.io to the code started.
>
> ## Community Health:
> There is a decrease in mailing list traffic comparing to the previous
> quarter (-10-20%). Activity related to code commits remains stable.
> The first committer was elected because of merit related to the non-code
> contribution, but efforts in the documentation.
> Apache Ignite users, developers, and PMC members continued to give talks
> related to the product in C-19 situation mostly online. See also
> https://ignite.apache.org/events.html
>
> Sincerely,
> Dmitriy Pavlov
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite Board report, August, 2020

Dmitriy Pavlov-3
Hi Denis,

thank you for your valuable feedback, this makes perfect sense to include
all these points.

A little bit off-top: PMCs, would anybody like to be a PMC representative
for the new group in addition to Denis M.? It is recommended to have 2
members at least to make sure that an event using the Apache-project brand
follows branding policy and all other Apache guidelines?

Anything else to add to the report?

Sincerely,
Dmitriy Pavlov

пн, 10 авг. 2020 г. в 23:27, Denis Magda <[hidden email]>:

> Hi Dmitry,
>
> Thanks for sending the draft. I would suggest mentioning the following in
> the project activity section:
>
>    - Ignite Extensions project that decouples the core features from
>    3rd-party integrations is being moved forward rapidly
>    <https://samaitra.blogspot.com/2020/08/apache-ignite-extensions.html>.
>    - Community members started the Virtual Apache Ignite Meetup
>    <https://www.meetup.com/Apache-Ignite-Virtual-Meetup/> group that is
>    envisioned as a place to meet and discuss Ignite best practices,
> internals,
>    use cases, share experiences.
>    - Ignite documentation is being migrated from the readme.io to the
>    Ignite codebase. The first version is planned to be released with Ignite
>    2.9 release.
>
> Also, I would just put the definition of Ignite from the website in the
> "description" section. That's what usually PMCs of other projects do in
> their reports:
>
> *Apache Ignite® is a horizontally scalable, fault-tolerant distributed
> in-memory computing platform for building real-time applications that can
> process terabytes of data with in-memory speed.*
>
> -
> Denis
>
>
> On Mon, Aug 10, 2020 at 12:14 PM Dmitriy Pavlov <[hidden email]>
> wrote:
>
> > Dear Apache Ignite community,
> >
> > PMC should submit the board report, not later than 12 August.
> >
> > Previous board with drafted publicly with sharing with all developers
> > community. Let us try it one more time. Please share your thoughts on
> what
> > might be added to the board meeting agenda.
> >
> > ## Description:
> > The mission of Ignite is the creation and maintenance of software related
> > to
> > High-performance, integrated and distributed in-memory platform for
> > computing
> > and transacting on large-scale data sets in real-time
> >
> > ## Issues:
> > There are no issues requiring board attention. (hopefully)
> >
> > ## Membership Data:
> > Apache Ignite was founded 2015-08-19 (5 years ago)
> > There are currently 53 committers and 34 PMC members in this project.
> > The Committer-to-PMC ratio is roughly 7:5.
> >
> > Community changes, past quarter:
> > - No new PMC members. Last addition was Maxim Muzafarov on 2020-04-28.
> > - Artem Budnikov was added as committer on 2020-07-14
> > - Sergey Chugunov was added as committer on 2020-06-12
> >
> > ## Project Activity:
> > Apache Ignite community is working on preparing release 2.9.0.
> > Release 3.0 discussion has been resurrected.
> > Project documentation migration from readme.io to the code started.
> >
> > ## Community Health:
> > There is a decrease in mailing list traffic comparing to the previous
> > quarter (-10-20%). Activity related to code commits remains stable.
> > The first committer was elected because of merit related to the non-code
> > contribution, but efforts in the documentation.
> > Apache Ignite users, developers, and PMC members continued to give talks
> > related to the product in C-19 situation mostly online. See also
> > https://ignite.apache.org/events.html
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite Board report, August, 2020

dmagda
>
> A little bit off-top: PMCs, would anybody like to be a PMC representative
> for the new group in addition to Denis M.? It is recommended to have 2
> members at least to make sure that an event using the Apache-project brand
> follows branding policy and all other Apache guidelines?


This should be unnecessary from the branding perspective as long as the
meetup group description already follows basic trademark guidelines
(see, a Cassandra
meetup group <https://www.meetup.com/Apache-Cassandra-Bay-Area/> for
comparison). Based on my experience this is the primary rule to follow. As
for speakers, they are free to talk about Ignite without any approval by
the Ignite PMC or ASF Legal. Please let me know if I'm missing anything.

In the future, we might need help with event coordination and organization
and will be happy to see Ignite committers and PMC members among
organizers. But as of now, it's premature since the group has just been
started.

-
Denis


On Mon, Aug 10, 2020 at 2:45 PM Dmitriy Pavlov <[hidden email]> wrote:

> Hi Denis,
>
> thank you for your valuable feedback, this makes perfect sense to include
> all these points.
>
> A little bit off-top: PMCs, would anybody like to be a PMC representative
> for the new group in addition to Denis M.? It is recommended to have 2
> members at least to make sure that an event using the Apache-project brand
> follows branding policy and all other Apache guidelines?
>
> Anything else to add to the report?
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 10 авг. 2020 г. в 23:27, Denis Magda <[hidden email]>:
>
> > Hi Dmitry,
> >
> > Thanks for sending the draft. I would suggest mentioning the following in
> > the project activity section:
> >
> >    - Ignite Extensions project that decouples the core features from
> >    3rd-party integrations is being moved forward rapidly
> >    <https://samaitra.blogspot.com/2020/08/apache-ignite-extensions.html
> >.
> >    - Community members started the Virtual Apache Ignite Meetup
> >    <https://www.meetup.com/Apache-Ignite-Virtual-Meetup/> group that is
> >    envisioned as a place to meet and discuss Ignite best practices,
> > internals,
> >    use cases, share experiences.
> >    - Ignite documentation is being migrated from the readme.io to the
> >    Ignite codebase. The first version is planned to be released with
> Ignite
> >    2.9 release.
> >
> > Also, I would just put the definition of Ignite from the website in the
> > "description" section. That's what usually PMCs of other projects do in
> > their reports:
> >
> > *Apache Ignite® is a horizontally scalable, fault-tolerant distributed
> > in-memory computing platform for building real-time applications that can
> > process terabytes of data with in-memory speed.*
> >
> > -
> > Denis
> >
> >
> > On Mon, Aug 10, 2020 at 12:14 PM Dmitriy Pavlov <[hidden email]>
> > wrote:
> >
> > > Dear Apache Ignite community,
> > >
> > > PMC should submit the board report, not later than 12 August.
> > >
> > > Previous board with drafted publicly with sharing with all developers
> > > community. Let us try it one more time. Please share your thoughts on
> > what
> > > might be added to the board meeting agenda.
> > >
> > > ## Description:
> > > The mission of Ignite is the creation and maintenance of software
> related
> > > to
> > > High-performance, integrated and distributed in-memory platform for
> > > computing
> > > and transacting on large-scale data sets in real-time
> > >
> > > ## Issues:
> > > There are no issues requiring board attention. (hopefully)
> > >
> > > ## Membership Data:
> > > Apache Ignite was founded 2015-08-19 (5 years ago)
> > > There are currently 53 committers and 34 PMC members in this project.
> > > The Committer-to-PMC ratio is roughly 7:5.
> > >
> > > Community changes, past quarter:
> > > - No new PMC members. Last addition was Maxim Muzafarov on 2020-04-28.
> > > - Artem Budnikov was added as committer on 2020-07-14
> > > - Sergey Chugunov was added as committer on 2020-06-12
> > >
> > > ## Project Activity:
> > > Apache Ignite community is working on preparing release 2.9.0.
> > > Release 3.0 discussion has been resurrected.
> > > Project documentation migration from readme.io to the code started.
> > >
> > > ## Community Health:
> > > There is a decrease in mailing list traffic comparing to the previous
> > > quarter (-10-20%). Activity related to code commits remains stable.
> > > The first committer was elected because of merit related to the
> non-code
> > > contribution, but efforts in the documentation.
> > > Apache Ignite users, developers, and PMC members continued to give
> talks
> > > related to the product in C-19 situation mostly online. See also
> > > https://ignite.apache.org/events.html
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite Board report, August, 2020

Saikat Maitra
Hi Dmitriy, Denis

I am thinking if it would be good to add that this year a dedicated track
for Apache Ignite is available in APACHECON 2020 @Home on September 29th.

https://apachecon.com/acah2020/tracks/

Regards,
Saikat

On Mon, Aug 10, 2020 at 7:18 PM Denis Magda <[hidden email]> wrote:

> >
> > A little bit off-top: PMCs, would anybody like to be a PMC representative
> > for the new group in addition to Denis M.? It is recommended to have 2
> > members at least to make sure that an event using the Apache-project
> brand
> > follows branding policy and all other Apache guidelines?
>
>
> This should be unnecessary from the branding perspective as long as the
> meetup group description already follows basic trademark guidelines
> (see, a Cassandra
> meetup group <https://www.meetup.com/Apache-Cassandra-Bay-Area/> for
> comparison). Based on my experience this is the primary rule to follow. As
> for speakers, they are free to talk about Ignite without any approval by
> the Ignite PMC or ASF Legal. Please let me know if I'm missing anything.
>
> In the future, we might need help with event coordination and organization
> and will be happy to see Ignite committers and PMC members among
> organizers. But as of now, it's premature since the group has just been
> started.
>
> -
> Denis
>
>
> On Mon, Aug 10, 2020 at 2:45 PM Dmitriy Pavlov <[hidden email]> wrote:
>
> > Hi Denis,
> >
> > thank you for your valuable feedback, this makes perfect sense to include
> > all these points.
> >
> > A little bit off-top: PMCs, would anybody like to be a PMC representative
> > for the new group in addition to Denis M.? It is recommended to have 2
> > members at least to make sure that an event using the Apache-project
> brand
> > follows branding policy and all other Apache guidelines?
> >
> > Anything else to add to the report?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пн, 10 авг. 2020 г. в 23:27, Denis Magda <[hidden email]>:
> >
> > > Hi Dmitry,
> > >
> > > Thanks for sending the draft. I would suggest mentioning the following
> in
> > > the project activity section:
> > >
> > >    - Ignite Extensions project that decouples the core features from
> > >    3rd-party integrations is being moved forward rapidly
> > >    <
> https://samaitra.blogspot.com/2020/08/apache-ignite-extensions.html
> > >.
> > >    - Community members started the Virtual Apache Ignite Meetup
> > >    <https://www.meetup.com/Apache-Ignite-Virtual-Meetup/> group that
> is
> > >    envisioned as a place to meet and discuss Ignite best practices,
> > > internals,
> > >    use cases, share experiences.
> > >    - Ignite documentation is being migrated from the readme.io to the
> > >    Ignite codebase. The first version is planned to be released with
> > Ignite
> > >    2.9 release.
> > >
> > > Also, I would just put the definition of Ignite from the website in the
> > > "description" section. That's what usually PMCs of other projects do in
> > > their reports:
> > >
> > > *Apache Ignite® is a horizontally scalable, fault-tolerant distributed
> > > in-memory computing platform for building real-time applications that
> can
> > > process terabytes of data with in-memory speed.*
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Mon, Aug 10, 2020 at 12:14 PM Dmitriy Pavlov <[hidden email]>
> > > wrote:
> > >
> > > > Dear Apache Ignite community,
> > > >
> > > > PMC should submit the board report, not later than 12 August.
> > > >
> > > > Previous board with drafted publicly with sharing with all developers
> > > > community. Let us try it one more time. Please share your thoughts on
> > > what
> > > > might be added to the board meeting agenda.
> > > >
> > > > ## Description:
> > > > The mission of Ignite is the creation and maintenance of software
> > related
> > > > to
> > > > High-performance, integrated and distributed in-memory platform for
> > > > computing
> > > > and transacting on large-scale data sets in real-time
> > > >
> > > > ## Issues:
> > > > There are no issues requiring board attention. (hopefully)
> > > >
> > > > ## Membership Data:
> > > > Apache Ignite was founded 2015-08-19 (5 years ago)
> > > > There are currently 53 committers and 34 PMC members in this project.
> > > > The Committer-to-PMC ratio is roughly 7:5.
> > > >
> > > > Community changes, past quarter:
> > > > - No new PMC members. Last addition was Maxim Muzafarov on
> 2020-04-28.
> > > > - Artem Budnikov was added as committer on 2020-07-14
> > > > - Sergey Chugunov was added as committer on 2020-06-12
> > > >
> > > > ## Project Activity:
> > > > Apache Ignite community is working on preparing release 2.9.0.
> > > > Release 3.0 discussion has been resurrected.
> > > > Project documentation migration from readme.io to the code started.
> > > >
> > > > ## Community Health:
> > > > There is a decrease in mailing list traffic comparing to the previous
> > > > quarter (-10-20%). Activity related to code commits remains stable.
> > > > The first committer was elected because of merit related to the
> > non-code
> > > > contribution, but efforts in the documentation.
> > > > Apache Ignite users, developers, and PMC members continued to give
> > talks
> > > > related to the product in C-19 situation mostly online. See also
> > > > https://ignite.apache.org/events.html
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Apache Ignite Board report, August, 2020

Dmitriy Pavlov-3
Hi Saikat, thank you, it definitely makes sense to add.

So, the following version has been filed to the board meeting agenda.

## Description:
Apache Ignite® is a horizontally scalable, fault-tolerant distributed
in-memory computing platform for building real-time applications that can
process terabytes of data with in-memory speed

## Issues:
There are no issues requiring board attention.

## Membership Data:
Apache Ignite was founded 2015-08-19 (5 years ago)
There are currently 53 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.

Community changes, past quarter:
- No new PMC members. Last addition was Maxim Muzafarov on 2020-04-28.
- Artem Budnikov was added as committer on 2020-07-14
- Sergey Chugunov was added as committer on 2020-06-12

## Project Activity:
- Apache Ignite community is working on preparing release 2.9
- Release 3.0 discussion has been started again.
- Ignite Extensions project that decouples the core features from
   3rd-party integrations is moving forward rapidly
   https://samaitra.blogspot.com/2020/08/apache-ignite-extensions.html
- New features will be available at 2.9: Persistence cache snapshot,
   Tracing, Java Thin Client cluster discovery & compute
- Ignite documentation is being migrated from the readme.io to the
   Ignite codebase. The first version is planned to be released with Ignite
   2.9 release.

## Community Health:
- There is a decrease in mailing list traffic comparing to the previous
   quarter (-10-20%). Activity related to commits count remains stable.
- Apache Ignite users, developers, and PMC members continued to give
   talks related to the product in the C-19 situation mostly online.
   See also https://ignite.apache.org/events.html
- Community members started the Virtual Apache Ignite Meetup
   https://www.meetup.com/Apache-Ignite-Virtual-Meetup/ group that is
   envisioned as a place to meet and discuss Ignite best practices,
internals,
   use cases, share experiences.
- There is a dedicated track for Apache Ignite available at APACHECON 2020
   @Home on September 29th. https://apachecon.com/acah2020/tracks/


Thanks for feedback,

Sincerely,
Dmitriy Pavlov

вт, 11 авг. 2020 г. в 04:40, Saikat Maitra <[hidden email]>:

> Hi Dmitriy, Denis
>
> I am thinking if it would be good to add that this year a dedicated track
> for Apache Ignite is available in APACHECON 2020 @Home on September 29th.
>
> https://apachecon.com/acah2020/tracks/
>
> Regards,
> Saikat
>
> On Mon, Aug 10, 2020 at 7:18 PM Denis Magda <[hidden email]> wrote:
>
> > >
> > > A little bit off-top: PMCs, would anybody like to be a PMC
> representative
> > > for the new group in addition to Denis M.? It is recommended to have 2
> > > members at least to make sure that an event using the Apache-project
> > brand
> > > follows branding policy and all other Apache guidelines?
> >
> >
> > This should be unnecessary from the branding perspective as long as the
> > meetup group description already follows basic trademark guidelines
> > (see, a Cassandra
> > meetup group <https://www.meetup.com/Apache-Cassandra-Bay-Area/> for
> > comparison). Based on my experience this is the primary rule to follow.
> As
> > for speakers, they are free to talk about Ignite without any approval by
> > the Ignite PMC or ASF Legal. Please let me know if I'm missing anything.
> >
> > In the future, we might need help with event coordination and
> organization
> > and will be happy to see Ignite committers and PMC members among
> > organizers. But as of now, it's premature since the group has just been
> > started.
> >
> > -
> > Denis
> >
> >
> > On Mon, Aug 10, 2020 at 2:45 PM Dmitriy Pavlov <[hidden email]>
> wrote:
> >
> > > Hi Denis,
> > >
> > > thank you for your valuable feedback, this makes perfect sense to
> include
> > > all these points.
> > >
> > > A little bit off-top: PMCs, would anybody like to be a PMC
> representative
> > > for the new group in addition to Denis M.? It is recommended to have 2
> > > members at least to make sure that an event using the Apache-project
> > brand
> > > follows branding policy and all other Apache guidelines?
> > >
> > > Anything else to add to the report?
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > пн, 10 авг. 2020 г. в 23:27, Denis Magda <[hidden email]>:
> > >
> > > > Hi Dmitry,
> > > >
> > > > Thanks for sending the draft. I would suggest mentioning the
> following
> > in
> > > > the project activity section:
> > > >
> > > >    - Ignite Extensions project that decouples the core features from
> > > >    3rd-party integrations is being moved forward rapidly
> > > >    <
> > https://samaitra.blogspot.com/2020/08/apache-ignite-extensions.html
> > > >.
> > > >    - Community members started the Virtual Apache Ignite Meetup
> > > >    <https://www.meetup.com/Apache-Ignite-Virtual-Meetup/> group that
> > is
> > > >    envisioned as a place to meet and discuss Ignite best practices,
> > > > internals,
> > > >    use cases, share experiences.
> > > >    - Ignite documentation is being migrated from the readme.io to
> the
> > > >    Ignite codebase. The first version is planned to be released with
> > > Ignite
> > > >    2.9 release.
> > > >
> > > > Also, I would just put the definition of Ignite from the website in
> the
> > > > "description" section. That's what usually PMCs of other projects do
> in
> > > > their reports:
> > > >
> > > > *Apache Ignite® is a horizontally scalable, fault-tolerant
> distributed
> > > > in-memory computing platform for building real-time applications that
> > can
> > > > process terabytes of data with in-memory speed.*
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Mon, Aug 10, 2020 at 12:14 PM Dmitriy Pavlov <[hidden email]>
> > > > wrote:
> > > >
> > > > > Dear Apache Ignite community,
> > > > >
> > > > > PMC should submit the board report, not later than 12 August.
> > > > >
> > > > > Previous board with drafted publicly with sharing with all
> developers
> > > > > community. Let us try it one more time. Please share your thoughts
> on
> > > > what
> > > > > might be added to the board meeting agenda.
> > > > >
> > > > > ## Description:
> > > > > The mission of Ignite is the creation and maintenance of software
> > > related
> > > > > to
> > > > > High-performance, integrated and distributed in-memory platform for
> > > > > computing
> > > > > and transacting on large-scale data sets in real-time
> > > > >
> > > > > ## Issues:
> > > > > There are no issues requiring board attention. (hopefully)
> > > > >
> > > > > ## Membership Data:
> > > > > Apache Ignite was founded 2015-08-19 (5 years ago)
> > > > > There are currently 53 committers and 34 PMC members in this
> project.
> > > > > The Committer-to-PMC ratio is roughly 7:5.
> > > > >
> > > > > Community changes, past quarter:
> > > > > - No new PMC members. Last addition was Maxim Muzafarov on
> > 2020-04-28.
> > > > > - Artem Budnikov was added as committer on 2020-07-14
> > > > > - Sergey Chugunov was added as committer on 2020-06-12
> > > > >
> > > > > ## Project Activity:
> > > > > Apache Ignite community is working on preparing release 2.9.0.
> > > > > Release 3.0 discussion has been resurrected.
> > > > > Project documentation migration from readme.io to the code
> started.
> > > > >
> > > > > ## Community Health:
> > > > > There is a decrease in mailing list traffic comparing to the
> previous
> > > > > quarter (-10-20%). Activity related to code commits remains stable.
> > > > > The first committer was elected because of merit related to the
> > > non-code
> > > > > contribution, but efforts in the documentation.
> > > > > Apache Ignite users, developers, and PMC members continued to give
> > > talks
> > > > > related to the product in C-19 situation mostly online. See also
> > > > > https://ignite.apache.org/events.html
> > > > >
> > > > > Sincerely,
> > > > > Dmitriy Pavlov
> > > > >
> > > >
> > >
> >
>