...

The collaboration tools/channels are ranged by priority. Prefer Ignite dev list all the times switching to speedy tools if needed.

Table of Contents

Ignite Dev List

This list is the primary and the default communication channel - dev@ignite.apache.org 

...

For the sake of openness, speed and transparency, the community members are free to use Ignite Slack or meet via the tools like Google Meeting. But, recalling the mantra, if any conversation took place between contributors using channels like Slack, a summary of the discussion/decision has to be shared via the dev list letting other contributors share their opinions. As a summary, final decisions are made only on the dev list. The other tools listed below are used for the sake of efficiency in certain occurrences.

Ignite Slack

Slack is used to/for:

• Speed up a resolution of a dev list conversation. Basically, to get down to the bottom if the dev list discussion doesn't make things clear while a Slack chat promises to solve the misunderstanding.
• Chat with a contributor or groups of contributors if you're working on a task previously discussed on the dev list. Feel free to create dedicated Slack channels "ignite-{topic}" for big topics. 
• Other occasions if you believe Ignite Slack is a more appropriate place for collaboration.

...

and type in "ignite" in the search window as shown below

Conference Meetings

Phone calls and other verbal forms of meetings (let's just call them conference meetings) are useful for:

...