Igniters,
I'd like to propose you to register at the ASF Slack [1] (committers seems to be already registered) and join the Ignite channel [2]. This should simplify communication between the contributors. P.s. I'm not saying we have to replace devlist with the Slack, but Slack is a more suitable place for short or private communications. [1] https://the-asf.slack.com [2] https://the-asf.slack.com/messages/C7E04VCPK |
Anton,
Can we create channels for ticket, IEP discussions in ASF slack? В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет: > Igniters, > I'd like to propose you to register at the ASF Slack [1] (committers seems > to be already registered) and join the Ignite channel [2]. > This should simplify communication between the contributors. > > P.s. I'm not saying we have to replace devlist with the Slack, but Slack is > a more suitable place for short or private communications. > > [1] https://the-asf.slack.com > [2] https://the-asf.slack.com/messages/C7E04VCPK |
Nikolay,
Let's try ;) On Mon, Aug 26, 2019 at 4:15 PM Nikolay Izhikov <[hidden email]> wrote: > Anton, > > Can we create channels for ticket, IEP discussions in ASF slack? > > > В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет: > > Igniters, > > I'd like to propose you to register at the ASF Slack [1] (committers > seems > > to be already registered) and join the Ignite channel [2]. > > This should simplify communication between the contributors. > > > > P.s. I'm not saying we have to replace devlist with the Slack, but Slack > is > > a more suitable place for short or private communications. > > > > [1] https://the-asf.slack.com > > [2] https://the-asf.slack.com/messages/C7E04VCPK > |
Hi,
If we use the example of Apache Beam, usually these channels relate to a module or language, e.g. beam-python, beam-ml, etc. I also support the idea of ASF slack usage. Moreover, we can ask Infra to install automatic translation of messages to English. It may help non-native speakers to communicate. Let's just remember the motto: If it didn't happen on the list - it didn't happen. Sincerely, Dmitriy Pavlov пн, 26 авг. 2019 г. в 16:22, Anton Vinogradov <[hidden email]>: > Nikolay, > > Let's try ;) > > On Mon, Aug 26, 2019 at 4:15 PM Nikolay Izhikov <[hidden email]> > wrote: > > > Anton, > > > > Can we create channels for ticket, IEP discussions in ASF slack? > > > > > > В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет: > > > Igniters, > > > I'd like to propose you to register at the ASF Slack [1] (committers > > seems > > > to be already registered) and join the Ignite channel [2]. > > > This should simplify communication between the contributors. > > > > > > P.s. I'm not saying we have to replace devlist with the Slack, but > Slack > > is > > > a more suitable place for short or private communications. > > > > > > [1] https://the-asf.slack.com > > > [2] https://the-asf.slack.com/messages/C7E04VCPK > > > |
I think that channels for separate IEP-s is too much.
But the slack is not indexing and not accessible for all people in the Internet. Maybe it's wrong idea to discuss something there instead of dev-list? пн, 26 авг. 2019 г. в 16:27, Dmitriy Pavlov <[hidden email]>: > Hi, > > If we use the example of Apache Beam, usually these channels relate to a > module or language, e.g. beam-python, beam-ml, etc. > > I also support the idea of ASF slack usage. Moreover, we can ask Infra to > install automatic translation of messages to English. It may help > non-native speakers to communicate. > > Let's just remember the motto: > If it didn't happen on the list - it didn't happen. > > Sincerely, > Dmitriy Pavlov > > пн, 26 авг. 2019 г. в 16:22, Anton Vinogradov <[hidden email]>: > > > Nikolay, > > > > Let's try ;) > > > > On Mon, Aug 26, 2019 at 4:15 PM Nikolay Izhikov <[hidden email]> > > wrote: > > > > > Anton, > > > > > > Can we create channels for ticket, IEP discussions in ASF slack? > > > > > > > > > В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет: > > > > Igniters, > > > > I'd like to propose you to register at the ASF Slack [1] (committers > > > seems > > > > to be already registered) and join the Ignite channel [2]. > > > > This should simplify communication between the contributors. > > > > > > > > P.s. I'm not saying we have to replace devlist with the Slack, but > > Slack > > > is > > > > a more suitable place for short or private communications. > > > > > > > > [1] https://the-asf.slack.com > > > > [2] https://the-asf.slack.com/messages/C7E04VCPK > > > > > > |
I agree with Alexey, since Dev list it better place in most cases. Apache
does not prohibit peer 2 peer communication, and ASF slack can be used as a messenger. The main thing here is that we (all community) clearly understand that ASF slack is the replacement to Skype/Rocket Chat/Calls, it is not a replacement for the list. Each private agreement should be published as intent in the list. Only after some time and there are no objections - it is valid agreement. пн, 26 авг. 2019 г. в 16:56, Alexey Zinoviev <[hidden email]>: > I think that channels for separate IEP-s is too much. > But the slack is not indexing and not accessible for all people in the > Internet. Maybe it's wrong idea to discuss something there instead of > dev-list? > > пн, 26 авг. 2019 г. в 16:27, Dmitriy Pavlov <[hidden email]>: > > > Hi, > > > > If we use the example of Apache Beam, usually these channels relate to a > > module or language, e.g. beam-python, beam-ml, etc. > > > > I also support the idea of ASF slack usage. Moreover, we can ask Infra to > > install automatic translation of messages to English. It may help > > non-native speakers to communicate. > > > > Let's just remember the motto: > > If it didn't happen on the list - it didn't happen. > > > > Sincerely, > > Dmitriy Pavlov > > > > пн, 26 авг. 2019 г. в 16:22, Anton Vinogradov <[hidden email]>: > > > > > Nikolay, > > > > > > Let's try ;) > > > > > > On Mon, Aug 26, 2019 at 4:15 PM Nikolay Izhikov <[hidden email]> > > > wrote: > > > > > > > Anton, > > > > > > > > Can we create channels for ticket, IEP discussions in ASF slack? > > > > > > > > > > > > В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет: > > > > > Igniters, > > > > > I'd like to propose you to register at the ASF Slack [1] > (committers > > > > seems > > > > > to be already registered) and join the Ignite channel [2]. > > > > > This should simplify communication between the contributors. > > > > > > > > > > P.s. I'm not saying we have to replace devlist with the Slack, but > > > Slack > > > > is > > > > > a more suitable place for short or private communications. > > > > > > > > > > [1] https://the-asf.slack.com > > > > > [2] https://the-asf.slack.com/messages/C7E04VCPK > > > > > > > > > > |
In reply to this post by Alexey Zinoviev
> But the slack is not indexing and not accessible for all people in the
Internet +1 On Mon, Aug 26, 2019 at 4:56 PM Alexey Zinoviev <[hidden email]> wrote: > > I think that channels for separate IEP-s is too much. > But the slack is not indexing and not accessible for all people in the > Internet. Maybe it's wrong idea to discuss something there instead of > dev-list? > > пн, 26 авг. 2019 г. в 16:27, Dmitriy Pavlov <[hidden email]>: > > > Hi, > > > > If we use the example of Apache Beam, usually these channels relate to a > > module or language, e.g. beam-python, beam-ml, etc. > > > > I also support the idea of ASF slack usage. Moreover, we can ask Infra to > > install automatic translation of messages to English. It may help > > non-native speakers to communicate. > > > > Let's just remember the motto: > > If it didn't happen on the list - it didn't happen. > > > > Sincerely, > > Dmitriy Pavlov > > > > пн, 26 авг. 2019 г. в 16:22, Anton Vinogradov <[hidden email]>: > > > > > Nikolay, > > > > > > Let's try ;) > > > > > > On Mon, Aug 26, 2019 at 4:15 PM Nikolay Izhikov <[hidden email]> > > > wrote: > > > > > > > Anton, > > > > > > > > Can we create channels for ticket, IEP discussions in ASF slack? > > > > > > > > > > > > В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет: > > > > > Igniters, > > > > > I'd like to propose you to register at the ASF Slack [1] (committers > > > > seems > > > > > to be already registered) and join the Ignite channel [2]. > > > > > This should simplify communication between the contributors. > > > > > > > > > > P.s. I'm not saying we have to replace devlist with the Slack, but > > > Slack > > > > is > > > > > a more suitable place for short or private communications. > > > > > > > > > > [1] https://the-asf.slack.com > > > > > [2] https://the-asf.slack.com/messages/C7E04VCPK > > > > > > > > > |
Anton,
Thanks for starting the conversation. I think that we need to explain to our community how and why we came to this proposal. I've started another discussion with details, sorry for not doing it earlier: http://apache-ignite-developers.2346864.n4.nabble.com/Making-Ignite-Collaboration-100-Open-and-Transparent-td43244.html -- Denis On Mon, Aug 26, 2019 at 7:43 AM Andrey Gura <[hidden email]> wrote: > > But the slack is not indexing and not accessible for all people in the > Internet > > +1 > > On Mon, Aug 26, 2019 at 4:56 PM Alexey Zinoviev <[hidden email]> > wrote: > > > > I think that channels for separate IEP-s is too much. > > But the slack is not indexing and not accessible for all people in the > > Internet. Maybe it's wrong idea to discuss something there instead of > > dev-list? > > > > пн, 26 авг. 2019 г. в 16:27, Dmitriy Pavlov <[hidden email]>: > > > > > Hi, > > > > > > If we use the example of Apache Beam, usually these channels relate to > a > > > module or language, e.g. beam-python, beam-ml, etc. > > > > > > I also support the idea of ASF slack usage. Moreover, we can ask Infra > to > > > install automatic translation of messages to English. It may help > > > non-native speakers to communicate. > > > > > > Let's just remember the motto: > > > If it didn't happen on the list - it didn't happen. > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > пн, 26 авг. 2019 г. в 16:22, Anton Vinogradov <[hidden email]>: > > > > > > > Nikolay, > > > > > > > > Let's try ;) > > > > > > > > On Mon, Aug 26, 2019 at 4:15 PM Nikolay Izhikov <[hidden email] > > > > > > wrote: > > > > > > > > > Anton, > > > > > > > > > > Can we create channels for ticket, IEP discussions in ASF slack? > > > > > > > > > > > > > > > В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет: > > > > > > Igniters, > > > > > > I'd like to propose you to register at the ASF Slack [1] > (committers > > > > > seems > > > > > > to be already registered) and join the Ignite channel [2]. > > > > > > This should simplify communication between the contributors. > > > > > > > > > > > > P.s. I'm not saying we have to replace devlist with the Slack, > but > > > > Slack > > > > > is > > > > > > a more suitable place for short or private communications. > > > > > > > > > > > > [1] https://the-asf.slack.com > > > > > > [2] https://the-asf.slack.com/messages/C7E04VCPK > > > > > > > > > > > > > |
Anton,
You need to have an apache email to register in the ASF Slack. Is it supposed to be like this? I don't think it's fair to limit the circle of communication this way. Non-blocking PME discussion is going to happen there, for example, and I won't be able to attend it, since I don't have an Apache email. But I'd really like to hear the discussion. Is there a way to relief this limitation? Denis пн, 26 авг. 2019 г. в 21:58, Denis Magda <[hidden email]>: > > Anton, > > Thanks for starting the conversation. I think that we need to explain to > our community how and why we came to this proposal. I've started another > discussion with details, sorry for not doing it earlier: > http://apache-ignite-developers.2346864.n4.nabble.com/Making-Ignite-Collaboration-100-Open-and-Transparent-td43244.html > > -- > Denis > > > > On Mon, Aug 26, 2019 at 7:43 AM Andrey Gura <[hidden email]> wrote: > > > > But the slack is not indexing and not accessible for all people in the > > Internet > > > > +1 > > > > On Mon, Aug 26, 2019 at 4:56 PM Alexey Zinoviev <[hidden email]> > > wrote: > > > > > > I think that channels for separate IEP-s is too much. > > > But the slack is not indexing and not accessible for all people in the > > > Internet. Maybe it's wrong idea to discuss something there instead of > > > dev-list? > > > > > > пн, 26 авг. 2019 г. в 16:27, Dmitriy Pavlov <[hidden email]>: > > > > > > > Hi, > > > > > > > > If we use the example of Apache Beam, usually these channels relate to > > a > > > > module or language, e.g. beam-python, beam-ml, etc. > > > > > > > > I also support the idea of ASF slack usage. Moreover, we can ask Infra > > to > > > > install automatic translation of messages to English. It may help > > > > non-native speakers to communicate. > > > > > > > > Let's just remember the motto: > > > > If it didn't happen on the list - it didn't happen. > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > пн, 26 авг. 2019 г. в 16:22, Anton Vinogradov <[hidden email]>: > > > > > > > > > Nikolay, > > > > > > > > > > Let's try ;) > > > > > > > > > > On Mon, Aug 26, 2019 at 4:15 PM Nikolay Izhikov <[hidden email] > > > > > > > > wrote: > > > > > > > > > > > Anton, > > > > > > > > > > > > Can we create channels for ticket, IEP discussions in ASF slack? > > > > > > > > > > > > > > > > > > В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет: > > > > > > > Igniters, > > > > > > > I'd like to propose you to register at the ASF Slack [1] > > (committers > > > > > > seems > > > > > > > to be already registered) and join the Ignite channel [2]. > > > > > > > This should simplify communication between the contributors. > > > > > > > > > > > > > > P.s. I'm not saying we have to replace devlist with the Slack, > > but > > > > > Slack > > > > > > is > > > > > > > a more suitable place for short or private communications. > > > > > > > > > > > > > > [1] https://the-asf.slack.com > > > > > > > [2] https://the-asf.slack.com/messages/C7E04VCPK > > > > > > > > > > > > > > > > > |
Denis,
You don't need an apache email to register in the ASF Slack. Here is the link [1] to join with any email. [1]: https://s.apache.org/slack-invite вт, 10 сент. 2019 г. в 12:52, Denis Mekhanikov <[hidden email]>: > Anton, > > You need to have an apache email to register in the ASF Slack. Is it > supposed to be like this? I don't think it's fair to limit the circle > of communication this way. > Non-blocking PME discussion is going to happen there, for example, and > I won't be able to attend it, since I don't have an Apache email. But > I'd really like to hear the discussion. > Is there a way to relief this limitation? > > Denis > > пн, 26 авг. 2019 г. в 21:58, Denis Magda <[hidden email]>: > > > > Anton, > > > > Thanks for starting the conversation. I think that we need to explain to > > our community how and why we came to this proposal. I've started another > > discussion with details, sorry for not doing it earlier: > > > http://apache-ignite-developers.2346864.n4.nabble.com/Making-Ignite-Collaboration-100-Open-and-Transparent-td43244.html > > > > -- > > Denis > > > > > > > > On Mon, Aug 26, 2019 at 7:43 AM Andrey Gura <[hidden email]> wrote: > > > > > > But the slack is not indexing and not accessible for all people in > the > > > Internet > > > > > > +1 > > > > > > On Mon, Aug 26, 2019 at 4:56 PM Alexey Zinoviev < > [hidden email]> > > > wrote: > > > > > > > > I think that channels for separate IEP-s is too much. > > > > But the slack is not indexing and not accessible for all people in > the > > > > Internet. Maybe it's wrong idea to discuss something there instead of > > > > dev-list? > > > > > > > > пн, 26 авг. 2019 г. в 16:27, Dmitriy Pavlov <[hidden email]>: > > > > > > > > > Hi, > > > > > > > > > > If we use the example of Apache Beam, usually these channels > relate to > > > a > > > > > module or language, e.g. beam-python, beam-ml, etc. > > > > > > > > > > I also support the idea of ASF slack usage. Moreover, we can ask > Infra > > > to > > > > > install automatic translation of messages to English. It may help > > > > > non-native speakers to communicate. > > > > > > > > > > Let's just remember the motto: > > > > > If it didn't happen on the list - it didn't happen. > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > пн, 26 авг. 2019 г. в 16:22, Anton Vinogradov <[hidden email]>: > > > > > > > > > > > Nikolay, > > > > > > > > > > > > Let's try ;) > > > > > > > > > > > > On Mon, Aug 26, 2019 at 4:15 PM Nikolay Izhikov < > [hidden email] > > > > > > > > > > wrote: > > > > > > > > > > > > > Anton, > > > > > > > > > > > > > > Can we create channels for ticket, IEP discussions in ASF > slack? > > > > > > > > > > > > > > > > > > > > > В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет: > > > > > > > > Igniters, > > > > > > > > I'd like to propose you to register at the ASF Slack [1] > > > (committers > > > > > > > seems > > > > > > > > to be already registered) and join the Ignite channel [2]. > > > > > > > > This should simplify communication between the contributors. > > > > > > > > > > > > > > > > P.s. I'm not saying we have to replace devlist with the > Slack, > > > but > > > > > > Slack > > > > > > > is > > > > > > > > a more suitable place for short or private communications. > > > > > > > > > > > > > > > > [1] https://the-asf.slack.com > > > > > > > > [2] https://the-asf.slack.com/messages/C7E04VCPK > > > > > > > > > > > > > > > > > > > > > > |
In reply to this post by Denis Mekhanikov
Guys, please disregard my previous message.
What I was missing is the following link: https://s.apache.org/slack-invite Denis On 10 Sep 2019, 12:52 +0300, Denis Mekhanikov <[hidden email]>, wrote: > Anton, > > You need to have an apache email to register in the ASF Slack. Is it > supposed to be like this? I don't think it's fair to limit the circle > of communication this way. > Non-blocking PME discussion is going to happen there, for example, and > I won't be able to attend it, since I don't have an Apache email. But > I'd really like to hear the discussion. > Is there a way to relief this limitation? > > Denis > > пн, 26 авг. 2019 г. в 21:58, Denis Magda <[hidden email]>: > > > > Anton, > > > > Thanks for starting the conversation. I think that we need to explain to > > our community how and why we came to this proposal. I've started another > > discussion with details, sorry for not doing it earlier: > > http://apache-ignite-developers.2346864.n4.nabble.com/Making-Ignite-Collaboration-100-Open-and-Transparent-td43244.html > > > > -- > > Denis > > > > > > > > On Mon, Aug 26, 2019 at 7:43 AM Andrey Gura <[hidden email]> wrote: > > > > > > But the slack is not indexing and not accessible for all people in the > > > Internet > > > > > > +1 > > > > > > On Mon, Aug 26, 2019 at 4:56 PM Alexey Zinoviev <[hidden email]> > > > wrote: > > > > > > > > I think that channels for separate IEP-s is too much. > > > > But the slack is not indexing and not accessible for all people in the > > > > Internet. Maybe it's wrong idea to discuss something there instead of > > > > dev-list? > > > > > > > > пн, 26 авг. 2019 г. в 16:27, Dmitriy Pavlov <[hidden email]>: > > > > > > > > > Hi, > > > > > > > > > > If we use the example of Apache Beam, usually these channels relate to > > > a > > > > > module or language, e.g. beam-python, beam-ml, etc. > > > > > > > > > > I also support the idea of ASF slack usage. Moreover, we can ask Infra > > > to > > > > > install automatic translation of messages to English. It may help > > > > > non-native speakers to communicate. > > > > > > > > > > Let's just remember the motto: > > > > > If it didn't happen on the list - it didn't happen. > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > пн, 26 авг. 2019 г. в 16:22, Anton Vinogradov <[hidden email]>: > > > > > > > > > > > Nikolay, > > > > > > > > > > > > Let's try ;) > > > > > > > > > > > > On Mon, Aug 26, 2019 at 4:15 PM Nikolay Izhikov <[hidden email] > > > > > > > > > > wrote: > > > > > > > > > > > > > Anton, > > > > > > > > > > > > > > Can we create channels for ticket, IEP discussions in ASF slack? > > > > > > > > > > > > > > > > > > > > > В Пн, 26/08/2019 в 16:09 +0300, Anton Vinogradov пишет: > > > > > > > > Igniters, > > > > > > > > I'd like to propose you to register at the ASF Slack [1] > > > (committers > > > > > > > seems > > > > > > > > to be already registered) and join the Ignite channel [2]. > > > > > > > > This should simplify communication between the contributors. > > > > > > > > > > > > > > > > P.s. I'm not saying we have to replace devlist with the Slack, > > > but > > > > > > Slack > > > > > > > is > > > > > > > > a more suitable place for short or private communications. > > > > > > > > > > > > > > > > [1] https://the-asf.slack.com > > > > > > > > [2] https://the-asf.slack.com/messages/C7E04VCPK > > > > > > > > > > > > > > > > > > > > > |
Free forum by Nabble | Edit this page |