cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Angus <paul.an...@shapeblue.com>
Subject RE: [DISCUSS] Change of the official CHAT channel
Date Fri, 23 Aug 2019 14:45:35 GMT
I don't think that we should be 'marketing' anything other than the mailing lists.    That
is where most people can be found and where previously asked questions can be searched for.
Having a ready to roll 'chat' tool has many advantages, so I'm cool with having one in the
back pocket.
But personally I'd like to see as little fragmentation of the community as possible.

+ a new visitor turning up to a slack channel with 4 people on it is not going to give a positive
impression, and that person is definitely is far less likely to get an answer to any question
that they have.

Paul.

paul.angus@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-----Original Message-----
From: Gabriel Beims Bräscher <gabrascher@gmail.com> 
Sent: 23 August 2019 14:56
To: dev <dev@cloudstack.apache.org>
Cc: Nux! <nux@li.nux.ro>
Subject: Re: [DISCUSS] Change of the official CHAT channel

Hello folks,

I see no problem with using chat platforms. The mail should stay as the default communication
tool indeed, but several times I used Slack when helping foes around, raising questions, and
pinging folks on private chat.
As far as we have tools and they are being used by the community I see no problem with keeping
them around.

However, I think that the main point raised by Andrija is regarding the "marketing" of the
channels. We normally promote IRC (pointing to irc.freenode.net), but CloudStack IRC channels
look pretty dead, especially considering that it is the "official" ACS chat tool.

Does promoting all channels (IRC + Slack) look a good idea? Should we keep only one option?
In one hand, IRC currently is not as active as Slack, but on the other hand, Slack requires
an invitation e-mail.

Regards,
Gabriel.



Em sex, 23 de ago de 2019 às 08:45, Rohit Yadav <rohit.yadav@shapeblue.com>
escreveu:

> All,
>
> I think email is the more persistent form of communication and it must 
> continue to be the default communication mechanism for the project
> dev+user+etc.
>
> For a more real-time/transient communication, IRC or slack are good tools.
> I don't have any preference on either, as I'm not an active user on 
> either of them. It just happened that someone asked me to join the-asf 
> slack for some other group, and I saw many projects having their 
> channels there and I made a comment about it on our current 
> apachecloudstack community slack which is outside of the-asf group. 
> I've got both of them setup on my desktop slack now, if it's too 
> difficult to migrate everyone from the old slack group to the-asf 
> slack group, let's continue as is; or perhaps add an IRC-gateway between the two.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> ________________________________
> From: Sven Vogel <S.Vogel@ewerk.com>
> Sent: Friday, August 23, 2019 01:01
> To: dev@cloudstack.apache.org <dev@cloudstack.apache.org>
> Cc: Nux! <nux@li.nux.ro>
> Subject: Re: [DISCUSS] Change of the official CHAT channel
>
> Hey Guys,
>
> I don’t understand the problem. I don’t like slack too but I don’t 
> like mailing list or  neither. I think the first one is closed and 
> slow. For me is an mailing list or irc also not the wisdom final 
> conclusion but hey do we have a better one? No.
>
> If IRC is death drop it. If we don’t want slack drop it. leave ONLY 
> the mailing list until there we get an better interactive technology, 
> maybe open source.
>
> Cheers
>
>
> __
>
> Sven Vogel
> Teamlead Platform
>
> EWERK RZ GmbH
> Brühl 24, D-04109 Leipzig
> P +49 341 42649 - 11
> F +49 341 42649 - 18
> S.Vogel@ewerk.com
> www.ewerk.com<http://www.ewerk.com>
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Frank Richter
> Registergericht: Leipzig HRB 17023
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 20000-1:2011
>
> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) 
> ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht 
> der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, 
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
> informieren Sie in diesem Fall unverzüglich den Absender und löschen 
> Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are 
> confidential and may be legally privileged. If you are not the 
> intended recipient of this e-mail, any disclosure, copying, 
> distribution or use of its contents is strictly prohibited, and you 
> should please notify the sender immediately and then delete it (including any attachments)
from your system. Thank you.
> > Am 22.08.2019 um 20:28 schrieb Andrija Panic <andrija.panic@gmail.com>:
> >
> > My whole idea is that having one (IRC) marketed on web pages, while 
> > using the other silently (Slack) makes less than zero sense to me.
> >
> > And, for me, a tool is a tool, I'm not married to it (some people 
> > prefer
> vi
> > editor and have religious attachments to it, I just use nano to get 
> > the
> job
> > done)
> >
> >> On Thu, Aug 22, 2019, 19:49 Nux! <nux@li.nux.ro> wrote:
> >>
> >> I'm heavily against Slack or any other proprietary, closed solutions.
> >>
> >> I think it's a step back generally for the Internet at large and 
> >> even more so for an open source project; I can't reconcile the two 
> >> in my heart.
> >>
> >> Having said that, I believe the chat is dead not because it's IRC, 
> >> but because people prefer async comms (ie email). It'll be the same 
> >> for Slack.
> >>
> >>
> >> We should be promoting the mailing lists. They are active and the 
> >> archives are open to search engines etc and can further provide 
> >> helpful information to everyone.
> >>
> >> I won't -1 the decision, I don't want to be in the way of 
> >> "progress", but it's not a +1 either. I won't be using it.
> >>
> >> My 2p
> >>
> >>
> >> ---
> >> Sent from the Delta quadrant using Borg technology!
> >>
> >>> On 2019-08-22 16:57, Andrija Panic wrote:
> >>> Hi guys,
> >>>
> >>> Since IRC is pretty dead, and we already have a Slack channel ( 
> >>> https://apachecloudstack.slack.com ) that we use atm, AND since 
> >>> there seems to be an official ASF slack channel at 
> >>> https://the-asf.slack.com/, I would like to open a discussion of 
> >>> the idea to "officially"  move (i.e.
> >>> marketing
> >>> this on all event pages and main web site) to that new CloudStack 
> >>> channel on the official ASF slack account/page - and abandon 
> >>> (close for good) all others chat channels.
> >>>
> >>> i.e. on this year conference page 
> >>> (http://us.cloudstackcollab.org/) we currently announce the IRC 
> >>> channel (???) to be the one (and AFAIK it's pretty dead) - so I 
> >>> would propose to move forward and update this, so the users can be 
> >>> aware of "alive" chat channel
> >>>
> >>> Suggestions, opinions ?
> >>>
> >>> Regards,
> >>>
> >>> Andrija Panić
> >>
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>
Mime
View raw message