...
The collaboration tools/channels are ranged by priority. Prefer Ignite dev list all the times switching to speedy tools if needed.
Table of Contents |
---|
This list is the primary and the default communication channel - dev@ignite.apache.org
...
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 If it's not on the dev list, it didn't happen". The project is being developed and moved forward by individuals living across the globe and speaking different languages. Thus, asynchronous written communication is a preferred way of engagement at ASF as well as within the Ignite community.
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.
Slack is used to/for:
...
Well, now you know why and how we use Slack. Next, go ahead and sign up there https://the-asf.slack.com/signup (use, https://s.apache.org/slack-invite if you don't have "@apache.org" account).
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 suits your needs.
...
and type in "ignite" in the search window as shown below
Phone calls and other verbal forms of meetings (let's just call them conference meetings) are useful for:
...