...
Send an email to dev-subscribe@ignite.apache.org to subscribe to the list. If you are an ASF committer, then prefer your @apache.org address for Ignite communications.
All the discussions related to contributions, changes, new ideas have to be started on the dev list first. Remember the mantra - "It didn't happen and if it hadn't happened on the dev list". The project is being developed and moved forward by individuals living across the globe and speaking different languages. Thus, an asynchronous written communication is a preferred way of engagement at ASF as well as within the Ignite community.
...
...
Ignite community uses Slack account that belongs to ASF. All ignite channels, and topics are named as "ignite-{topic}". There is a generic topic named "ignite" for quick chatting among contributors on Ignite matters. Before creating a new topic look through existing ones, there already might be the one that suites suits your needs.
Too look for existing topics in Slack, click on "Channels" icon
...
Phone calls and other verbal forms of meetings (let's just call them conference meetings) are usefull useful for:
You are not obliged but suggested to use Google Meetings that are free and open, and go with screen sharing as well as video-call capabilities. Moreover, most of us have google accounts and will be able to arrange a meeting easily. Just go to https://calendar.google.com and select a time spot slot that suits everyones everyone's time. But don't forget do to add "Hangouts" reference and invite dev@ignite.apache.org to the meeting, as shown on in the picture below.
; , or they might want just to sit and listen learning more about Ignite. If you are willing to speak your native language different from English, then just put a disclaimer in the title or description of the invite.
The reason why the whole dev list should be invited is that some of the contributors might be willing to take part in the meeting and share their thoughts in advance...