>From today's community meeting, we had an item from the issue queue:https://github.com/gluster/community/issues/13 Should we have a Gluster Community slack team? I'm interested in everyone's thoughts on this. - amye -- Amye Scavarda | amye at redhat.com | Gluster Community Lead
On Wed, Nov 8, 2017 at 4:22 PM, Amye Scavarda <amye at redhat.com> wrote:> From today's community meeting, we had an item from the issue queue: > https://github.com/gluster/community/issues/13 > > Should we have a Gluster Community slack team? I'm interested in > everyone's thoughts on this. > >+1 to the idea. One of the limitations I have encountered in a few slack channels is the lack of archiving & hence limited search capabilities. If we establish a gluster channel, what would be the archiving strategy? Thanks, Vijay -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171108/9cdcc04c/attachment.html>
It's great idea! :) But think about creating Slack for all RedHat provided opensource projects. For example one Slack workspace with separated Gluster, Ceph, Fedora etc. channels. I can't wait for it! Bartosz On 08.11.2017 22:22, Amye Scavarda wrote:> From today's community meeting, we had an item from the issue queue: > https://github.com/gluster/community/issues/13 > > Should we have a Gluster Community slack team? I'm interested in > everyone's thoughts on this. > - amye >
The archival process of the mailing list makes searching for past issues possible. Slack, and irc in general, is a more closed garden than a public archived mailing list. That said, irc/slack is good for immediate interaction between people, say, gluster user with a nightmare and a knowledgeable developer with deep understanding and willingness to assist. If there's a way to make a debug/help/fix session publicly available, and crucially, referenced in the mailing list archive, then irc/slack is a great additional communication channel. On November 8, 2017 4:22:44 PM EST, Amye Scavarda <amye at redhat.com> wrote:>From today's community meeting, we had an item from the issue queue: >https://github.com/gluster/community/issues/13 > >Should we have a Gluster Community slack team? I'm interested in >everyone's thoughts on this. >- amye > >-- >Amye Scavarda | amye at redhat.com | Gluster Community Lead >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://lists.gluster.org/mailman/listinfo/gluster-users-- Sent from my Android device with K-9 Mail. All tyopes are thumb related and reflect authenticity. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171108/3758c4f1/attachment.html>
On Wed, Nov 8, 2017 at 3:23 PM, Jim Kinney <jim.kinney at gmail.com> wrote:> The archival process of the mailing list makes searching for past issues > possible. Slack, and irc in general, is a more closed garden than a public > archived mailing list. > > That said, irc/slack is good for immediate interaction between people, say, > gluster user with a nightmare and a knowledgeable developer with deep > understanding and willingness to assist. > > If there's a way to make a debug/help/fix session publicly available, and > crucially, referenced in the mailing list archive, then irc/slack is a great > additional communication channel.So at the moment, we do have the logs from IRC made public. We could probably do the same thing for a possible slack instance, but that's not really an improvement. I think being able to get some of the debug sessions into documentation might improve that problem. However, willing to hear more about what else we should be doing to support users! - amye> > On November 8, 2017 4:22:44 PM EST, Amye Scavarda <amye at redhat.com> wrote: >> >> From today's community meeting, we had an item from the issue queue: >> https://github.com/gluster/community/issues/13 >> >> Should we have a Gluster Community slack team? I'm interested in >> everyone's thoughts on this. >> - amye > > > -- > Sent from my Android device with K-9 Mail. All tyopes are thumb related and > reflect authenticity.-- Amye Scavarda | amye at redhat.com | Gluster Community Lead
On Wed, Nov 8, 2017 at 3:12 PM, Bartosz Zi?ba <kontakt at avatat.pl> wrote:> It's great idea! :) > > But think about creating Slack for all RedHat provided opensource projects. > For example one Slack workspace with separated Gluster, Ceph, Fedora etc. > channels. > > I can't wait for it! > > Bartosz >At the moment, we're just limited to Gluster's footprint in the world, but I can take that feedback back to the teams at Red Hat. Thanks! -- amye> > > On 08.11.2017 22:22, Amye Scavarda wrote: >> >> From today's community meeting, we had an item from the issue queue: >> https://github.com/gluster/community/issues/13 >> >> Should we have a Gluster Community slack team? I'm interested in >> everyone's thoughts on this. >> - amye >> > >-- Amye Scavarda | amye at redhat.com | Gluster Community Lead
Sankarshan Mukhopadhyay
2017-Nov-09 00:28 UTC
[Gluster-users] Adding a slack for communication?
On 09-Nov-2017 03:53, "Amye Scavarda" <amye at redhat.com> wrote:>From today's community meeting, we had an item from the issue queue:https://github.com/gluster/community/issues/13 Should we have a Gluster Community slack team? I'm interested in everyone's thoughts on this. Will this be in addition to the Gitter.im channel which exists? Being present on multiple popular places isn't a bad thing. Does Slack offer a fully featured instance for communities? - amye -- Amye Scavarda | amye at redhat.com | Gluster Community Lead _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171109/5f0612dc/attachment.html>
On Wed, Nov 8, 2017 at 3:09 PM, Vijay Bellur <vbellur at redhat.com> wrote:> > > On Wed, Nov 8, 2017 at 4:22 PM, Amye Scavarda <amye at redhat.com> wrote: >> >> From today's community meeting, we had an item from the issue queue: >> https://github.com/gluster/community/issues/13 >> >> Should we have a Gluster Community slack team? I'm interested in >> everyone's thoughts on this. >> > > > +1 to the idea. > > One of the limitations I have encountered in a few slack channels is the > lack of archiving & hence limited search capabilities. If we establish a > gluster channel, what would be the archiving strategy? > > Thanks, > Vijay >If we want this, we can use something like slackarchive to be able to archive this and then publish it on the website. We could also look at being able to use Gitter more, which we already have, or a Slack-IRC bridge. Many options! - amye -- Amye Scavarda | amye at redhat.com | Gluster Community Lead
> On Wed, Nov 8, 2017 at 4:22 PM, Amye Scavarda <amye at redhat.com <mailto:amye at redhat.com>> wrote: > From today's community meeting, we had an item from the issue queue: > https://github.com/gluster/community/issues/13 <https://github.com/gluster/community/issues/13> > > Should we have a Gluster Community slack team? I'm interested in > everyone's thoughts on this. >As fancy as Slack is, I really don't like how dependant so many projects have become on it, it's not open source, the desktop client is dreadful (heavy javascript webframe), you're at the mercy of the companies decisions around the direction of their 'black box' software platform etc... Personally I've found that discourse is a fantastic platform for project discussion, help and ideas: https://discourse.org <https://discourse.org/> and for chat I've found that if IRC + a good web frontend for history/search isn't enough using either Mattermost (https://about.mattermost.com/ <https://about.mattermost.com/>) or Rocket Chat (https://rocket.chat/ <https://rocket.chat/>) has been very successful. Just my 2c and I'll be happy to be a part of the community no matter where it ends up. -- Sam McLeod https://smcleod.net https://twitter.com/s_mcleod -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171109/9a77336b/attachment.html>
@Amye +1 for this great Idea, I am 100% for it. @Vijay for archiving purposes maybe it will be possible to use free service as https://slackarchive.io/ <https://slackarchive.io/> BR, Martin> On 9 Nov 2017, at 00:09, Vijay Bellur <vbellur at redhat.com> wrote: > > > > On Wed, Nov 8, 2017 at 4:22 PM, Amye Scavarda <amye at redhat.com <mailto:amye at redhat.com>> wrote: > From today's community meeting, we had an item from the issue queue: > https://github.com/gluster/community/issues/13 <https://github.com/gluster/community/issues/13> > > Should we have a Gluster Community slack team? I'm interested in > everyone's thoughts on this. > > > > +1 to the idea. > > One of the limitations I have encountered in a few slack channels is the lack of archiving & hence limited search capabilities. If we establish a gluster channel, what would be the archiving strategy? > > Thanks, > Vijay > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20171109/9251660a/attachment.html>