[openstack-dev] [Rally][all] Gitter as an alternative way for communication
akurilin at mirantis.com
Fri Nov 25 13:57:07 UTC 2016
On Fri, Nov 25, 2016 at 12:51 PM, Thierry Carrez <thierry at openstack.org>
> Andrey Kurilin wrote:
> > I'm happy to announce our new chats at gitter.im <http://gitter.im> :
> > [...]
> While I understand where you're coming from, I would like to remind you
> that the OpenStack community standardized on IRC for community
> communication. Maintaining alternate communication channels might make
> it slightly easier for your team members, but it makes it more difficult
> for others in the OpenStack community to follow what is happening, and
> participate to Rally development.
As I said before, we do not plan to abandon our regular IRC channel and we
have a bot for synchronisation messages between gitter and irc channels, so
users from Gitter can participate in IRC discussions, and vice versa users
can ping guys from our Gitter channel. It is just an extension of rally
workflow, not replacement of IRC at all.
> This is why as part of the official
> OpenStack project team requirements we have usage of IRC baked in.
> IRC is a standard protocol, implemented in a lot of open source clients.
> Alternatives like Slack or Gitter are closed-source services with terms
> of use (and future decisions on openness and pricing) that may or may
> not be acceptable by our community members -- using them creates
> fragmentation within the OpenStack community.
> That is not saying that IRC is perfect and that we will never move to
> something else. But when we do, it will be as a community (and after an
> open community discussion) and not project per project.
I can believe that OpenStack community will move from Freenode to another
IRC service (if Freenode dies) someday, but moving to another protocol is
thing for me. OpenStack community will never do it. :) We'd rather maintain
IRC protocol by ourself...
That is why Rally-community decided to use "not-irc tool" without
discussion. BUT, as I said before, we did it without breaking compatibility
other OpenStack projects and we will not do it..
> It is also
> likely to be toward an open protocol supported by open source software,
> rather than one specific third-party proprietary web service.
Why? Why we can not use convenient free for opensource projects things?
Why not enjoy all the advantages of the modern world?:) It is out of
current topic, but
why we use inconvenient launchpad instead of bitbucket and so on?
> Thierry Carrez (ttx)
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev