ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@apache.org>
Subject Making Ignite Collaboration 100% Open and Transparent
Date Mon, 26 Aug 2019 18:53:40 GMT
Folks, let me share more details on why Anton started the conversation
about Ignite Slack:

Recently, a group of GridGain and Sberbank committers of Ignite has met to
discuss how to make our community more transparent and open. Anton and I
took part in that meeting. The primary problems we see in regards to
transparency and openness are as follows:

   - A lot of discussions on the dev list abrupts suddenly and it's unclear
   whether a discussion is abandoned or something else is going on in the
   background with a task/bug/improvement. In many cases, we tend to fall back
   to faster communication ways like instant messaging, calls, or face-to-face
   meetings that are not visible to the rest of the community. Emails (dev
   list) are the right communication channel but not for all of the stages.
   - Change reviews seem to be in a chaotic state. Sometimes it takes many
   rounds for a committer to urge another committer to do a review. In many
   cases, the other committer might be simply overwhelmed with regular tasks
   imposed by an employer. It will be good to come up with some public
   tracking approach that will help us all to see who and when will be able to
   review certain changes and make them to Ignite.

To address the problems we want to propose the following:

   - Keep using dev list the way you do today. No changes need to be done
   - Introduce Ignite Slack for instant messaging across all the community
   members who are obviously employed by different companies. Ignite PMC will
   be managing channels for various topics. Go to Slack when email (dev list)
   conversation is no longer effective, the way we do daily, no need to
   complicate our lives just because we work on an open-source project
   - Two or more committers need to talk verbally? Go ahead and schedule a
   meeting with Google Hangouts or another tool. Send an invite to the dev
   list for those who'd like to join and listen or share opinion. Want to talk
   in your native language? Go ahead and put a disclaimer that a conversation
   will be in Chinese, Russia, French, whatever. Simple and open.
   - Don't know how soon you'll be able to review some changes and, thus,
   ignoring other committers requests? GridGain and Sberbank are ready to
   propose a solution here. Both vendors use an approach to cooperate between
   GridGain and Sberbank committers. Now we'd like to make it fully open and
   adjust for community needs if required.

Thoughts, suggestions? I think we'll schedule a community meeting to finish
the conversation or discuss any cornerstone points. But start with your
questions first.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message